Skip to content

8. Security Best Practices

The ideas from this whole module come together under one principle: defense in depth — no single control is trusted to be perfect, so several layers each cover for the others' weaknesses.

A defense-in-depth stack, top to bottom

Layer Example from this module
Physical Locked server room, BIOS/UEFI password (Lesson 1)
Network Firewalls, VLANs, VPNs (Lesson 4)
Access MFA, least privilege, RBAC (Lesson 5)
Device Encryption, screen locks, MDM (Lesson 6)
Human Social engineering awareness (Lesson 3)
Data lifecycle Proper destruction and disposal (Lesson 7)

If an attacker gets past one layer — say, a phished password — the other layers (MFA, least privilege, network segmentation) are what stop that single failure from becoming a total compromise.

Keeping it current

Security isn't a one-time setup. Patching closes known vulnerabilities as they're discovered; security policies (acceptable use, password requirements, incident reporting) keep the human layer consistent; regular review catches access and configurations that made sense once but don't anymore.

Try it

Pick any one lesson from this module and explain which layer of the defense-in-depth stack it belongs to, and what a failure at just that one layer alone would and wouldn't expose.

Tip

"We have a firewall" is not a complete security answer by itself — defense in depth means the real answer is always a list of overlapping protections, not any single one.

Play it

Open the Security Fundamentals Lab and use the Best practice tab. Once you've been through all eight lessons, try the Quiz tab for a review drawing from everything in this module.