7.4 Import the Transfer Bundle [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 7.4 Import the Transfer Bundle ======

[[dido:02-crusible:07-disconnected-and-air-gapped-operations:start|Go to 7. Disconnected and Air-Gapped Operations]]

After an authorized transfer reaches the destination environment, [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] imports the identified [[dido:99_annexes:annex-b-terms-and-definitions:t:transfer_bundle|Transfer Bundle]] into the applicable [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]] or [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environment]].

Import makes approved bundle content available for subsequent repository population, construction, assessment, deployment, or validation. Import does not independently authorize use of every item contained in the bundle.

===== Receive the Transfer Bundle =====

Crucible receives the Transfer Bundle through the approved destination-side transfer process.

The received bundle remains associated with:

  * The Transfer Bundle identifier
  * The source environment
  * The destination environment
  * The source Security Domain
  * The destination Security Domain
  * The authorized transfer activity
  * The intended destination lifecycle activity
  * The available integrity information

Crucible does not treat unidentified content or an unassociated collection of files as the approved Transfer Bundle.

===== Apply Destination Controls =====

The destination Security Domain applies its access restrictions, information-handling rules, and import controls to the received bundle.

Destination controls can determine:

  * Whether the bundle can enter the destination environment
  * Whether the receiving actor can perform the import
  * Which bundle content the destination can accept
  * Which content requires additional review
  * Which information must remain restricted
  * Whether the bundle requires inspection or verification
  * Whether the destination can use the imported content

A successful transfer across the boundary does not require the destination environment to accept or use the bundle.

===== Verify Bundle Identity and Integrity =====

Crucible verifies that the received bundle corresponds to the Transfer Bundle selected for import.

Verification can include:

  * Confirmation of the Transfer Bundle identifier
  * Comparison of the received content with the recorded integrity value
  * Verification of an associated Digital Signature
  * Confirmation of the expected bundle representation
  * Confirmation of required bundle metadata
  * Confirmation of the intended destination environment

An integrity mismatch, missing identifier, invalid signature, or unexpected bundle representation prevents Crucible from treating the received content as the verified Transfer Bundle.

A successful integrity verification establishes that the evaluated bundle corresponds to the expected representation. It does not independently establish that every included item is compliant, approved, or suitable for use.

===== Inspect the Bundle Contents =====

Crucible identifies the content and relationships represented within the verified Transfer Bundle.

The bundle can include:

  * Captured direct Dependencies
  * Captured transitive Dependencies
  * Dependency metadata
  * Content intended for Offline Repositories
  * Compliance Findings
  * Associations between Compliance Findings and the artifacts they describe
  * Integrity information
  * Other content required by the approved destination activity

The import activity preserves the identity of each included item and does not merge unrelated content into a single unidentified artifact.

===== Preserve Included Associations =====

Crucible preserves the relationships represented by the Transfer Bundle during import.

These relationships can associate:

  * A Dependency with its version or revision
  * A Dependency with its original source
  * A direct Dependency with its transitive Dependencies
  * An artifact with its associated Compliance Findings
  * A Compliance Finding with the subject assessed
  * Included content with the destination activity that requires it
  * An imported item with the Transfer Bundle that carried it

Import does not change the recorded meaning or status of a Compliance Finding.

===== Handle Import Exceptions =====

Crucible records conditions that prevent successful import.

Import exceptions can include:

  * An unidentified Transfer Bundle
  * An integrity mismatch
  * An invalid Digital Signature
  * Missing bundle metadata
  * Missing required content
  * Content prohibited by destination information-handling rules
  * Content unsupported by the destination environment
  * An unauthorized import request
  * An incomplete or unreadable bundle

Crucible does not silently replace, omit, repair, or substitute bundle content when doing so would change the approved Transfer Bundle.

The applicable policy or authorized actor determines whether an exception requires rejection, quarantine, additional review, retransmission, or creation of a replacement bundle.

===== Complete the Import =====

After successful verification and application of destination controls, Crucible makes the accepted bundle content available within the destination environment.

Successful import can make the content available for:

  * Population of Offline Repositories
  * Image construction
  * Compliance Assessment
  * Infrastructure deployment
  * Deployment Validation
  * Another approved disconnected or air-gapped lifecycle activity

Import does not itself perform those subsequent activities.

===== Import Result =====

The import result identifies:

  * The Transfer Bundle received
  * The destination environment
  * The receiving Security Domain
  * The import operation
  * The identity-verification result
  * The integrity-verification result
  * The destination-control result
  * The content accepted for import
  * The content rejected or held for review
  * The associations preserved during import
  * The overall import status
  * Any exception or unresolved condition

The successfully imported content becomes a controlled input to [[dido:02-crusible:07-disconnected-and-air-gapped-operations:07-05-populate-offline-repositories|7.5 Populate Offline Repositories]] or another approved destination lifecycle activity.

===== Requirements Addressed =====

^ Requirement ^ Statement ^
| [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-003:or-003d]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-003:or-003d#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-003:or-003e]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-003:or-003e#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-003:or-003f]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-003:or-003f#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-002]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-002#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-003]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-003#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-005]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-005#Statement&noheader&nofooter&noeditbtn}} |

The linked leaf requirement pages remain the canonical sources.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>