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

SecurityEngineering

Hardening session tokens

Practical steps, not promises.

Ivo Santos / Lu Brandt
Published 2 min read

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

#What we measured

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
const key = `${route}:${hash(content)}:${hash(template)}`;
const hit = await cache.match(key);
if (hit) return hit;

#What changed

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.

#Results

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.

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.

  • Report problems in plain language
  • Run independent steps in parallel
  • Skip what has not changed

#Rolling it out

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.

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
const key = `${route}:${hash(content)}:${hash(template)}`;
const hit = await cache.match(key);
if (hit) return hit;

#The details

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.

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.

  • Report problems in plain language
  • Run independent steps in parallel
  • Skip what has not changed

#Trade-offs

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.

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.