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

Security

Hardening sandbox isolation, part 2

How we make the safe path the easy path.

Bo Lindqvist
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.

#Rolling it out

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.

“Measure the time from done to live, and treat every minute of it as a bug.”
Ivo Santos

#Trade-offs

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

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.

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

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 changed

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.

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.

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

#What we measured

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

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.

#The constraint

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.

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.

  • Report problems in plain language
  • Keep the previous version one click away
  • Skip what has not changed
  • Run independent steps in parallel

#What's next

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.

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