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

Security

Hardening audit logs, part 3

How we make the safe path the easy path.

Ada Rivers
Published 2 min read

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

#Results

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 we measured

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

ts
export async function publish(post: Post) {
  const problems = validate(post);
  if (problems.length) return { ok: false, problems };
  await commit(post);
  return { ok: true, url: `/blog/${post.slug}/` };
}

#Rolling it out

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

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.

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

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

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

#Trade-offs

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

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.

  • Run independent steps in parallel
  • Keep the previous version one click away
  • Cache what never changes
  • Skip what has not changed