At deploy time, Binary Authorization can use signatures called attestations to determine that a process was completed earlier.
For example, you can use Binary Authorization to:
Verify that a container image was built by a specific build system or
continuous integration (CI) pipeline.
Validate that a container image is compliant with vulnerability signing policy.
Verify that a container image passes criteria for promotion to the next
deployment environment, such as development to QA.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-06 UTC."],[[["Binary Authorization is a Google Cloud service that enforces security policies at deploy-time for environments like GKE, Cloud Run, and Google Distributed Cloud."],["It supports container images in Artifact Registry and other container image registries by verifying signatures called attestations."],["Binary Authorization can verify that a container image was built by a specific system, is compliant with vulnerability signing policy, or meets promotion criteria."],["It provides documentation on how to use Binary Authorization on their documentation site."]]],[]]
