OneNym.idDiscuss deployment
English

THE HARDENED STACK / Appendix E

Plain-Language Glossary

Security writing is full of acronyms that are used as if everyone already knows them. This appendix defines the terms used throughout the book in one plain sentence each, so readers can keep moving.

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

Why a plain-language glossary

The author argues that the field's unexplained vocabulary quietly keeps newcomers out and makes capable people feel behind when they simply have not been told what the words mean. The glossary gives a short definition for each recurring term and points back to the chapter that treats it in depth. It is meant for quick orientation, not as a replacement for the chapters.

What it covers

The entries span identity (MFA, passkey, conditional access, PIM, PAM, JML, break-glass account, OAuth, OIDC, workload identity), endpoints (EDR, LAPS, MDM, golden image, tamper protection), network (segmentation, microsegmentation, ZTNA, lateral movement), cloud (CSPM, guardrail, tenant, shared responsibility), email (SPF, DKIM, DMARC), vulnerability management (CVE, CVSS, EPSS, KEV, SBOM), recovery (immutable backup, RPO, RTO) and incident response (IOC, containment, eradication). Frameworks such as the NIST CSF appear as well.

A few examples

Several definitions carry a practical point. An access key is described as convenient but dangerous because it does not expire by itself and leaks easily. The JML entry notes that the leaver step is where access most often lingers. Shared responsibility is defined as the cloud model in which the provider secures the infrastructure and the customer secures configuration, identities and data, with the boundary between them being where most cloud breaches happen. The NIST CSF entry lists six functions, Govern, Identify, Protect, Detect, Respond and Recover, noting that Govern was added in version 2.0 in 2024.

How to use it

The glossary works best as a companion while reading the chapters or vendor documentation: look up a term, get the short version, and carry on. When a term bears on a real decision, such as how to prioritise patches or how far to trust a remote connection, the author asks readers to go back to the chapter where the mechanism and trade-offs are explained, because a one-line definition cannot carry that detail.

KEY POINTS

Key points

  • Share the glossary with new IT staff so unfamiliar terms do not slow them down.
  • Treat long-lived access keys as a risk and replace them with short-lived credentials where possible.
  • Check the leaver step of your JML process, where access most often lingers.
  • Prioritise patches with EPSS and the KEV catalogue alongside CVSS.
  • Follow a term back to its chapter whenever it affects a real decision.

QUESTIONS

Common questions

What is the difference between CVSS, EPSS and KEV?
CVSS is a 0-10 score of how severe a vulnerability is in principle. EPSS estimates the probability that a vulnerability will actually be exploited in the near future. KEV is a CISA catalogue of vulnerabilities confirmed to be exploited in the wild. Used together they support much better patch prioritisation than CVSS alone.
What is a break-glass account?
A break-glass account is an emergency administrator account used only when normal administrative access fails. Its credentials are stored offline, and any use of it should trigger an alert so that it cannot be misused quietly.
What does shared responsibility mean in the cloud?
Shared responsibility is the cloud model in which the provider secures the underlying infrastructure and the customer secures its own configuration, identities and data. The Hardened Stack notes that the line between the two is where most cloud breaches happen.
What is the difference between RPO and RTO?
RPO, the recovery point objective, is how much data, measured in time, an organisation can afford to lose in a disaster, and it drives backup frequency. RTO, the recovery time objective, is how quickly a system must be running again, and it drives the recovery design and its cost.
What is ZTNA and how is it different from a VPN?
ZTNA, Zero Trust Network Access, is remote access that takes identity and context into account and grants reach only to specific applications. A traditional VPN, by contrast, gives reach to the whole network. The Hardened Stack recommends moving remote access from flat VPN toward identity-aware access where possible and requiring MFA on any remote access that remains.