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

SecurityEngineering

Our approach to least-privilege defaults, part 3

Practical steps, not promises.

Our approachtoleast-privilegedefaults,HALFTONE / JOURNAL
Ada Rivers
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.

#Trade-offs

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.

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

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

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.

#Results

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

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.

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

#Where we started

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.

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.

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

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.

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