All Controls
Security Control

Network Access Review & Monitoring

NIST DetectDE.CM-1CIS Control 13: Network Monitoring and Defense

What This Control Means

Network monitoring is the continuous observation and analysis of network traffic to detect suspicious activity, unauthorized access, and performance anomalies. Without monitoring, breaches can persist undetected for weeks or months, the median dwell time for breaches discovered by internal teams rather than external parties remains measured in weeks. Effective monitoring reduces this dwell time dramatically.

Network monitoring tools range from basic flow analysis (NetFlow, sFlow) that tracks traffic patterns and volumes, to full packet capture that records all network data, to Security Information and Event Management (SIEM) platforms that correlate events from multiple sources. For small and mid-sized businesses, a managed SIEM or managed detection and response (MDR) service provides the most practical path to effective monitoring without requiring an in-house security operations center.

Key indicators to monitor include unusual outbound data transfers (potential exfiltration), connections to known malicious IP addresses, lateral movement between internal systems, failed authentication attempts, and new devices connecting to the network. Alerting thresholds should be tuned to minimize false positives while ensuring that genuine threats are escalated promptly.

Network access review complements monitoring by periodically verifying which devices and users are connected to the network. Network access control (NAC) solutions can enforce policies requiring devices to meet security standards (current patches, active endpoint protection, encryption enabled) before allowing network access. Unknown or non-compliant devices should be quarantined or placed on a restricted network segment.

Why Insurers Care

Monitoring and detection capabilities are increasingly important to cyber insurers because they directly affect how quickly a breach is contained and how large the resulting claim becomes. Applications ask whether the organization monitors its network for suspicious activity and whether it has a managed detection and response service.

Organizations with 24/7 monitoring and defined escalation procedures receive more favorable underwriting because they can detect and contain incidents faster. The difference between detecting a breach in hours versus months often translates to orders of magnitude difference in claim costs.

Industry-Specific Notes

Healthcare (HIPAA)

HIPAA requires audit controls under 45 CFR 164.312(b) and monitoring of information system activity under 45 CFR 164.308(a)(1)(ii)(D). Healthcare organizations must monitor access to systems containing ePHI and be able to detect unauthorized access or data exfiltration. Network monitoring complements application-level audit logs.

Legal (ABA Guidelines)

Law firms must monitor for unauthorized access to systems containing privileged client information. Network monitoring can detect data exfiltration attempts and unauthorized access to case management systems. Firms handling high-profile or sensitive matters should consider enhanced monitoring for those specific data repositories.

Financial Services (GLBA/PCI-DSS)

FFIEC requires financial institutions to implement robust monitoring and detection capabilities. PCI-DSS Requirements 10 and 11 mandate logging, monitoring, and regular testing of security systems. Financial institutions are expected to have or contract for continuous security monitoring.

Retail / E-commerce (PCI-DSS)

PCI-DSS Requirement 10 requires tracking and monitoring all access to network resources and cardholder data. Requirement 11 requires regular testing of security systems and processes. Retail organizations must ensure monitoring covers all locations, including distributed stores and warehouses.

Government / Defense (CMMC 2.0)

NIST 800-171 controls AU.L2-3.3.1 and SI.L2-3.14.6 require audit logging and monitoring for security-relevant events. CMMC assessors verify that monitoring capabilities exist and are actively used. Government contractors must demonstrate the ability to detect and report security incidents affecting CUI.

Implementation Steps

Deploy a SIEM or subscribe to a managed detection and response (MDR) service for 24/7 monitoring

Configure log collection from firewalls, servers, endpoints, and cloud services into the central monitoring platform

Define alerting rules for high-risk indicators: data exfiltration, lateral movement, and connections to known malicious IPs

Establish escalation procedures defining who is notified and what actions are taken when alerts are triggered

Conduct quarterly reviews of monitoring coverage to ensure new systems and services are included

Want to know how your organization measures up on this control?

Take the free assessment →