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

Security

Our approach to least-privilege defaults

How we make the safe path the easy path.

Kit Moreau / Ada Rivers
Published 1 min read

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

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.

#The constraint

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.

#What's next

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.

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.

  • Report problems in plain language
  • Run independent steps in parallel
  • Cache what never changes
  • Skip what has not changed

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

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 changed

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.

“Measure the time from done to live, and treat every minute of it as a bug.”
Dee Marsh