6. Connected Operations

Go to Crucible

Connected Operations describe how Crucible performs lifecycle activities when the operating environment can access authorized external systems and resources through available network connections.

A Connected Environment can provide access to source repositories, software repositories, image registries, assessment services, deployment providers, and other approved resources required by the selected operation.

Connectivity does not remove security, authorization, integrity, provenance, or traceability controls. Crucible uses only authorized sources and preserves the identity and revision of the inputs used during each lifecycle activity.

Connected Operations can include:

• Accessing authorized source and artifact repositories
• Retrieving selected Baselines, Images, packages, and Dependencies
• Constructing Images and other controlled artifacts
• Performing Compliance Assessments
• Deploying resources to an authorized Deployment Target
• Validating the resulting environment
• Generating the applicable Evidence and lifecycle records

The selected lifecycle activity determines which connected resources Crucible requires. An available network connection does not authorize unrestricted access to an external resource.

Connected Operations can also prepare artifacts and Dependencies for later use in a Disconnected Environment or Air-Gapped Environment. Section 7. Disconnected and Air-Gapped Operations describes those operations.

• 6.1 Construct and Assess the Environment
• 6.2 Deploy in a Connected Environment

The child pages describe connected operational behavior and identify the applicable canonical leaf requirements from Annex C: Requirements.