13.2
IG2 IG3

Deploy a Host>Based Intrusion Detection Solution

Asset Type: Devices
Security Function: Detect

Description

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

Implementation Checklist

1
Deploy detection tools or enable detection capabilities
2
Configure alerting thresholds and notification channels
3
Establish monitoring schedule and review process
4
Test detection capabilities with simulated events
5
Document detection procedures and escalation paths

Threats & Vulnerabilities (CIS RAM)

Threat Scenarios

Fileless Malware Execution on Unmonitored Endpoints

Confidentiality

An attacker deploys fileless malware using PowerShell or WMI that operates entirely in memory, evading network-level detection because no host-based intrusion detection solution is monitoring process behavior.

Insider Threat Data Harvesting on Endpoints

Confidentiality

A malicious insider installs credential harvesting tools or keyloggers on their workstation, which go undetected without host-based intrusion detection monitoring local system activity.

Rootkit Persistence Without Host-Level Detection

Integrity

An attacker installs a kernel-level rootkit that persists across reboots and hides malicious processes from standard OS tools, remaining invisible without a dedicated HIDS examining system integrity.

Vulnerabilities (When Safeguard Absent)

No Visibility into Host-Level Attack Indicators

Without host-based intrusion detection, suspicious process executions, file integrity changes, and registry modifications on individual endpoints go unmonitored, allowing attackers to operate freely post-compromise.

Inability to Detect Memory-Resident Threats

Absent HIDS capabilities, attacks that never touch disk such as in-memory exploits, living-off-the-land techniques, and process injection cannot be identified at the endpoint level.

Evidence Requirements

Type Evidence Item Collection Frequency
Technical Detection tool deployment evidence (dashboard screenshots, agent status) Captured monthly
Technical Sample alert/detection output demonstrating capability Captured quarterly
Document Governing policy document (current, approved, communicated) Reviewed annually