Skip to content
NewSee how this site publishes in seconds
Halftone

Security

Defaults matter: secrets rotation, part 2

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

Defaultsmatter:secretsrotation,HALFTONE / JOURNAL
Ada Rivers
Published 2 min read

We assume something will go wrong and design for recovery. Containment, rollback and clear alerts matter more than any single control. This post covers what we changed, why, and what it means for you.

#What changed

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.

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.

  • Cache what never changes
  • Skip what has not changed
  • Run independent steps in parallel

#What's next

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 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;

#Where we started

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.

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.

#The constraint

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

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.

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

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