Skip to main content

END-07: Host Intrusion Detection and Prevention Systems (HIDS / HIPS)

END 9 — Critical Protect

Mechanisms exist to utilize Host-based Intrusion Detection / Prevention Systems (HIDS / HIPS), or similar technologies, to monitor for and protect against anomalous host activity, including lateral movement across the network.

Control Question: Does the organization utilize Host-based Intrusion Detection / Prevention Systems (HIDS / HIPS), or similar technologies, to monitor for and protect against anomalous host activity, including lateral movement across the network?

General (10)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) CC6.8
CIS CSC 8.1 13.2 13.7
CIS CSC 8.1 IG2 13.2
CIS CSC 8.1 IG3 13.2 13.7
CSA IoT SCF 2 SAP-06
NIST 800-171 R3 (source) 03.14.06.a.01 03.14.06.a.02 03.14.06.b 03.14.06.c
Shared Assessments SIG 2025 N.7
SCF CORE Mergers, Acquisitions & Divestitures (MA&D) END-07
SCF CORE ESP Level 2 Critical Infrastructure END-07
SCF CORE ESP Level 3 Advanced Threats END-07
US (4)
Framework Mapping Values
US CJIS Security Policy 5.9.3 (source) 5.10.1.3
US DHS CISA TIC 3.0 3.PEP.IN.IDPSY 3.PEP.WE.ACMIT 3.PEP.SE.ACMIT
US HIPAA HICP Large Practice 1.L.A 2.L.C 2.L.D
US - NY DFS 23 NYCRR500 2023 Amd 2 500.14(b)(1)
EMEA (2)
Framework Mapping Values
EMEA Israel CDMO 1.0 7.4 7.5 12.18 12.24 23.6
EMEA Spain CCN-STIC 825 7.6.1 [OP.MON.1]
APAC (2)
Framework Mapping Values
APAC Australia ISM June 2024 ISM-1034 ISM-1341 ISM-1418
APAC New Zealand NZISM 3.6 18.4.13.C.01
Americas (2)
Framework Mapping Values
Americas Canada CSAG 4.3 4.4
Americas Canada ITSP-10-171 03.14.06.A.01 03.14.06.A.02 03.14.06.B 03.14.06.C

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to utilize Host-based Intrusion Detection / Prevention Systems (HIDS / HIPS), or similar technologies, to monitor for and protect against anomalous host activity, including lateral movement across the network.

Level 1 — Performed Informally

Endpoint Security (END) efforts are ad hoc and inconsistent. CMM Level 1 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • Asset management is informally assigned as an additional duty to existing IT/cybersecurity personnel.
  • IT/cybersecurity personnel use an informal process to design, build and maintain secure configurations for test, development, staging and production environments, including the implementation of appropriate cybersecurity and data protection controls.
  • Anti-malware technologies are decentralized but are deployed on all technology assets that can run Anti-malware software.
  • Data management is decentralized.
Level 2 — Planned & Tracked

Endpoint Security (END) efforts are requirements-driven and governed at a local/regional level, but are not consistent across the organization. CMM Level 2 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • Endpoint security management is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
  • IT/cybersecurity personnel identify cybersecurity and data protection controls that are appropriate to address applicable statutory, regulatory and contractual requirements for endpoint security management.
  • Anti-malware technologies are decentralized but are deployed on all technology assets that can run anti-malware software.
  • Physical controls, administrative processes and technologies focus on protecting High Value Assets (HVAs), including environments where sensitive/regulated data is stored, transmitted and processed.
  • Technologies are configured to protect data with the strength and integrity commensurate with the classification or sensitivity of the information and mostly conform to industry-recognized standards for hardening (e.g., DISA STIGs, CIS Benchmarks or OEM security guides), including cryptographic protections for sensitive/regulated data.
Level 3 — Well Defined

Endpoint Security (END) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • Configuration management is centralized for all operating systems, applications, servers and other configurable technologies.
  • Technologies are configured to protect data with the strength and integrity commensurate with the classification or sensitivity of the information and conform to industry-recognized standards for hardening (e.g., DISA STIGs, CIS Benchmarks or OEM security guides), including test, development, staging and production environments.
  • Configurations conform to industry-recognized standards for hardening (e.g., DISA STIGs, CIS Benchmarks or OEM security guides) for test, development, staging and production environments.
  • An Identity & Access Management (IAM) function, or similar function, centrally manages permissions and implements “least privileges” practices for the management of user, group and system accounts, including privileged accounts.
  • An IT Asset Management (ITAM) function, or similar function, categorizes endpoint devices according to the data the asset stores, transmits and/ or processes and applies the appropriate technology controls to protect the asset and data that conform to industry-recognized standards for hardening (e.g., DISA STIGs, CIS Benchmarks or OEM security guides).
  • A Security Operations Center (SOC), or similar function, centrally manages anti-malware and anti-phishing technologies, in accordance with industry-recognized practices for Prevention, Detection & Response (PDR) activities.
  • A Security Incident Event Manager (SIEM), or similar automated tool, is tuned to detect and respond to anomalous behavior that could indicate account compromise or other malicious activities.
  • The Human Resources (HR) department ensures that every user accessing a system that processes, stores, or transmits sensitive/regulated data is cleared and regularly trained in proper data handling practices.
  • Unauthorized configuration changes are responded to in accordance with an Incident Response Plan (IRP) to determine if the any unauthorized configuration is malicious in nature.
Level 4 — Quantitatively Controlled

Endpoint Security (END) efforts are metrics driven and provide sufficient management insight (based on a quantitative understanding of process capabilities) to predict optimal performance, ensure continued operations and identify areas for improvement. In addition to CMM Level 3 criteria, CMM Level 4 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • 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.
  • Both business and technical stakeholders are involved in reviewing and approving proposed changes.
Level 5 — Continuously Improving

See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to utilize Host-based Intrusion Detection / Prevention Systems (HIDS / HIPS), or similar technologies, to monitor for and protect against anomalous host activity, including lateral movement across the network.

Assessment Objectives

  1. END-07_A01 Host-based Intrusion Detection / Prevention Systems (HIDS / HIPS), or a similar technology, is deployed on business-critical systems.
  2. END-07_A02 Host-based Intrusion Detection / Prevention Systems (HIDS / HIPS), or a similar technology, is deployed on systems that store, process and/or transmit sensitive / regulated data.

Technology Recommendations

Micro/Small

  • Host-based Intrusion Detection / Prevention Systems (HIDS / HIPS)

Small

  • Host-based Intrusion Detection / Prevention Systems (HIDS / HIPS)

Medium

  • Host-based Intrusion Detection / Prevention Systems (HIDS / HIPS)

Large

  • Host-based Intrusion Detection / Prevention Systems (HIDS / HIPS)

Enterprise

  • Host-based Intrusion Detection / Prevention Systems (HIDS / HIPS)

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.