A.5 Organizational controls

A.5.5 Contact with authorities

Not mandatory by default – decided in your SoA

What it means in plain language

Know which authorities to contact (police, data protection authority, CERT, regulator) and keep the contacts up to date, so you can react quickly in an incident.

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

During an incident, hesitation over who to call can waste the response window and complicate legal duties. Teams should maintain a current list of authorities such as police, national CERT, and the relevant data protection authority, while defining who is allowed to contact them, under what circumstances, and what information may be shared. The Legal & Regulatory Requirements Register should anchor jurisdiction-specific obligations and notification triggers.

Common auditor findings to check for

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

  • The incident team cannot quickly identify the correct authority for a cybercrime, privacy breach, or regulated-service event, so escalation stalls and deadlines may be missed.
  • Contact details are outdated or unverified, with no record of review, no named backup contact, and no clear approval to communicate externally on behalf of the organization.
  • The response procedure mentions authorities in general terms, but there is no decision tree for notification, no evidence retention plan, and no legal mapping to triggers.

How you can implement it

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

  • Maintain a living authority contact list in the incident response pack, including names, role titles, telephone numbers, email addresses, out-of-hours channels, and language or regional notes where relevant. Verify entries on a risk-based cadence and after any organizational or jurisdiction change.
  • Assign one or more authorized contacts for each authority interface, such as legal, privacy, or security lead. The procedure should show who decides to notify, who drafts the message, who approves it, and who preserves the evidence of that communication.
  • Tie each authority to a trigger from the legal register: personal data breach, ransomware with criminal indicators, sector-specific reporting, or contractual notice. This keeps escalation consistent and avoids ad hoc decisions made under pressure.
  • Run tabletop exercises that include a notification decision, a draft call script, and preservation of timestamps, email chains, and case notes. After exercises or real incidents, update the list, test alternative contacts, and record the changes made.

What an auditor will ask to see

  • An authority contact directory with verified dates, named alternates, and authorization to contact each body.
  • Incident logs or exercise records showing notification decisions, draft communications, and timestamps of calls or emails.
  • Legal register entries mapping specific incident triggers to authority reporting obligations and owners.

Baseline documents in the kit

These free kit documents help you document or evidence A.5.5. 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.31 — Legal, statutory, regulatory and contractual requirements. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core 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.