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

Security

A practical guide to audit logs, part 2

Practical steps, not promises.

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

#The constraint

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.

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 details

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.

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.

text
# p95 before / after
build      41.2s -> 6.8s
deploy     18.0s -> 4.4s
end-to-end 11m   -> 1m 52s

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

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

#What we measured

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.

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.

#Rolling it out

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.

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

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