Implementation Project
/
Step 3

Implementation Project

var(--variable-QsTa4u5mL)

How to Win Management Support for ISO 27001

var(--variable-Cl6cRG5u3)

Written by

Aron Lange

Published

Nov 6, 2026

Implementation Project

var(--variable-QsTa4u5mL)

How to Win Management Support for ISO 27001

var(--variable-Cl6cRG5u3)

Written by

Aron Lange

Published

Nov 6, 2026

You know your scope, and after the gap analysis in Step 2, you know where you stand. But so far, nobody has agreed to pay for closing the gaps. That’s Step 3: the support of top management.

And support doesn’t mean a friendly nod in a meeting. It means a real commitment: the budget, the people and the authority to run the project. Without it, your ISMS becomes a side project of IT, and side projects lose every fight for time and money.

Step 3 sits right after the gap analysis for a reason: now you can show top management what they’re committing to. And it comes before the information security policy in Step 4, because the policy is top management’s own document, and they’ll only sign it if they’re on board.

What ISO 27001 expects from top management

Clause 5.1 asks top management to demonstrate leadership and commitment with respect to the ISMS. The important word is demonstrate. It isn’t enough that the CEO supports the project. It has to be visible, and in an audit, it has to be shown.

Who is top management? The person or group of people who runs the organization at the highest level, typically the management board, the CEO or a general manager. If your ISMS covers only part of the organization, it’s the people who run that part. And watch out in your own organization: sometimes the person everybody calls “the boss” isn’t the one who signs the budget. Find out who really decides before you ask for commitment.

Clause 5.1 then lists eight ways top management shows its commitment. In short: it makes sure the policy and objectives exist and fit the strategy, builds the ISMS into the organization’s processes, provides the resources, explains why information security matters, makes sure the ISMS achieves what it should, directs and supports the people who contribute, promotes continual improvement, and supports the other managers in their own areas.

Clause 7.1 adds the resources, and resources means more than money: people and their time, a budget for tools, external support and the certification audits, the infrastructure your controls need, and expertise, inside or outside the organization.

Commitment you can show: the approved project charter in Step 3, the approved information security policy in Step 4, decisions on risks in Step 8 and the management review in Step 10

So what shows commitment? Not a speech at the kickoff. Decisions do: the approved project charter here in Step 3, the signed policy in Step 4, the decisions on residual risks in Step 8 and the management review in Step 10.

What top management can’t delegate

A question I get a lot: what can top management delegate? Basically, the work. Someone else writes the policy, runs the risk assessment and manages the ISMS day to day. What they can’t delegate is the accountability: approving the policy and the objectives, providing the resources, and answering for the ISMS.

Delegate or keep: top management can delegate writing the policy, running the risk assessment and managing the ISMS, but not approving the policy and objectives, providing the resources and answering for the ISMS

So the CEO doesn’t have to know how multi-factor authentication works. But they have to know that it’s their ISMS.

1. Build the business case

Top management won’t commit to something they don’t understand. So before you ask for a signature, you prepare two documents: the business case and the project charter. ISO 27001 requires neither of them. But they’re how you turn “yes, sounds important” into a budget, people and a mandate.

A business case compares two things: what the ISMS costs, and what it costs not to have one.

What’s at stake: doing nothing can cost customers, fines under laws like NIS2 and incidents; the ISMS takes budget and people and brings contracts kept and fewer incidents

Start with doing nothing. Maybe a key customer requires ISO 27001 for the next contract. Maybe a law like NIS2 applies to you, with fines and with management being held accountable. And then there are the incidents you’ve already had, and what they cost. On the other side, the ISMS: a budget for tools, audits and external support, and time from IT and the departments. And the benefits: the contracts you keep and the incidents you avoid.

A good business case follows a simple order. It starts with the business need: why now? A customer requirement, a law, an incident. Then the options, and always include doing nothing, because that’s the option top management compares you with. Then the benefits and the costs. Put a number on them wherever you can. The costs come straight from your gap analysis report, and that’s exactly why you did Step 2. And at the end, the decision you’re asking for.

Top management makes this kind of decision every day. Your job is to give them the numbers in the language they use: revenue, costs and risks, not firewalls and controls. And keep it short. I would say, if it doesn’t fit on two or three pages, it’s typically too long for the people who have to read it.

2. Write the project charter

Once the business case is approved, you write the project charter. The business case answers the question: should we do this? The project charter answers: how do we do it, and who’s in charge?

What a project charter does: it authorizes the project, appoints the people and commits the budget and resources

It does three things. It authorizes the project, so it officially exists, with a clear purpose and objectives. It appoints the people: the sponsor from top management, the project lead and the team. And it commits the budget and the resources.

A charter typically contains an overview with the sponsor, the project lead, the target date and the approved budget. Then the objectives, each with a success criterion, so you know when you’re done. The milestones, taken from the project plan. And the project organization: the sponsor, a steering committee, the project lead, the team, and the person with overall responsibility for the ISMS. Further down come the budget, the project risks and how the project communicates.

When top management approves the charter with its budget and its team, that’s clause 5.1 and clause 7.1 in one signature. It’s typically the first piece of evidence you show an auditor for top management’s commitment.

3. Set up the governance process

The charter covers the project. But the ISMS runs long after the project, so top management needs a place to keep steering it. That’s the information security governance process. It follows the model of ISO/IEC 27014, governance of information security: top management evaluates, directs, monitors and communicates.

Making it yours means three decisions: who’s in it, how often they meet, and where the decisions are recorded. Typically, that’s a steering committee or the management board itself. The process does its first work right here in Step 3, when top management assigns the roles. Later, it’s where the policy is approved in Step 4 and the residual risks are accepted in Step 8.

4. Assign and communicate the roles

Ask five people in an organization who’s responsible for information security, and you might get five different answers. Or just: “IT, I guess.” Clause 5.3 makes sure there’s one clear answer. Top management has to make sure that the roles relevant to information security are assigned to people, and that everyone knows about them. Two verbs: assigned, and communicated. A role nobody knows about doesn’t help anyone.

Clause 5.3 names two responsibilities explicitly: making sure the ISMS conforms to ISO 27001, and reporting on its performance to top management. Typically, both go to one person: the CISO, the information security officer or the ISMS manager. The title doesn’t matter. What matters is that everyone knows who it is, and that this person has the authority to do the job.

And that brings us to the reporting line.

Two reporting lines: on the left, the CISO reports directly to top management; on the right, the CISO reports to the CIO, with a committee as a bridge to top management

ISO 27001 doesn’t say where this role has to sit. But think about it: if the CISO reports to the head of IT, who reports on IT’s security gaps? A committee can help as a bridge. But I would say, a direct line to top management is typically the cleaner solution.

For the other roles, from risk owners to asset owners, a simple RACI matrix helps. For every activity, you decide who’s responsible (does the work), accountable (answers for it), consulted before and informed after. One rule: there’s exactly one A per activity. If two people are accountable, typically nobody is.

When you assign roles, consider three things. Skills: people need the competence for their role, and if they don’t have it yet, that’s what Step 9 is for. Segregation of duties: the person who requests access shouldn’t be the one who approves it, and not the one who sets it up either. And conflicts of interest: nobody should approve or audit their own work. A head of IT who’s also responsible for the ISMS is, let’s say, in an awkward position when the internal audit finds gaps in IT.

Then communicate. Roles that only exist in a spreadsheet don’t work. Write the security responsibilities into the job descriptions, put the roles into the information security policy and the organization chart, and have top management announce them. When the CEO says “this is our ISMS manager, and here’s why it matters”, people listen differently than when IT sends an email.

At Barvello: €1.02 million, approved with one condition

Barvello Coffee Systems is the fictional company of our ISO 27001 Lead Implementer course: a family-owned maker of professional coffee machines in Munich, with about 500 employees and its own cloud platform, Barvello Connect. In Step 2, project lead Nadia Berger found that Barvello meets 14 percent of the requirements. On 25 January, she presents the gap analysis to the management board. And Thomas Weber, the CFO, says what you’d probably expect: “We’ve been in business for almost 60 years without an ISMS. I’m not against it, but I want to see what we get for the money.”

The dates were set long ago. The advisory board meets on 3 February, and any investment above one million euros needs its approval. So Nadia has four days for the business case, and she writes it together with Thomas Weber, because the CFO’s numbers are the ones the advisory board trusts.

The business need fits in one paragraph. Ovena, Barvello’s largest customer with €21.2 million of revenue a year, requires the certificate for the renewal of its framework agreement. NIS2 makes Barvello an important entity. And since 1 January, the cyber insurer has excluded ransomware until its six conditions are met.

Then the options: doing nothing, meeting only the insurer’s conditions, or the full ISMS. The second option costs about €400,000, but without a certificate, Ovena is still gone. Nadia doesn’t build a straw man. She shows why it isn’t enough.

Then the numbers, in euros wherever possible:

Item

Amount

Revenue at stake

€21.2 million a year from Ovena

NIS2 fines

Up to €7 million

Incidents already paid for

€3.1 million of revenue delayed by ransomware at the grinder supplier, €46,800 lost to fake bank details, a €38,000 service credit after a certificate outage at Connect

Costs in 2027

€1.02 million, from the gap analysis

Costs from 2028

About €380,000 a year

Put next to each other, the decision isn’t that hard anymore. That’s the point of a business case. On 3 February, the advisory board approves the budget, with one condition: Nadia reports to the advisory board every quarter.

The charter takes her two days, because most of it already exists. Julia Keller, the CEO, is the sponsor. The objectives each have a success criterion: the certificate by 30 September with no major nonconformity, Ovena’s renewal signed by the end of 2027, the insurer’s six conditions met by 30 June. The steering committee is the management board, Nadia and Anna Schulz, because the ISMS will build on the ISO 9001 system. And the project risks are honest: Nadia and Lukas Meier, who works on the project half his time, can’t do everything themselves, there are no changes to production from September to November, and the works council has to agree to tools like EDR and central logging. So Nadia plans the works agreements for March, not for the week before the audit.

On 8 February, Julia Keller approves the charter for the management board, after Thomas Weber has reviewed it himself. That signature is Barvello’s first evidence for clauses 5.1 and 7.1.

Barvello’s reporting line: Nadia Berger and the ISMS project report to the CEO, Julia Keller, while IT and finance report to the CFO and production to the COO

The next day, the steering committee meets for the first time. It approves the governance process, monthly during the project and quarterly afterwards, and makes its first decision: Nadia has the overall responsibility for the ISMS, and she reports to the CEO, not to IT. IT reports to the CFO, and IT is where many of the gaps are. With a direct line to Julia Keller, Nadia can report on the ISMS without going through the department whose gaps she’s reporting on.

On 10 February, Julia announces it to all staff, by email, on the intranet and in the shift briefings. Management support is obtained, and with more than a nod: an approved budget, a signed charter, a steering committee that meets every month and a person in charge.

Watch the full lecture above. It’s “Business Case and Project Charter” from the course, with what goes into each document and how they lead to the approval.

Your turn: Step 3 in the project plan

In the project plan of our ISO 27001 Toolkit, Step 3 is seven tasks and one milestone:

ID

Task

Clause

26

Outline business case
Deliverable: Business case



27

Obtain approval for business case



28

Develop project charter
Deliverable: Project charter



29

Obtain approval for project charter

5.1, 7.1

30

Establish information security governance process

5.1, 4.4, 6.2

31

Assign overall responsibility for the ISMS

5.3

32

Communicate roles, responsibilities and authorities for the ISMS

5.3

33

Milestone: Management support is obtained



At the end of Step 3, you have three deliverables, and the toolkit has a template for each: the governance process (PRO-001), the business case (REC-006) and the project charter (REC-007).

The three Step 3 deliverables: the governance process (PRO-001), the business case (REC-006) and the project charter (REC-007), all determined by the organization

None of them is required as documented information. But when an auditor asks how top management demonstrates its commitment, an approved charter and a working governance process are typically the first things you show. You’re done with Step 3 when you have more than a nod in a meeting: an approved charter, a person in charge and a governance process that runs.

From the auditor’s chair

When I audit clause 5.1, I don’t look for a quote from the CEO in the policy. I look for evidence that top management actually decides: an approved charter, a signed policy, decisions on risks, the minutes of a management review.

And auditors typically talk to top management directly. What are the objectives of your ISMS? What did you decide in the last management review? It usually becomes clear very quickly whether the answers come from the person or from a briefing note.

Frequently asked questions

Does ISO 27001 require a business case or a project charter?

No. Neither is required as documented information. But they’re how you get the budget and the mandate, and an approved charter is strong evidence for clauses 5.1 and 7.1.

Who counts as top management?

The person or group of people who runs the organization at the highest level, typically the management board, the CEO or a general manager. If your ISMS covers only part of the organization, it’s the people who run that part.

Can top management delegate the ISMS?

The work, yes: writing the policy, running the risk assessment, managing the ISMS day to day. The accountability, no: approving the policy and objectives, providing the resources and answering for the ISMS stay with top management.

Who should the CISO report to?

ISO 27001 doesn’t say. But if the person responsible for the ISMS reports to the head of IT, they have to report on IT’s gaps through IT. A direct line to top management is typically the cleaner solution.

Do we need a steering committee?

Not necessarily. You need a place where top management steers the ISMS and its decisions are recorded. In smaller organizations, that’s often the management board itself.

Step 3 in the course.

Watch Barvello get its budget.

6 lectures (26 min) show you how to build the business case and the project charter, and what clauses 5.1 and 5.3 require from top management. Then you watch Nadia win over Barvello’s CFO and the advisory board. Your turn: 7 tasks in the project plan and the templates for the business case, the charter and the governance process.

Business Case and Project Charter

03:38

Case Study: Barvello’s Management Support

06:11

Template: Business Case

REC-006

Template: Project Charter

REC-007

With management support obtained, you’re ready for Step 4: the information security policy, which is top management’s own document.


€690

/ year

incl. 19% VAT · billed yearly

12-hour Video Course

ISO 27001 Toolkit

Practice Exam

Weekly Live Q&A

Exam Voucher + Free Retake

Bundle

Study Guide

Bundle

€690

/ year

incl. 19% VAT · billed yearly

12-hour Video Course

ISO 27001 Toolkit

Practice Exam

Weekly Live Q&A

Exam Voucher + Free Retake

Bundle

Study Guide

Bundle