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

Security

Defaults matter: secrets rotation, part 3

Practical steps, not promises.

Ivo Santos / Cam Okafor
Published 2 min read

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. This post covers what we changed, why, and what it means for you.

#What we would do differently

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.

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.

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

#Rolling it out

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.

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

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.

StepBeforeAfter
Install94s12s
Build41s7s
Deploy18s4s

#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.

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.

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

#What's next

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

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.

ts
const key = `${route}:${hash(content)}:${hash(template)}`;
const hit = await cache.match(key);
if (hit) return hit;

#The details

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

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

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.

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.