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.
5 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.
Least privilege fails when people cannot do their jobs. Here is an identity model with read-only production and an access review that produces evidence.
A guardrail works only if engineers cannot route around it. Here is how to design, exempt and test a service control policy before it blocks production.
Static cloud keys in CI are a liability you chose to keep. OIDC federation replaces them with short-lived tokens your pipeline requests per job.
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.