← ISO 27001: Critical success factors ISO 27001

ISO 27001: Management Commitment

Leadership, roles and support (clauses 5.1, 5.3 and 7.1 to 7.4)

Tom Whipp · 31 October 2026 · 8 min read

Part of ISO 27001: Critical success factors, a series on building a management system that reflects how your organisation really runs.

Commitment is built

The heart of ISO 27001 is clause 5: leadership. An auditor will expect to spend time with your senior managers and come away convinced they genuinely support the programme. Their impression of your leadership colours everything else they see.

The good news is that commitment is made of concrete behaviours. It's something you build, one decision at a time, and the same behaviours work whatever the original motive. Whether your leadership team wants to improve security or mainly wants the certificate, these behaviours make certification easier. They also embed security in how the organisation already runs, which takes friction and cost out of the wider business.

What the standard asks

  • Leadership and commitment (5.1). Top management has to demonstrate leadership by making sure the policy and objectives are set and fit the organisation's strategic direction, that ISMS requirements are integrated into the organisation's processes, and that the resources are there. They also need to communicate why information security matters, make sure the ISMS achieves what it's meant to, direct and support the people doing the work, promote continual improvement, and support other managers in their own areas.
  • Roles, responsibilities and authorities (5.3). Responsibilities have to be assigned and communicated, including who makes sure the ISMS conforms to the standard and who reports on its performance to top management.
  • Support (7.1 to 7.4). The organisation provides the resources the ISMS needs, makes sure the people involved are competent, makes people aware of the policy and their part in it, and decides what gets communicated, when, to whom and how.

It's worth noticing the second point under 5.1. Integration into the organisation's processes is a requirement, not a nice-to-have.

The behaviours that matter

  • A named sponsor who visibly owns it. The auditor has a clear senior person to talk to about direction, resource and priorities. For the organisation, escalations have somewhere to go and the programme isn't negotiating its authority team by team.
  • Owning the risks in their own area. Risk owners can explain their risks and accept what's left, which is exactly what risk treatment asks for. The right people with authority make the trade-offs; the security function exists to help them frame those decisions. The team time follows naturally from ownership.
  • Making decisions at the forum. Minutes that show decisions are what management review and the improvement plan need. Decisions get made once, in one place, and stop being relitigated in every team.
  • Talking about it in existing meetings. Even a sentence or two in the right meeting matters. This is evidence of communication and awareness, and of the culture that colours the whole audit. Security becomes part of normal management, with no parallel set of meetings to resource.
  • Treating events and findings as learning. Events get reported, root causes are honest, and the improvement plan becomes credible. People report problems early, while they're still cheap to fix. Organisations with zero problems simply don't exist, and auditors know this.
  • Asking for the metrics, and reading them. Monitoring results are visibly reviewed and acted on. Measurement effort goes into the things leaders actually use.

A worked example: accepting risk

Accepting risk is where a leader shows they are genuinely accountable, and that's exactly what the auditor wants to see.

Maintaining service quality. Imagine an access policy that says third-party support needs manager-level approval before being given admin access. During a live issue, often out of hours, the person on call is a junior member of the team and the manager can't be reached. The service director, who owns the service levels, watches restoration wait while someone tracks down an approver.

Demonstrated accountability. The leadership team collectively agree that the policy itself is what they want as the general case; however, the service director, as risk owner, accepts that on-call staff can approve third-party admin access during a live issue, with conditions:

  • access goes through named supplier accounts with multi-factor authentication, never shared credentials
  • access is time-limited and ends when the issue closes
  • each approval is recorded against the live event, and sessions are logged
  • a manager reviews every emergency approval the next working day
  • usage is reported to the forum, and the acceptance is reviewed in six months

Where it's recorded. In the forum minutes, in the risk register with the residual risk accepted by the service director, and in the event records where each use is logged.

The story the leader tells. At audit, this becomes something the service director can talk about with confidence:

"Out-of-hours approvals were slowing down service restoration, so I agreed that on-call staff can approve supplier access during a live issue, with conditions. Every use is logged against the incident, a manager checks it the next day, and we review it at the forum. It's been used six times so far, and we've tightened one condition. Do I love this? Not really, but it's the best balance we could find."

What the auditor sees. A business leader who understands the risk, made a deliberate trade-off against a service objective, and put conditions, an audit log and a review date around it. That's risk acceptance working as intended, and strong evidence of leadership engagement.

What the organisation gains. Service is restored faster. A junior team member is trusted with a clear rule. The supplier has a defined route in, and the next-day review catches anything unexpected quickly.

How to build it

Start with a conversation, not a document. Sit down with pen and paper and ask what they're worried about, and where they'd like more clarity. Come back with suggested wording.

Bring prepared decisions. Set out the trade-off, two or three options, a recommendation and the conditions, so a leader can decide in minutes.

Make the asks small and specific. "Can we add this one item to your meeting agenda?" lands far better than "we need your commitment".

Help leaders find their stories to tell. Each decision they make becomes something they can talk about at audit, like the example above. Stress that it's the decision making more than the decision that matters.

Make their contribution visible. The minutes and the risk register record who decided what, so their engagement is credited to them.

Brief them before the audit, on what the auditor is really looking for. The auditor isn't expecting perfection; what they need to see is a commitment to improvement. Current issues are fine, as long as leaders recognise them as problems that are understood and being managed through the improvement plan. A leader who can say "yes, that's a gap, here's the plan and here's where we are" makes a far stronger impression than one who plays it down or doesn't know. A short reminder of the decisions they've made and the open items they own is usually enough.

What good looks like

  • Leadership behaviours are visible in the minutes, the risk register and the improvement plan.
  • Meetings fit the organisation. A few standing agenda items in meetings that already happen; a quarterly review in an existing leadership forum or risk committee covering the senior decisions and management review inputs; and a more frequent operational security meeting underneath, which leadership attends less often or with fewer senior people. Together, the minutes from both layers show an ISMS woven into how the organisation is managed.
  • The ISMS is cross-linked to the rest of the organisation. Information security risks sit in, or link to, the main risk register. Security is part of procurement, HR and change processes. Security events are reviewed alongside operational incidents.
  • Roles are clear. Who sponsors, who owns which risks, who runs the ISMS day to day, and who reports to leadership are all written down and known.

Evidence an auditor will ask for

  • Minutes from leadership meetings showing ISMS items and decisions
  • Terms of reference for the forum and the operational security meeting
  • A record of roles, responsibilities and authorities
  • The risk register, with business owners and accepted residual risk
  • Decisions on resources for the ISMS
  • Records of competence, awareness and communication
  • Conversations with the leaders themselves

Common failure modes

  • Hiding the gaps. Leaders who present everything as fine lose credibility the moment the auditor finds something.
  • The ISMS as a separate island. The ISMS runs its own meetings, its own risk register and its own processes, with no links to the rest of the organisation. Security risks never reach the main risk register, forum decisions never reach the executive meeting, and procurement, HR and incident reviews carry on without reference to it. Often the operational security meeting exists but nothing flows up to the leadership meetings. An auditor who can't find the cross-links sees a compliance project rather than an organisation managing its risks.

How it connects

Feeds from

  • Leadership's own view of why the organisation is doing this

Feeds into

Where it sits in the plan

Stage: Commit. This comes before the loop starts. Brief your leadership on what they're signing up to and why, agree a sponsor, set up the forum, and agree the scope and top-level policy. You're ready to move on when leadership has formally agreed the scope and the forum has met.

After that, commitment is built and shown every cycle, through the decisions leaders make and the stories they can tell about them. Management review is where it's checked: whether the resources, roles and integration still match what the ISMS needs.

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.

Ready to leave the spreadsheets behind?

Start your free trial today. No credit card required. No sales call. Your data, your platform, in minutes.