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

SecurityEngineering

A practical guide to session tokens, part 2

How we make the safe path the easy path.

Eli Tanaka / Kit Moreau
Published 2 min read

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

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

  • Cache what never changes
  • Run independent steps in parallel
  • Report problems in plain language

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

#What we would do differently

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.

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.

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.

“The safe path has to be the easy path.”
Cam Okafor

#What's next

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

#The details

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.

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.

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

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