OneNym.idDiscuss deployment
English

THE HARDENED STACK / Preface

Preface

Many small and mid-size organisations have no security team, only one or two IT people who inherited the job on top of everything else. The preface explains how this book is built to help them decide what to do first and get it done.

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

Written for the accidental security owner

The book opens with a familiar picture: an IT administrator who resets passwords, fixes printers and runs a cloud migration, and who also became the de facto security function because nobody else understood how the systems fit together. Phishing incidents, auditor questions and cyber-insurance questionnaires all ended up on the same desk.

The intended reader is not a large security operation with a round-the-clock monitoring centre and a big tooling budget. It is the small team that keeps the whole estate running at a smaller organisation: technical, short on time, and in need of clear priorities rather than theory that never reaches a keyboard.

A defensive field guide, not a catalogue

The scope covers the systems a small IT team actually operates: identity, endpoints, networks, cloud accounts, Microsoft 365, email, the software the organisation builds or customises, data and backups, and logging. The chapters follow the order a time-pressed team would tackle them in: foundations first, then everyday infrastructure, then applications and data, and finally detection and response.

Each chapter explains how a mechanism works before showing commands, so readers can adapt a setting when their environment differs from the example. The book is strictly defensive. It contains no attack tutorials or exploitation walkthroughs; attacks are described only far enough to recognise and stop them, and every command is meant to be run against systems the reader owns and is authorised to inspect.

The author is also clear about what the book is not. It is not an exam guide, a one-off compliance checklist or a product list. Real tools are named, but the principle comes first so that the advice survives product renames and interface changes. Compliance and security overlap without being the same thing, and the book does not pretend a two-person team can do everything. Much of the work is choosing what to do now and what to defer, and being honest about the friction good controls create.

The readers and the fictional company

The preface names its audience: Windows, Microsoft 365 and Intune administrators; cloud and DevOps engineers who know infrastructure as code but were never taught least-privilege IAM; network engineers moving from a flat network towards zero trust; service desk leads who run the joiner-mover-leaver process; and junior admins learning everything at once. Part I is recommended for everyone, while the remaining chapters can be read in whatever order the reader's problems require.

To give the advice a concrete setting, the book follows Meridian Foods, a deliberately ordinary fictional food company of about 450 staff with a head office, two production sites and a distribution centre. It runs Microsoft 365, some Azure and AWS workloads, Active Directory with Entra ID, a loyalty app with around 300,000 members and a trade ordering portal. Its IT team, led by head of IT Tom Brennan and security lead Aiko Tanaka, appears throughout, getting things right and wrong.

How to read the boxes, code and appendices

Four recurring boxes serve different depths. In Plain English restates an idea simply, which also helps when explaining a control to non-technical colleagues. At Meridian shows the team carrying out the chapter's work. For the Experts goes into protocol details, edge cases and trade-offs. Do This Now lists concrete actions for the coming week.

Code samples carry a language label and a comment explaining their intent, and use consistent placeholders such as meridian.example.com and 10.20.0.0/16. Readers are asked to read every line before running it and to prefer reversible changes. All scripts, policies, queries and checklists are also published in a free companion repository organised by chapter.

The appendices are designed as working references: a consolidated hardening checklist, a 30/60/90-day plan for a new security lead, incident runbook templates, a baseline configuration quick-reference, a plain-language glossary and a guide to tools and standards. The book then begins, as the author puts it, with a way of thinking rather than with tools.

KEY POINTS

Key points

  • Accept that a small team cannot do everything, and decide openly what to do first and what to defer.
  • Learn how a control works before applying it, so you can adapt it when your environment differs.
  • Read every script line before running it, and prefer reversible changes until you understand the impact.
  • Use the chapter-end action lists to make one concrete improvement per week.
  • Keep the appendices, especially the hardening checklist and runbook templates, as standing references.

QUESTIONS

Common questions

Who is The Hardened Stack written for?
The Hardened Stack by Sho Shimoda is written for the one or two IT people at a small or mid-size organisation who keep systems running and have also inherited responsibility for security. It targets system administrators, cloud and DevOps engineers, network engineers, service desk leads and junior admins rather than large, dedicated security teams.
Does The Hardened Stack teach hacking or attack techniques?
No. The book is explicitly defensive and contains no attack tutorials, exploitation walkthroughs or malware. Attacks are described only in enough detail to recognise and block them, and all commands are intended for systems the reader owns and is authorised to inspect.
Do I need to read The Hardened Stack chapters in order?
No. The author recommends Part I to every reader because it sets out how the book reasons about risk, but the other chapters can be read in any order. A reader weak on identity can go straight to the identity chapter, and one who has never tested a backup restore can go to the backup chapter.
Is there companion code for The Hardened Stack?
Yes. Every script, policy, query and checklist in the book is published in a free companion toolkit on GitHub, organised by chapter and released under a permissive licence. The author asks readers to read and test each file before running it and to use it only on systems they are responsible for.
What is Meridian Foods in The Hardened Stack?
Meridian Foods is a fictional mid-size food company of about 450 staff used as a running example throughout the book. It runs Microsoft 365, Entra ID and Active Directory, some Azure and AWS workloads, a customer loyalty app and a trade ordering portal, so the advice can be shown on a realistic, ordinary estate.