ISO 27001 A.8.16: Monitoring activities
Logging (A.8.15) captures the raw data. This control - new in ISO 27001:2022 - is about actually watching that data in real time to spot attacks as they happen. The average breach goes undetected for months. Active monitoring is how you shrink that window from months to minutes.
Work through the ISO 27001 assessment, record supporting evidence and review the gaps in your answers.
Requirement summary
Networks, systems and applications shall be monitored for anomalous behaviour and appropriate actions taken to evaluate potential information security incidents.
Check the source wording and scope in ISO/IEC 27001:2022. The guidance below explains how to approach a review.
In Plain Language
You need to detect both known threats (using signatures and rules) and novel ones (using anomaly detection and behavioural analysis). Sophisticated attackers specifically design their techniques to evade signature-based detection, so relying on signatures alone leaves you blind to lateral movement, slow data exfiltration, and insider threats.
Monitoring should span your entire stack: network traffic, system behaviour, application logs, user activity patterns, and cloud service events. When something looks wrong, it needs to flow into your incident management process for investigation and response.
How to Implement
Deploy monitoring tools that match your environment. The key capabilities are: SIEM for log correlation and alerting, network detection and response (NDR) for traffic analysis, endpoint detection and response (EDR) for endpoint behaviour, user and entity behaviour analytics (UEBA) for anomaly detection, cloud security monitoring for cloud workloads, and application performance monitoring (APM) for application behaviour.
Build detection use cases around your risk assessment and threat model. Focus on what actually matters: brute force attacks, privilege escalation attempts, lateral movement, data exfiltration indicators, command and control communications, unauthorised access to sensitive data, anomalous user behaviour, and unusual cloud resource provisioning.
Create detection rules for each use case. Mix signature-based rules for known threats, threshold-based rules for volumetric indicators, and anomaly-based rules for behavioural deviations. Tune aggressively to reduce false positives without sacrificing detection. Integrate threat intelligence feeds to keep your rules current with evolving attack patterns.
Set up monitoring operations. Define who watches the alerts and when. Critical environments need 24/7 coverage. Create triage procedures with clear response actions for different alert types. Build escalation paths for alerts that need senior analysis or full incident response. Track alert volumes, false positive rates, and mean time to investigate.
Measure and improve continuously. Track detection coverage (map against MITRE ATT&CK to see your blind spots), mean time to detect (MTTD), mean time to respond (MTTR), and false positive rates. Use red team exercises and penetration tests to validate your detection capabilities. Review and tune detection rules regularly.
Evidence to review
- Monitoring strategy and tool deployment documentation
- Detection use cases and alert rule documentation
- SIEM alert triage and investigation records
- Monitoring operations procedures including escalation paths
- Monitoring effectiveness metrics and improvement records
Common Mistakes
- Monitoring relies solely on signature-based detection without behavioral analysis
- Alert fatigue leads to alerts being ignored or inadequately investigated
- No 24/7 monitoring for internet-facing or critical systems
- Monitoring coverage has gaps in cloud environments or specific system types
- Detection rules are not updated to reflect current threat patterns
Related Controls Across Frameworks
| Framework | Control ID | Relationship |
|---|---|---|
| SOC 2 | SOC 2 CC7.2: System Operations - Monitoring of System Components for Anomalies | Equivalent |
| SOC 2 | SOC 2 CC7.3: System Operations - Evaluation of Security Events | Related |
| NIS2 | NIS2 Art.21(2)(b): Incident Handling Procedures | Equivalent |
Frequently Asked Questions
Is this control new in ISO 27001:2022?
Do we need 24/7 monitoring?
Related Articles
Compliance Costs: Budgeting for DIY, Consulting and Software
Compare staff time, audit fees, consulting, software and remediation without treating different services as interchangeable.
Read article →ISO 27001 Certification Cost: Build a Budget from Your Scope
Separate certification fees, preparation, staff time and remediation. Learn what to include in a quote request and a first-year ISO 27001 budget.
Read article →How to Get ISO 27001 Certified: A Step-by-Step Guide
A practical walkthrough of the ISO 27001 certification process - from scoping to stage 2 audit. Covers timelines, costs, common mistakes, and what auditors actually look for.
Read article →Track ISO 27001 compliance in one place
Work through the ISO 27001 assessment, record supporting evidence and review the gaps in your answers.
Start Free AssessmentStart without an account · Sign up only to save