Part of ISO 27001: Critical success factors, a series on building a management system that reflects how your organisation really runs.
What it is
The management forum is where leadership makes the decisions the ISMS depends on: approving the improvement plan, agreeing priorities and resources, and putting risk owners' acceptance of residual risk on the record. Acceptance itself stays with each risk owner; the forum reviews, challenges and endorses. In the standard it's called management review, and it's a required process rather than a particular committee: many organisations split it between existing leadership meetings and a security forum.
It sits at the top of the diagram for a reason. Everything else in the ISMS exists to give this group what it needs to decide well, and the auditor will read its minutes closely.
What the standard asks
Clause 9.3 requires top management to review the ISMS at planned intervals. The review has to consider:
- the status of actions from previous reviews
- changes in internal and external issues, and in the needs and expectations of interested parties
- feedback on information security performance: nonconformities and corrective actions, monitoring and measurement results, audit results, and progress against objectives
- feedback from interested parties
- the results of risk assessment and the status of the risk treatment plan
- opportunities for continual improvement
The outputs are decisions on continual improvement and any changes needed to the ISMS, and the results have to be documented.
What good looks like
- The right people. Members can actually make decisions about risk and resource. A forum that has to escalate everything isn't the forum.
- A sensible split. In most organisations the work is shared between existing management meetings and a security forum that handles the detail. Both show up in agendas and minutes.
- A standing agenda that covers the required inputs over the year, so nothing is missed at the formal review.
- Decisions in the minutes: who decided what, which risks their owners accepted, which actions were approved, and what changes.
- Scope revisited. At least once a year, the forum asks whether the context, interested parties and scope still hold.
Evidence an auditor will ask for
- Terms of reference: membership, authority and frequency
- Agendas showing each required input has been covered
- Minutes recording decisions and actions
- Action logs carried from one meeting to the next
Common failure modes
- The annual tick-box meeting. One review the month before the audit, working through a slide deck nobody has read. A report that nobody reads is always worthless.
- Too junior. A forum of implementers reporting to each other can't endorse risk decisions or commit resource, and the auditor will notice the gap between the minutes and the authority.
- Discussion without decisions. Minutes that record what was presented but not what was decided give the auditor nothing to test.
- Inputs missing. Audit results or interested-party feedback never reach the meeting, so the review can't be complete.
How it connects
Feeds from
- Risk analysis and the risk register
- Security events
- Metrics
- Assurance and audit findings
- Progress on the risk improvement plan
Feeds into
- The risk improvement plan, where its decisions are recorded
- Control selection and policies and standards
- The scope, on the occasions it needs to change
Where it sits in the plan
Stage: Commit, then Check and Act. Set the forum up before the loop starts, with terms of reference and a first meeting. It carries out management review in Check and makes the decisions in Act. Before the main certification audit, certification bodies will normally expect to see a full management review, covering every required input, as part of the evidence that the ISMS has been running.
The plan in the main article shows how this fits with everything else, and the bootstrapping guide covers each stage in detail.
Resources
Tom Whipp is the founder of RiskQuilt. He spent around thirty years in cyber and technology risk in UK financial services, including CISO and Director of Technology Risk roles.