Security
DevSecOps & secrets management
DevSecOps means security is built into the delivery pipeline and platform rather than bolted on at the end. Senior DevOps interviews ask how you secure the software supply chain (code → dependencies → build → image → deploy), manage secrets, harden Kubernetes workloads, and respond when a scanner reports 400 vulnerabilities. The OPA and IAM topics cover policy and identity in depth; this topic connects the rest.
After this topic you can
- Store and rotate secrets properly
- Add scanning and signing to a pipeline
- Harden containers and clusters against common attacks
Lessons
-
1Shift-left security in the pipeline
- Where each control fits
- Making scanners useful rather than noisy
-
2Software supply chain security
- Threats
- SBOMs
- Signing and provenance
- SLSA levels (simplified)
- Hardening the pipeline itself
-
3Container image security
- Building secure images
-
4Kubernetes workload and cluster security
- Pod security
- Cluster-level controls
-
5Secrets management
- Principles
- Delivering secrets to Kubernetes workloads
- ExternalSecret example
- Secret leak response
-
6Compliance, vulnerability management and the bigger picture
- Vulnerability management lifecycle
- Example: Log4Shell-style response
- Compliance as code
- Threat modelling (lightweight)
-
7Interview questions and model answers
- "How do you integrate security into a CI/CD pipeline?"
- "A scan reports 400 vulnerabilities in our base image. What do you do?"
- "How do you manage secrets for applications on EKS?"
- "What is an SBOM and why does it matter?"
- "How do you ensure only trusted images run in your cluster?"
- "How would you harden a Kubernetes pod?"
- "A developer pushed an AWS key to GitHub. What happens next?"