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

SecurityEngineering

A practical guide to secrets rotation, part 2

Practical steps, not promises.

Lu Brandt
Published 2 min read

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

#The details

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.

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

ts
export async function publish(post: Post) {
  const problems = validate(post);
  if (problems.length) return { ok: false, problems };
  await commit(post);
  return { ok: true, url: `/blog/${post.slug}/` };
}

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

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.

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

#Trade-offs

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.

  • Cache what never changes
  • Keep the previous version one click away
  • Skip what has not changed

#Rolling it out

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.

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

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.

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

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.

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