MO-004c — Unauthorized Resource Prohibition

Go to MO-004 — Connected and Disconnected Operations

Statement

Crucible SHALL NOT access a resource that is not an Authorized Resource for the applicable operational environment.

Derived From

This requirement derives from:

The Original Requirement states:

The system SHALL support both connected and disconnected operational environments.[C1]

MO-004c preserves the implied constraint that Crucible operates within the resource-authorization boundary established for the applicable operational environment.

The separate requirements derived from MO-004 address:

Assessment

The Original Requirement does not identify the resource-authorization constraints applicable within connected and disconnected operational environments.

The phrase support both connected and disconnected operational environments does not identify:

The resources Crucible is permitted to accessThe authority that approves a resource for useThe operational environment to which the authorization appliesThe duration or conditions of the authorizationThe treatment of a resource whose authorization expires or is revokedThe behavior required when Crucible encounters an unauthorized resourceThe Evidence required to demonstrate compliance with the authorization boundaryMO-004c:

Identifies Crucible as the responsible actorStates the prohibited behavior directly through SHALL NOTIdentifies an unauthorized resource as the prohibited object of accessTies resource authorization to the applicable operational environmentSeparates authorization from resource availabilitySeparates unauthorized-resource prohibition from connected operation, disconnected operation, and external-resource independence

Rationale

A resource can be available within an operational environment without being authorized for use.

Examples include:

An unapproved repositoryAn unapproved packageAn unapproved container registryAn unapproved network serviceAn unapproved external endpointAn imported Artifact that has not completed admission checksA resource whose authorization has expiredA resource whose authorization has been revokedA resource approved for a different operational environmentA resource approved for a different Operational Lifecycle activityAn Authorized Resource has an identified authorization that applies to the operational environment and intended use.

Prohibiting access to unauthorized resources supports:

Enforcement of environment boundariesSupply-chain controlPrevention of unapproved dependency usePrevention of unauthorized external communicationConfiguration controlSecurity control enforcementCompliance evaluationProvenanceTraceabilityGeneration of auditable EvidenceThis requirement does not require every Authorized Resource to be available.

This requirement does not establish the resources required for execution in a Disconnected Environment. MO-004b addresses disconnected execution, and MO-004d addresses independence from unavailable external resources.

Applies To

This requirement applies to:

Unauthorized resourcesConnected EnvironmentsDisconnected EnvironmentsAir-Gapped EnvironmentsOperational Lifecycle activitiesControlled InputsArtifactsArtifact repositoriesPackage repositoriesImage registriesNetwork servicesExternal endpointsImported dependenciesTransfer BundlesAttached storageRuntime servicesEvidenceProvenanceTraceability

Verification

Verification confirms that:

The applicable operational environment is identifiedThe resources authorized for the operational environment are identifiedEach resource accessed by Crucible has a valid authorization for the operational environmentEach resource authorization applies to the intended useCrucible does not access a resource absent from the authorized resource setCrucible does not access a resource whose authorization has expired or been revokedCrucible does not access a resource authorized only for another operational environmentEach attempted access to an unauthorized resource is deniedEach attempted unauthorized access is recordedThe generated Evidence supports the authorization determinationVerification includes:

Authorized Resource inventory inspectionResource authorization inspectionAuthorization-scope inspectionAuthorization-validity inspectionRepository-access testingRegistry-access testingNetwork-service access testingExternal-endpoint access testingImported Artifact admission testingExpired-authorization testingRevoked-authorization testingCross-environment authorization testingAccess-denial testingAudit-record inspectionEvidence inspectionProvenance inspectionTraceability inspectionThe verification record identifies:

The applicable operational environmentThe Authorized Resource setEach resource accessed during executionThe authorization applicable to each accessed resourceThe authorization scopeThe authorization statusEach attempted unauthorized resource accessThe denial result for each attempted unauthorized accessThe audit record associated with each attempted unauthorized accessEach identified failure or exceptionThe observed resultThe generated Evidence

Requirements Realized By

This requirement is realized by:

Related Architecture Sections

Referenced By

The following pages reference this requirement:

Delivery Phase

Phase 1 and subsequent phases

Implementation Status

Not Assessed

Implementation status requires verification that the current Crucible implementation denies access to resources that are not authorized for the applicable operational environment.

Requirement Status

Draft

This requirement derives from MO-004 in the Crucible System Requirements Specification, Version 1.1 Draft.

Notes for Editors

This requirement page should retain the stable requirement identifier MO-004c.

This page is a leaf requirement page and omits a trailing :start from its namespace.

Changes to the Statement SHALL preserve the unauthorized-resource prohibition derived from MO-004.

The authorization record for each Authorized Resource should identify:

The resource identifierThe resource typeThe applicable operational environmentThe permitted useThe authorizing authorityThe authorization dateThe authorization statusThe authorization expiration conditionAny applicable restrictionsThe supporting EvidenceMaterial changes should receive review and should update the related verification criteria, requirements realization, related architecture sections, and source records.

To reference this requirement Statement from another wiki page, insert:

{{section>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:mo-004c#Statement&noheader&nofooter&noeditbtn}}

Do not rename this page after an external citation unless a redirect or move plan is in place.

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