net-kingdom/canon/standards
tegwick cb32f6d68c Correct question 3: whitehat is NetKingdom's
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>
2026-08-17 18:01:17 +02:00
..
credential-management_v0.2.md Add OpenBao runtime secret authority; complete NK-WP-0006/0007/0008 2026-05-20 22:51:20 +02:00
iam-profile_v0.2.md Ratify tenant grouping identifiers 2026-07-27 20:39:12 +02:00
iam-profile_v0.3.md ADR-0014 + tenant-engine boundary contract + IAM Profile v0.3 2026-07-23 21:45:37 +02:00
playbook-capability-contract_v0.1.md Implement NK-WP-0013 playbook capability contract 2026-05-22 14:49:25 +02:00
tenancy-posture_v0.1.md Correct question 3: whitehat is NetKingdom's 2026-08-17 18:01:17 +02:00
tenant-engine-boundary-contract_v0.1.md ADR-0014 + tenant-engine boundary contract + IAM Profile v0.3 2026-07-23 21:45:37 +02:00
user-engine-boundary-contract_v0.1.md docs: persist user-engine vs net-kingdom integration assessment (new doc + cross-references in SCOPE, boundary contract, guidance, responsibility map, 0018/0019 workplans). Also updated user-engine integration doc to reference it. 2026-06-03 10:33:31 +02:00