Approve rules of engagement and define attacker models
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a0260c-4067-7052-9647-ad000d576e38
This commit is contained in:
parent
30af1be843
commit
25a07d16f7
7 changed files with 298 additions and 26 deletions
|
|
@ -25,9 +25,10 @@ responsible party.
|
|||
|
||||
## Non-negotiable safety boundary
|
||||
|
||||
- The rules of engagement are pending personal operator approval. Until they
|
||||
are approved, perform only documentation work and non-networked fixture
|
||||
design. Send no packets to a target.
|
||||
- The rules of engagement are accepted, but that acceptance authorizes no live
|
||||
target. Without a complete, target-specific engagement record and every
|
||||
approval required by the rules of engagement §1, perform only documentation
|
||||
work and non-networked fixture design. Send no packets to a target.
|
||||
- Even after approval, no live run starts without a dated engagement record
|
||||
naming authorization, target owner, exact scope, window, technique,
|
||||
credentials, rate/concurrency ceiling, abort contact and finding destination.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue