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

Correct audit engagement and idempotent fixture setup

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-22 00:05:15 +02:00
parent edc9df0491
commit 8a97fac17f
5 changed files with 34 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

3
engagements/2026-08-21-audit-core-e2.json
View file

@ -6,7 +6,8 @@
"expires_at": "2026-08-21T23:15:00Z",
"target": "http://audit-core.audit-core.svc.cluster.local:8080",
"target_owner": "audit-core / infrastructure operator",
"target_owner_acknowledged_at": "2026-08-21T21:56:00Z",
"target_owner_acknowledged_at": null,
"target_owner_acknowledgement_status": "pending corrected adapter/record review; target review received 2026-08-21T22:04:19Z",
"environment": "production",
"production_approval": "Explicit user approval of engagements/2026-08-21-e2-proposals.md in the coordinating session",
"namespace": "audit-core",

5
engagements/2026-08-21-e2-proposals.md
View file

@ -53,8 +53,9 @@ invented tenant claim is not acceptable evidence.
## Explicitly excluded
These E2 approvals do not cover direct PostgreSQL access, RLS probes, schema or
role changes, connection/load saturation, recovery, production, adjacent
These E2 approvals cover only the two exact named production deployments and
do not cover any other production target, direct PostgreSQL access, RLS
probes, schema or role changes, connection/load saturation, recovery, adjacent
services, real tenant identifiers, or collection of response bodies. E3 and
P1/P2 each receive a separate approval package after E2 establishes the safe
execution path.