Skip to content
NewSee how this site publishes in seconds
Halftone

SecurityEngineering

Our approach to session tokens, part 2

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

Hana Pike
Published Updated 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.

#Rolling it out

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.

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

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.

#Where we started

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.

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

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.

“The safe path has to be the easy path.”
Bo Lindqvist

#What changed

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

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
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}/` };
}

#Trade-offs

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.

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.

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