ISO 27001:2022 · Technological controls
ISO 27001:2022 8.16: Monitoring activities
ISO 27001:2022 8.16 covers Monitoring activities. The held text names 5 evidence records for it, the first being Statement of Applicability entry for control A.8.16, showing inclusion or justified exclusion, implementation status and the risks it.... The common gap an assessor flags is Monitoring tools are deployed but no baseline was set, so anomalies are not recognized.
Networks, systems and applications are to be monitored for anomalous behaviour, with appropriate steps taken to evaluate possible information security incidents. Purpose (stated in ISO/IEC 27002:2022): spots abnormal behaviour and possible security incidents. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 8.16.
What evidence supports 8.16?
- Annex A technological controlStatement of Applicability entry for control A.8.16, showing inclusion or justified exclusion, implementation status and the risks it treats
- Annex A technological controlA documented monitoring scope covering network traffic, system access, configuration files, security tool logs, code integrity and resource use, with retention periods
- Annex A technological controlBaselines of normal behaviour for systems and user groups, and the detection rules built on them
- Annex A technological controlAlerting configuration with thresholds and evidence of tuning to reduce false positives
- Annex A technological controlMonitoring team rota or SOC arrangement with trained staff and redundant alert channels
Where this requirement comes from
This is our own statement of ISO 27001:2022 8.16, read from the copy we hold (licensed complete copy) and stated in our words, not the standard verbatim. The framework as we hold it.
Common gaps an assessor flags
- Monitoring tools are deployed but no baseline was set, so anomalies are not recognized
- Alerts go to an unmonitored mailbox outside business hours
- Outbound traffic to known malicious domains is not monitored
- Alert fatigue from untuned rules causes real incidents to be missed
How it maps to SOC 2
- CC7.2 high Monitoring activities detect anomalies indicating malicious acts.
A link is a topical overlap with a confidence and a reason. It does not establish that meeting one requirement satisfies the other, and it is not certification.