Skip to main content

Resources

Everything worth reading is ungated

Practical worksheets for evidence ownership, minimum access and approval boundaries — the questions a security review asks first, answered before it does.
No form between you and the work.

Open libraryreadinessevidence ownershipengineering notes
Document register

Working documents, no empty archive.

A register entry appears only when an attributable, date-stamped artifact exists. Each one is the whole worksheet, on this page, with nothing behind a form.

REG-01

VerifiedReviewed

Evaluation guide

Incident investigation readiness checklist

A buyer worksheet for evidence ownership, minimum access, retention, approvers, escalation, and evaluation criteria.

  • □ Name one representative incident and success criterion
  • □ Map evidence systems and minimum connector scopes
  • □ Name the human approver for every proposed action
  • □ Record retention, model, and deployment constraints
Author
Tamir Cohen
Type
Checklist
Updated
2026-07-22
Length
3 min

REG-02

VerifiedReviewed

Security review

Minimum read-only access for an incident investigation

Work out the least privilege that still answers the question, before a security review asks. One row per evidence system: what it is read for, the narrowest scope that satisfies it, who grants it, and who revokes it.

  • □ List every system an investigation must read — logs, metrics, traces, deploy history, tickets — and what question each one answers
  • □ For each, write the narrowest scope that still answers it: read-only, time-bounded, and scoped to a namespace or service rather than an account
  • □ Name who grants each scope and who revokes it, with the date the grant expires
  • □ Decide what must never leave your network, then pick the deployment that honours it rather than the other way round
  • □ Agree the retention window for evidence copies before the first investigation runs, not after
Author
Production Master engineering
Type
Worksheet
Updated
2026-08-02
Length
4 min

Engineering notes, by email

Occasional engineering notes on what shipped and what broke while building the product.

Occasional build notes. No spam, unsubscribe any time. Reply to stop any time.

Bring an incident worth making legible

Use the worksheet to frame the evidence, approvers, and constraints before a closed-beta investigation starts.

Join the closed beta