Skip to content
NewSee how this site publishes in seconds
Halftone

Security

A practical guide to least-privilege defaults

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

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

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

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.

#The details

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 publish what we change and why. Customers should be able to check our work, not just take our word for it.

  • Skip what has not changed
  • Report problems in plain language
  • Cache what never changes

#What's next

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.

  • Report problems in plain language
  • Cache what never changes
  • Run independent steps in parallel
  • Keep the previous version one click away

#The constraint

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.

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.

#Rolling it out

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.

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

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

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

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