Security & secrets¶
Security is not a chapter you bolt on at the end — it's a property of every layer, and a discipline of limiting what a compromised component can do. Every chapter before this one built something that can now be attacked: a shell (Part I) that runs arbitrary commands, a network (Part II) that routes packets to places they shouldn't go, a git history (Part II) that never forgets a committed key, containers (Part III) that share a kernel with their host, a cluster (Part III) whose API server is a remote-control for your entire fleet, infrastructure-as-code (Part IV) that can provision a public S3 bucket as easily as a private one, and a CI/CD pipeline (Part V) that has write access to production by design. …
🔒 La suite est en accès freemium — lecture complète 100 % gratuite
Tu lis ici l'aperçu libre. Le reste du chapitre (code, schémas, maths, exercices) fait partie du livre complet : crée un compte gratuit (30 secondes, aucun paiement) pour tout lire.