NIST SP 800-171 Rev 3
03.14 SI (System and Information Integrity)

NIST SP 800-171 Rev 3 03.14.06: System Monitoring

Monitor the system to detect attacks and indicators of potential attacks; identify unauthorized use of the system; deploy monitoring devices strategically.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 58 controls across 24 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • ASD37-28 Continuous incident detection and response (Excellent)
  • ASD37-29 Host-based IDS/IPS (Very Good)
  • ASD37-30 Endpoint detection and response (Very Good)
  • ASD37-32 Network-based IDS/IPS (Limited)
  • ASD37-33 Capture network traffic (Limited)
  • ASBv3-LT-1 Enable threat detection capabilities
  • ASBv3-LT-2 Enable threat detection for identity and access management
  • ASBv3-NS-4 Deploy intrusion detection/intrusion prevention systems (IDS/IPS)
  • DP-2 Monitor anomalies and threats targeting sensitive data
  • ES-1 Use Endpoint Detection and Response (EDR)

CIS Controls v8 · 5 controls

  • CIS-13.1 Centralize Security Event Alerting
  • CIS-13.2 Deploy a Host-Based Intrusion Detection Solution
  • CIS-13.3 Deploy a Network Intrusion Detection Solution
  • CIS-13.6 Collect Network Traffic Flow Logs
  • CIS-13.8 Deploy a Network Intrusion Prevention Solution

FedRAMP High · 5 controls

  • SI-4 System Monitoring
  • SI-4(1) System Monitoring | System-wide Intrusion Detection System (SI-4(1))
  • SI-4(2) Automated Tools and Mechanisms for Real-Time Analysis
  • SI-4(4) Inbound and Outbound Communications Traffic
  • SI-4(5) System-Generated Alerts

FedRAMP Moderate · 5 controls

  • SI-4 System Monitoring
  • SI-4(1) System Monitoring | System-wide Intrusion Detection System (SI-4(1))
  • SI-4(2) Automated Tools and Mechanisms for Real-Time Analysis
  • SI-4(4) Inbound and Outbound Communications Traffic
  • SI-4(5) System-Generated Alerts

PCI DSS 4.0 · 4 controls

  • 11.2.1 11.2.1 Detect authorized and rogue wireless access points
  • 11.5.1 11.5.1 IDS/IPS monitoring of CDE traffic
  • 11.5.1.1 11.5.1.1 Service providers detect covert malware channels
  • 11.5.2 11.5.2 Change detection on critical files

C5 (Germany) · 3 controls

  • C5-COS-01 Technical safeguards
  • C5-COS-03 Monitoring of connections in the Cloud Service Provider's network
  • C5-OPS-13 Logging and Monitoring - Identification of Events
  • NIST-CSF-DE.AE-02 Potentially adverse events are analyzed to better understand associated activities
  • NIST-CSF-DE.CM-01 Networks and network services are monitored to find potentially adverse events
  • NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events

CMMC 2.0 · 2 controls

HIPAA Security Rule · 2 controls

NIST SP 800-172 · 2 controls

  • 3.11.2e Threat Hunting
  • 3.14.2e Monitor Organizational Systems with Specialized Capabilities

NIST SP 800-66 Rev 2 · 2 controls

  • E8-APP-ML3 Application Control (ML3)

APRA CPS 234 · 1 control

  • AUCDR-IS-5 Limit, prevent, detect and remove malware

ISO 27001:2022 · 1 control

  • 8.16 Monitoring activities

ISO 27002:2022 · 1 control

  • 8.16 Monitoring activities

SOC 2 · 1 control

  • SOC2-CC7.2 CC7.2 Monitoring system components for anomalies

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in 03.14 SI (System and Information Integrity)

You are reading one control. How much of NIST SP 800-171 Rev 3 have you already done?

NIST SP 800-171 Rev 3 03.14.06 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-171 Rev 3 your existing evidence covers. Hold PCI DSS 4.0 and 69 of 97 NIST SP 800-171 Rev 3 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the PCI DSS 4.0 pair alone.

Query this from an agent

The graph holds this control, the 58 it maps to, and the evidence behind each claim, over MCP and REST.