coulomb/whitehat-security
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
whitehat-security/engagements/README.md
tegwick b8facab717 Schedule 18:00Z custody for acknowledged audit-core E2 
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
2026-08-22 12:16:29 +02:00

999 B
Raw Blame History

Engagement records

Copy template.json to a dated, target-specific record and have both the operator and target owner approve it before a live run. The runner validates the record at execution time and fails closed when it is incomplete, expired, outside its window, too permissive, or mismatched to the requested technique or route.

An engagement record contains authorization metadata only. Never put a token, password, database URL, secret path value, or real tenant identifier here.

Live admission also requires a matching file in targets/ and a plane lease from whitehat admit-plane. WH-ENG-20260821-AUDIT-E2 and WH-ENG-20260821-TENANT-E2 are cancelled and must not be reused. The pod manifest under runtime/ is bound to a cancelled ID and must not be applied.

WH-ENG-20260822-AUDIT-E2-01 is operator-approved and owner-acknowledged. Offline validation currently fails closed because the window has not started. Do not mint the 900s identities until 2026-08-22T18:00:00Z.