← All posts Practice

ISO 27001: Critical success factors

Getting real value, starting from day one

Tom Whipp · 31 October 2026 · 8 min read

Good security management is risk management

Every hire, supplier contract and system change is a risk decision. Your leadership team already makes these decisions every day; it's the core of their job. Good management is risk management.

ISO 27001 builds on that. It simply asks you to make those decisions visibly, consistently and on the record, then check whether they're working and improve them over time. Done well, the result is better decisions and fewer unpleasant surprises. The certificate is a useful way of showing customers that, but most of the benefit shows up in how the business runs day to day.

That's worth holding onto from the start, because it shapes everything else about how you implement the standard.

What the auditor is really looking at

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. That means they own the risk decisions, back the work with resource, and know where the gaps are. Don't underestimate the importance of seeing some emotional connection to the programme from these key people — an implicit part of any assessment is culture, which flows from your leadership.

In a more tangible sense, ISO 27001 is about accountability for decision making. The standard assesses two kinds of evidence of that.

Management activities — things that happen regularly and leave a record. In most organisations these will be split between existing management meetings and, most likely, a new security forum to deal with more detailed issues. It's important to show both, through agendas and minutes, where the following are happening:

  • Leadership setting direction and providing resource (5.1)
  • Assessing risk, at planned intervals and when things change (6.1.2, 8.2)
  • Deciding how to treat each risk, with risk owners approving the plan and accepting what's left (6.1.3, 8.3)
  • Setting objectives and tracking progress against them (6.2)
  • Building competence and awareness across the organisation (7.2, 7.3)
  • Monitoring and measuring whether controls work (9.1)
  • Running internal audits (9.2)
  • Reviewing the whole system at management level (9.3)
  • Learning from things that go wrong and fixing the causes (10.1, 10.2)

Foundational ISMS documents — away from the meetings, there are a few foundational documents that need to be in place. This isn't the full list of what the standard asks you to document: the activities above also need records, such as audit results, management review minutes and corrective actions.

  • The scope of the management system (4.3)
  • The information security policy (5.2)
  • How you assess and treat risk (6.1.2, 6.1.3)
  • The risk treatment plan (6.1.3)
  • The Statement of Applicability (6.1.3)
  • Your information security objectives (6.2)

In my experience, while the auditor may spend most of their time reviewing controls, they are also influenced by their impression of your culture. Problems identified within a control review are viewed very differently if the auditor is convinced that your leadership will take effective action — it'll still go in the report, but is more likely to be viewed as part of a normal management cycle rather than a point of failure.

That's why management commitment comes first. Before scope, risk assessment or controls, your leadership needs to understand what they're signing up to and why. Get that conversation right and everything that follows builds on solid ground.

Why that surprises people

Most security frameworks are control-centric. For example, Cyber Essentials (UK), the Essential Eight (Australia) and PCI DSS each set out which controls to run, and the assessment checks the scope is complete and that the controls are in place.

ISO 27001 is different. You certify against the requirements in the main body of the standard, clauses 4 to 10, which are surprisingly short and describe a management system. The same document also contains Annex A, which in the current version lists 93 controls. That's what most people focus on, as it's a much larger volume of paper, but the standard itself titles it a controls reference. There's no requirement to select your controls from it. The requirement is to compare the controls you do run against it, and record that mapping in your Statement of Applicability.

Your controls can come from anywhere: another framework, your existing enterprise controls, or simply what your business needs. The comparison is there so nothing obvious is missed. If you genuinely don't need a control for some reason, the obligation is to say why — not invent a reason to include it. The standard also expects you to add controls of your own wherever your risks call for them.

So think of Annex A as a cross-check you run your own controls against, rather than a list to work through from the top.

Two further elements sit at the centre of ISO 27001 and fall outside a control-centric view.

  • Events. In most control-centric frameworks a security event gets handled much like a break-fix IT incident: fix it, restore service, close the ticket. ISO 27001 asks how you are learning from it. What does this tell us about our risks? Did a control fail, or was it the right control in the first place? That learning feeds back into the risk register and up to leadership.
  • Action plans. Every organisation has gaps, and the standard is realistic about that. You can be certified while carrying known risks and unfinished improvements, as long as they're understood, owned and on an approved plan. Failures to meet the standard's own requirements, which auditors call nonconformities, are treated more strictly; the risk improvement plan guide explains how. What matters is knowing where you stand and improving, and the credibility of your action (improvement) plan is critical to passing certification.

Put those two together and you get something that keeps moving: events and gaps come in, decisions and actions go out, and the picture improves each time round.

An expression of the organisation

Because you can keep the controls you already run and map them, a well-built ISMS describes how your organisation actually operates.

You can usually tell when an ISMS is connected to how the business really runs. Leadership use it to make decisions, the risk register reflects what they genuinely worry about, the documents describe what people actually do, and the audit becomes a by-product of normal work. If it drifts away from that, it tends to become a parallel process kept up for the auditor, and the certificate starts to feel like a cost to renew each year.

I've seen GRC work as a genuine performance tool, and I've seen it run as a pure cost exercise. In my experience, culture has a lot more to do with which one you end up with than the implementation does.

How it fits together

The ISO 27001 management system A management forum sits at the top. Risk analysis, the risk register, security events, metrics, and assurance and audit all feed into it. The forum produces a risk improvement plan and drives control selection, the Statement of Applicability, policies and standards, and control operation, whose results feed back through metrics. Everything sits within an agreed ISMS scope and rests on management commitment. Management Forum Management Forum Risk Improvement Plan Risk Improvement Plan Scope ISMS Scope Control Selection and SoA SoA Control Selection and SoA Control Selection Risk Analysis and Risk Register Risk Register Risk Analysis and Risk Register Risk Analysis Security Events Security Events Assurance and Audit Assurance + Audit Policies and Standards Policies + Standards Control Operation Control Operation Control Operation Control Operation Control Operation Control Operation Control Operation Control Operation Metrics Metrics Management Commitment (culture, resource, budget)
Scroll sideways to see the whole diagram. The ISO 27001 management system. Elements link to their detail pages as each one is published.

Leadership sits at the top, in a management forum, and everything flows to it:

The forum makes decisions and records them in a risk improvement plan. That drives control selection and the Statement of Applicability, and then the day-to-day operation of controls, guided by policies and standards. The results feed back into metrics and events, and the loop turns again.

All of this sits within an agreed scope, and rests on management commitment: culture, resource and budget.

Bootstrapping the cycle

The first time through, you're bootstrapping a cycle: building just enough of each part to get the loop turning, then improving it on every pass. Plan, Do, Check, Act is a useful lens, and the standard's structure follows it closely. Real implementations overlap more than any plan suggests, and some activities, like capturing events, can start on day one. The bootstrapping guide covers each stage in detail.

Commit. Before the loop starts, brief your leadership on what they're signing up to and why. Agree a sponsor, set up the management 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.

Plan. Agree how you'll assess risk. Then sit down with managers, pen and paper, and ask what they're worried about. Ten to twenty well-worded risks is a good starting point for a first workshop; the final number follows your scope. Describe the controls you already run as what happens, when, where, who does it and why, and say what evidence each leaves behind. Map them to Annex A in your Statement of Applicability, and write policies that match how people actually work. Don't rush this stage: shortcuts here come back as cost in Check and Act.

Do. Operational teams run the controls as part of normal work, file evidence as they go, and capture events and what they teach you.

Check. Gather the metrics the forum needs, run an internal audit and a management review. Before the main certification audit, the ISMS needs to have run long enough to produce credible evidence, and certification bodies will normally expect that to include at least one of each.

Act. The forum turns what Check found into decisions and an updated improvement plan, and the next pass through Plan starts from there.

Then turn the loop. Each cycle is a chance to refine how things work. The organisations that get real value from ISO 27001 treat it as a way of running the business, with each audit confirming progress.

Further reading


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.