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

21
workplans/WHITEHAT-WP-0001-cross-tenant-evidence.md
View file

@ -80,7 +80,7 @@ As above. Gates everything.
```task
id: WHITEHAT-WP-0001-T01
status: progress
status: done
priority: high
state_hub_task_id: "0d28fd14-1b82-4ac1-907b-02f43e8baae8"
```
@ -88,14 +88,15 @@ state_hub_task_id: "0d28fd14-1b82-4ac1-907b-02f43e8baae8"
Drafted in `docs/rules-of-engagement.md` on 2026-08-18 with authorization
classes, per-run records, initial target envelope, hard prohibitions,
credential/attribution rules, rate defaults, abort/cleanup and evidence
schema. It authorizes no live traffic until the operator personally approves
§10. T01 remains progress and continues to gate every later task.
schema. The operator accepted v0.1 on 2026-08-21 with the scope recorded in
§10. The acceptance approves the operating rules and offline fixture work; it
does not pre-authorize any live target.
### T02 — The attacker model per axis
```task
id: WHITEHAT-WP-0001-T02
status: wait
status: done
priority: high
state_hub_task_id: "e0070ee6-6060-4a29-bd88-f664034db28e"
```
@ -112,15 +113,19 @@ distinguishes them:
| P1/P2 | A co-resident consumer behaving badly within its own allowance | What degradation do neighbours experience? |
| R | A copy of a backup taken before an erasure | Is the erased data still readable? |
**Output:** `docs/attacker-model.md`. Note that the E3 row exists because the
framework corrected itself: E3 stops accident, not compromise, and a probe that
only tested accident would report a strength E3 does not have.
**Output:** `docs/attacker-model.md`, completed 2026-08-21. It separates
credential-bearing tenant attacks, omitted-predicate accidents, SQL-capable
compromise, structural credential confinement, bounded co-resident saturation,
and both R4 erasure routes. It preserves the framework's correction that E3
stops accident, not compromise: resetting the tenant GUC after SQL execution
is recorded as E3's documented limit, not misreported as an E3 conformance
failure.
### T03 — Differential cross-tenant harness (the E2 artifact)
```task
id: WHITEHAT-WP-0001-T03
status: wait
status: todo
priority: high
state_hub_task_id: "742561f1-97b6-4fcc-8e06-d18508ddecae"
```