Skip to content
NewSee how this site publishes in seconds
Halftone

SecurityEngineering

Hardening sandbox isolation, part 2

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

Kit Moreau / Jun Calder
Published 2 min read

We publish what we change and why. Customers should be able to check our work, not just take our word for it. This post covers what we changed, why, and what it means for you.

#Rolling it out

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.

  • Run independent steps in parallel
  • Skip what has not changed
  • Cache what never changes

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

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.

“Good defaults are invisible until they are missing.”
Cam Okafor

#The details

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

#Where we started

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.

#What we measured

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.

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.

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

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

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

“Good defaults are invisible until they are missing.”
Bo Lindqvist

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