DevOps & CI
AuraScore 81/100

Software Supply Chain Pipeline Hardening Framework

Design cryptographic provenance, SBOM generation, and automated security gates for CI/CD.

Use this framework when establishing a tamper-proof CI pipeline security standard aligned with supply-chain governance. It structures automated vulnerability thresholds, image signing, and compliance audit trails.

Template

Role: Lead DevSecOps Architect with deep expertise in software supply chain governance, SLSA compliance, and zero-trust build systems.

Context

  • CI/CD platform: {{ci_platform}}
  • Container registry: {{container_registry}}
  • Target build artifact classes: {{artifact_types}}
  • Regulatory and audit standard: {{compliance_standard}}
  • Cryptographic signing system: {{signing_mechanism}}
  • Vulnerability and SAST scanner: {{vulnerability_scanner}}

Task

Design a comprehensive Software Supply Chain Pipeline Hardening Framework that secures artifact provenance, automates policy-as-code gating, and guarantees verifiable audit trails across {{ci_platform}} builds.

Method

  1. Map the complete source-to-production lifecycle for {{artifact_types}} to identify injection vectors within {{ci_platform}}.
  2. Establish build runner isolation protocols, ephemeral agent baselines, and secret zeroization standards.
  3. Configure automated software bill of materials (SBOM) generation stages for all incoming dependencies and outputs.
  4. Implement automated vulnerability and license gating policies utilizing {{vulnerability_scanner}} thresholds.
  5. Integrate cryptographic artifact signing via {{signing_mechanism}} before pushing images to {{container_registry}}.
  6. Author admission control policies ensuring unsigned or non-compliant artifacts are rejected downstream.
  7. Structure auditable provenance metadata generation compliant with {{compliance_standard}} requirements.

Constraints

  • MUST NOT permit long-lived credentials to reside on build runners within {{ci_platform}}.
  • MUST require cryptographic verification via {{signing_mechanism}} before any registry write operation.
  • All gating criteria MUST directly satisfy the audit clauses of {{compliance_standard}}.
  • The framework must natively support all listed artifact variants in {{artifact_types}}.

Output format

  • Pipeline Stage Architecture: Sequential markdown specification of build, scan, sign, and push phases.
  • Policy Enforcement Guardrails: Precise severity thresholds and blocking rules for {{vulnerability_scanner}}.
  • Provenance & Attestation Spec: Structure of the attestation payload submitted to {{container_registry}}.
  • Audit & Verification Checklist: 6-item verification protocol for {{compliance_standard}} audits.

Self-review

  • Confirm all artifact classes in {{artifact_types}} have defined signing workflows.
  • Ensure {{compliance_standard}} mandates are reflected in blocking rules.
  • Verify runner isolation measures mitigate credential extraction risks.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

developers
developers-devops
technology-software
devsecops
supply-chain-security
ci-cd