public:99_annexes:annex-b-terms-and-definitions:t:transfer_boundary

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:t:transfer_boundary [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:t:transfer_boundary [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Transfer Boundary ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Transfer Boundary separates transfer domains between which the movement of information or [[public:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]] is subject to defined controls.
 +
 +The separated domains may differ by:
 +
 +  * Security classification
 +  * Security policy
 +  * Administrative authority
 +  * Ownership
 +  * Trust level
 +  * Network connectivity
 +  * Physical location
 +  * Operational purpose
 +  * Legal jurisdiction
 +  * Regulatory obligations
 +
 +A Transfer Boundary may exist between:
 +
 +  * A Connected Environment and a Disconnected Environment
 +  * A Disconnected Environment and an Air-Gapped Environment
 +  * Classified and unclassified environments
 +  * Development and production environments
 +  * Provider environments
 +  * Organizational domains
 +  * Security zones
 +  * Geographic or jurisdictional domains
 +
 +Controls applied at a Transfer Boundary may include:
 +
 +  * Transfer Authorization
 +  * Identity verification
 +  * Content inspection
 +  * Classification checking
 +  * Policy evaluation
 +  * Encryption
 +  * Digital signature verification
 +  * Transfer Bundle Integrity verification
 +  * Malware scanning
 +  * Import and export logging
 +  * Human approval
 +  * Chain-of-custody recording
 +
 +A Transfer Boundary is a logical or physical separation. The boundary does not require a single gateway, device, interface, or implementation mechanism.
 +
 +===== Definition =====
 +
 +//boundary separating transfer domains across which movement of information or artifacts is subject to defined controls//
 +
 +===== Source =====
 +
 +Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +
 +===== Note =====
 +
 +A single transfer may cross multiple Transfer Boundaries.
 +
 +Each boundary may impose different:
 +
 +  * Authorizing authorities
 +  * Permitted transfer subjects
 +  * Inspection requirements
 +  * Handling procedures
 +  * Evidence requirements
 +  * Import and export controls
 +
 +A network boundary may also serve as a Transfer Boundary, but the concepts are not identical. A Transfer Boundary concerns controlled movement between domains regardless of whether the movement occurs through a network, removable media, or another mechanism.
 +
 +===== Example =====
 +
 +The separation between an unclassified Connected Environment and a classified Air-Gapped Environment is a Transfer Boundary. Artifacts crossing that boundary require authorization, content inspection, integrity verification, and recorded import and export results.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>