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

SecurityEngineering

A practical guide to least-privilege defaults, part 2

Practical steps, not promises.

Fen Alvarez / Gus Heller
Published 1 min read

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

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

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.

“A cache key must include everything that can change the output, and nothing that cannot.”
Jun Calder

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

  • Keep the previous version one click away
  • Report problems in plain language
  • Run independent steps in parallel
  • Skip what has not changed

#Trade-offs

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.

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.

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

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.

StepBeforeAfter
Install94s12s
Build41s7s
Deploy18s4s