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

16
docs/rules-of-engagement.md
View file

@ -1,6 +1,6 @@
# Rules of engagement for tenancy evidence
Status: **pending personal operator approval**
Status: **accepted**
Version: 0.1
@ -139,7 +139,13 @@ known-good fixture in the same revision.
## 10. Approval
Personal operator approval is still required. Record approver, date and scope
in this section or an immutable linked decision before changing the status to
accepted. Until then, only documentation and non-networked test-fixture design
may proceed; no target packets are authorized by this draft.
Approved by: **repository operator**, by explicit approval in the coordinating
session
Approval date: **2026-08-21**
Approved scope: these rules are accepted as the operating boundary for
`whitehat-security`. This approval permits documentation and non-networked
fixture work. It does **not** authorize a live target or a packet to any target.
Every live run still requires the engagement record, target-owner
acknowledgement and any technique-specific operator approval required by §1.