Open security core for dev sec ops on kubernetes
whitehat-security takes the adversarial evidence artifacts - the framework's highest-severity gap, unowned since it was drafted. audit-core and tenant-engine were right to decline it as fleet-scope work; the answer was a home of its own rather than a volunteer. Recorded here with the part that bears on this document: the facility is deliberately not owned by NetKingdom, which owns this framework. Verifying conformance to a standard while reporting to the standard's owner is self-grading one level up. Two consequences land back on the framework. Cadence becomes a security parameter rather than a schedule, since for a detection-based control the interval between runs is the exposure window. And a passing suite is proof that the attacks attempted did not work, not proof of isolation - recording a green run as "E2 verified" would be exactly the overclaim section 6 prohibits. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .claude | ||
| .forgejo/workflows | ||
| .githooks | ||
| canon | ||
| docs | ||
| examples | ||
| history | ||
| identity-provisioner | ||
| keys | ||
| local-identity | ||
| registry | ||
| sso-mfa | ||
| tests | ||
| tools | ||
| wiki | ||
| workplans | ||
| .custodian-brief.md | ||
| .gitignore | ||
| .repo-classification.yaml | ||
| .sops.yaml | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| CONFIG.md | ||
| DECISIONS.md | ||
| INTENT.md | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| SCOPE.md | ||
| WORK-RECORDS.md | ||
NetKingdom
NetKingdom provides a dynamic self optimizing full circle security-platform for kubernetes deployed IT-infrastructures.
Orientation
- SCOPE.md — what this repo owns, current state, and when it is relevant
Security Infrastructure Documents
- secrets-engine security infrastructure boundary defines how secrets-engine participates in the NetKingdom security infrastructure and how it interacts with OpenBao, flex-auth, user-engine, ops-warden, ops-bridge, info-tech-canon, State Hub, and agents.