Chapter 13: Defence Principles and Key Takeaways¶
Understanding attacks is only half the equation. This chapter gathers the defences from all the earlier chapters into six principles: identity is the new perimeter, assume breach, patch fast, visibility equals detection equals response, humans are the first attack vector, and supply-chain trust must be verified. If you remember only six sentences from this book, remember these.
13.1 Identity Is the New Perimeter¶
Traditional security assumed: "inside the corporate network = trusted." With cloud computing, remote work, mobile devices, and third-party services, this assumption is completely broken. Your "perimeter" is now every identity credential in your organisation.
Modern Principle: ZERO TRUST — "Never trust, always verify." Treat every access request — regardless of where it comes from, inside or outside the network — as potentially hostile until verified.
- Enable MFA on every single account, without exception
- Adopt Passkeys (FIDO2) where possible — cryptographically phishing-resistant
- Assume credentials will eventually be stolen — make stolen credentials useless without the second factor
13.2 Assume Breach Mentality¶
The question is not "Will we be breached?" but "When we are breached, how quickly can we detect it, contain it, and recover from it?" Build your defences assuming the attacker is already inside.
- Zero Trust architecture — no implicit trust anywhere on the network
- Least privilege access — users and systems get the minimum permissions required
- Network segmentation — a breach of one area cannot automatically spread to all others
- Regular penetration testing — find your weaknesses before attackers do
- Incident response planning and drills — practised response is ten times faster than improvised response
13.3 Patch Fast¶
FACT: Studies consistently show that 60% of successful breaches exploit known vulnerabilities for which a patch was already available but had not been applied.
The moment a security patch is released, attackers reverse-engineer it to understand the underlying vulnerability and immediately target all systems that haven't yet applied the fix. The window between patch release and active exploitation is often measured in hours, not weeks.
- Implement automated patch management for all systems
- Vulnerability scanning: continuously identify unpatched systems
- Establish an emergency patching process for critical CVEs (Common Vulnerabilities and Exposures)
- Include third-party software and firmware — not just the OS
13.4 Visibility = Detection = Response¶
You cannot defend what you cannot see. You cannot respond to what you haven't detected. Comprehensive visibility across your entire environment is the foundation of effective defence.
- SIEM (Security Information and Event Management) — centralised log collection and automated correlation
- EDR (Endpoint Detection and Response) — behavioural monitoring on every laptop, server, and device
- NDR (Network Detection and Response) — monitor and analyse all network traffic for anomalies
- SOAR (Security Orchestration, Automation, and Response) — automate responses to common, known threats
13.5 Humans are the first attack vector¶
FACT: 91% of all cyberattacks begin with a phishing email or other human manipulation. The most sophisticated technical security controls can be — and regularly are — rendered completely ineffective by a single employee clicking a single malicious link.
- Regular, engaging security awareness training — not annual checkbox exercises that are immediately forgotten
- Phishing simulation exercises with immediate, constructive feedback
- Clear, simple reporting procedures for suspicious emails, calls, and requests
- Create a culture where employees feel safe reporting mistakes without fear of punishment
- Measure and track the human risk across the organisation
13.6 Supply Chain Trust Must Be Verified¶
FACT: The SolarWinds attack proved that your most trusted, most established software tools can be your biggest security risk. Every dependency, every vendor, every update is a potential attack vector.
- Audit third-party vendor security posture before granting access
- Maintain a Software Bill of Materials (SBOM) — know every component in your software stack
- Verify software integrity via cryptographic checksums before deploying updates
- Limit and monitor all third-party access — grant minimum necessary access only
Final thought
Security is not a product you buy or a project you complete — it is a continuous process of awareness, vigilance, and adaptation. The threat landscape evolves every day. Defenders must evolve with it.
13.7 Summary¶
- Identity is the new perimeter: MFA everywhere, passkeys where possible, and Zero Trust (never trust, always verify).
- Assume breach: least privilege, segmentation, penetration testing and rehearsed incident response.
- Patch fast: attackers reverse-engineer patches within hours; include firmware and third-party software.
- Visibility equals detection equals response (SIEM, EDR, NDR, SOAR); humans are the first vector (training, simulations, a no-blame reporting culture); supply-chain trust must be verified (vendor audits, SBOM, checksums).
13.8 Exercises¶
-
State the Zero Trust principle in one sentence and say what it replaces.
Answer
Never trust, always verify: every access request is treated as potentially hostile until verified, wherever it comes from. It replaces the older assumption that anything inside the corporate network is trusted.
-
What does "assume breach" change in the way defences are designed?
Answer
The question shifts from whether an attacker will get in to how quickly the breach will be detected, contained and recovered from. That means least privilege, segmentation, regular testing and rehearsed incident response.
-
Why is MFA not a complete defence against phishing, and what is?
Answer
A real-time reverse-proxy phishing tool (such as Modlishka) can relay the victim's one-time code as it is typed. FIDO2 passkeys are bound to the real domain and cannot be relayed to a fake one.
-
Expand SIEM, EDR, NDR and SOAR and say what each contributes to "visibility equals detection equals response".
Answer
SIEM: Security Information and Event Management, central log collection and correlation. EDR: Endpoint Detection and Response, behavioural monitoring of devices. NDR: Network Detection and Response, analysis of network traffic. SOAR: Security Orchestration, Automation and Response, automating the response to known threats.
-
Map each attack to the principle that addresses it most directly: credential stuffing, SolarWinds, exploitation of a known CVE months after its patch, ransomware that spreads from one workstation.
Answer
Credential stuffing: identity is the new perimeter (unique passwords and MFA). SolarWinds: supply-chain trust must be verified. Exploitation of a known CVE: patch fast. Ransomware spreading from one workstation: assume breach (segmentation and least privilege).