Navigation

Book Creator
Add this page to your book

Book Creator
Remove this page from your book

This is an old revision of the document!

Annex D maps the canonical leaf requirements in Annex C: Requirements to the Crucible pages that reference them.

Annex C remains the canonical source for requirement titles, Statements, rationale, and verification information. Annex D provides traceability links and coverage information without restating or redefining the requirements.

The Requirements Traceability Index lists the canonical leaf requirements alphabetically by title.

The Requirement Title column links to the canonical requirement page. The Referenced By column identifies the Crucible pages that link to that requirement.

A requirement with no references requires review to determine whether:

The requirement lacks ConOps coverage
The requirement belongs outside the ConOps
The requirement represents a future capability
The requirement page or backlink is incomplete
The requirement requires an additional operational page

Requirement Title	Referenced By
FR-COMP-009c — Authorization to Operate Evidence	5.4 Assess Compliance 5.7 Preserve Evidence and Lifecycle Records 6.1 Construct and Assess the Environment 8.4 Generate Supporting Evidence Annex D: Requirements Traceability
FR-BAS-001 — Consume Baseline Repositories from a Workspace	5.1 Select and Compose Baselines Annex D: Requirements Traceability
FR-BAS-002 — Compose Selected Baselines	5.1 Select and Compose Baselines Annex D: Requirements Traceability
FR-BAS-003 — Process Predeployment and Postdeployment Steps	5.1 Select and Compose Baselines Annex D: Requirements Traceability
FR-BAS-004 — Perform Noninteractive Workspace Execution	5.1 Select and Compose Baselines Annex D: Requirements Traceability
OR-003a — Classified Environment Operations	3.3 Security Domains and Transfer Boundaries Annex D: Requirements Traceability
FR-UI-002 — Command-Line Interface	9.2 Command-Line Interface C.3.11 Crucible Interfaces Annex D: Requirements Traceability
FR-COMP-001 — Compliance Baseline Definitions	5.4 Assess Compliance 6.1 Construct and Assess the Environment 8.1 Select Compliance Criteria and Baselines Annex D: Requirements Traceability
FR-COMP-004 — Compliance Evidence Artifacts	5.4 Assess Compliance 6.1 Construct and Assess the Environment 8.4 Generate Supporting Evidence Annex D: Requirements Traceability
FR-COMP-010a — Compliance Finding Transfer Bundle Inclusion	5.4 Assess Compliance 5.7 Preserve Evidence and Lifecycle Records 6.1 Construct and Assess the Environment 7.2 Produce the Transfer Bundle 8.5 Transfer Compliance Findings Annex D: Requirements Traceability
FR-COMP-010b — Compliance Finding Association Preservation	5.4 Assess Compliance 5.7 Preserve Evidence and Lifecycle Records 6.1 Construct and Assess the Environment 7.7 Preserve Traceability Across Environments 8.5 Transfer Compliance Findings Annex D: Requirements Traceability
FR-COMP-003 — Compliance Reporting	5.4 Assess Compliance 6.1 Construct and Assess the Environment 8.3 Produce Compliance Reports Annex D: Requirements Traceability
FR-COMP-008a — Compliance Scanning Abstraction	5.4 Assess Compliance 6.1 Construct and Assess the Environment 8.2 Perform Compliance Assessments Annex D: Requirements Traceability
FR-COMP-002 — Compliance Scanning Tool Integration	5.4 Assess Compliance 6.1 Construct and Assess the Environment 8.2 Perform Compliance Assessments Annex D: Requirements Traceability
FR-IMG-002 — Build Container Images	5.2 Construct Images 6.1 Construct and Assess the Environment 7.6 Rebuild and Deploy Annex D: Requirements Traceability
OR-003f — Cross-Domain Transfer Control	3.3 Security Domains and Transfer Boundaries 4.1 Human Actors 7.3 Transfer Across the Boundary 7.4 Import the Transfer Bundle Annex D: Requirements Traceability
FR-COMP-007 — Custom Compliance Frameworks	5.4 Assess Compliance 6.1 Construct and Assess the Environment 8.1 Select Compliance Criteria and Baselines Annex D: Requirements Traceability
FR-DEPC-001 — Capture Build Dependencies	5.3 Capture and Preserve Dependencies 7.1 Capture and Preserve Dependencies Annex D: Requirements Traceability
FR-DEPC-002 — Preserve Dependencies in a Dependency Store	5.3 Capture and Preserve Dependencies 7.1 Capture and Preserve Dependencies Annex D: Requirements Traceability
FR-DEPC-005 — Dependency Store Implementation Independence	5.3 Capture and Preserve Dependencies 7.1 Capture and Preserve Dependencies Annex D: Requirements Traceability
FR-DEP-001 — Deploy Infrastructure Resources	3.2 Deployment Environments 5.5 Deploy the Environment 6.2 Deploy in a Connected Environment 7.6 Rebuild and Deploy Annex D: Requirements Traceability
FR-DEP-004 — Deploy Containerized Workloads	3.2 Deployment Environments 5.5 Deploy the Environment 6.2 Deploy in a Connected Environment 7.6 Rebuild and Deploy Annex D: Requirements Traceability
FR-DEP-003 — Deploy Kubernetes Clusters	3.2 Deployment Environments 5.5 Deploy the Environment 6.2 Deploy in a Connected Environment 7.6 Rebuild and Deploy Annex D: Requirements Traceability
FR-DEP-005 — Deploy Platform Services	3.2 Deployment Environments 5.5 Deploy the Environment 6.2 Deploy in a Connected Environment 7.6 Rebuild and Deploy Annex D: Requirements Traceability
FR-DEP-002 — Deploy Virtual Machines	3.2 Deployment Environments 5.5 Deploy the Environment 6.2 Deploy in a Connected Environment 7.6 Rebuild and Deploy Annex D: Requirements Traceability
FR-DEP-007 — Deployment Validation	5.6 Validate the Result Annex D: Requirements Traceability
FR-COMP-005 — DISA STIG Compliance Baselines	5.4 Assess Compliance 6.1 Construct and Assess the Environment 8.1 Select Compliance Criteria and Baselines Annex D: Requirements Traceability
FR-MC-005 — Edge Deployments	3.2 Deployment Environments 5.5 Deploy the Environment 6.2 Deploy in a Connected Environment Annex D: Requirements Traceability
FR-COMP-006 — FedRAMP Baseline Definitions	5.4 Assess Compliance 6.1 Construct and Assess the Environment 8.1 Select Compliance Criteria and Baselines Annex D: Requirements Traceability
FR-MC-004 — Hybrid-Cloud Deployments	3.2 Deployment Environments 5.5 Deploy the Environment 6.2 Deploy in a Connected Environment Annex D: Requirements Traceability
FR-IMG-006 — Image Promotion Workflows	5.2 Construct Images 6.1 Construct and Assess the Environment Annex D: Requirements Traceability
FR-IMG-004 — Image Signing	5.2 Construct Images 6.1 Construct and Assess the Environment Annex D: Requirements Traceability
FR-IMG-005 — Image Verification	5.2 Construct Images 6.1 Construct and Assess the Environment Annex D: Requirements Traceability
FR-IMG-003 — Immutable Infrastructure Workflows	5.2 Construct Images 6.1 Construct and Assess the Environment Annex D: Requirements Traceability
OR-003e — Information Handling Rule Enforcement	3.3 Security Domains and Transfer Boundaries 4.1 Human Actors 7.3 Transfer Across the Boundary 7.4 Import the Transfer Bundle Annex D: Requirements Traceability
FR-COMP-008b — Multiple Operating-System Support	5.4 Assess Compliance 6.1 Construct and Assess the Environment 8.2 Perform Compliance Assessments Annex D: Requirements Traceability
FR-DEPC-004 — Populate Offline Repositories	5.3 Capture and Preserve Dependencies 7.5 Populate Offline Repositories 7.6 Rebuild and Deploy Annex D: Requirements Traceability
FR-MC-001 — Cloud Provider Abstraction	3.2 Deployment Environments 5.5 Deploy the Environment 6.2 Deploy in a Connected Environment Annex D: Requirements Traceability
FR-MC-003 — Deployment Portability Across Cloud Providers	3.2 Deployment Environments 5.5 Deploy the Environment 6.2 Deploy in a Connected Environment Annex D: Requirements Traceability
FR-MC-002 — Provider-Specific Extensions	3.2 Deployment Environments 5.5 Deploy the Environment 6.2 Deploy in a Connected Environment Annex D: Requirements Traceability
FR-COMP-009b — Risk Management Framework Evidence	5.4 Assess Compliance 5.7 Preserve Evidence and Lifecycle Records 6.1 Construct and Assess the Environment 8.4 Generate Supporting Evidence Annex D: Requirements Traceability
OR-003g — Security Domain Access Control	3.3 Security Domains and Transfer Boundaries 4.1 Human Actors 4.3 External Systems Annex D: Requirements Traceability
OR-003d — Security Domain Information Enforcement	3.3 Security Domains and Transfer Boundaries 4.1 Human Actors 4.3 External Systems 7.3 Transfer Across the Boundary 7.4 Import the Transfer Bundle Annex D: Requirements Traceability
OR-003c — Security Domain Resource Enforcement	3.3 Security Domains and Transfer Boundaries 4.1 Human Actors 4.3 External Systems Annex D: Requirements Traceability
FR-COMP-009a — Security Control Traceability Matrix Evidence	5.4 Assess Compliance 5.7 Preserve Evidence and Lifecycle Records 6.1 Construct and Assess the Environment 8.4 Generate Supporting Evidence Annex D: Requirements Traceability
FR-UI-001 — Shared Interface Operations	9.1 Shared Interface Operations C.3.11 Crucible Interfaces Annex D: Requirements Traceability
FR-DEPC-003 — Produce a Transfer Bundle	5.3 Capture and Preserve Dependencies 7.2 Produce the Transfer Bundle Annex D: Requirements Traceability
OR-003b — Unclassified Environment Operations	3.3 Security Domains and Transfer Boundaries Annex D: Requirements Traceability
FR-IMG-001 — Build Virtual Machine Images	5.2 Construct Images 6.1 Construct and Assess the Environment 7.6 Rebuild and Deploy Annex D: Requirements Traceability
FR-UI-003 — Web-Based User Interface	9.3 Web-Based User Interface C.3.11 Crucible Interfaces Annex D: Requirements Traceability

Each requirement title is displayed from the canonical requirement page
Do not add custom display text to requirement links
Confirm the canonical page title and namespace for each requirement
Add every remaining Annex C leaf requirement
Exclude true parent requirements that contain child requirements
Retain start for leaf requirements implemented as namespace index pages
Sort the completed table alphabetically by the displayed canonical page title
Treat a requirement with no returned backlinks as requiring coverage review

Confirm each displayed title against the canonical requirement page
Add every remaining Annex C leaf requirement
Exclude parent requirements that contain child requirements
Retain start for leaf requirements implemented as namespace index pages
Sort the final table alphabetically by canonical displayed title
A requirement with no returned backlinks requires coverage review

Include only canonical leaf requirements
Treat a requirement implemented as a namespace start page as a leaf when it has no child requirements
Exclude parent requirements that have leaf children
Link each requirement title to its canonical Annex C page
Sort the Requirements Traceability Index alphabetically by displayed title
Identify every Crucible page that directly references the requirement
Do not copy or paraphrase the canonical requirement Statement
Record requirements without references as uncovered until reviewed
Record ConOps pages without supporting requirements as unsupported until reviewed

Detailed traceability pages can use the following coverage statuses:

Status	Meaning
Complete	The referenced Crucible content provides operational coverage consistent with the requirement Statement
Partial	The referenced content addresses only part of the requirement Statement
Not Covered	No current Crucible page provides identifiable coverage
Outside ConOps Scope	The requirement applies to another specification, design, implementation, verification, or governance artifact
Future Capability	The requirement applies to a capability outside the current operational baseline
Review Required	The available requirement or coverage information is insufficient to determine the appropriate status

Annex E: Issues records problems discovered during traceability review.

Examples include:

A requirement without operational coverage
A ConOps capability without a supporting requirement
A requirement that requires further decomposition
An ambiguous or incomplete requirement Statement
An incorrect parent or leaf classification
A missing requirement page
An inconsistent requirement namespace or title
A proposed future capability

Annex D records the traceability condition. Annex E records the issue and its resolution status.

Populate the Requirements Traceability Index only after confirming the complete Annex C leaf-requirement inventory.

Do not list true parent requirements when their leaf children provide the normative Statements.

Where a leaf requirement uses a namespace start page for numerical ordering, link to the actual start page.

The Referenced By column should derive from direct links to the canonical requirement page wherever the available DokuWiki backlink mechanism permits dynamic generation.