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

Security

Our approach to audit logs

Practical steps, not promises.

Dee Marsh
Published 2 min read

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. This post covers what we changed, why, and what it means for you.

#What we would do differently

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.

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.”
Lu Brandt

#What's next

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.

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.

#The details

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.

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.

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.

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.

#Rolling it out

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.

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

#What changed

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.

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.