3.3 Security Domains and Transfer Boundaries [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.
====== 3.3 Security Domains and Transfer Boundaries ======

[[dido:02-crusible:03-operational-context:start|Go to 3. Operational Environment]]

[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] operates across environments governed by different security controls, access restrictions, information-handling rules, and transfer constraints.

A [[dido:99_annexes:annex-b-terms-and-definitions:s:security_domain|Security Domain]] establishes the security conditions under which information, software, infrastructure resources, and operational activities are controlled. Different Security Domains can apply different authorization, access, handling, auditing, retention, and transfer requirements.

A [[dido:99_annexes:annex-b-terms-and-definitions:t:transfer_boundary|Transfer Boundary]] separates environments or Security Domains and governs the movement of permitted [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]], [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependencies]], records, and supporting [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] between them.

===== Security Domains =====

Crucible can perform applicable [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] activities within [[dido:99_annexes:annex-b-terms-and-definitions:c:classified_environment|Classified Environments]] and [[dido:99_annexes:annex-b-terms-and-definitions:u:unclassified_environment|Unclassified Environments]].

The controls applicable to a Security Domain can affect:

  * Which users, systems, and processes can access the environment
  * Which Artifacts and Dependencies can enter or leave the environment
  * Which repositories, services, and providers can be used
  * Which information-handling and retention rules apply
  * Which assessment, logging, and auditing activities are required
  * Which transfer mechanisms and approvals are permitted
  * Which [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]], configurations, and deployment subjects are authorized

Crucible applies the controls and restrictions established for the environment. Crucible does not establish the Security Classification, authorize access, or approve movement between Security Domains.

===== Transfer Boundaries =====

A Transfer Boundary governs movement between environments that do not share unrestricted access to the same resources.

A transfer can occur between:

  * Connected and Disconnected Environments
  * Connected and Air-Gapped Environments
  * Classified and Unclassified Environments
  * Security Domains with different access or handling restrictions
  * Environments operated by different organizations or authorities

The responsible organization determines whether a transfer is permitted and identifies the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:transfer_authorization|Transfer Authorization]], review process, handling controls, and transfer mechanism.

Crucible supports the controlled preparation and consumption of content associated with an authorized transfer. Crucible does not independently authorize the transfer.

===== Transfer Bundles =====

A [[dido:99_annexes:annex-b-terms-and-definitions:t:transfer_bundle|Transfer Bundle]] provides a controlled package for moving identified Artifacts between environments.

The same Transfer Bundle retains its identity through:

  - Creation in the source environment
  - Review under the applicable Transfer Authorization
  - Movement across the Transfer Boundary
  - Receipt in the destination environment
  - Verification of [[dido:99_annexes:annex-b-terms-and-definitions:t:transfer_bundle_integrity|Transfer Bundle Integrity]]
  - Import of identified Artifacts
  - Recording of the resulting Provenance, Traceability, and Evidence

A Transfer Bundle can contain permitted content such as:

  * Machine Images
  * Container Images
  * Infrastructure Configurations
  * Baselines
  * Software packages
  * Dependencies
  * Manifests
  * Content digests
  * Digital Signatures
  * Provenance records
  * Traceability records
  * Assessment results
  * Supporting Evidence

The content of a Transfer Bundle depends on the selected lifecycle activity and the applicable transfer controls.

===== Export and Import =====

In the source environment, Crucible creates a Transfer Bundle for identified Artifacts selected for transfer.

The export activity identifies:

  * The Transfer Bundle
  * The included Artifacts
  * The Artifact identifiers and revisions
  * The source environment
  * The intended destination environment
  * The applicable transfer information
  * The associated Provenance, Traceability, and Evidence

In the destination environment, Crucible imports identified Artifacts from the Transfer Bundle.

The import activity identifies:

  * The received Transfer Bundle
  * The Artifacts selected for import
  * The destination environment and repository
  * The import result
  * The associated Provenance, Traceability, and Evidence

Import does not independently approve an Artifact for deployment, promotion, or operation. The applicable acceptance, security, compliance, and authorization processes determine whether the imported Artifact can be used.

===== Traceability Across Boundaries =====

Crucible preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] between the source and destination environments.

The traceability information can identify:

  * The source and destination environments
  * The applicable Security Domains
  * The Transfer Boundary
  * The Transfer Bundle identifier and revision
  * The included Artifact identifiers and revisions
  * The applicable Transfer Authorization
  * Transfer Bundle Integrity information
  * The export, transfer, receipt, and import activities
  * The actors or processes associated with those activities
  * The deployment or lifecycle result that consumes the imported content
  * The Evidence generated during the transfer lifecycle

Preserving this information allows a reader or auditor to follow an Artifact from its source environment through transfer and import into the receiving environment.

Detailed transfer operations appear in [[dido:02-crusible:07-disconnected-and-air-gapped-operations:start|Section 7: Disconnected and Air-Gapped Operations]].

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

^ Requirement ^ Statement ^
| [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-003:or-003a]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-003:or-003a#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-003:or-003b]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-003:or-003b#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-003:or-003c]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-003:or-003c#Statement&noheader&nofooter&noeditbtn}} |
| [[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:02-operational-requirements:or-003:or-003g]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-003:or-003g#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>