attestation

Related topics

• attestation depends on attestor From the official documentation: “An attestation is a statement by an attestor that a required process in your pipeline is complete and a container image is authorized for deployment.”
• attestation is part of Binary Authorization From the official documentation: “This guide describes how to create and use Binary Authorization [attestations](/binary-authorization/docs/key-concepts#attestations).”
• attestation works with Confidential VM From the official documentation: “Remote attestation is the process of verifying that a Confidential VM instance's identity is legitimate, and that it's operating in an expected state.”
• attestation depends on policy From the official documentation: “To use attestations, you must require attestations in the appropriate [rule](/binary-authorization/docs/key-concepts#rules) of your [policy](/binary-authorization/docs/key-concepts#policies).”
• attestation depends on signer From the official documentation: “An *attestation* is a digital document created by a [signer](/binary-authorization/docs/key-concepts#signers) that certifies that GKE is allowed to deploy the associated container image.”
• attestor depends on attestation From the official documentation: “At deploy time, the attestor verifies the attestation using the public key from the key pair.”
• attestor is part of Binary Authorization From the official documentation: “Create the attestor itself in Binary Authorization”
• Binary Authorization depends on attestor From the official documentation: “Binary Authorization uses the public key in the attestor to verify the attestation.”
• Binary Authorization works with Google Kubernetes Engine From the official documentation: “Using Binary Authorization on Google Kubernetes Engine ensures that the MLLP adapter can only be deployed from a verified and signed container image.”
• Binary Authorization secures Google Kubernetes Engine From the official documentation: “This lab describes how to secure a GKE cluster using Binary Authorization.”
• Confidential VM works with Google Kubernetes Engine From the official documentation: “Confidential VM is also available for use in the following products: - [Dataflow](/dataflow/docs/reference/service-options) - [Managed Service for Apache Spark](/dataproc/docs/concepts/configuring-clusters/confidential-compute) - [Google Kubernetes…”
• Dry run mode is part of Binary Authorization From the official documentation: “To test dry-run mode, deploy images that violate the policy and then view dry-run mode events from Binary Authorization for [GKE](/binary-authorization/docs/viewing-audit-logs#dry_run_events), [Cloud…”
• Dry run mode is part of policy From the official documentation: “Dry run mode is an enforcement mode in a policy that allows non-conformant images to be deployed, but writes details about the policy violation and deployment to the audit log.”
• policy is part of Binary Authorization From the official documentation: “A [policy](/binary-authorization/docs/key-concepts#policies) in Binary Authorization is a set of rules that govern the deployment of container images.”