Skip to main content

END-03: Endpoint Protection Mechanisms

END 9 — Critical Protect

Mechanisms exist to protect the confidentiality, integrity, availability and safety of endpoint devices.

Renumbered: Formerly END-02 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, END-03 was Prohibit Installation Without Privileged Status. That control is now CHG-04.2.

Control Question: Does the organization protect the confidentiality, integrity, availability and safety of endpoint devices?

General (35)
US (17)
EMEA (10)
APAC (5)
Framework Mapping Values
APAC India RBI Digital Payments 2021 71.a
APAC Japan ISMAP 6.2.1 6.2.1.1 6.2.1.2 6.2.1.3 6.2.1.4 6.2.1.5 6.2.1.6 6.2.1.7 6.2.1.8 6.2.1.9 6.2.1.10 6.2.1.11 6.2.1.12 6.2.1.13 6.2.1.14 6.2.1.15 6.2.1.16 6.2.1.17 6.2.1.21 6.2.1.22
APAC Malaysia RMiT 2025 A2-C12
APAC New Zealand HISF Microsmall 2023 HMS09 HMS12
APAC Singapore MAS TRM 2021 11.1.3 11.1.4 11.1.5
Americas (1)
Framework Mapping Values
Americas Argentina Reg 132 2018 E.1.2-5

Capability Maturity Model

Level 0 — Not Performed

Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.

Level 1 — Performed Informally

Endpoint Security (END) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with END domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Endpoint security management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ Endpoint devices containing sensitive/regulated data use a cryptographic mechanism to prevent the unauthorized disclosure of information at rest (e.g., full drive encryption).

Level 2 — Planned & Tracked

Endpoint Security (END) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with END domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with END domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with END domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Endpoint security-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Endpoint security management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.

Level 3 — Well Defined

Endpoint Security (END) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with END domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with END domain capabilities are well-documented and kept current by process owners. ▪ An endpoint technology management team, or similar function, is appropriately staffed and supported to implement and maintain END domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of endpoint security operations (e.g., unified endpoint management solution). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with END domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to protect the confidentiality, integrity, availability and safety of endpoint devices.

Level 4 — Quantitatively Controlled

Endpoint Security (END) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs). ▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs). ▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties. ▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review). ▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes. ▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.

Level 5 — Continuously Improving

Endpoint Security (END) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ Based on predictive analysis, process improvements are implemented according to “continuous improvement” practices that affect process changes. ▪ Stakeholders make time-sensitive decisions to support operational efficiency, which may include automated remediation actions via Artificial Intelligence (AI) or Machine Learning (ML) technologies.

Assessment Objectives

  1. END-03_A01 the confidentiality and integrity of sensitive / regulated data at rest is protected.
  2. END-03_A02 information at rest requiring protection is defined.

Evidence Requirements

E-END-01 Endpoint Security Tools

Documented evidence of endpoint security tools employed by the organization to ensure secure, compliant and resilient Technology Assets, Applications and/or Services (TAAS) (e.g., antimalware, FIM, etc.).

Endpoint Security

Technology Recommendations

Micro/Small

  • Secure Baseline Configurations (SBC)
  • IT Asset Management (ITAM) program
  • Configuration Management (CM) program
  • Change control program

Small

  • Secure Baseline Configurations (SBC)
  • IT Asset Management (ITAM) program
  • Configuration Management (CM) program
  • Change control program

Medium

  • Secure Baseline Configurations (SBC)
  • IT Asset Management (ITAM) program
  • Configuration Management (CM) program
  • Change control program

Large

  • Secure Baseline Configurations (SBC)
  • IT Asset Management (ITAM) program
  • Configuration Management (CM) program
  • Change control program

Enterprise

  • Secure Baseline Configurations (SBC)
  • IT Asset Management (ITAM) program
  • Configuration Management (CM) program
  • Change control program

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.