Skip to content
NewSee how fast an edit goes live on this site
Halftone

SecurityEngineering

Defaults matter: secrets rotation, part 2

How we make the safe path the easy path.

Defaultsmatter:secretsrotation,HALFTONE / JOURNAL
Eli Tanaka
Published 2 min read

Credentials never reach the code that runs on your behalf. A broker holds them and hands out short-lived tokens scoped to a single task. This post covers what we changed, why, and what it means for you.

#What's next

We assume something will go wrong and design for recovery. Containment, rollback and clear alerts matter more than any single control.

We publish what we change and why. Customers should be able to check our work, not just take our word for it.

Permissions only shrink during a run. A task can give up access it no longer needs, but it can never gain access it did not start with.

StepBeforeAfter
Install94s12s
Build41s7s
Deploy18s4s

#Where we started

Every action is attributed to a person or an agent acting for one. The audit log answers who did what, when, and with which permissions.

Security work is mostly about making the safe path the easy path. If doing the right thing takes extra steps, people will eventually skip them.

Diagram of the request path before and after the change
Figure: the request path, before and after.

#What changed

Credentials never reach the code that runs on your behalf. A broker holds them and hands out short-lived tokens scoped to a single task.

We assume something will go wrong and design for recovery. Containment, rollback and clear alerts matter more than any single control.

We publish what we change and why. Customers should be able to check our work, not just take our word for it.

Diagram of the request path before and after the change
Figure: the request path, before and after.

#The details

Permissions only shrink during a run. A task can give up access it no longer needs, but it can never gain access it did not start with.

Every action is attributed to a person or an agent acting for one. The audit log answers who did what, when, and with which permissions.

Diagram of the request path before and after the change
Figure: the request path, before and after.

#Results

Security work is mostly about making the safe path the easy path. If doing the right thing takes extra steps, people will eventually skip them.

Credentials never reach the code that runs on your behalf. A broker holds them and hands out short-lived tokens scoped to a single task.

#What we measured

We assume something will go wrong and design for recovery. Containment, rollback and clear alerts matter more than any single control.

We publish what we change and why. Customers should be able to check our work, not just take our word for it.

Permissions only shrink during a run. A task can give up access it no longer needs, but it can never gain access it did not start with.