OneNym.idDiscuss deployment
English

THE BOARDROOM FIREWALL / Appendix D

Plain-Language Glossary

Security briefings, vendor proposals and insurance documents are full of terms that leaders are expected to understand. This appendix explains around fifty of them in language that makes sense on first reading.

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

What the glossary is for

The glossary covers the terms a leader is most likely to meet in security briefings, vendor proposals, insurance documents and the press. Each definition is meant to be understood without needing a second glossary, and many borrow the building metaphor used throughout the book: firewalls as a guarded perimeter wall, administrator accounts as the master key, patches as routine repairs to a lock.

The definitions are deliberately simple. Specialists will know the finer distinctions, but a leader's aim is narrower: recognise the term, understand what it is for, and know what to ask next. Readers who want more depth are pointed to the expert notes in the main chapters and to the standards in Appendix E.

A few sample entries

Several entries are especially useful for board conversations. Multi-factor authentication is described as one of the most effective and affordable protections a company can adopt. A backup is said to be only as good as the last successful test of restoring from it. Compliance is necessary but not the same as being secure, in the way that passing a building inspection does not mean a fire can never start.

Recovery Point Objective and Recovery Time Objective are explained side by side: the first is how much data, measured in time, the business can afford to lose; the second is how long a system can be down before the damage becomes unacceptable. Residual risk is the risk left after protections are in place, which never reaches zero and must be accepted consciously. The shared responsibility model is pictured as a landlord who secures the building while each tenant still locks their own flat.

When a term is not on the list

Security vocabulary grows every year, and vendors often give old ideas new names. The book suggests a simple response to unfamiliar jargon: ask for a one-sentence explanation and for the risk it reduces. If the answer takes several minutes and introduces more jargon, either the idea matters less than its name suggests, or the speaker does not yet understand it well enough to explain it simply. In the book's view, plain language is a test of clear thinking, not a favour to non-experts.

KEY POINTS

Key points

  • Use the glossary to recognise a term, understand its purpose and decide what to ask next.
  • Remember that compliance and security are not the same thing.
  • Treat a backup as only as reliable as its last successful restore test.
  • Ask for any unfamiliar term in one sentence, along with the risk it reduces.
  • Be cautious when an explanation needs several minutes and more jargon.

QUESTIONS

Common questions

What is the difference between RPO and RTO?
The Recovery Point Objective (RPO) is the maximum amount of data, measured in time, that the business can afford to lose; with an RPO of four hours, backups are needed at least every four hours. The Recovery Time Objective (RTO) is the maximum time a system can be unavailable before the damage becomes unacceptable, and it tells IT how fast recovery must be.
What is the shared responsibility model in cloud security?
The shared responsibility model is the division of security duties between a cloud provider and its customer. Moving to the cloud does not hand over all of security; part of it stays with the customer. The Boardroom Firewall compares it to a landlord who secures the building while each tenant must still lock their own flat.
What is business email compromise?
Business email compromise (BEC) is a fraud in which criminals impersonate a trusted person, often a senior executive or a supplier, by email. The aim is to trick staff into sending money or sensitive information. It relies on manipulating people rather than breaking technology.
What is zero trust in simple terms?
Zero trust is an approach to security in which no user or device is trusted automatically just because it is inside the company network; every request is checked. It is like asking for a pass at every door in a building, not only at the front gate.
What is the difference between a penetration test and a vulnerability scan?
A vulnerability scan is an automated check of systems for known weaknesses; it is quick and broad but not deep. A penetration test is an authorised, controlled attempt by hired specialists to find weaknesses before real attackers do, like a commissioned inspection by people who think like burglars.