Before images from the tax-portal pipeline can deploy, the workflow runs container image scanning and secret detection. Why include those steps?
Select an answer to reveal the explanation.
Short Explanation
Image scanning and secret sniffing are the security checkpoint in the pipeline—catch the CVEs and the accidental API keys before production. Shifting that left beats finding a leaked key in a public registry later. Pretty PDFs and marketing timers aren’t the point.
Full Explanation
Security stages in CI/CD—such as container vulnerability scanning and secret detection—identify known package flaws and accidental credential exposure before deployment. Embedding those checks reduces the chance municipal workloads ship with exploitable images or embedded secrets. They complement, rather than replace, identity providers and are unrelated to PDF accessibility or marketing telemetry.