Clause 7 – Support

Clause 7.4 Communication

Mandatory requirement

What it means in plain language

Decide what security topics you communicate, when, to whom, and how – both internally (staff, management) and externally (customers, authorities, suppliers).

Is it mandatory? Yes. Clauses 4–10 are the management-system requirements; all of them must be met to be certified, and none can be excluded.

Documented information

  • Not explicitly required; a communication plan is the usual evidence.

Why this requirement matters

Security decisions often fail at the handoff between people who know about a problem and people who can act on it. Internal communications need to reach the right teams without flooding them with irrelevant alerts, while external communications may carry contractual or legal consequences. A communication plan turns these different audiences, triggers and approval responsibilities into predictable routes that remain usable under pressure.

Common auditor findings to check for

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

  • The communication matrix lists regular newsletters but omits urgent incident communications, regulator contacts or the approval of customer security statements.
  • An external notice was delayed because the plan named an unavailable individual and provided neither a deputy nor an escalation route.
  • Staff receive contradictory instructions through informal channels, with no owner responsible for updating the approved message after a policy change.

How you can implement it

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

  • Map recurring and event-driven communications by topic, audience, timing, responsible role and channel. Distinguish management reporting, workforce awareness, supplier coordination and incident notices because they require different content, urgency, confidentiality and approval controls.
  • Agree a workable approval path for sensitive external messages with legal, communications and operational leads. Define deputies and out-of-hours arrangements, and link notification triggers to the legal register rather than assuming one deadline applies everywhere.
  • Prepare short message structures for predictable events such as policy updates or service disruption. Test the contact routes using a tabletop scenario, including loss of the usual collaboration platform, and retain the delivery and escalation results.
  • Review the matrix after organisational changes and communication failures. Ask recipients whether they received sufficient information to act, then adjust the channel or level of detail. Track changes so an auditor can distinguish a maintained plan from an unused template.

What an auditor will ask to see

  • A communication plan identifying what is communicated, when, to whom, by whom and through which channels, with applicable approval responsibilities.
  • Examples of approved internal updates and external notices, showing the audience, delivery record, timing and any required confidentiality or legal review.
  • Exercise records or actual incident timelines demonstrating that deputies, alternative channels and escalation arrangements work when the normal communication route is unavailable.

Baseline documents in the kit

These free kit documents help you document or evidence clause 7.4. 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 7.3 — Awareness. 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.