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.
92 commits 1 branch 0 tags 1.1 MiB
Find a file
tegwick db32a4174f Record the offline disposition of Emergent knowledge 0.2.6. 
The sealed digest passes the calibrated library probes. The recorded corpus
shows no unsafe effect, and the zones and model-switch routes match the
fixture. RISK-F-0015 and EMERGENT-WP-0002-T07 stay with their owners.

Assistant: grok
Assistant-Session: 01a10450-dda4-7253-91a9-b8dccb2f0173
2026-10-04 02:38:29 +02:00
docs Promote ASM T-01–T-10 into WHITEHAT-WP-0007 and triage each test 2026-09-02 01:11:16 +02:00
engagements Record the audit-core E2-03 target pass and close T03/T07 2026-08-23 00:42:31 +02:00
evidence Record the offline disposition of Emergent knowledge 0.2.6. 2026-10-04 02:38:29 +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
runners Prepare receipt-bound audit E2 third attempt 2026-08-22 23:23:48 +02:00
schemas Promote ASM T-01–T-10 into WHITEHAT-WP-0007 and triage each test 2026-09-02 01:11:16 +02:00
src/whitehat_security Add in-process known-bad fixtures for remaining ASM T-01–T-10 2026-09-02 13:05:42 +02:00
targets Add in-process known-bad fixtures for remaining ASM T-01–T-10 2026-09-02 13:05:42 +02:00
tests Apply GH-DEC-2026-017 and GH-DEC-2026-020 to the layer declaration. 2026-09-21 09:36:53 +02:00
tools Record the offline disposition of Emergent knowledge 0.2.6. 2026-10-04 02:38:29 +02:00
workplans Record the offline disposition of Emergent knowledge 0.2.6. 2026-10-04 02:38:29 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-10-03 19:59:27 +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 Apply GH-DEC-2026-017 and GH-DEC-2026-020 to the layer declaration. 2026-09-21 09:36:53 +02:00
Makefile Add in-process known-bad fixtures for remaining ASM T-01–T-10 2026-09-02 13:05:42 +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 Record the offline disposition of Emergent knowledge 0.2.6. 2026-10-04 02:38:29 +02:00
WORK-RECORDS.md Refresh the work-record index for finished WHITEHAT-WP-0009. 2026-10-03 19:59:40 +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.