Show pageOld revisionsBacklinksAdd to bookExport to PDFODT exportBack to top Backlinks This is a list of pages that seem to link back to the current page. 1.1 Purpose1.2 Scope1.3 Intended Audience1.4.2 What the Wiki Contains1. Introduction2.2 Mission and Expected Outcomes3.1 Connectivity Conditions3.2 Deployment Environments3.3 Security Domains and Transfer Boundaries3. Operational Environment4.1 Human Actors4.2 Automated Actors4.3 External Systems4. Actors and Responsibilities5.1 Select and Compose Baselines5.2 Construct Images5.3 Capture and Preserve Dependencies5.4 Assess Compliance5.5 Deploy the Environment5.6 Validate the Result5.7 Preserve Evidence and Lifecycle Records5. Operational Concept6.1 Construct and Assess the Environment6.2 Deploy in a Connected Environment6. Connected Operations7.1 Capture and Preserve Dependencies7.2 Produce the Transfer Bundle7.3 Transfer Across the Boundary7.4 Import the Transfer Bundle7.5 Populate Offline Repositories7.6 Rebuild and Deploy7.7 Preserve Traceability Across Environments7. Disconnected and Air-Gapped Operations8.1 Select Compliance Criteria and Baselines8.2 Perform Compliance Assessments8.3 Produce Compliance Reports8.4 Generate Supporting Evidence8.5 Transfer Compliance Findings8. Compliance Operations9.1 Shared Interface Operations9.2 Command-Line Interface9.3 Web-Based User Interface9. Crucible InterfacesMO-001a — Infrastructure Environment CreationMO-001b — Deployment DurationMO-001c — ReproducibilityMO-001d — Security Baseline ConformanceMO-001e — Compliance Baseline ConformanceMO-001 — Repeatable, Compliant, and Secure Infrastructure EnvironmentsMO-002a — Maximum Platform Deployment DurationMO-002b — Platform Deployment Duration ReductionMO-003a — Cross-Platform DeploymentMO-003b — Provider-Independent Crucible DescriptionMO-003c — Provider-Independent Infrastructure BaselineMO-003d — Limitation of Provider-Specific DependenciesMO-003 — Cloud-Agnostic DeploymentMO-004a — Connected Environment OperationsMO-004b — Disconnected Environment OperationsMO-004c — Authorized Resource UseMO-004d — Disconnected Resource AvailabilityMO-004 — Connected and Disconnected OperationsMO-005a — Infrastructure Baseline Artifact ManagementMO-005b — Infrastructure Baseline IdentificationMO-005c — Infrastructure Baseline Revision ControlMO-005d — Approved Infrastructure Baseline SelectionMO-005e — Infrastructure Baseline ReuseMO-005f — Approved Infrastructure Baseline PreservationMO-005g — Infrastructure Deployment Baseline TraceabilityMO-005 — Reusable and Version-Controlled Infrastructure BaselinesMO-006a — Operational Lifecycle AssociationMO-006b — Infrastructure Lifecycle InitiationMO-006c — Infrastructure Lifecycle State RecordingMO-006d — Infrastructure Lifecycle Transition ExecutionMO-006e — Infrastructure Environment RetirementMO-006 — Infrastructure Lifecycle ManagementC.1 Mission ObjectivesOR-001a — Developer OperationsOR-001b — DevSecOps Engineer OperationsOR-001c — Platform Engineer OperationsOR-001d — System Administrator OperationsOR-001e — Security Engineer OperationsOR-001f — Compliance Officer OperationsOR-001 — Operation by Identified User CategoriesOR-002a — Deployment to a Supported TargetOR-002b — Deployment Acceptance AssessmentOR-002c — Deployment Acceptance RecordOR-002 — Deployment EnvironmentsOR-003a — Classified Environment OperationsOR-003b — Unclassified Environment OperationsOR-003c — Security Domain Resource EnforcementOR-003d — Security Domain Information EnforcementOR-003e — Information Handling Rule EnforcementOR-003f — Cross-Domain Transfer ControlOR-003g — Security Domain Access ControlOR-003 — Classified and Unclassified EnvironmentsOR-004a — Concurrent Environment DeploymentOR-004b — Concurrent Environment ManagementOR-004 — Concurrent Environment Deployment and ManagementOR-005 — Distributed Environment ManagementC.2 Operational RequirementsFR-CFG-001 — Declarative Infrastructure ConfigurationFR-CFG-002 — Infrastructure as CodeFR-CFG-003 — Reusable Infrastructure BlueprintsFR-CFG-004 — Environment InheritanceFR-CFG-005 — Configuration Version HistoryC.3.1 Configuration ManagementFR-IMG-001 — Build Virtual Machine ImagesFR-IMG-002 — Build Container ImagesFR-IMG-003 — Immutable Infrastructure WorkflowsFR-IMG-004 — Image SigningFR-IMG-005 — Image VerificationFR-IMG-006 — Image Promotion WorkflowsC.3.2 Image ManagementFR-DEP-001 — Deploy Infrastructure ResourcesFR-DEP-002 — Deploy Virtual MachinesFR-DEP-003 — Deploy Kubernetes ClustersFR-DEP-004 — Deploy Containerized WorkloadsFR-DEP-005 — Deploy Platform ServicesFR-DEP-006 — Deployment RollbackFR-DEP-007 — Deployment ValidationC.3.3 Deployment OrchestrationFR-MC-001 — Cloud Provider AbstractionFR-MC-002 — Provider-Specific ExtensionsFR-MC-003 — Deployment Portability Across Cloud ProvidersFR-MC-004 — Hybrid-Cloud DeploymentsFR-MC-005 — Edge DeploymentsC.3.4 Multi-Cloud ManagementFR-AG-001 — Disconnected Deployment OperationsFR-AG-002 — Artifact Export PackagesFR-AG-003 — Artifact Import PackagesFR-AG-004 — Baseline SynchronizationFR-AG-005 — Deployment Traceability Across Disconnected EnvironmentsC.3.5 Air-Gapped OperationsFR-COMP-001 — Compliance Baseline DefinitionsFR-COMP-002 — Compliance Scanning Tool IntegrationFR-COMP-003 — Compliance ReportingFR-COMP-004 — Compliance Evidence ArtifactsFR-COMP-005 — DISA STIG Compliance BaselinesFR-COMP-006 — FedRAMP Baseline DefinitionsFR-COMP-007 — Custom Compliance FrameworksFR-COMP-008a — Compliance Scanning AbstractionFR-COMP-008b — Multiple Operating-System SupportFR-COMP-009a — Security Control Traceability Matrix EvidenceFR-COMP-009b — Risk Management Framework EvidenceFR-COMP-009c — Authorization to Operate EvidenceFR-COMP-009 — Security-Control Implementation EvidenceFR-COMP-010a — Compliance Finding Transfer Bundle InclusionFR-COMP-010b — Compliance Finding Association PreservationC.3.6 Compliance ManagementFR-DSO-001 — Git-Based Workflow IntegrationFR-DSO-002 — GitOps Workflow IntegrationFR-DSO-003 — CI/CD Pipeline IntegrationFR-DSO-004 — Automated Build ExecutionFR-DSO-005 — Automated Deployment ExecutionFR-DSO-006 — Automated Validation ExecutionC.3.8 DevSecOps IntegrationFR-BAS-001 — Consume Baseline Repositories from a WorkspaceFR-BAS-002 — Compose Selected BaselinesFR-BAS-003 — Process Predeployment and Postdeployment StepsFR-BAS-004 — Perform Noninteractive Workspace ExecutionC.3.9 Baseline Composition and WorkspaceFR-DEPC-001 — Capture Build DependenciesFR-DEPC-002 — Preserve Dependencies in a Dependency StoreFR-DEPC-003 — Produce a Transfer BundleFR-DEPC-004 — Populate Offline RepositoriesFR-DEPC-005 — Dependency Store Implementation IndependenceC.3.10 Dependency Capture and Offline TransferFR-UI-001 — Shared Interface OperationsFR-UI-002 — Command-Line InterfaceFR-UI-003 — Web-Based User InterfaceC.3.11 Crucible InterfacesC.3 Functional RequirementsCrucibleAccredited Software FactoryAuthorizing AuthorityCentralized ManagementContainer ImageCDeployment PlatformDeployment TargetDeployment Target CatalogDistributed Immutable Data Object Test Environment (DIDO-TE)Distributed EnvironmentFunctional RequirementImageImage SigningTransfer BundleVirtual MachineP1-REQ-13-9-00513.9 Relationship to Logical Architecture / PIM Requirements3.1 Traceability to SIP-RA3.5 Coverage of the Original FX Demo Reference Architecture3.6 Traceability Position4.2 FX Domain Scope before Implementation19.2 Boundary Between Part 4 and Part 520.11 Deployment and Evidence Concerns Remain Outside Part 4 dido/99_annexes/annex-b-terms-and-definitions/c/crucible.txt Last modified: 2026/08/04 07:09by nick_dido