Building Secure Cloud Infrastructure For Growth
Explore how cloud-native technologies improve scalability, reliability, and deployment speed.
The default posture is not yours yet
Most cloud accounts start more open than intended: broad IAM policies, long-lived access keys, security groups open wider than the service needs. None of this requires a security hire to fix, and all of it is worth fixing this month.
Start with identities
Replace shared credentials with per-person IAM identities, enforce multi-factor authentication everywhere, and cut long-lived access keys in favour of short-lived, role-based assumed credentials. This is a day of work that removes an entire class of credential-leak incidents.
Secrets do not belong in your repository
Move every secret into a managed secret store, and make CI inject them at runtime rather than at build time. A secret committed once is compromised forever, because git history remembers even after you delete the line.
Make the network boring
Databases and internal services belong in private subnets with no route to the internet. Only the load balancer is public. Most breaches that reach a database start with a publicly reachable port that nobody knew was open.
Log what you would want during an incident
Structured logs, retained for long enough to be useful, with authentication events separated out, answer most incident questions. Without them, a compromise is only measurable by its effects.