C.3.8 DevSecOps Integration

Go to Crucible Functional Requirements

The Development, Security, and Operations (DevSecOps) Integration requirements define how Crucible participates in Git-based workflows, applies GitOps practices, operates as part of a CI/CD Pipeline, and performs automated build, deployment, and validation activities.

Together, these requirements establish noninteractive and automated workflow behavior within a Development and Operations (DevOps) lifecycle. The requirements integrate security-related activities into development and operational workflows and contribute to controlled change, repeatable execution, Reproducibility, Provenance, and Traceability.

Contents

Requirement Status

Issues

Notes for Editors

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

The namespace for this page is:

dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-08-devsecops-integration:start

Use the following controlling Terms and Definitions entries:

The individual requirement pages retain the stable identifiers FR-DSO-001 through FR-DSO-006.

Individual requirement pages are leaf nodes nested beneath the DevSecOps Integration namespace and omit a trailing :start.

The Derived From section on each leaf requirement page preserves the original wording from the controlling System Requirements Specification.

Normalized Statements use direct, testable behavior and identify the repository state, workflow event, CI/CD Pipeline operation, input Artifact, or required result only when the controlling source establishes that information.

Verification criteria test only the behavior stated in the normalized Statement and do not introduce additional normative obligations.

Incoming Traceability uses the wiki Backlinks function rather than a manually maintained list.

Each leaf requirement page includes its actual namespace in the DokuWiki section-transclusion example. Do not use a placeholder namespace in a completed leaf requirement page.

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

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