coulomb/whitehat-security
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Automated white hat it-security, pen-testing and isolation-probing.
111 commits 1 branch 0 tags 1.1 MiB
Find a file
tegwick 42fe7a12c7 docs(reuse): establish reviewed NetKingdom security capabilities 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a137ca-5c77-7a71-b9ae-23ad9b0b5684
2026-10-14 06:46:53 +02:00
docs Keep layer declaration separate from dated observer evidence 2026-10-11 02:22:08 +02:00
engagements Record the rapp-postgres file grant that still leaves live E3 blocked. 2026-10-04 12:09:58 +02:00
evidence Classify I and A as mechanical and calibrate V observations offline. 2026-10-04 11:15:01 +02:00
history State the harness scope and calibrate E4 and R4 offline. 2026-10-04 08:54:40 +02:00
intakes repo.work.close_intake WHITEHAT-IN-0002 2026-09-02 01:11:26 +02:00
outbox Add governed test plane and close T04/T08 2026-08-22 00:44:21 +02:00
plane Record the audit-core E2-03 target pass and close T03/T07 2026-08-23 00:42:31 +02:00
probe-packs Build authorization-gated tenancy evidence harness 2026-08-21 23:53:27 +02:00
registry docs(reuse): establish reviewed NetKingdom security capabilities 2026-10-14 06:46:53 +02:00
runners Prepare receipt-bound audit E2 third attempt 2026-08-22 23:23:48 +02:00
schemas Classify I and A as mechanical and calibrate V observations offline. 2026-10-04 11:15:01 +02:00
src/whitehat_security Classify I and A as mechanical and calibrate V observations offline. 2026-10-04 11:15:01 +02:00
targets Record the rapp-postgres file grant that still leaves live E3 blocked. 2026-10-04 12:09:58 +02:00
tests Keep layer declaration separate from dated observer evidence 2026-10-11 02:22:08 +02:00
tools Record the offline disposition of Emergent knowledge 0.2.6. 2026-10-04 02:38:29 +02:00
workplans Keep layer declaration separate from dated observer evidence 2026-10-11 02:22:08 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-10-04 12:10:54 +02:00
.gitignore Build authorization-gated tenancy evidence harness 2026-08-21 23:53:27 +02:00
.repo-classification.yaml Register whitehat-security and align operating boundaries 2026-08-21 22:52:37 +02:00
AGENTS.md docs(agents): repoint remote State Hub URL to the in-cluster address 2026-08-25 00:22:21 +02:00
INTENT.md Keep layer declaration separate from dated observer evidence 2026-10-11 02:22:08 +02:00
Makefile Classify I and A as mechanical and calibrate V observations offline. 2026-10-04 11:15:01 +02:00
pyproject.toml Build authorization-gated tenancy evidence harness 2026-08-21 23:53:27 +02:00
README.md State the harness scope and calibrate E4 and R4 offline. 2026-10-04 08:54:40 +02:00
SCOPE.md Keep layer declaration separate from dated observer evidence 2026-10-11 02:22:08 +02:00
WORK-RECORDS.md Record the hub identifiers for blocked WHITEHAT-WP-0012. 2026-10-04 11:17:28 +02:00

README.md

whitehat-security

NetKingdom's offensive security facility. It calibrates adversarial probes offline and admits a live run only under a complete engagement record. No live target is authorized by the repository itself.

The estate's adversarial evidence facility: it can test whether a claimed boundary holds, and today that capability is the offline harness plus one terminal historical audit-core E2 pass. It does not run on a schedule.

It exists because a repo testing its own boundary grades its own homework. The probes most worth having are the ones an author would not think to write.

  • Independent in operation. It does not take a declared posture as true. NetKingdom owns both the security canon and this facility, so findings leave through risk-nexus under separate ownership rather than being resolved here.

  • It finds; it does not fix. Findings route to risk-nexus, which owns severity and disclosure. The repo that owns the defect owns the repair.

  • A pass means the attacks we tried did not work — not that the boundary holds. Reports say so.

  • Intent: INTENT.md

  • Scope: SCOPE.md

  • Workplans: workplans/

  • Attacker model: docs/attacker-model.md

  • Rules of engagement (accepted; live targets still require engagement approval): docs/rules-of-engagement.md

  • Operator runbook: docs/operator-runbook.md

  • Session cutoff and redesign handoff: docs/session-cutoff-2026-08-22.md

  • Governed test plane: docs/test-plane.md

  • Target registrations: targets/

  • Target packs: probe-packs/

Offline calibration

make check
make fixture-evidence

This proves that every current differential probe, including the audit-core shaped pack, passes an enforcing fixture and detects the corresponding missing-tenant-predicate fixture. It sends no network traffic and is not evidence about a target service. Live execution requires a current target-specific record, a registered applicable target, and plane admission. See docs/test-plane.md.