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.
82 commits 1 branch 0 tags 868 KiB
Find a file
tegwick b5cc6706b9 Apply GH-DEC-2026-017 and GH-DEC-2026-020 to the layer declaration. 
This repository never received GH-DEC-2026-017 (gate-house's gap, recorded
in GH-DEC-2026-020), so both rulings land here together.

- INTENT.md frontmatter: remove standard_version: "0.7" (017 section 5) and
  de-version the standard: path to net-kingdom/canon/standards/
  security-layer-model (020 section 1). layer: Staff is unchanged and
  INTENT.md remains the declaration (017 section 1); no layer.yaml added.
- tests/test_layer_declaration.py: stop asserting the old
  standard_version; case-fold the layer comparison (017 section 2); fail if
  any frontmatter key or value carries a standard or companion version,
  including a versioned standard: path or companion_version (020 sections
  1-2); comments are not reached. Known-bad forms are exercised.

conformance_state is left untouched pending gate-house's open question.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 63291@bnt-lap001
Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703
2026-09-21 09:36:53 +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 Add in-process known-bad fixtures for remaining ASM T-01–T-10 2026-09-02 13:05:42 +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
workplans Classify open workplans with flavor (CUST-WP-0072). 2026-09-14 15:50:50 +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 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 Finish WHITEHAT-WP-0007 and own live ASM residuals in WP-0008 2026-09-02 15:43:07 +02:00
WORK-RECORDS.md chore(registrar): assign State Hub identifiers 2026-09-02 15:47:24 +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.