Why frameworks exist
The book compares security frameworks to building codes: collected experience, much of it learned after things went wrong, that tells you what a safe building needs without designing it for you. Without such a structure, companies tend to fund whatever is in the news or whatever the last auditor mentioned, and important areas such as detecting an intruder or recovering from a disaster can go untouched for years.
A framework helps in four ways. It shows the whole field so gaps become visible. It gives the board, auditors, regulators, insurers and customers a shared vocabulary. It turns progress into something measurable, from where you are today to where you want to be. And it signals that the company works from tested practice rather than an approach it invented. What a framework does not provide is judgement. Which systems matter most, how much to spend and which risks to accept remain business decisions.
NIST CSF 2.0: six functions on one page
The NIST Cybersecurity Framework, from the US National Institute of Standards and Technology, is used by organisations of every size around the world. First published in 2014 with critical infrastructure in mind, version 2.0 arrived in 2024, widened its audience and added a Govern function. Its six functions read like a short story: Govern decides how the building will be looked after, Identify works out what is in it, Protect keeps intruders out, Detect notices when someone gets in, Respond deals with them, and Recover puts things right. Govern sits at the centre because it shapes the other five.
The framework describes outcomes rather than products, so it stays relevant as technology changes. Two ideas are especially useful to boards. Profiles describe the current position and the target, and the gap between them becomes the roadmap. Tiers describe how rigorous and integrated the approach to risk is; they are meant to be chosen according to risk, not climbed by everyone. In the book's example, the security head of the fictional Meridian Foods replaces a forty-page control spreadsheet with a single page of six rows, and the audit committee immediately sees that Detect and Recover are the weak spots.
ISO 27001 and what certification really signals
ISO/IEC 27001 is an international standard built around an information security management system: an organised way of setting objectives, assigning responsibility, managing risk, checking results and improving. It combines management requirements, such as leadership commitment, risk assessment, internal audit and management review, with an annex of reference controls that a company selects and justifies. Its distinctive feature is certification by an accredited body, usually valid for three years with surveillance audits in between.
Certification shows discipline: that a functioning management system exists within a defined scope and an independent auditor has checked it. It does not show that the company is secure, since certified organisations are breached. The scope may cover only one site or product line, the audit is a sample at a point in time, and certification bodies vary in rigour. Leaders should always ask to see the scope statement. Whether to pursue certification is a business decision, worthwhile when customers ask for it or the discipline genuinely improves how security is run.
The CIS Controls and using frameworks together
The CIS Critical Security Controls, published by the non-profit Center for Internet Security, are the most concrete of the three: a prioritised list of safeguards drawn from what works against common attacks. Their implementation groups give smaller companies a clear starting point. The first group, often called essential cyber hygiene, is the minimum every organisation should have; the second and third add safeguards for more complex or exposed environments.
The three frameworks are not rivals. A common pattern is NIST CSF as the board's map, the CIS Controls as the security team's to-do list, and ISO 27001 where customers expect certification. Mappings between them mean work done once usually counts for the others.
Steering rather than drowning, and testing capability
Used badly, a framework becomes a paperwork machine. The book recommends starting from the systems and data whose failure would hurt most, choosing one framework as the spine, reporting to the board on one page, setting targets from risk appetite, turning each significant gap into a funded project with an owner and a date, reassessing about once a year, and keeping documents short enough that people use them.
The chapter ends by separating maturity from capability. Maturity is how documented and repeatable processes are; capability is whether they actually stop, detect and recover from real attacks. A company can have a polished plan that has never been rehearsed, or a skilled team whose knowledge lives only in their heads. Capability is best tested rather than assessed, through tabletop exercises, timed restores from backup, authorised independent testing and short reviews after real incidents. At Meridian, adding a line to the quarterly page showing when each function was last tested in practice soon became the most discussed part of the report.
KEY POINTS
Key points
- Pick one framework as the spine of the security programme and map other requirements to it.
- Ask for a one-page view of the six NIST CSF functions showing current position, target and the biggest gap.
- When relying on an ISO 27001 certificate, yours or a supplier's, read the scope statement first.
- Confirm that the first CIS implementation group, essential cyber hygiene, is fully in place.
- Turn every significant gap into a funded project with an owner, a timeline and a cost.
- Ask when each area was last tested in practice, not only how it scored on paper.
QUESTIONS
Common questions
- Which cybersecurity framework should our company use?
- Most companies benefit from choosing one framework as the spine for board reporting, often the NIST Cybersecurity Framework 2.0, and mapping other requirements to it. The CIS Controls work well as the security team's prioritised to-do list, and ISO 27001 is worth adding where customers or markets expect certification. The frameworks overlap, so work done under one usually counts toward the others.
- Does ISO 27001 certification mean a company is secure?
- No. ISO 27001 certifies that an information security management system exists and operates within a defined scope, and that an independent auditor has checked it. It signals discipline, not invulnerability, and certified organisations still suffer breaches. Always check the scope statement, because a certificate may cover only one site or product line.
- What are the six functions of NIST CSF 2.0?
- NIST CSF 2.0 organises cybersecurity into Govern, Identify, Protect, Detect, Respond and Recover. Govern, added in version 2.0 in 2024, sits at the centre and covers strategy, risk appetite, roles, policy, oversight and supplier risk. Boards can use the six functions to see their current position, their target and the gaps between them on a single page.
- Where should a small company start with cybersecurity?
- A practical starting point is the first implementation group of the CIS Controls, often called essential cyber hygiene. It is the minimum set of safeguards every organisation, however small, should have in place. Once it is fully implemented, the company can decide whether its risks justify moving to the more demanding groups.
- What is the difference between security maturity and capability?
- Maturity describes how well established, documented and repeatable security processes are. Capability is whether those processes actually prevent, detect and recover from the attacks the company is likely to face. A company can score well on maturity with a plan nobody has rehearsed, so capability should be tested through exercises, timed restores, independent testing and lessons from real incidents.