OneNym.idDiscuss deployment
English

THE BOARDROOM FIREWALL / Appendix E

Further Reading and Standards

Leaders do not need to read security standards cover to cover, but they should recognise the names and know what each one does and does not prove. This appendix describes the frameworks, guidance and public resources most worth knowing.

This page summarises the chapter. The full text is in the book.

How a leader should use standards

The appendix deliberately gives no web addresses, because addresses and versions change; instead it describes each resource well enough to find the current edition with a simple search. The book compares standards to building codes and fire-safety guidance: they hold a great deal of hard-won experience, but they make nothing safe on their own. When a security leader says the company aligns to one framework and is certified to another, the useful follow-up is to ask what that tells the board and what it does not.

The core frameworks

The NIST Cybersecurity Framework is described as probably the most widely used way to organise and discuss cyber risk. Version 2.0, released in 2024, has six functions: Govern, Identify, Protect, Detect, Respond and Recover. The new Govern function reflects the book's central point that security is a leadership responsibility. It is free, voluntary and a good shared vocabulary for a board and its security team.

ISO/IEC 27001 differs in that organisations can be formally certified against it. Certification shows a structured, documented and regularly reviewed management system, but not that every control is strong; the key question is always what the certificate covers. The CIS Critical Security Controls offer a prioritised list of practical actions, especially helpful for smaller companies deciding where to start. Other schemes, such as the payment card standard and SOC 2 assurance reports, apply depending on sector and country.

Guidance for boards and regulators to know

Some of the most useful material is written for directors: board toolkits from national cyber security agencies, cyber oversight handbooks from director institutes, and disclosure rules from securities regulators for listed companies. Data protection authorities, including Japan's Personal Information Protection Commission and the regulators that enforce the GDPR in Europe and the UK, publish guidance on what counts as a reportable breach. Because sector and regional rules differ and change often, the book's practical advice is to ask the general counsel for a one-page summary of which rules apply, where, and with what deadlines.

Incidents, measurement and peers

The appendix also points to incident handling and ransomware guidance from national agencies, contact routes to law enforcement, and FAIR, an open method for expressing cyber risk in financial terms using ranges and probabilities. Industry reports on breach costs are useful for context, but they are often based on surveys or a vendor's own customers, so they should prompt questions rather than set budgets. Sector information-sharing groups and peer leaders who have lived through incidents are named as valuable sources too. Above all, a leader does not need to keep up personally; someone in the organisation should, and the board should ask them once or twice a year what has changed.

KEY POINTS

Key points

  • Know which framework your company follows, and why.
  • When you hear about a certification, ask what is in scope and what it does not prove.
  • Ask the general counsel for a one-page summary of the security and breach-reporting rules that apply to you.
  • Find out whether your industry has an information-sharing group and whether you belong.
  • Once or twice a year, ask the person tracking standards what has changed that the board should know.

QUESTIONS

Common questions

What is the NIST Cybersecurity Framework 2.0?
The NIST Cybersecurity Framework is a free, voluntary framework from the US National Institute of Standards and Technology for organising and communicating about cyber risk. Version 2.0, released in 2024, groups security into six functions: Govern, Identify, Protect, Detect, Respond and Recover. The addition of Govern reflects the view that security is a leadership responsibility, not only a technical one.
What does ISO 27001 certification actually prove?
ISO/IEC 27001 certification shows that an organisation has a structured, documented and regularly reviewed system for managing information security risk, checked by an accredited auditor. It does not by itself guarantee that every control is strong, or that the certified scope covers the parts of the business that matter most. Boards should always ask what is in scope.
Which cyber security framework should a small company start with?
The Boardroom Firewall points to the CIS Critical Security Controls as particularly helpful for smaller companies wondering where to start. They are a prioritised list of specific actions against the most common attacks, grouped by organisation size and resources. If the NIST framework is the map, the CIS Controls are the first roads to build.
How can a board keep track of the cyber regulations that apply to the company?
Because sector and regional rules change frequently and differ from place to place, the practical step is to ask the general counsel or compliance lead for a short, current summary. It should say which security and breach-reporting rules apply to the company, in which countries, and with what deadlines.
Can industry breach cost reports be used to set a security budget?
They are useful for context and conversation, but should be read with care. Many are based on surveys or on a vendor's own customers, and their averages may not fit a company of your size or sector. The book advises using them to ask questions, not to set budgets.