Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:u:unclassified_environment [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:u:unclassified_environment [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Unclassified Environment ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | An Unclassified Environment is an operating environment that is not authorized to store, process, or transmit classified information. | ||
| + | |||
| + | An Unclassified Environment can still require security controls for information that is sensitive, regulated, proprietary, | ||
| + | |||
| + | Information handled within an Unclassified Environment can include: | ||
| + | |||
| + | * Public information | ||
| + | * Internal organizational information | ||
| + | * Proprietary information | ||
| + | * Personal information | ||
| + | * Export-controlled information | ||
| + | * Law-enforcement-sensitive information | ||
| + | * Controlled Unclassified Information | ||
| + | * Information subject to contractual restrictions | ||
| + | * Information subject to statutory or regulatory protection | ||
| + | * Security configuration information | ||
| + | * Authentication and authorization information | ||
| + | |||
| + | The designation **Unclassified Environment** does not mean: | ||
| + | |||
| + | * The environment contains only public information | ||
| + | * The environment requires no security controls | ||
| + | * Every user can access every resource | ||
| + | * Information can be released without authorization | ||
| + | * The environment can accept classified information | ||
| + | * The environment has a low security-impact categorization | ||
| + | |||
| + | An Unclassified Environment can operate as a: | ||
| + | |||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | |||
| + | Connectivity and classification describe different environment characteristics. An Unclassified Environment can remain disconnected or air-gapped because of operational, | ||
| + | |||
| + | Within the Crucible architecture, | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //operating environment that is not authorized to store, process, or transmit classified information// | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * Dido Solutions, Crucible architecture and requirements terminology | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | Unclassified information can still require safeguarding and dissemination controls. | ||
| + | |||
| + | Controlled Unclassified Information is unclassified information subject to controls established by law, regulation, or government-wide policy. Controlled Unclassified Information is not a Security Classification. | ||
| + | |||
| + | An Unclassified Environment can have a high security-impact categorization based on the consequences of unauthorized disclosure, modification, | ||
| + | |||
| + | An Unclassified Environment differs from a [[public: | ||
| + | |||
| + | * An Unclassified Environment is not authorized to handle classified information | ||
| + | * A Classified Environment is authorized to handle specified classified information | ||
| + | |||
| + | Information does not become unclassified merely because it enters an Unclassified Environment. Classified information introduced into an Unclassified Environment constitutes a security incident and remains subject to the governing classification authority. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | An Air-Gapped Deployment Target hosts Controlled Unclassified Information but is not authorized for classified information. | ||
| + | |||
| + | The Deployment Target remains an Unclassified Environment even though it requires: | ||
| + | |||
| + | * Restricted physical access | ||
| + | * Multifactor authentication | ||
| + | * Role-based authorization | ||
| + | * Encrypted storage | ||
| + | * Controlled media transfer | ||
| + | * Audit logging | ||
| + | * Approved software repositories | ||
| + | * Information-retention controls | ||
| + | * Information-destruction procedures | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||