Open security core for dev sec ops on kubernetes
tegwick
cb32f6d68c
An earlier revision of this section asserted the adversarial facility was deliberately not NetKingdom's, on independence grounds. Overruled, and the counter-argument is better: offensive security is security work. The facility is also framed more broadly than this document assumed - it is pointed at infrastructure we choose, our own estate among them, and testing conformance to this framework is one use of a general capability rather than its purpose. The tension I raised is left in the text rather than deleted, because it is real: NetKingdom now owns both this framework and the facility that tests conformance to it. The mitigation is that findings leave for risk-nexus under separate ownership instead of being closed in place, and the trigger to revisit is conformance findings starting to close quietly. 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.