CIS Controls v8 13.2 — Deploy a Host-Based Intrusion Detection Solution

What this control requires

Deploy a host-based intrusion detection solution on enterprise assets, where appropriate and/or supported.

In plain English

Deploy a host-based intrusion detection solution on enterprise assets, where appropriate and/or supported. In practice, this means you can prove you deploy edr-level controls on a defined cadence.

Why it matters

The CIS Controls are an industry-vetted, prioritised defence: skipping a safeguard widens the attack surface that the safeguards above and below it assume is closed. Audit frameworks (FedRAMP, PCI DSS, HIPAA) all cite CIS as evidence of due care.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

What an auditor looks for

A CIS-aligned reviewer wants to see (a) which Implementation Group you are targeting, (b) a documented owner for the safeguard, and (c) a tooling or process artefact (config, scan output, ticket) that proves the safeguard runs on the cadence the control demands.

Within Detect, the assessor will trace your implementation back to the catalogue reference (Control 13.2) and look for objective evidence on the latest two assessment cycles.

How to implement

Endpoint Protection

MDM. Make MDM enrollment a hard gate for device access (Intune compliance + Conditional Access, or Jamf + Okta device trust). Unmanaged devices simply don't get a session token.

EDR. Deploy CrowdStrike / SentinelOne / Defender for Endpoint to every server and laptop; alert on any host that stops sending telemetry for >24h.

Operational checklist

• Deploy. Document the trigger, the owner and the cadence.
• Scope: edr, enterprise.

Evidence to collect

• Edr Scan. edr_scan evidence

EDR telemetry (CrowdStrike, Defender for Endpoint) confirms threat detection. Focus: Deploy a Host-Based Intrusion Detection Solution.

Common pitfalls

• Pilot MDM rollouts that quietly exclude executives or engineers; carving out the highest-risk users is the most common audit failure.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• ISO/IEC 27001:2022 A.8.7 — Protection against malware

Related controls in CIS Controls v8

• Control 13.11 — Tune Security Event Alerting Thresholds
• Control 8.9 — Centralize Audit Logs
• Control 10.7 — Use Behavior-Based Anti-Malware Software
• Control 8.6 — Collect DNS Query Audit Logs
• Control 8.7 — Collect URL Request Audit Logs
• Control 10.1 — Deploy and Maintain Anti-Malware Software

References

• Center for Internet Security — CIS Controls v8
• Catalogue identifier: Control 13.2

Topics: governance riskedr xdrendpoint protectionthreat intelligence