A.8 Technological controls

A.8.16 Monitoring activities

Not mandatory by default – decided in your SoA

What it means in plain language

New in 2022: monitor networks, systems and applications for anomalous behaviour and act on it.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

Monitoring activities fail when teams collect alerts but do not define what counts as anomalous, who triages it, or which actions close the loop. Teams should connect SIEM, EDR, cloud telemetry, and managed detection services to accountable response paths, so operators can prove that suspicious behavior is reviewed and handled in line with the incident process and improvement records.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • High-severity alerts are acknowledged in a dashboard but lack documented triage notes, escalation decisions, or closure evidence showing why the event was benign.
  • Telemetry sources cover servers but exclude cloud admin actions and endpoint privilege changes, creating a visibility gap for abnormal behavior involving identities and remote access.
  • Analysts receive alerts from several tools, yet no role owns tuning, correlation rules, or weekly review of false positives versus genuine security events.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Define the monitored event set by asset class and risk: authentication anomalies, privilege changes, malware detections, network beaconing, cloud configuration drift, and service health indicators. Assign primary ownership to Security Operations or IT operations, with a named manager approving threshold changes and documenting business context for alert priorities.
  • Build an alert triage workflow that records receipt time, analyst action, severity rationale, supporting artifacts, and escalation path. Use a case ticket, SIEM note, or incident record to capture decisions, then feed recurring patterns into corrective action or continual improvement when rules are noisy, blind, or consistently misclassify events.
  • Calibrate tools through routine tuning sessions. For example, review impossible-travel thresholds, privileged account use outside maintenance windows, and MDR provider summaries against known change calendars. Keep change tickets, rule version history, and exceptions register entries so reviewers can trace why a detection was added, muted, or escalated.
  • Coordinate monitoring with logging, incident response, and vendor oversight. Require cloud and endpoint log forwarding, define UTC timestamps for correlation, and verify that outsourced monitoring includes response SLAs, handoff contacts, and evidence retention. This prevents isolated alerting from becoming a weak signal rather than an actionable control.

What an auditor will ask to see

  • SIEM correlation rule set, alert threshold settings, and change log showing approved tuning decisions.
  • Weekly or monthly triage report with cases, disposition codes, escalations, and unresolved items.
  • MDR service summary, escalation matrix, and ticket references for events routed to incident management.
  • False-positive reduction register and corrective action entries linked to repeated detection issues.

Baseline documents in the kit

These free kit documents help you document or evidence A.8.16. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.8.15 — Logging and A.5.26 — Response to information security incidents. Keep the ownership and evidence consistent across these activities.

ISO/IEC 27001 vs SOC 2: evidence you can reuse for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.