A.5 Organizational controls

A.5.25 Assessment and decision on information security events

Not mandatory by default – decided in your SoA

What it means in plain language

Assess security events and decide whether they are incidents that need a response.

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

Event assessment breaks down when staff rely on intuition instead of defined triage criteria. separate harmless alerts from security events and how to escalate only when impact, sensitivity, scope, or legal exposure justify incident handling. It also helps connect the Incident Response Policy and Incident Response Procedure to a repeatable decision trail that an auditor can follow.

Common auditor findings to check for

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

  • Alerts arrive through email or chat, but the reporting route is unclear, so triage starts from scattered messages rather than a controlled queue or ticket category.
  • Analysts assign severity inconsistently because impact, data type, system criticality, and suspected maliciousness are not described with enough decision examples.
  • Event decisions are made, but the incident register lacks the reason for classification, reviewer identity, timestamps, and escalation path, weakening traceability of triage outcomes.

How you can implement it

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

  • Define triage criteria that convert raw alerts into consistent decisions. Include impact on operations, affected asset criticality, data sensitivity, external exposure, and signs of malicious intent. Editors should place these factors in a decision tree or scoring table inside the Incident Response Procedure, with a clear point where a security event becomes an incident.
  • Set up a controlled reporting path, such as a security mailbox, service desk category, or SOC queue, and state who monitors it, during what hours, and what happens if a message arrives after hours. Include a rule that duplicate reports are linked to one case so the register reflects the full chain of evidence.
  • Require each triage outcome to be recorded with the rationale, person making the decision, date and time, and any escalation or closure action. If an event is downgraded, note why. If it is upgraded, add the next responder, initial containment step, and any notification deadline triggers.
  • Use short worked examples in the procedure, such as a lost laptop, a suspicious login, or a malware alert with no confirmed spread. These examples help analysts apply the same standard, while supporting supervisors in reviewing decisions during periodic quality checks or post-incident learning.

What an auditor will ask to see

  • Incident Response Procedure with triage criteria, escalation thresholds, and worked examples for common event types.
  • Security mailbox or ticket category configuration showing controlled intake and assignment rules.
  • Incident Register entries with classification rationale, reviewer name, timestamps, and escalation or closure actions.

Baseline documents in the kit

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

Connect this work to your ISMS

Review the dependencies with A.5.24 — Information security incident management planning and preparation and A.5.26 — Response to information security incidents. Keep the ownership and evidence consistent across these activities.

NIS2 and ISO/IEC 27001: reuse controls and check legal gaps 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.