ISO 27001 Annex A 8.16: Monitoring activities

What Control 8.16 means in practice

Actively monitor relevant systems, networks, applications and identities so unusual behaviour is detected, investigated and escalated. The useful question is not whether a policy mentions the topic, but whether scope, decisions, ownership and records show a repeatable response to actual risk.

Design should fit the organization’s services and dependencies. A smaller team can use lightweight records and existing platforms; a complex environment normally needs clearer separation of duties, automated coverage checks and governed exceptions.

Implementation steps

1. Step 1. Define ownership, scope and operating criteria for monitoring activities.
2. Step 2. Implement monitoring standard that fits the organization’s risks, services and working practices.
3. Step 3. Integrate the activity with relevant change, exception and review processes.
4. Step 4. Review performance and improve the arrangement when risks, technology or obligations change.

Translate each step into an owner, trigger, expected record and review rule. This makes the activity testable and prevents an attractive document from becoming the whole implementation.

What good implementation looks like

• recent alerts with attributable investigation and closure
• missing-log-source reports and recovery action
• rule tuning based on false positives, incidents and environmental change
• response-time evidence and escalations for high-severity alerts

These outcomes should be observable in normal work, not only during audit preparation. Owners should be able to explain weak results, accepted exceptions and the next improvement action.

Implementation evidence and effectiveness evidence

Implementation evidence shows that the arrangement exists. Effectiveness evidence shows whether it produces the intended result across the relevant scope and over time. Auditors commonly corroborate both.

How an auditor may test Control 8.16

1. Select a representative in-scope service, asset or process.
2. Confirm the accountable owner and expected operation.
3. Trace a recent example: Repeated failed logins followed by success from an unusual location.
4. Inspect the operating record and corroborating technical evidence.
5. Compare the design with evidence that the control operated effectively.
6. Follow an exception or adverse result through decision and closure.
7. Review trends, metrics and improvement decisions.

Questions to prepare for

• How is monitoring activities implemented in practice?
• Who owns the activity and how are decisions approved?
• Show me a recent example from operation through review.
• How are exceptions, changes or overdue actions handled?

Practical examples

Monitoring scope and detection lifecycle

Define which identities, endpoints, networks, cloud services, applications and critical processes need monitoring. Connect each important scenario to a signal, rule, severity, owner and response path. Coverage includes source health: a silent agent or missing log stream can be as important as an alert.

1. Identify relevant threat and failure scenarios.
2. Select trustworthy telemetry with time, identity and asset context.
3. Design and test detection logic, severity and ownership.
4. Triage, investigate and preserve a decision record.
5. Escalate, contain or close with a reviewable reason.
6. Tune using incidents, false positives, change and missed detections.

Logging, monitoring and SIEM are not interchangeable

A large volume of stored logs is not proof of monitoring. The differentiator is that relevant signals are reviewed, investigated and used to drive action. A SIEM can centralize analysis and workflow, but is not mandatory. Microsoft 365, Azure, AWS and other native services can support effective monitoring when signals are deliberately selected, assigned and tested.

Useful performance and coverage measures

• critical systems with active monitoring
• alert acknowledgement and investigation time
• log sources silent beyond threshold
• high-fidelity rules reviewed and tuned
• repeat alerts closed without corrective action

Use measures to expose coverage, timeliness, recurrence and exception age. Raw activity volume is not success; a metric should help an owner decide or investigate.

Approach for smaller and mature organizations

Smaller organization

Start with identity, endpoint, email, cloud-administration and critical-service alerts. Assign named reviewers, define severity and keep a simple investigation record.

Mature or complex organization

Use governed detection engineering, source-health monitoring, tiered analysis, case management, threat-informed scenarios and measured tuning across SOC and platform teams.

Practical implementation checklist

• □ Define ownership, scope and operating criteria for monitoring activities.
• □ Implement monitoring standard that fits the organization’s risks, services and working practices.
• □ Integrate the activity with relevant change, exception and review processes.
• □ Review performance and improve the arrangement when risks, technology or obligations change.
• □ Sample evidence has been checked for operation and effectiveness.
• □ Exceptions have owners, rationale, review dates and closure evidence.

Common implementation mistakes

• documenting monitoring activities without consistent operation
• unclear ownership or review frequency
• evidence that does not cover the full ISMS scope
• exceptions accepted without risk-based approval or follow-up

Related controls, clauses and resources