coulomb/whitehat-security
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Automated white hat it-security, pen-testing and isolation-probing.
70 commits 1 branch 0 tags 706 KiB
Find a file
Exact
repo-manager dea2477492 repo.work.close_intake WHITEHAT-IN-0001 
correlation_id: 90a20f2b-e027-4d55-b0dd-c97c75fccd15
reason: Declared Staff in INTENT.md in this repository's own voice. gate-house may specify the invariant; it does not author our probes.
source: repo-manager

Assistant: grok
Assistant-Session: 01a05e32-c776-72a3-86ec-c490e027aca9
2026-09-01 21:00:23 +02:00
docs Finish WHITEHAT-WP-0001 and own live residuals in WP-0006 2026-09-01 20:26:47 +02:00
engagements Record the audit-core E2-03 target pass and close T03/T07 2026-08-23 00:42:31 +02:00
evidence Finish WHITEHAT-WP-0001 and own live residuals in WP-0006 2026-09-01 20:26:47 +02:00
intakes repo.work.close_intake WHITEHAT-IN-0001 2026-09-01 21:00:23 +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
runners Prepare receipt-bound audit E2 third attempt 2026-08-22 23:23:48 +02:00
schemas Add WHITEHAT-WP-0002 receipt example, CLI coverage, and abort records 2026-08-22 21:40:33 +02:00
src/whitehat_security Finish WHITEHAT-WP-0001 and own live residuals in WP-0006 2026-09-01 20:26:47 +02:00
targets Record the audit-core E2-03 target pass and close T03/T07 2026-08-23 00:42:31 +02:00
tests Declare Staff in INTENT.md and record WP-0001 DoD-Ok 2026-09-01 20:49:53 +02:00
workplans Record DoD-Ok on WHITEHAT-WP-0002 through 0005 2026-09-01 20:52:54 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-09-01 20:51:37 +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 Declare Staff in INTENT.md and record WP-0001 DoD-Ok 2026-09-01 20:49:53 +02:00
Makefile Finish WHITEHAT-WP-0001 and own live residuals in WP-0006 2026-09-01 20:26:47 +02:00
pyproject.toml Build authorization-gated tenancy evidence harness 2026-08-21 23:53:27 +02:00
README.md Add governed test plane and close T04/T08 2026-08-22 00:44:21 +02:00
SCOPE.md Declare Staff in INTENT.md and record WP-0001 DoD-Ok 2026-09-01 20:49:53 +02:00
WORK-RECORDS.md Record DoD-Ok on WHITEHAT-WP-0002 through 0005 2026-09-01 20:52:54 +02:00

README.md

whitehat-security

NetKingdom's offensive security facility. Automated white hat IT-security, pen-testing and isolation-probing — pointed at infrastructure we choose, including our own.

The estate's adversarial evidence facility: it attacks our own systems, on a schedule, to find out whether the security properties they claim are actually true.

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.