Principles for choosing tools
The book holds that tools support decisions and remove toil; they do not create security by themselves. A tool nobody has time to run, tune and act on gives a false sense of coverage. Choose fewer tools, operate them well, and start with your platform's built-in capabilities, which need no extra integration or licence and already sit where your data is. Add a third-party product only when you have felt a real gap.
The NIST Cybersecurity Framework functions are offered as a lens for balance, so that a team does not end up with several detection tools and no recovery capability.
Tool categories
The appendix walks through identity (where the identity provider, such as Entra ID or Google Workspace, is the most important tool), endpoint and device management, network, cloud security, email security, logging and detection, vulnerability and configuration assessment, secrets and keys, and backup and recovery. It mixes free and open-source options with commercial ones and gives no prices or URLs.
A few examples of its points: native cloud tools such as Microsoft Defender for Cloud or AWS Security Hub with GuardDuty and Config are the right starting point; DMARC-reporting services make the raw XML reports readable; and for backup, exercising the restore and protecting the backup system's own credentials matter more than the brand.
Standards worth knowing
The CIS Controls and Benchmarks are the most directly actionable. The NIST CSF gives a shared vocabulary for talking with leadership, NIST SP 800-61 underpins the incident-handling material, and NIST 800-53 is a broad control catalogue. ISO/IEC 27001 is a sound management-system model even without certification. OWASP is the reference for application security, and CVSS, EPSS and the CISA KEV catalogue together guide patch priorities. MITRE ATT&CK, NIST 800-171 and your own jurisdiction's data-protection law are also named. The author's advice is to treat standards as scaffolding, not scripture.
KEY POINTS
Key points
- List your tools against the NIST CSF functions and look for the function with no coverage.
- Use your platform's native security features before adding a third-party product.
- Retire or properly operate any tool nobody has time to tune and act on.
- Add secret scanning to the CI pipeline and run a periodic sweep of existing code.
- Automate certificate issuance and renewal to avoid expired-certificate outages.
- Confirm which data-protection laws apply to the data you hold before an incident.
QUESTIONS
Common questions
- Should a small IT team buy third-party security tools or use built-in features?
- The Hardened Stack recommends starting with the platform's built-in capabilities, because they need no extra integration, carry no extra licence and already sit where the data lives. A third-party tool makes sense only when the native capability has a real gap the team has actually experienced, since integration overhead falls entirely on the team.
- Why can having more security tools make an organisation less safe?
- A tool that nobody has time to run, tune and act on produces a false sense of coverage, which is worse than having no tool. Security comes from decisions and action; tools only support those decisions and remove repetitive work. Fewer tools that are well operated and integrated with existing systems usually defend better.
- Which security standards should IT administrators know?
- Useful starting points are the CIS Controls and Benchmarks, the NIST Cybersecurity Framework, NIST SP 800-61 for incident handling, NIST 800-53, ISO/IEC 27001 and OWASP for application security. CVSS, EPSS and the CISA KEV catalogue help prioritise patching, and MITRE ATT&CK helps check detection coverage. The local data-protection law also matters because it turns some controls into legal obligations.
- How can the NIST Cybersecurity Framework help a small team choose tools?
- Mapping tools to the framework's functions, such as identify, protect, detect, respond and recover, shows where coverage is lopsided. Many small teams collect several detection tools while having little recovery capability, or the reverse, and the framework makes that imbalance visible.
- Do you need ISO 27001 certification to benefit from it?
- No. Even without certifying, the structure of ISO/IEC 27001, with policies, risk assessment and continual improvement, is a sound model for running security. The Hardened Stack also notes that customers increasingly ask whether an organisation follows it.