MON-23: Network Intrusion Detection & Prevention Systems (NIDS & NIPS) Monitoring
Mechanisms exist to monitor Network Intrusion Detection / Prevention Systems (NIDS / NIPS) technologies on critical systems, key network segments and network choke points.
Renumbered: Formerly MON-01.1 in SCF 2025.4.
Control Question: Does the organization implement Intrusion Detection / Prevention Systems (IDS / IPS) technologies on critical systems, key network segments and network choke points?
General (25)
| Framework | Mapping Values |
|---|---|
| AICPA TSC 2017:2022 (used for SOC 2) (source) | CC7.2 CC7.2-POF2 CC7.2-POF3 |
| COBIT 2019 | DSS05.07 |
| CSA IoT SCF 2 | OPA-04 |
| GovRAMP | SI-04(01) |
| GovRAMP Moderate | SI-04(01) |
| GovRAMP High | SI-04(01) |
| ISO 27002 2022 | 8.16 |
| ISO 27018 2025 | 8.16 |
| MPA Content Security Program 5.3.1 | TS-2.7 |
| NIST 800-53 R4 | SI-4(1) |
| NIST 800-53 R5.2 | SI-04(01) SI-04(25) |
| NIST 800-82 R3 | SI-04(01) SI-04(25) |
| NIST 800-160 Vol2 R1 | SI-04(01) SI-04(25) |
| NIST 800-171 R3 (source) | 03.13.01.a |
| NIST 800-171A R3 (source) | A.03.13.01.a[01] |
| NIST CSF 2.0 (source) | DE.CM-01 |
| OWASP Top 10 2025 | A01:2025 A09:2025 |
| PCI DSS 4.0.1 (source) | 1.4.3 11.5 11.5.1 11.5.1.1 12.10.5 |
| PCI DSS 4.0.1 SAQ A-EP (source) | 1.4.3 11.5.1 |
| PCI DSS 4.0.1 SAQ B-IP (source) | 1.4.3 |
| PCI DSS 4.0.1 SAQ D Merchant (source) | 1.4.3 11.5.1 12.10.5 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 1.4.3 11.5.1 11.5.1.1 12.10.5 |
| Shared Assessments SIG 2025 | N.7 |
| SPARTA 4.0 | CM0032 |
| SWIFT CSF 2025 | 6.5A |
US (8)
| Framework | Mapping Values |
|---|---|
| USA Federal CMS MARS-E 2.0 | SI-4(1) |
| USA Federal DHS CISA TIC 3.0 | 3.PEP.IN.IDPSY |
| USA Federal C2M2 2.1 | ARCHITECTURE-2f |
| USA Federal CMMC 2.0 Level 3 | SI.L3-3.14.6E |
| USA Federal FedRAMP R5 (moderate) | SI-04(01) |
| USA Federal FedRAMP R5 (high) | SI-04(01) |
| USA Federal IRS 1075 2021 | SI-4(CE-1) |
| USA California CCPA 2025 | 7123(c)(8)(A) |
EMEA (1)
| Framework | Mapping Values |
|---|---|
| EMEA Germany C5 2026 | OPS-34.02B.7 COS-01.01B |
APAC (3)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2026 | ISM-1030 |
| APAC New Zealand NZISM 3.9 | 16.6.10.C.01 16.6.10.C.02 18.4.7.C.01 18.4.7.C.02 18.4.7.C.03 18.4.8.C.01 18.4.8.C.02 18.4.8.C.03 18.4.9.C.01 18.4.9.C.02 18.4.11.C.01 18.4.11.C.02 18.4.11.C.03 18.4.12.C.01 18.4.14.C.01 |
| APAC Singapore CCOP CII 2026 | 6.1.2(d) |
Americas (2)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 2025 | 03.13.01.A |
| Americas Canada OSFI B-13 2022 | 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
SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.
Level 2 — Planned & Tracked
Continuous Monitoring (MON) 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 MON domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with MON 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 MON domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Continuous monitoring-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Continuous monitoring 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
Continuous Monitoring (MON) 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 MON domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Cybersecurity personnel use a structured process via Standardized Operating Procedures (SOP) to review and analyze logs. ▪ A Security Operations Center (SOC) team, or similar function, is appropriately staffed and supported to implement and maintain MON domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of continuous monitoring operations (e.g., Security Incident Event Manager (SIEM)). ▪ 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 MON 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). ▪ Secure Baseline Configurations (SBC) enforce security event logging to contain sufficient information to establish necessary details of activity and allow for forensics analysis. ▪ An implemented and operational capability exists to implement Intrusion Detection / Prevention Systems (IDS / IPS) technologies on critical systems, key network segments and network choke points.
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
- MON-23_A01 visibility into network traffic at external system interfaces is provided to optimize the effectiveness of monitoring devices.
- MON-23_A02 visibility into network traffic at key internal system interfaces is provided to optimize the effectiveness of monitoring devices.
- MON-23_A03 individual intrusion detection tools are connected to a system-wide intrusion detection system.
- MON-23_A04 individual intrusion detection tools are configured into a system-wide intrusion detection system.
- MON-23_A05 Network Intrusion Detection / Prevention Systems (NIDS / NIPS) technologies are deployed on critical systems, key network segments and network choke points.
- MON-23_A06 alerts and events generated by Network Intrusion Detection / Prevention Systems (NIDS / NIPS) technologies are monitored and reviewed.
Evidence Requirements
- E-NET-11 Intrusion Detection / Prevention Deployment
-
Documented evidence of Network and Host Intrusion Detection / Prevention Systems (NIDS / NIPS, HIDS / HIPS) deployment and monitoring coverage.
Network Security
Technology Recommendations
Micro/Small
- Intrusion Detection / Prevention Systems (IDS/IPS)
- Next-Generation Firewall (NGFW) with IPS (e.g., Fortinet FortiGate, Palo Alto)
Small
- Intrusion Detection / Prevention Systems (IDS/IPS)
- Next-Generation Firewall (NGFW) with built-in IPS (e.g., Fortinet, Palo Alto)
Medium
- Intrusion Detection / Prevention Systems (IDS/IPS)
- Next-Generation Firewall (NGFW) with IPS
- Extended Detection and Response (XDR) (e.g., CrowdStrike Falcon, SentinelOne, Microsoft Defender XDR)
Large
- Intrusion Detection / Prevention Systems (IDS/IPS)
- Extended Detection and Response (XDR) (e.g., CrowdStrike Falcon, Palo Alto Cortex XDR)
- Network Detection and Response (NDR) (e.g., Darktrace, ExtraHop)
Enterprise
- Enterprise IDS/IPS integrated with SIEM
- Extended Detection and Response (XDR) (e.g., CrowdStrike Falcon, Palo Alto Cortex XDR)
- Network Detection and Response (NDR) (e.g., Darktrace, ExtraHop, Vectra AI)
- AI-driven anomaly detection