MO-004c — Authorized Resource Use

Go to MO-004 — Connected and Disconnected Operations

Statement

Crucible SHALL access only Authorized Resources for the identified 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 constraint that Crucible operates within the resource-authorization boundary established for the identified operational environment.

The separate requirements derived from MO-004 address:

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 authorized for a different operational environmentA resource authorized for a different Operational Lifecycle activityAn Authorized Resource has an identified authorization for the operational environment and intended use.

Restricting Crucible to Authorized 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 within the operational environment.

This requirement does not identify the resources required for execution in a Disconnected Environment. MO-004b addresses disconnected execution, and MO-004d addresses resource availability.

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 operational environment is identifiedThe Authorized Resources for the identified operational environment are identifiedEach resource accessed by Crucible has a valid authorization for the identified operational environmentEach resource authorization permits 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 resource access is recordedThe verification record preserves Traceability among the operational environment, Authorized Resource set, accessed resources, authorization records, access decisions, and recorded results

Referenced By

The following pages reference this requirement:

Delivery Phase

Implemented and Verified

Implementation Status

Requirement Status

Issues

The following unresolved issues affect this requirement:

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.

The parent MO-004 page is a non-leaf page and retains a trailing :start in its namespace.

Changes to the Statement should preserve:

as the responsible actorAuthorized Resources as the permitted resourcesThe identified operational environment as the authorization contextProhibition of access to resources outside the Authorized Resource setThe authorization record for each Authorized Resource should identify:

The resource identifierThe resource typeThe operational environmentThe permitted useThe authorizing authorityThe authorization dateThe authorization statusThe authorization expiration conditionAny restrictionsMaterial changes should receive review and should update the verification criteria, source records, and Issues section.

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.