1. Executive Summary & Scope
Supply chain attacks increasingly target build environments rather than production code directly. If an attacker gains write access to CI/CD workflows, build runner secrets, or container registries, they can inject backdoors directly into release binaries without touching source code repositories.
2. Threat Model & Attack Vectors
Adversaries tamper with GitHub Actions or Jenkins pipelines to exfiltrate deployment credentials, inject malicious telemetry into web assets, or replace signed production docker images.
3. Code Analysis & Remediation Playbook
Vulnerable Implementation Pattern
Hardened Defense-in-Depth Implementation
4. Audit Verification Checklist & Pass Criteria
| Verification Phase | Audit Test Description | Mandatory Passing Criteria |
|---|---|---|
| Static Secret Audit in CI | Audit CI/CD runners to verify zero permanent credentials stored in runner environments. | Short-lived OIDC tokens replace long-lived static secrets. |
| Action SHA Immutability | Verify all third-party GitHub Actions are pinned to full 40-character commit hashes. | Zero mutable tags (@v1, @main) permitted in pipeline definitions. |
| Binary Attestation Check | Verify released Docker images and zip artifacts against Sigstore / Cosign public keys. | Deployments reject unsigned or untrusted provenance attestations. |
WebOTG Application Security Directorate
WebOTG provides benchmark reference documentation, automated matrix evaluators, and security test harnesses for government digital platforms, WQMS architectures, and STQC compliance frameworks.