craigthompson.dev

$ cat case-studies/security.md

Closing doors, not adding locks

// security & privacy · 2021 → 2026

Closing doors, not adding locks

When a product handles confidential data, security and privacy are part of the product. We focused on removing whole classes of risk rather than layering controls on top.

areabeforeafter
server accessSSH & bastionsSSM Session Manager; port 22 closed everywhere
admin accessIAM admin usersSSO only, via IAM Identity Center and Control Tower
networksVPC peeringPrivateLink and VPC endpoints
public surfaceinternet-facing load balancerOne CDN entry point, with WAF in block mode
dev secretsplaintext .env filesInjected at runtime from a password manager
dependenciesknown CVEs lingeringVulnerable packages swapped out; pentest findings fixed and tracked
incidentsad hocBlameless post-mortems, with runbooks and tooling as the fix
# in practice
  • Far fewer standing keys and passwords for anyone to leak.
  • No servers reachable from the internet except through the CDN.
  • External penetration-test findings were fixed in code and tracked to closure.

$ ls case-studies/

Search and jump