net-kingdom/registry/capabilities/capability.security.iam-tooling-suite.md
tegwick e99c3e9791
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s
docs(reuse): establish reviewed NetKingdom security capabilities
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a137ca-5c77-7a71-b9ae-23ad9b0b5684
2026-10-14 06:40:30 +02:00

133 lines
4.8 KiB
Markdown

---
id: capability.security.iam-tooling-suite
name: NetKingdom security architecture and conformance tooling
summary: Versioned IAM, layer, tenancy and credential contracts plus validators.
owner: net-kingdom
status: draft
domain: infotech
tags:
- security
- iam
- kubernetes
- conformance
- netkingdom
- framework-reuse
maturity:
discovery:
current: D3
target: D5
confidence: medium
rationale: SCOPE plus docs/secrets-engine-security-infrastructure-boundary.md
describe an explicit integration boundary with OpenBao, flex-auth, user-engine,
ops-warden, ops-bridge, info-tech-canon, and State Hub; canon/standards/ holds
versioned IAM v0.3, playbook capability, scenario composition, tenancy, zone,
and boundary standards that provider repos implement against.
availability:
current: A2
target: A3
confidence: medium
rationale: 'Source interface assessed 2026-10-14: Versioned IAM, layer, tenancy
and credential contracts plus validators. Availability describes the delivery
form, not production acceptance. Mixed accepted and proposed standards; framework
integration remains incomplete.'
external_evidence:
completeness:
level: C1
confidence: low
basis: scope_vs_intent_and_consumer_expectations
satisfied_expectations:
- versioned canon standards already implemented by a sibling repo (key-cape)
- documented, runnable conformance, posture, composition, and bootstrap tools
under tools/
broken_expectations: []
out_of_scope_expectations: []
reliability:
level: R1
confidence: low
basis: consumer_quality_signals
known_reliability_risks:
- no top-level packaging; each tool under tools/ has its own runtime dependencies,
no unified install path yet
discovery:
intent: Versioned IAM, layer, tenancy and credential contracts plus validators
includes:
- Versioned IAM, layer, tenancy and credential contracts plus validators
excludes:
- Mixed accepted and proposed standards; framework integration remains incomplete
assumptions: []
use_cases:
- 'U01: Architect composes a security deployment from explicit owner contracts and
case types'
- 'U02: Human signs in with MFA and manages account or factor recovery'
- 'U03: Application combines identity, tenant and resource facts and enforces a
bound decision'
- 'U14: Framework adopter validates and reuses selected contracts, tools and reference
compositions'
research_memos: []
availability:
current_level: A2
target_level: A3
current_artifacts:
- SCOPE.md
- SECURITY-COMPANION.md
target_artifacts: []
consumption_modes:
- CLI
- source
relations:
depends_on: []
supports: []
related_to:
- capability.security.practice-canon
- capability.security.doctrine-review
- capability.iam.key-cape
- capability.authorization.policy-evaluate
- capability.registry.register
evidence:
documentation:
- SCOPE.md
- SECURITY-COMPANION.md
tests:
- tools/iam-profile-conformance (pytest fixtures)
consumer_feedback: []
bug_reports: []
incidents: []
consumer_guidance:
recommended_for:
- Architect composes a security deployment from explicit owner contracts and case
types
- Human signs in with MFA and manages account or factor recovery
- Application combines identity, tenant and resource facts and enforces a bound
decision
- Framework adopter validates and reuses selected contracts, tools and reference
compositions
not_recommended_for:
- Mixed accepted and proposed standards; framework integration remains incomplete
known_limitations:
- Mixed accepted and proposed standards; framework integration remains incomplete
- 2026-10-14 architecture review estimates operational maturity separately; a registry
entry does not authorize execution or establish deployment.
promotion_history: []
---
# NetKingdom security architecture and conformance tooling
Versioned IAM, layer, tenancy and credential contracts plus validators.
## Reuse boundary
Mixed accepted and proposed standards; framework integration remains incomplete.
## Supported use cases
- U01: Architect composes a security deployment from explicit owner contracts and case types
- U02: Human signs in with MFA and manages account or factor recovery
- U03: Application combines identity, tenant and resource facts and enforces a bound decision
- U14: Framework adopter validates and reuses selected contracts, tools and reference compositions
## Evidence and integration
- [SCOPE.md](../../SCOPE.md)
- [SECURITY-COMPANION.md](../../SECURITY-COMPANION.md)
Assessment: CUST-WP-0081, 2026-10-14. Relations identify interfaces to compose; they do not certify native integration. Existing external evidence levels are retained where present. New entries use conservative C1/R0 until consumer assessment exists.