Clause 4 – Context of the organization

Clause 4.4 Information security management system

Mandatory requirement

What it means in plain language

You must actually build, run, maintain and keep improving a management system – not just write documents. The ISMS is the set of processes (risk management, audits, reviews, improvement) and how they interact.

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

  • No specific document; the whole kit evidences it.

Why this requirement matters

An ISMS fails as a management system when each activity operates in isolation: risks are assessed but never affect investment, audits produce findings but no corrective action follows, and management sees documents rather than decisions. Connecting these activities makes security part of ordinary business management instead of a separate compliance exercise. The important question is whether an issue discovered in one process reliably changes the work performed by another.

Common auditor findings to check for

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

  • The risk assessment, internal audit programme and management review calendar exist separately, with no agreed handoff of results between their owners.
  • An outsourced security activity appears in the scope, but nobody can explain how its performance enters internal monitoring or improvement decisions.
  • Procedures describe intended processes, while staff demonstrate informal alternatives that bypass escalation, document control or the approval of significant changes.

How you can implement it

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

  • Draw an ISMS process map showing inputs, outputs and dependencies for risk assessment, treatment, competence, monitoring, internal audit, review and improvement. For each connection, identify the receiving role and the decision that the information should support.
  • Build a working calendar around your organisation’s planning cycle rather than copying a generic annual schedule. Arrange review meetings after the relevant evidence becomes available, and assign deputies so absence does not stop time-sensitive security work.
  • Use a shared action tracker to connect audit issues and operational incidents to treatment or improvement work. Keep the original source reference, accountable owner, agreed target and closure evidence so the chain remains inspectable across meetings.
  • Walk through one recent change with the process owners. Check whether its effects reached scope, risk, controls and training, then correct broken handoffs. Record the walkthrough and the resulting process changes as evidence that the system itself is maintained.

What an auditor will ask to see

  • A current process map and responsibility table showing how operational information reaches risk treatment, leadership review and improvement decisions.
  • Calendar entries and completed records from an actual operating cycle, with explanations and revised plans for activities that slipped.
  • An end-to-end action trail connecting an incident or audit finding to a management decision, implemented change and effectiveness check.

Baseline documents in the kit

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

Connect this work to your ISMS

Review the dependencies with 5.1 — Leadership and commitment and 9.3 — Management review. 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.