You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
A disposable investigation stack, so an incident does not touch odin's durable store #438
ADR-0030
puts Wazuh and Velociraptor in stacks/soc/ on odin, sized to a 2 GiB heap
and thirty days of retention derived from twenty-five-shards-per-GiB. That is
the right shape for the durable case: the thing that has been watching all
along.
It is the wrong shape for the other case. Detonating a sample, or working a
single question over a weekend, wants a store you can fill with noise, query
hard, and then delete — without spending odin's shard budget, without
polluting the record the estate is judged by, and without a retention policy
argument every time.
What this is
A sibling under stacks/, on a guest that is expected to be destroyed.
This fits ADR-0004 without
amending it — a stack is the unit that gets deployed together, and a second host
means a second directory. scripts/stacks.sh already treats any directory with
a compose.yaml as a stack, and validate.sh, ci.yml and the Python checkers
all read from it, so a new stack is checked from the day it is authored.
It can be authored and CI-validated before the guest exists — the stacks/lab and stacks/sensitive precedent.
The thing to get right
Its lifecycle must be visible. A throwaway stack that quietly stays up for
four months is odin with worse retention and no one watching it. Whatever
marks it disposable — a naming convention, a documented teardown, a liveness
expectation that inverts so that still-running is the thing that gets noticed
— should be decided here rather than discovered later.
Its age recipient is its own, per ADR-0020's rule: a stack that holds
investigation data should not be able to decrypt the estate's credentials.
What it waits on
#266 — this is a variation on
that stack's shape, and it is easier to write the disposable one once the
durable one exists to differ from.
Purchases this needs
None.
Corrected 2026-09-19
Nothing delivered, nothing stale. stacks/soc (#434) is now the second worked precedent for authoring a stack ahead of its guest and CI-validating it, which is what this issue proposes for the disposable one. Gate stays #266.
Activity
feat(scratch): a disposable investigation stack whose age is what get…
docs(scratch): put the runbook's "You will need" on one line, for MD0…
fix(agents): alert when a guest's config cannot be read, so the age r…
feat(scratch): a disposable investigation stack whose age is what get…
docs(adr): renumber the Packer ADR to 0073 (#440)
Packer templates for the lab domain, built from phoenix (#440) (#792)