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

Security

Hardening audit logs

Practical steps, not promises.

Jun Calder
Published 2 min read

We assume something will go wrong and design for recovery. Containment, rollback and clear alerts matter more than any single control. This post covers what we changed, why, and what it means for you.

#Where we started

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.

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

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 constraint

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.

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.

#What changed

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.

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.

#Results

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.

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.

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.

#What we measured

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.

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}/` };
}

#What we would do differently

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

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.