Skip to content
Technological controls
ISO 27001A.8.16

ISO 27001 Annex A 8.16 Monitoring activities

What it says

Networks, systems and applications shall be monitored for anomalous behaviour and appropriate actions taken to evaluate potential information security incidents.

Quoted as published. Everything else on this page is written by Control Stack.

In plain English

Watch networks, systems and applications for unusual activity, and take appropriate steps to check whether it may be an information security incident.

Your organisation must monitor networks, systems and applications for anomalous behaviour, meaning activity that differs from what is normal or expected, and take appropriate actions to evaluate potential information security incidents. Both parts are required:

  • Monitor all three: networks, systems and applications.
  • Evaluate: when something unusual appears, check whether it may be an incident. Your organisation decides what actions are appropriate, based on its risks and context.

Annex A 5.25 covers the decision on whether an event is an incident.

Why it matters

Malware or an attacker using stolen credentials can go unnoticed when nobody is watching for unusual activity. Monitoring against what is normal brings it to attention, and evaluating each alert separates potential incidents from false alarms.

How to implement

  1. Decide what to monitor, based on business and security requirements.

    Cover inbound and outbound traffic, access to systems and applications, changes to critical configuration files, security tool logs and resource use. Start with critical systems. List what is covered, with a named person's risk decision for anything left out. Check privacy and workplace surveillance law before monitoring people's activity.

  2. Establish a baseline of normal behaviour.

    Record typical use at normal and peak times, and usual access times, locations and frequency for each user group. Where a tool learns this itself, review what it has learned before relying on it.

  3. Set up tools to alert on anomalies.

    Options include a security information and event management (SIEM) platform or intrusion detection system, fed by logs (Annex A 8.15) and threat intelligence (analysed threat information, Annex A 5.7). Alert on unusual sign-ins, known malicious addresses, unapproved scanning and unexpected application failures. Send alerts to a watched channel, with a backup contact.

  4. Define how each alert is evaluated.

    Write who receives alerts and during what hours, how quickly they respond, what checks they run and how they rule an alert in or out. Pass possible incidents to the Annex A 5.25 assessment and record each outcome. Tune rules that give false alarms rather than ignoring them.

  5. Cover bought services and outsourced monitoring.

    Turn on each service's audit logs and security alerts and feed them into your tool. If a provider does the monitoring, agree what it watches, its hours of cover, how alerts reach you and who decides next steps. Ask platform providers what they monitor and how they would tell you.

Keep it running

Update the baseline when systems, usage or locations change, such as a new office or cloud service. Review coverage and rules after any incident that monitoring missed, and fix rules whose alerts nobody acts on.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    The monitoring coverage list, compared with the asset inventory.

    Look at

    Whether networks, systems and applications are all covered, since applications and cloud services are often missed.

    Good evidence

    Every network, system and application in scope feeds the monitoring tool, no category is left out, and each exclusion has a risk decision recorded by a named person.

  2. Check 2 of 5What an auditor asks for

    Ask for

    A harmless simulated anomaly, such as a sign-in from an unusual location or an unapproved scan.

    Look at

    Whether it raises an alert, who receives it and how long that takes, including outside business hours if your cover includes them.

    Good evidence

    The test raises an alert that reaches the person on duty within the time your organisation set.

  3. Check 3 of 5What an auditor asks for

    Ask for

    Alert records for a recent period, with triage notes.

    Look at

    Whether each alert was evaluated, what was checked and whether any were closed without a reason.

    Good evidence

    Every sampled alert has a recorded evaluation and outcome, and possible incidents went on to the Annex A 5.25 assessment.

  4. Check 4 of 5What an auditor asks for

    Ask for

    The baseline and the rules built on it.

    Look at

    Whether the baseline reflects current systems and usage, and whether rules were switched off to quieten alerts.

    Good evidence

    The baseline matches current use, and every disabled rule has a recorded reason.

  5. Check 5 of 5What an auditor asks for

    Ask for

    The service agreement and handover records for any outsourced monitoring.

    Look at

    What the provider watches and its hours, compared with your coverage list, and a recent alert traced from the provider to your decision.

    Good evidence

    The provider's scope covers what your list says it should, and a sampled alert was handed over and evaluated as agreed.

Mappings

Closest match in ASD Essential Eight: E8-AC-ML2.7, Event logs from internet-facing servers are analysed to detect cyber security events, which this control covers in full and more.

Essential Eight

ASD Essential Eight: 18 mappings

ASD ISM

ASD Information Security Manual: 36 mappings

ASD Essentials

ASD Essentials for enterprise IT: 8 mappings

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.

Get help with this control

ISO 27001 training

Mindset Cyber, a PECB Authorised Titanium Partner, sells official PECB ISO/IEC 27001 courses that map directly to the controls in this library.