public:99_annexes:annex-b-terms-and-definitions:e:enclave

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:e:enclave [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:e:enclave [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Enclave ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +An Enclave groups systems, services, infrastructure, information, users, processes, and controls within a defined operational and security boundary.
 +
 +The boundary establishes common rules for access, communication, administration, information handling, monitoring, and risk management. An Enclave may operate as a connected, disconnected, or [[private:99_annexes:annex-b-terms-and-definitions:a:air_gapped_environment|Air-Gapped Environment]].
 +
 +An Enclave may contain multiple networks, platforms, systems, or trust zones. The shared boundary and governance controls distinguish the Enclave from its surrounding environment.
 +
 +In the Crucible operating model, an Enclave may receive transfer bundles, host local package repositories and container mirrors, maintain infrastructure source history, and reproduce controlled machine images and deployment environments without external access.
 +
 +===== Definition =====
 +
 +//group of systems, services, infrastructure, information, users, processes, and controls governed within a defined operational and security boundary//
 +
 +===== Source =====
 +
 +Generalised from cybersecurity, defense, network architecture, information assurance, and operational-environment usage and specialized for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +An Enclave does not necessarily correspond to a single physical location, network segment, organization, or deployment platform.
 +
 +An [[public:99_annexes:annex-b-terms-and-definitions:a:accreditation_boundary|Accreditation Boundary]] and an Enclave boundary may coincide, overlap, or differ according to the applicable governance and operational model.
 +
 +===== Example =====
 +
 +A regulated organization operates an Enclave containing build services, deployment infrastructure, package repositories, compliance services, administrative workstations, and controlled interfaces for importing approved transfer bundles.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>