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

State the harness scope and calibrate E4 and R4 offline.

Browse source 
SCOPE.md now matches the commands that run. E4 and R4 fail known-bad fixtures in process, and the cadence register schedules nothing.

Assistant: grok
Assistant-Session: 01a10450-dda4-7253-91a9-b8dccb2f0173
This commit is contained in:
tegwick 2026-10-04 08:54:40 +02:00
parent 314e2a8bf2
commit 7a2373ae4c
24 changed files with 989 additions and 58 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/attacker-model.md
View file

@ -165,6 +165,9 @@ credential and substrate confinement.
A platform, migration, break-glass or tenant B credential; control of the
credential issuer; or permission to alter routing/provisioning state.
Executable calibration is `whitehat e4-fixtures`. It is in-process, projects
no credential, and is not target assurance. No live E4 target is registered.
## 6. Shared P1/P2 capacity — bounded co-resident
This model tests capacity assurance, not the truth of the P1/P2 topology.
@ -232,6 +235,10 @@ outcome is inconclusive rather than pass.
targets R2. The facility does not erase the evidence service's retained facts
to satisfy a fleet-wide aspiration.
Executable calibration is `whitehat r4-fixtures`. It is in-process, opens no
store, and is not target assurance. An incomplete copy inventory stays
inconclusive. No live R4 target is registered.
## 8. Axes outside this first model
Identity (`I`), authorization (`A`) and availability (`V`) have evidence

4
docs/e3-cadence.md
View file

@ -4,7 +4,9 @@ The E3 detection interval is **24 hours**, so the declared maximum exposure
window is **24 hours plus run and reporting latency**. A run is also required
before deployment promotion following any schema migration, RLS policy change,
role/grant change, security-definer function change, or posture-mechanism
change. The event-triggered run does not reset the daily schedule.
change. The event-triggered run does not reset the daily schedule. Nothing in this
repository schedules that run. `whitehat cadence` is the register, and every
family in it has `scheduled: false`.
This is a detection control, not prevention. A migration can introduce an
unprotected table between runs; the interval states how long that condition