coulomb/whitehat-security
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Schedule 18:00Z custody for acknowledged audit-core E2

Browse source 
Record the owner-acknowledged window, pin the runner invocation including
the forged fixture id, and ask railiance-platform to project identities
only at window start. No mint, no pod apply, no packets.

Assistant: grok
Assistant-Session: 01a02670-3345-76f2-a014-70fde8e2a2bb
This commit is contained in:
tegwick 2026-08-22 12:16:29 +02:00
parent 32afceb68e
commit b8facab717
8 changed files with 139 additions and 39 deletions
Download patch file Download diff file Expand all files Collapse all files

38
engagements/2026-08-22-audit-core-e2.md
View file

@ -1,26 +1,22 @@
# WH-ENG-20260822-AUDIT-E2-01
Status: **operator-approved, awaiting target-owner acknowledgement**.
This is not yet authorization to send a packet or project credentials.
Status: **operator-approved and target-owner-acknowledged**. The window has
not started. Credentials must not be minted until window start so the 900s
TTL covers the run and cleanup.
Operator approved `2026-08-22T09:52:55Z` in the coordinating session
(`operator-session-2026-08-22-e2-approval`). Audit-core acknowledgement is
still pending. The cancelled ID `WH-ENG-20260821-AUDIT-E2` remains terminal.
| Field | Value |
| Gate | State |
| --- | --- |
| Target | `audit-core.audit-core.svc.cluster.local:8080` |
| Registration | `targets/audit-core-e2.json` (`applicable`, `live-e2`) |
| Source | pod `whitehat/whitehat-e2-audit` with plane and target labels, SA `whitehat-runner`, no token |
| Image pin | `forgejo.coulomb.social/coulomb/audit-core@sha256:7febc28e8a828dbc245144a38e5728e0fbf496b594dd7591170b450a1265fb10` |
| Identities | two ordinary tenant-scoped `may_read`/`may_write` senders, `source=whitehat-security`, TTL ≤ 900s, mount-only |
| Routes | `GET /readyz`, `POST /v1/events`, `GET /v1/events/{event_id}`, `GET /v1/events?correlation_id=` |
| Ceiling | concurrency 1; 10/min; at most 30 requests |
| Window | 2026-08-22T18:00:00Z–18:15:00Z |
| Cleanup | revoke both leases; delete only named synthetic fixtures; prove cleanup |
| Reporting | `risk-nexus`, no severity |
| Operator approval | `2026-08-22T09:52:55Z` |
| Owner acknowledgement | `2026-08-22T10:04:56Z` at `32afceb` |
| Foundational plane | applied by ops-mason `c26a6e5` |
| Window | `2026-08-22T18:00:00Z`–`18:15:00Z` |
| Image | `sha256:c2fe39a0185b99be3fc0cb14d2de69772b8e66e20490097c9d11d90cc39719a6` |
| Custody projection | scheduled, not minted |
| Runner pod | not applied |
Offline preflight must fail closed until `target_owner_acknowledged_at` is
set. After acknowledgement, the live custody broker is still unconnected and
must fail closed until two identities are projected. Do not apply
`plane/runner-pod.yaml` before that.
Offline preflight now fails closed with `engagement window has not started`.
At `18:00Z`, `Engagement.load` authorizes the record; `admit-plane` still
fails closed until the live custody broker is connected.
Invocation, including required `--forged-event whitehat-e2-forged-b-20260822`:
`engagements/runtime/WH-ENG-20260822-AUDIT-E2-01-invocation.md`.