Skip to content
NewSee how this site publishes in seconds
Halftone

Security

A practical guide to secrets rotation, part 2

How we make the safe path the easy path. Practical steps, not promises. Our defaults, our reasoning, and what you can check yourself.

Bo Lindqvist
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.

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

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.

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

#The constraint

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.

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.

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

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.

  • Skip what has not changed
  • Keep the previous version one click away
  • Run independent steps in parallel

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

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

StepBeforeAfter
Install94s12s
Build41s7s
Deploy18s4s

#Trade-offs

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

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.

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

#What we would do differently

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.

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.

  • Cache what never changes
  • Report problems in plain language
  • Run independent steps in parallel
  • Keep the previous version one click away

Security9 min

Our approach to sandbox isolation

Our defaults, our reasoning, and what you can check yourself. Practical steps, not promises. How we make the safe path the easy path.

Hana Pike

Security4 min

Our approach to credential handling

Our defaults, our reasoning, and what you can check yourself. How we make the safe path the easy path. Practical steps, not promises.

Bo Lindqvist / Fen Alvarez

Security8 min

Defaults matter: secrets rotation

Our defaults, our reasoning, and what you can check yourself. Practical steps, not promises. How we make the safe path the easy path.

Jun Calder