Housing authority CI must prevent unsigned build outputs from entering the production promote path. Which control belongs there?
Select an answer to reveal the explanation.
Short Explanation
Signatures are the wax seal on the housing build—no seal, no promote. Skipping checks for Friday speed is how bad bits waltz into prod.
Full Explanation
Housing authority CI must prevent unsigned build outputs from entering the production promote path by requiring signature or attestation verification before promoting artifacts. Signatures/attestations prove which trusted pipeline produced the build and bind identity to the digest. Promotion gates that verify those signatures stop arbitrary or tampered artifacts—including unsigned bits from laptops or informal transfers—from becoming production housing workloads.
Disabling all signature checks to speed Friday afternoon promotes fails by concept: speed is not a reason to drop integrity controls on civic housing systems. Promoting every artifact that appears in any developer’s Downloads folder fails provenance entirely. Replacing registries with unauthenticated USB drives between offices fails AuthN/Z, inventory, and signature enforcement.
Exam caveat: signature verification complements SBOM and registry AuthN/Z; exams may mention attestations (for example provenance attestations) alongside classic image signing. “Require verification before promote” is the control—not merely generating a signature that nothing checks.
Operational check: sign housing artifacts in CI with the official key, configure the promote stage to verify signature/attestation and fail closed on mismatch, deny unsigned digests in prod repos, prohibit USB/Downloads as promote sources, and periodically test that an unsigned build cannot advance to production.