OR-003f — Cross-Domain Transfer Control

Go to OR-003 — Classified and Unclassified Environments

Statement

Crucible SHALL transfer information between Security Domains only through an authorized Cross-Domain Transfer.

Derived From

This requirement derives from:

Crucible System Requirements Specification, Version 1.1 Draft, Operational Requirements, OR-003The Original Requirement states:

The system SHALL support classified and unclassified deployment environments.[C1]

OR-003f isolates the obligation to control information movement between Security Domains.

Rationale

Authorization to process information within one Security Domain does not authorize movement of that information into another Security Domain.

A transfer can cross boundaries established by different security policies, classification levels, compartments, handling restrictions, organizations, missions, or release authorities.

OR-003f prevents Crucible from moving information across a Security Domain boundary without an authorized Cross-Domain Transfer.

The Crucible Concept of Operations describes dependency capture, transfer-bundle creation, import, validation, and offline use across connected, disconnected, and air-gapped environments.

When the source and destination environments belong to different Security Domains, that workflow constitutes a Cross-Domain Transfer and requires the controls established by OR-003f.

Applies To

This requirement applies to:

Information transferred by CrucibleArtifactsMachine ImagesInfrastructure BaselinesCrucible DescriptionsDependenciesEvidenceClassified EnvironmentsUnclassified EnvironmentsConnected EnvironmentsDisconnected EnvironmentsAir-Gapped Environments

Verification

Verification confirms that:

Each tested transfer identifies its source Security DomainEach tested transfer identifies its destination Security DomainEach tested transfer identifies the information selected for transferEach tested transfer identifies an authorized Cross-Domain TransferCrucible transfers the selected information when the Cross-Domain Transfer is authorizedCrucible prevents the transfer when the Cross-Domain Transfer is not authorizedCrucible prevents the transfer when the source Security Domain is not identifiedCrucible prevents the transfer when the destination Security Domain is not identifiedCrucible records the result of each attempted Cross-Domain TransferEach transfer record identifies the source Security Domain, destination Security Domain, transferred information, transfer authorization, and transfer result

Referenced By

The following pages reference this requirement:

Delivery Phase

Implemented and Verified.

Implementation Status

Requirement Status

Issues

Notes for Editors

This requirement page should retain the stable requirement identifier OR-003f.

This page is a leaf requirement page and omits a trailing :start from its namespace.

OR-003f governs whether information may cross a Security Domain boundary. It does not define the detailed processing steps performed by a Cross-Domain Transfer mechanism.

The responsible authority establishes:

The authorized source Security DomainThe authorized destination Security DomainThe information authorized for transferThe authorized transfer mechanismThe transfer directionThe conditions governing transfer authorizationThe evidence required to demonstrate authorizationChanges to the Statement should preserve:

as the responsible actorTransfer as the controlled behaviorInformation as the transferred objectDistinct Security Domains as the source and destination contextsAn authorized Cross-Domain Transfer as the required transfer pathRequirements governing whether information is authorized within a Security Domain should remain in OR-003d — Security Domain Information Enforcement.

Requirements governing the permitted handling of information should remain in OR-003e — Information Handling Rule Enforcement.

To reference this requirement Statement from another wiki page, insert:

{{section>dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-003:or-003f#Statement&noheader&nofooter&noeditbtn}}

Do not rename this page after an external citation unless a redirect or move plan is in place.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.