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

SecurityEngineering

Defaults matter: session tokens, part 3

Practical steps, not promises.

Fen Alvarez / Lu Brandt
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

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.

#What changed

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.

text
# p95 before / after
build      41.2s -> 6.8s
deploy     18.0s -> 4.4s
end-to-end 11m   -> 1m 52s

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

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

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

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.

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

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

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