--- id: capability.security.practice-canon owner: security-canon status: draft domain: infotech maturity: discovery: current: D3 target: D5 confidence: medium rationale: Owner scope, neighboring responsibilities, concrete use cases and limitations are documented; no exhaustive or generalized maturity claim. availability: current: A0 target: A0 confidence: medium rationale: 'Source interface assessed 2026-10-14: Versioned SEC-DSM and Mode of Authority documents. Availability describes the delivery form, not production acceptance. Normative practice; no runtime control or certification.' external_evidence: completeness: level: C1 confidence: low basis: Source artifacts establish a bounded capability; no independent consumer-completeness assessment in this review. reliability: level: R0 confidence: low basis: No longitudinal consumer reliability measurement established by this review. name: Security practice and authority vocabulary summary: Versioned SEC-DSM and Mode of Authority documents. tags: - security - netkingdom - framework-reuse discovery: intent: Versioned SEC-DSM and Mode of Authority documents includes: - Versioned SEC-DSM and Mode of Authority documents excludes: - Normative practice; no runtime control or certification use_cases: - 'U01: Architect composes a security deployment from explicit owner contracts and case types' - 'U07: Owner inventories, rotates, revokes and detects exposure of credentials' - 'U10: Operator recovers identity, custody or data with independently held recovery material' - 'U14: Framework adopter validates and reuses selected contracts, tools and reference compositions' availability: current_level: A0 target_level: A0 current_artifacts: - SCOPE.md - infospace/standards/devops-secrets-management/SecurityCanonDevOpsSecretsManagementStandard.md consumption_modes: - informational relations: related_to: - capability.security.iam-tooling-suite evidence: documentation: - SCOPE.md - infospace/standards/devops-secrets-management/SecurityCanonDevOpsSecretsManagementStandard.md consumer_guidance: recommended_for: - Architect composes a security deployment from explicit owner contracts and case types - Owner inventories, rotates, revokes and detects exposure of credentials - Operator recovers identity, custody or data with independently held recovery material - Framework adopter validates and reuses selected contracts, tools and reference compositions not_recommended_for: - Normative practice; no runtime control or certification known_limitations: - Normative practice; no runtime control or certification - 2026-10-14 architecture review estimates operational maturity separately; a registry entry does not authorize execution or establish deployment. --- # Security practice and authority vocabulary Versioned SEC-DSM and Mode of Authority documents. ## Reuse boundary Normative practice; no runtime control or certification. ## Supported use cases - U01: Architect composes a security deployment from explicit owner contracts and case types - U07: Owner inventories, rotates, revokes and detects exposure of credentials - U10: Operator recovers identity, custody or data with independently held recovery material - U14: Framework adopter validates and reuses selected contracts, tools and reference compositions ## Evidence and integration - [SCOPE.md](../../SCOPE.md) - [infospace/standards/devops-secrets-management/SecurityCanonDevOpsSecretsManagementStandard.md](../../infospace/standards/devops-secrets-management/SecurityCanonDevOpsSecretsManagementStandard.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.