Start from a published baseline
The appendix names guidance rather than linking to it. Two sources recur: the CIS Benchmarks, consensus-built hardening guides split into Level 1 (sensible for most) and Level 2 (stricter), with the CIS-CAT tool to measure systems against them; and each vendor's own security baselines, which are often more current for their products. The book suggests the vendor baseline as the practical start and the CIS Benchmark as the independent cross-check.
It also warns against applying Level 2 wholesale to an ordinary office estate. A baseline that is mostly applied and stable is better than a complete one that frustrated users quietly switch off.
Platform by platform
For each platform the appendix lists the settings that matter most. A few examples: on Windows, manage through Group Policy or Intune, use LAPS, enable BitLocker with escrowed keys, turn on Defender tamper protection and attack-surface-reduction rules, and disable SMBv1 and NTLMv1. On Linux, keep SELinux or AppArmor enabled rather than switching it off, harden SSH and use configuration management. In Microsoft 365, use Secure Score as a map, with security defaults as a floor for the smallest tenants.
Azure, AWS, browsers and office software, network devices, and often-forgotten appliances such as cameras, printers and operational-technology devices are covered the same way. For many of those appliances, isolation on their own segment is the main control.
In Azure the reference points are Defender for Cloud and the Microsoft Cloud Security Benchmark, with Azure Policy guardrails, managed identities and keys held in Key Vault. In AWS the appendix starts from account structure: Organizations with service control policies, CloudTrail in all regions, GuardDuty, Security Hub and Config, and IAM roles instead of long-lived access keys. For office software, the highest-value setting is blocking macros from the internet by default.
Applying a baseline without breaking things
The book describes four steps: measure the starting state with an assessment tool, apply to a small pilot group long enough for breakages to appear, record every kept deviation with reason, owner and ideally an expiry date, then widen in waves and schedule the re-check. Keep baselines in version control where possible, and change the baseline rather than hand-tuning individual machines, because each manual change becomes drift nobody remembers.
KEY POINTS
Key points
- Pick one published baseline per platform and apply it through management tooling, not by hand.
- Start at CIS Level 1 and pilot every baseline with a small, willing group.
- Record each kept deviation with a reason, an owner and an expiry date.
- Keep baselines in version control so they can be reviewed, compared and rolled back.
- Block internet-sourced macros by default in office software.
- Schedule re-checks for drift instead of assuming the baseline still holds.
QUESTIONS
Common questions
- Should I use CIS Benchmarks or the vendor's security baseline?
- The Hardened Stack suggests using both: the vendor baseline, often more current for its own products, as the practical starting point, and the CIS Benchmark as an independent, thorough cross-check. CIS Benchmarks are divided into Level 1 settings suitable for most organisations and stricter Level 2 settings for high-security needs.
- Should a normal office apply CIS Level 2 settings?
- Usually not as a whole. Level 2 settings are meant for environments that genuinely need them, and applying them across an ordinary office estate tends to break printing and legacy applications. Start at Level 1, pilot with a small group, and record any exceptions as time-limited decisions with a named owner.
- How do you roll out a security baseline without breaking systems?
- Measure the current state with an assessment tool such as CIS-CAT or a cloud posture service, apply the baseline to a small pilot group long enough for problems to surface, document each deviation you keep with a reason, owner and expiry date, and then widen the rollout in waves. Schedule regular re-checks, because baselines drift as systems change.
- What are the key Windows hardening settings for a small organisation?
- Manage Windows centrally through Group Policy or Intune, enforce strong authentication and lockout policy, restrict local administrators and manage their password with LAPS, enable BitLocker with keys escrowed to the directory, configure the Windows firewall, enable Microsoft Defender with tamper protection and attack-surface-reduction rules, forward security event logs, and disable SMBv1 and NTLMv1.
- How should cameras, printers and OT devices be secured?
- Inventory them, change their default credentials, and place them on their own tightly controlled network segment with no path to the internet or to critical systems. Because these devices are rarely patched and often cannot be fully hardened, isolation is frequently the primary control for them.