Skip to main content

END-10: Extended Detection & Response (XDR)

END 5 — Medium Protect

Mechanisms exist to implement Extended Detection & Response (XDR) technologies to correlate data and respond to threats across multiple security layers, including: (1) Endpoints; (2) On-premises networks; (3) Cloud-based networks; (4) Electronic communications; (5) Applications; and (6) Services.

Renumbered: Formerly END-06.8 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, END-10 was Mobile Code. That control is now END-13.

Control Question: Does the organization implement Extended Detection & Response (XDR) technologies to correlate data and respond to threats across multiple security layers, including: (1) Endpoints; (2) On-premises networks; (3) Cloud-based networks; (4) Electronic communications; (5) Applications; and (6) Services?

General (2)
Framework Mapping Values
NIST 800-172 R3 03.14.11E
NIST 800-172A R3 DS-A.03.14.11E
US (1)
Framework Mapping Values
USA Federal DoD Zero Trust Execution Roadmap v1.1 2.7.2 2.7.3
EMEA (2)
Framework Mapping Values
EMEA Saudi Arabia ECC-1 2018 2-4-3-4
EMEA Saudi Arabia OTCC-1 2022 2-3-1-1 2-3-1-12
Americas (1)
Framework Mapping Values
Americas Canada OSFI Self-Assessment Guidance 3.3.2

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.

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 implement Extended Detection & Response (XDR) technologies to correlate data and respond to threats across multiple security layers, including: (1) Endpoints; (2) On-premises networks; (3) Cloud-based networks; (4) Electronic communications; (5) Applications; and (6) Services.

Level 4 — Quantitatively Controlled

Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.

Level 5 — Continuously Improving

Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.

Assessment Objectives

  1. END-10_A01 Extended Detection & Response (XDR) technologies are used to correlate data and respond to threats across security layers, including at a minimum: endpoints; on-premises networks; cloud-based networks; electronic communications; applications; and services.

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

  • Antivirus/antimalware software
  • Keep OS updated

Small

  • Endpoint protection platform (e.g., Windows Defender)
  • Patch management

Medium

  • EDR solution (e.g., CrowdStrike Falcon Go)
  • Centralized endpoint management

Large

  • Enterprise EDR/EPP (e.g., CrowdStrike, SentinelOne)
  • MDM/UEM (e.g., Microsoft Intune)

Enterprise

  • Enterprise EDR/XDR platform (e.g., CrowdStrike, SentinelOne)
  • UEM (e.g., Microsoft Intune, JAMF)
  • Zero-trust endpoint controls

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.