Software Supply Chain and Pipeline Security Compliance Report
Assess CI/CD pipeline vulnerabilities, artifact provenance, dependency risks, and automated compliance gates across the SDLC.
Utilize this template when preparing for security audits or upgrading pipeline security posture against supply chain vectors. It provides an in-depth report on artifact integrity, scanner efficacy, and remediation SLAs.
Role: Staff DevSecOps Engineer specializing in artifact provenance, automated security scanning, and pipeline supply chain integrity.
Context
- Source Control Infrastructure: {{source_control_system}}
- Artifact Registry Solution: {{artifact_registry}}
- Pipeline Security Scanning Stack: {{vulnerability_scanner_stack}}
- Software Bill of Materials (SBOM) Standard: {{sbom_standard}}
- Mandatory Security Framework: {{compliance_framework}}
- Mean Time to Remediate Criticals (MTTR): {{mean_time_to_remediate}}
Task
Author an extensive DevSecOps supply chain security report reviewing the build-to-deploy pipeline across {{source_control_system}} and {{artifact_registry}}, pinpointing vulnerabilities in toolchain handoffs and defining gate controls required by {{compliance_framework}}.
Method
- Map the complete artifact lineage from source commit in {{source_control_system}} to {{artifact_registry}}.
- Audit coverage gaps and false positive overhead across the {{vulnerability_scanner_stack}}.
- Review provenance attestations, cryptographic signing, and verification mechanisms against {{compliance_framework}}.
- Evaluate compliance of {{sbom_standard}} generation during container and package builds.
- Analyze branch protection rules, runner isolation, and secret management within pipelines.
- Compare current {{mean_time_to_remediate}} against industry standard remediation thresholds.
- Formulate automated policy-as-code admission gates to block non-compliant artifacts.
Constraints
- MUST align all policy recommendations directly with {{compliance_framework}} specifications.
- MUST NOT recommend manual approval gates for recurring standard builds.
- Include explicit artifact signing and verification workflows using public key infrastructure or keyless signing.
- Clearly distinguish between pre-commit, build-time, and admission-time security controls.
Output format
Provide a technical compliance and gap assessment report structured as:
- Threat Landscape & Supply Chain Exposure Summary
- Pipeline Security Posture Audit (covering {{source_control_system}} through to {{artifact_registry}})
- Automated Toolchain Evaluation (assessing {{vulnerability_scanner_stack}} and {{sbom_standard}} output)
- Remediation SLA & MTTR Analysis (comparing {{mean_time_to_remediate}} against compliance targets)
- DevSecOps Remediation Roadmap (Actionable checklist mapped to {{compliance_framework}})
Self-review
- Are all components of {{vulnerability_scanner_stack}} evaluated without generic tool generalizations?
- Does the artifact signing process integrate with {{artifact_registry}} cleanly?
- Does the roadmap provide explicit controls to reduce the {{mean_time_to_remediate}}?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.