Stop promotion when required security scan results are missing
A scan service times out and the build pipeline treats absence of findings as a clean result.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Fail-closed gates · Supply-chain checks
Estimated field mix
- Security60%
- Platform engineering40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional reporting API is rebuilt separately for staging and production. Different dependency resolutions and mutable tags make incident rollback unreliable.
Setup prerequisites
- Create a tiny local HTTP service and nonprivileged image build.
- Use synthetic registries or provider fixtures; no production deployment.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- AIMAGE-101 · Exclude local credentials and bulky artifacts from the image context
- AIMAGE-102 · Pin service build inputs to immutable identities
- AIMAGE-103 · Run the service image as an unprivileged user with a read-only root
- AIMAGE-104 · Record image provenance without embedding build credentials
- AIMAGE-105 · Promote the tested digest instead of rebuilding for each environment
Acceptance criteria
- Represent passed, failed and unavailable scan states distinctly.
- Require scan policy and artifact digest to match.
- Unavailable required results block promotion with a retry path.
Implementation constraints
- Use synthetic scan responses; do not claim current vulnerability coverage.
Verification to include
- Promote with matching passed policy results.
- Timeout or return a different digest and verify promotion remains blocked.
Deliverables
- Scan-result gate and unavailable-state tests
Rollout and recovery
Run the gate before environment selection; retry scans without rebuilding the artifact.
Value of the work
For the engineer: Practice artifact identity, least privilege and reproducible delivery.
For the team: Review whether deployed bytes can be traced and rolled back reliably.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.