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

SecurityEngineering

Our approach to session tokens

Practical steps, not promises.

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

#What we measured

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.

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.

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

#What's next

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.

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

ts
const key = `${route}:${hash(content)}:${hash(template)}`;
const hit = await cache.match(key);
if (hit) return hit;

#Trade-offs

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.

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.

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 assume something will go wrong and design for recovery. Containment, rollback and clear alerts matter more than any single control.

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

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

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.

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