Zero trust access for engineers
How people should reach production: federated sessions instead of users, no long-lived keys anywhere, and access that ends the day someone leaves.
4 posts on this subject.
How people should reach production: federated sessions instead of users, no long-lived keys anywhere, and access that ends the day someone leaves.
Encrypted secrets in Git, one key per stage, and a sync to parameter storage: why repository write access still does not let anyone read production.
A separate account, an organization-wide trail with file validation, and a policy that forbids stopping it — plus what tamper-resistant does not mean.
What GuardDuty, Security Hub, Config, CloudTrail and their siblings each actually catch, what they cost, and the order to switch them on.
A 30 minutes call with an engineer who scopes engagements, not a salesperson. Tell us what you run and what is coming: a funding round, an audit, a first enterprise customer, a migration. You leave with a next step, a fixed fee, or an honest no.