OR-003 — Classified and Unclassified Environments

Go to Operational Requirements

Original Requirement

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

Assessment of Original Requirement

The Original Requirement preserves the approved operational intent but does not express independently testable normative statements.

The following Specification Discipline and Authoring findings apply:

The system does not use the defined system name CrucibleSupport is a weak verb that does not identify an observable behavior performed by CrucibleClassified and unclassified combines two operating contexts that can pass or fail independentlyDeployment environments does not identify the Operational Lifecycle activities that Crucible performsThe Original Requirement does not identify the Security Domain governing an environmentThe Original Requirement does not identify the Security Classification authorized for a Classified EnvironmentThe Original Requirement does not identify the Classification Authority governing classified informationThe Original Requirement does not require enforcement of access restrictionsThe Original Requirement does not require enforcement of Information Handling RulesThe Original Requirement does not identify the conditions governing movement of information between Security DomainsThe Original Requirement does not require use of an authorized Cross-Domain TransferThe Original Requirement does not identify the behavior required when information is not authorized for an operation or destinationThe Original Requirement does not provide independently identifiable statements for verification and TraceabilityThe previously normalized Statement also combined:

Execution of selected Operational Lifecycle activities within Classified EnvironmentsExecution of selected Operational Lifecycle activities within Unclassified EnvironmentsRestriction of operations to the governing Security DomainEnforcement of access restrictionsEnforcement of Information Handling RulesControl of information transfer between Security DomainsThese obligations can pass or fail independently.

For example:

Crucible can operate successfully in an Unclassified Environment and fail in a Classified EnvironmentCrucible can enforce access restrictions and fail to enforce Information Handling RulesCrucible can operate within both environment types and permit an unauthorized Cross-Domain TransferCrucible can enforce Security Domain boundaries for users while failing to restrict an automated processCrucible can reject an unauthorized transfer while failing to preserve the required transfer recordThe Original Requirement therefore requires decomposition into independently identifiable normative requirements.

The decomposition preserves OR-003 as the stable parent requirement identifier. Each proposed replacement requirement receives a lettered identifier and a separate leaf requirement page.

Proposed Statements

The Original Requirement is decomposed into the following proposed replacement requirements:

Requirement Status

Issues

The following unresolved issues affect the decomposition of OR-003:

Notes for Editors

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

This page is a non-leaf requirement page and retains a trailing :start in its namespace.

The child requirements are leaf requirement pages and omit a trailing :start from their namespaces.

The explicit child-page links should remain while the proposed decomposition is being developed. After the child pages have been created and finalized, the explicit links may be removed because the indexmenu displays the child requirement pages contained within the OR-003 namespace.

This page preserves:

The Original RequirementThe assessment of the Original RequirementThe reason for decompositionTraceability to the proposed replacement requirementsThe unresolved cross-cutting issues affecting the decompositionThe supersession decisionThe derived requirements should distinguish:

Execution of Operational Lifecycle activities within Classified EnvironmentsExecution of Operational Lifecycle activities within Unclassified EnvironmentsRestriction of operations, resources, and information to the governing Security DomainEnforcement of Information Handling RulesControl of information movement through authorized Cross-Domain TransfersRestriction of access according to identity, role, authorization, need to know, and Security DomainThe proposed child Statements should retain the following intent:

OR-003a requires Crucible to execute selected Operational Lifecycle activities within a Classified EnvironmentOR-003b requires Crucible to execute selected Operational Lifecycle activities within an Unclassified EnvironmentOR-003c requires Crucible to restrict each operation to resources and information authorized for the governing Security DomainOR-003d requires Crucible to enforce the Information Handling Rules governing each information object processed by a Crucible operationOR-003e requires Crucible to transfer information between Security Domains only through an authorized Cross-Domain TransferOR-003f requires Crucible to permit a user or process to access only operations, resources, and information authorized for its identity, role, and Security DomainThe Original Requirement should not be marked as superseded until the requirement owner:

Approves the proposed decompositionApproves the child requirementsDefines the Operational Lifecycle activities required in each environment typeDefines the supported Security DomainsDefines the governing Security Classifications and Classification AuthoritiesDefines the Information Handling RulesDefines the authorized Cross-Domain Transfer mechanismsDefines the access-control modelConfirms that the child requirements collectively preserve the complete approved intent of OR-003Confirms that no additional child requirements are requiredAfter supersession, this page should remain as the parent Traceability record and should continue to preserve the Original Requirement and its assessment.

Material changes to the decomposition should update the child requirements, Requirement Status, Issues, and Traceability records.

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