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

Security

A practical guide to sandbox isolation

Practical steps, not promises.

Jun Calder / 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.

#Trade-offs

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

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.

#What's next

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.

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

#Where we started

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

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.

#What we measured

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.

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

#What changed

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.

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