Skip to content
NewSee how this site publishes in seconds
Halftone

SecurityEngineering

Defaults matter: least-privilege defaults, 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.

Ivo Santos / Lu Brandt
Published 2 min read

We assume something will go wrong and design for recovery. Containment, rollback and clear alerts matter more than any single control. This post covers what we changed, why, and what it means for you.

#Results

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.

“Good defaults are invisible until they are missing.”
Kit Moreau

#Trade-offs

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.

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's next

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

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.

“The safe path has to be the easy path.”
Fen Alvarez

#What we would do differently

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.

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

ts
const key = `${route}:${hash(content)}:${hash(template)}`;
const hit = await cache.match(key);
if (hit) return hit;

#Where we started

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.

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.

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

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

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.

Diagram of the request path before and after the change
Figure: the request path, before and after.

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