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

Record the owner requirements that keep the live residuals blocked.

Browse source 
WHITEHAT-WP-0006 still waits on rapp-postgres, an operator substrate
window, and access-engine or a new audit-core engagement. WHITEHAT-WP-0008
still waits on a named live ASM surface, with T-06 on approval-engine.

Assistant: grok
Assistant-Session: 01a10450-dda4-7253-91a9-b8dccb2f0173
This commit is contained in:
tegwick 2026-10-04 02:48:59 +02:00
parent de7235420a
commit 7b5bc1e444
3 changed files with 60 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

8
SCOPE.md
View file

@ -69,8 +69,12 @@ boundary always holds.
closed.
- Finished: `WHITEHAT-WP-0001` through `WHITEHAT-WP-0005` and
`WHITEHAT-WP-0007`. Residual live Tenancy Posture evidence is
`WHITEHAT-WP-0006`. Residual live ASM is `WHITEHAT-WP-0008`. Both are
blocked on authorization.
`WHITEHAT-WP-0006`. Residual live ASM is `WHITEHAT-WP-0008`. Both stay
`blocked` after the 2026-10-04 recheck. T01 waits on `rapp-postgres` for
an ordinary runtime identity. T02 waits on an operator substrate window.
T03 waits on `access-engine` or a new `audit-core` engagement ID. Live ASM
waits on a surface owner, with T-06 on `approval-engine` and a consuming
PEP. No packet is authorized.
- `WHITEHAT-WP-0007` triaged Gate House ASM T-01…T-10. Live `asm-tNN`
registrations remain `pending`. In-process `fixture-asm-t01`…`t10`
calibrations exist. That work authorized no live probe.