On-Demand scanning

Related topics

• Artifact Registry works with On-Demand scanning From the official documentation: “The On-Demand Scanning API lets you scan images stored locally on your computer or remotely in Artifact Registry.”
• Cloud Build works with On-Demand scanning From the official documentation: “Use the On-Demand Scanning API in your Cloud Build pipeline”
• On-Demand scanning is part of Artifact Analysis From the official documentation: “Artifact Analysis provides two features for scanning your containers: on-demand scanning and automatic scanning.”
• Artifact Registry works with Cloud Build From the official documentation: “Builds your container and pushes it to Artifact Registry.”
• Artifact Analysis works with Artifact Registry From the official documentation: “Artifact Analysis scans new images when they're uploaded to Artifact Registry.”
• Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
• Binary Authorization secures Cloud Run From the official documentation: “Binary Authorization is a software supply chain security product for GKE and Cloud Run.”
• Cloud Build works with Cloud Run From the official documentation: “Cloud Build - create container images and deploy to Cloud Run.”
• Cloud Build works with Cloud Storage From the official documentation: “Cloud Build then stores Terraform files and the Terraform State File in a Cloud Storage bucket.”
• Cloud Run is an alternative to GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
• Cloud Storage works with Identity and Access Management From the official documentation: “To learn how to use IAM with Cloud Storage, see [Using IAM Permissions](/storage/docs/access-control/using-iam-permissions).”
• Artifact Registry works with Cloud Run From the official documentation: “Cloud Run recommends using Artifact Registry.”
• Artifact Registry works with Image Builder From the official documentation: “When you configure an Artifact Registry destination, Image Builder performs the following steps:”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• Artifact Registry works with GKE From the official documentation: “In the next tutorial, you deploy those images from the Artifact Registry repository to a GKE cluster:”
• Binary Authorization works with Cloud Build From the official documentation: “Cloud Build, which produces attestations and provenance that Binary Authorization can use for enforcement and monitoring.”
• Binary Authorization works with GKE From the official documentation: “Binary Authorization is disabled on a GKE cluster.”
• Cloud Build works with GKE From the official documentation: “Remove the permission granted to Cloud Build to connect to GKE.”
• Artifact Analysis works with Binary Authorization From the official documentation: “With Binary Authorization, you may use Artifact Analysis to store attestors and attestations as notes and occurrences, respectively.”
• Artifact Analysis works with Cloud Build From the official documentation: “Cloud Build generates this metadata and Artifact Analysis stores the information if you use Cloud Build to build the image.”
• Cloud Build works with Image Builder From the official documentation: “Image Builder outputs the test outcomes in a standard JUnit XML format directly to the Cloud Build logs.”
• Cloud Run works with GKE From the official documentation: “Leverage Google Kubernetes Engine (GKE) and Cloud Run to deploy applications to the Google Cloud, optimizing costs, performance, and management overhead.”
• Cloud Run works with Identity and Access Management From the official documentation: “Cloud Run also offers the ability to control access to a service with Identity and Access Management (IAM).”
• Artifact Analysis secures Artifact Registry From the official documentation: “Turn on Artifact Analysis, which allows for security scanning, for your Artifact Registry repository.”
• Artifact Analysis works with Cloud Storage From the official documentation: “Artifact Analysis stores your SBOMs in Cloud Storage in your Google Cloud project.”
• Artifact Analysis works with Identity and Access Management From the official documentation: “Artifact Analysis uses [Identity and Access Management (IAM)](/iam/docs/overview) to grant granular access to specific resources depending on the task you are going to perform.”
• Artifact Registry secures Cloud Run From the official documentation: “You can use Artifact Registry together with other Google Cloud products and features to improve the security posture of developer workflows and tools, software dependencies, CI/CD systems used to build and deploy your software, and runtime environments such as Google Kubernetes…”
• Artifact Registry depends on Cloud Storage From the official documentation: “The registry service hosts your custom images in Cloud Storage under your Google Cloud project.”
• Artifact Registry works with Cloud Storage From the official documentation: “| Artifact Registry | Stored in Cloud Storage, for each data chunk | |”
• Artifact Registry is an alternative to Cloud Storage From the official documentation: “Re-upload the template or definition to Artifact Registry or Cloud Storage.”
• Binary Authorization secures Artifact Registry From the official documentation: “If you're using Artifact Registry to store your artifacts, we recommend that you configure controls to help you secure your artifact repositories, such as access control, data exfiltration prevention, vulnerability scanning, and Binary Authorization.”
• Binary Authorization works with Cloud Run From the official documentation: “This guide shows you how to disable Binary Authorization for Cloud Run.”
• Binary Authorization secures GKE From the official documentation: “Binary Authorization is disabled on a GKE cluster.”
• Cloud Build depends on Cloud Storage From the official documentation: “Cloud Build uses Cloud Storage to store build resources.”
• Cloud Build depends on GKE From the official documentation: “To deploy the application in your Kubernetes cluster, Cloud Build needs the Kubernetes Engine Developer [Identity and Access Management Role](/iam/docs/understanding-roles).”
• Cloud Run depends on Artifact Registry From the official documentation: “Cloud Run function deployments use Artifact Registry to store artifacts and manage container images.”
• Cloud Run depends on Cloud Build From the official documentation: “By default, Cloud Run uses the [default machine type provided by Cloud Build](/build/pricing).”
• Cloud Storage works with GKE From the official documentation: “Route Cloud Storage events to GKE”
• GKE depends on Artifact Registry From the official documentation: “When you create or update a cluster, GKE pulls container images for the Kubernetes system software running on the control plane and nodes from Artifact Registry repositories in the `pkg.dev` or the `gcr.io` domain.”
• GKE depends on Identity and Access Management From the official documentation: “GKE relies on and can be used with many other Google Cloud services, from IAM for access control to Cloud Billing for managing your costs.”
• Identity and Access Management secures Artifact Registry From the official documentation: “This page describes access control with Identity and Access Management (IAM) in Artifact Registry.”
• Identity and Access Management secures Cloud Build From the official documentation: “To grant other users access, you can grant Identity and Access Management (IAM) roles on the project, or on a specific Cloud Build resource.”
• Identity and Access Management secures Cloud Run From the official documentation: “Cloud Run services are secured by IAM.”
• Identity and Access Management configures GKE From the official documentation: “First, as you would with most services on Google Cloud, you need to configure [IAM](/iam) roles in order to set up authorization on GKE.”
• Image Builder depends on Cloud Build From the official documentation: “Image Builder is only supported in [regions where Cloud Build is available](/build/docs/locations).”