
Clause 5 of ISO/IEC 27001:2022 requires top management to personally lead the information security management system (ISMS): commit to it (5.1), approve a security policy (5.2) and assign and communicate security roles (5.3). Auditors test whether leaders made decisions and gave resources, not whether a policy has a signature on it. This guide walks through each subclause, the evidence that proves it and the gaps that cause findings. It also shows how to check your position before an audit. Our free 2-minute check gives you a first read on where you stand.
TL;DR
- Clause 5 has three parts: leadership and commitment (5.1), information security policy (5.2), and roles, responsibilities and authorities (5.3).
- “Top management” means the people who direct and control the organization. In a startup, that is usually the founder or CEO, not the IT lead.
- Leaders may delegate tasks, but they stay accountable for results and must show visible decisions: budget, objectives, reviews.
- The most common gaps are a policy nobody was told about, no documented security appointment and a management review that is a formality.
- Collect evidence early: dated approvals, minutes, budget lines, an org chart and a RACI matrix.
Table of Contents
- What Clause 5 covers
- Clause 5.1: leadership and commitment
- Clause 5.2: the information security policy
- Clause 5.3: roles, responsibilities and authorities
- What auditors ask for, and what counts as evidence
- Common Clause 5 gaps and how to close them
- How Clause 5 connects to the rest of the standard
- A 30-day plan to get Clause 5 audit ready
- Budget the leadership effort, not just the tooling
- Where our calculator and assessment fit
- Our perspective
- FAQ
- Sources
What Clause 5 covers
Clause 5 sits between context and planning (Clauses 4 and 6) and decides whether the rest of the ISMS has authority. It has three subclauses: 5.1 leadership and commitment, 5.2 policy, and 5.3 organizational roles, responsibilities and authorities. The 2022 edition was published on 25 October 2022.
The structure is simple. The weight sits on one word: top management. The standard does not ask the CISO, the IT manager or the compliance officer to show leadership. It asks the people at the top, because security decisions about budget, risk appetite and priorities belong to them.
That is why Clause 5 is audited differently from technical clauses. One practitioner describes it as audited in the executive office, not in the server room: the auditor traces a chain from a decision to its effect.
Clause 5.1: leadership and commitment
Clause 5.1 lists what top management must do. In plain language, top management has to:
- Make sure the security policy and objectives are set and fit the strategic direction of the organization.
- Build ISMS requirements into ordinary business processes.
- Make sure the resources the ISMS needs are available.
- Communicate why effective security management and conformity matter.
- Make sure the ISMS achieves its intended results.
- Direct and support people so they contribute to the ISMS.
- Promote continual improvement.
- Support other managers in showing leadership in their own areas.
The full list in the standard’s wording is a set of actions, not a set of documents. Its intent is that top management is personally involved and accountable, and the last item asks leaders to create a culture where managers actively work toward ISMS requirements.
What you can delegate and what you cannot
The word “ensuring” matters. Top management may delegate specific actions but remains accountable for making sure they happen. A CEO can ask the security lead to draft objectives. The CEO still has to review and approve them, and be able to explain them to an auditor.
Security practitioner Gary Hinson makes the same point in his ISMS implementation guidelines: senior management may delegate activities such as assigning roles, allocating resources or endorsing policy, but 5.1 expects active involvement, not just offered support. He also warns that an ISMS without visible, ongoing management backing can end up sidelined and starved of resources.

Who counts as top management
In a 15-person SaaS startup, the founder is top management. In a regional bank, it is the executive committee or the CEO and direct reports who steer the organization. In a subsidiary, you need to decide whether the ISMS scope sits under the local leadership team or the parent. Write that decision down in the scope document, because the auditor will ask to meet these people.
Clause 5.2: the information security policy
The policy is the visible artifact of Clause 5, and it is where many first-time teams stop. The standard text, as reproduced in an official-language edition, requires the policy to:
- be appropriate to the purpose of the organization;
- include information security objectives or provide the framework for setting them;
- include a commitment to satisfy applicable information security requirements;
- include a commitment to continual improvement of the ISMS.
It must also be available as documented information, communicated within the organization and available to interested parties as appropriate.
Write a policy you can actually operate
Keep the top-level policy short, usually one to two pages. Put detail in topic-specific policies underneath. A policy that promises controls you do not run creates a gap between paper and practice, and auditors look for exactly that.
Good document hygiene helps here. Version numbers, an owner, an approval date and a review date should all be visible. If you need a refresher on controlling documents in general, corporate document governance practices cover the same ideas of approval, storage and access. For the ISO-specific evidence pack, see our guide to Clause 7.5 document control.
Communication is where policies fail
Signing is not communicating. The policy has to reach employees and, where relevant, suppliers and customers. Keep proof: an intranet publication with a date, an onboarding step, an all-hands announcement or an acknowledgement log. Interviewed staff should be able to say, in their own words, what the policy means for their job.
Clause 5.3: roles, responsibilities and authorities
Clause 5.3 requires top management to make sure responsibilities and authorities for relevant security roles are assigned and communicated within the organization. The official text names two specific assignments:
- responsibility and authority for making sure the ISMS conforms to the standard;
- responsibility and authority for reporting ISMS performance to top management.
A note adds that top management may also assign responsibility for reporting performance elsewhere in the organization.
A practical roles set
Most small and mid-sized organizations cover 5.3 with four artifacts:
| Artifact | What it shows | Typical owner |
|---|---|---|
| Appointment letter or role description for the ISMS manager or CISO | Someone has named authority over conformity and reporting | CEO or executive sponsor |
| RACI matrix | Who is responsible, accountable, consulted and informed for key ISMS activities | ISMS manager |
| Org chart with security reporting lines | Security has a path to top management | HR or ISMS manager |
| Role communication record | People were told what is expected of them | HR or line managers |
A documented appointment is a frequent miss. Our article on ISO 27001 roles for implementers covers three audit findings that come from unclear role assignments.
What auditors ask for, and what counts as evidence
Auditors look for behaviors, decisions and outcomes, not just documents. A signed policy is a declaration. Evidence of leadership is a chain: the leader decides, resources move, work happens, results get reviewed.
The following table maps each subclause to evidence you can usually produce from normal business activity.
| Subclause | Evidence that works | Evidence that falls short |
|---|---|---|
| 5.1 | Management review minutes with decisions, approved security budget lines, security objectives with named owners, leadership emails or all-hands notes about security | A one-line statement of support |
| 5.2 | Dated, version-controlled policy approved by named leaders, intranet publication, acknowledgement records | An undated PDF on a shared drive |
| 5.3 | Appointment of the ISMS manager, RACI matrix, role descriptions, org chart | A job title with no stated authority |
Auditors commonly ask who approved the top-level policy, when, and whether it has been reviewed since. The approval date should match the document history. On resourcing, they look for proof that leaders provided people, budget, tools and time, such as approved budget lines, headcount for security roles and time allocated to internal audit.
The finance side matters too. If the finance director approves the security budget, they should be able to explain why security receives what it receives. Prepare leaders for that conversation.
For a deeper look at categories of proof, see our practical guide to evidence for ISO 27001 audits. Management review is the richest single source of Clause 5 evidence, so build your agenda from our management review agenda guide.
Startups: the founder is the evidence
For a startup, the founder or CEO is top management, and their engagement must be visible and auditable. Practically, that means the founder attends the management review, approves the policy and signs off on budget. Interviews will be short, so the founder should know the scope, the objectives and the top risks without notes.
Common Clause 5 gaps and how to close them
These are the patterns that recur across audit guidance.
- A policy that exists but was never communicated. A frequent gap is a policy document with no formal communication. Fix: publish it, add it to onboarding and keep an acknowledgement log.
- No documented security appointment. The same source lists the absence of a documented appointment of an information security officer. Fix: a signed appointment with authority and reporting duties stated.
- Weak accountability. A council of auditors lists lack of accountability for information security as a common nonconformity under 5.1, leading to delays in incident response and risk management. Fix: assign roles, set up a governance forum with top management and meet regularly on security performance.
- A management review that is a formality. If the last review was more than twelve months ago, schedule one before the external audit. The same guide notes that staff who may be interviewed should know the policy, their responsibilities and how to report incidents.
- No leadership representative on the day. If no leader can speak to the ISMS during the audit, the organization will not conform and cannot certify. Fix: brief the executive sponsor and agree who answers what.
If you want a structured way to find these gaps before the certification body does, rate each subclause as conforming, partly conforming or nonconforming, and attach the evidence to each rating. Our readiness assessment gives you a maturity view across the four Annex A control themes, so leadership gaps appear next to the technical ones.
How Clause 5 connects to the rest of the standard
Leadership is not a stand-alone chapter. The objectives top management approves in 5.1 and 5.2 drive the risk work in Clause 6. The resources leaders commit show up in Clause 7 support. The process controls they integrate land in Clause 8 operation, and the performance reports they receive come from Clause 9. If the Clause 5 decisions are vague, every later clause inherits the vagueness.

A 30-day plan to get Clause 5 audit ready
Week 1: decide who top management is. Name the individuals, document them in the ISMS scope and confirm they accept the role.
Week 2: policy and objectives. Draft a short top-level policy with the four required commitments. Set two to five measurable security objectives with owners. Have top management approve both, with dates.
Week 3: roles. Appoint the ISMS manager in writing, build the RACI matrix and update the org chart. Communicate the roles and keep the record.
Week 4: evidence of leadership. Hold a management review with real inputs and recorded decisions, including any budget or staffing choices. Publish the policy and collect acknowledgements.
Then walk through the table above and check each cell has a dated artifact behind it.
Budget the leadership effort, not just the tooling
Leadership work takes executive time, and that is a real cost. Review meetings, approvals and interviews all come out of leaders’ calendars, and the effort grows with company size and with how mature your security practices already are. Our ISO 27001 cost calculator estimates implementation cost and effort by company size, industry and security maturity, so leaders see the full picture before they commit resources under 5.1.
Where our calculator and assessment fit
We built ISMS Calculator for teams who need to plan ISO 27001 with numbers. You can run the first calculation without signing up, edit the assumptions, compare benchmarks for your industry and save several estimates side by side. Our readiness assessment covers the four Annex A control themes, and the project planner produces Gantt-style timelines for implementation phases. Start with the free 2-minute readiness check to see where leadership and the other clauses stand today.

Our perspective
Most teams treat Clause 5 as paperwork: write the policy, get a signature, move on. We see it as the budget conversation you have to win. When leaders understand what the ISMS costs in money and hours, they commit with open eyes, and that is the commitment an auditor can see.
That is why we put the estimate first. A leader who has seen a range for their size and industry, and who has edited the assumptions, can explain the budget line when asked. A leader who signed a policy without that picture usually cannot.
Our approach is to make the numbers traceable and editable, so top management can challenge them, approve them and show the decision trail. Leadership then becomes a set of recorded choices rather than a statement of intent.
Martin
FAQ
Is Clause 5 the same in ISO 27001:2013 and 2022?
The structure is the same: leadership and commitment, policy, and roles. The 2022 edition added an explicit requirement in 5.3 to communicate roles, responsibilities and authorities within the organization. If you certified under the 2013 edition, check that communication is documented.
Can the CISO or IT manager satisfy Clause 5.1 on their own?
No. The requirement addresses top management, and auditors expect to see those people involved. The CISO can prepare materials and run the ISMS day to day, but leaders must approve, resource and review. Delegated tasks are fine, as accountability stays with top management.
What evidence is the minimum for Clause 5?
Plan for a dated policy approved by named leaders, proof it was communicated, a documented appointment for ISMS responsibility, a RACI or role descriptions, and management review minutes with decisions and resource commitments. Add budget approvals to show that resources were provided.
How often should top management review the ISMS?
At planned intervals, and many auditors expect at least once a year. A review older than twelve months is a risk before an external audit, so schedule a new one in advance and record real decisions, not just attendance.
Sources
- DeployOpen: ISO 27001 leadership requirements
- Enable-ISO: 5.1 Leadership and commitment
- olivLaw: Clause 5 and leadership
- SecAware ISMS implementation guidelines
- ISO/IEC 27001:2022 standard text (policy requirements)
- ISO/IEC 27001:2022 standard text (roles requirements)
- Audit Workshop: Auditing leadership under Clause 5
- CertPro: ISO 27001 gap analysis
- GSDC: 100 common non-conformities in ISO 27001 audits
- Cliffside: ISO 27001 internal audit checklist
- URM Consulting: Clause 5.1 explained
- NQA: ISO 27001:2022 gap guide