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

Approve rules of engagement and define attacker models

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a0260c-4067-7052-9647-ad000d576e38
This commit is contained in:
tegwick 2026-08-21 23:09:22 +02:00
parent 30af1be843
commit 25a07d16f7
7 changed files with 298 additions and 26 deletions
Download patch file Download diff file Expand all files Collapse all files

15
SCOPE.md
View file

@ -35,8 +35,9 @@ boundary always holds.
## Safety invariants
- Until the rules of engagement receive personal operator approval, only
documentation and non-networked fixture design may proceed.
- The rules of engagement are accepted, but their acceptance authorizes no live
target. Without a complete approved engagement record, only documentation
and non-networked fixture design may proceed.
- No live target is authorized by this scope document.
- Every live run names its authorization, target, owner, window, technique,
credential lane, rate ceiling, abort contact and finding destination.
@ -65,10 +66,12 @@ boundary always holds.
- Repository status: active.
- Active plan: `WHITEHAT-WP-0001`.
- `T01` is in progress: the rules of engagement are drafted and awaiting
personal operator approval.
- No live probe traffic is authorized yet.
- `T02` through `T07` remain gated by `T01`.
- `T01` is complete: the rules of engagement were accepted on 2026-08-21.
- `T02` is complete: the per-axis attacker model is recorded in
`docs/attacker-model.md`.
- `T03` is ready to begin with offline harness and fixture design.
- No live probe traffic is authorized; each target still requires its own
engagement record and approvals.
## Relationships