7. Disconnected and Air-Gapped Operations

Go to Crucible

Disconnected and Air-Gapped Operations describe how Crucible supports lifecycle activities when required external resources are unavailable through direct network access.

A Disconnected Environment operates without continuous access to one or more external resources needed by the selected lifecycle activity.

An Air-Gapped Environment enforces physical, logical, or procedural separation from external networks and systems.

Crucible prepares the artifacts, dependencies, compliance information, and associated records required for operation within those environments. Authorized personnel and approved transfer mechanisms move the prepared content across the applicable security or connectivity boundary.

Disconnected and Air-Gapped Operations can include:

• Identifying and capturing required dependencies
• Preserving captured dependencies in a controlled form
• Producing a Transfer Bundle
• Transferring the bundle through an authorized process
• Importing and verifying the bundle
• Populating Offline Repositories
• Rebuilding and deploying within the destination environment
• Preserving associations and traceability across environments

The operational sequence does not permit Crucible to bypass a Security Domain restriction, information-handling rule, transfer authorization, or access-control decision.

The applicable leaf requirements in Annex C: Requirements define the required behavior. Each child page identifies and transcludes the canonical requirement Statements that support the activity described.

• 7.1 Capture and Preserve Dependencies
• 7.2 Produce the Transfer Bundle
• 7.3 Transfer Across the Boundary
• 7.4 Import the Transfer Bundle
• 7.5 Populate Offline Repositories
• 7.6 Rebuild and Deploy
• 7.7 Preserve Traceability Across Environments

The child pages describe only operational behavior supported by approved leaf requirements.

Requirements remain canonical in Annex C: Requirements and SHALL NOT be duplicated on these pages.