Artifact guard

Related topics

• Artifact guard works with Artifact Registry From the official documentation: “Evaluates images stored in Artifact Registry.”
• Artifact guard depends on Binary Authorization From the official documentation: “Using Binary Authorization, artifact guard blocks non-compliant images from being deployed to Google Kubernetes Engine (GKE) clusters.”
• Artifact guard works with GKE From the official documentation: “The runtime scope enables artifact guard to monitor container images running in your GKE environment.”
• Artifact guard depends on Identity and Access Management From the official documentation: “Artifact guard uses [Identity and Access Management (IAM)](/iam) roles and permissions to manage access to resources.”
• Artifact guard is part of Security Command Center From the official documentation: “Follow the steps in [Configure Security Command Center services](/security-command-center/docs/how-to-configure-security-command-center#enable-service) to enable artifact guard.”
• Artifact guard works with Security Command Center From the official documentation: “Combines scan results from CI/CD pipelines, artifact registries, and running GKE clusters into a single view in Security Command Center.”
• Artifact Registry works with Cloud Build From the official documentation: “Builds your container and pushes it to Artifact Registry.”
• Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
• Compute Engine is an alternative to GKE From the official documentation: “To use TPU7x, you can use Google Kubernetes Engine (GKE) or Compute Engine.”
• 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).”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• Artifact Registry works with Cloud Run From the official documentation: “Cloud Run recommends using Artifact Registry.”
• 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 Compute Engine From the official documentation: “Compute Engine can pull containers directly from Artifact Registry repositories.”
• 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.”
• Cloud Storage works with Compute Engine From the official documentation: “You can use a web browser, the Google Cloud CLI, or a programming language to transfer files between Cloud Storage and Compute Engine VMs.”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• VPC Service Controls secures Artifact Registry From the official documentation: “If your VPC Service Controls settings are blocking access to Artifact Registry, you must add the Artifact Registry service to the service perimeter of your VPC Service Controls.”
• VPC Service Controls secures Gemini Enterprise Agent Platform From the official documentation: “The API for Agent Platform can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”
• 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).”
• Cloud Storage works with Gemini Enterprise Agent Platform From the official documentation: “This page describes how to use Gemini Enterprise Agent Platform to export your image AutoML Edge models to Cloud Storage.”
• Identity and Access Management secures Compute Engine From the official documentation: “Compute Engine uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management secures Gemini Enterprise Agent Platform From the official documentation: “Agent Platform uses IAM to manage access to resources.”
• Identity and Access Management works with VPC Service Controls From the official documentation: “VPC Service Controls perimeters and Identity and Access Management (IAM) roles work together.”
• VPC Service Controls secures Binary Authorization From the official documentation: “By adding Binary Authorization to the security perimeter, VPC Service Controls can help protect these resources and services.”
• VPC Service Controls secures Compute Engine From the official documentation: “To further protect your Compute Engine resources, you can protect them using [VPC Service Controls](/vpc-service-controls/docs/overview).”
• 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.”
• Artifact Registry works with Gemini Enterprise Agent Platform From the official documentation: “Agent Platform supports Gemini Enterprise Agent Platform serverless training with container images on Artifact Registry or Docker Hub.”
• Artifact Registry works with Security Command Center From the official documentation: “Security Command Center aggregates vulnerability findings from Artifact Registry scans, allowing you to view container image vulnerabilities within your running workloads, across all projects alongside your other security risks in Security Command Center.”
• 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 works with Compute Engine From the official documentation: “Automating builds on repository events ensures that Cloud Build immediately validates, builds, and publishes your custom OS images to Compute Engine and Artifact Registry upon code review or merge.”
• Cloud Build is an alternative to Compute Engine From the official documentation: “If Cloud Build is not available, use a small Compute Engine VM with a cron job to pull IOC data and write to GCS.”
• 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 Run works with Compute Engine From the official documentation: “This lets Cloud Run clients use this backend service route to send requests directly to Compute Engine instances.”
• Cloud Run is an alternative to Compute Engine From the official documentation: “The decision of whether to use Cloud Run, GKE, or Compute Engine as your application host involves trade-offs between configuration flexibility and management effort.”
• Cloud Run is an alternative to Gemini Enterprise Agent Platform From the official documentation: “The application that's deployed on Cloud Run or on Gemini Enterprise routes the request to the SOC manager.”
• Cloud Storage works with GKE From the official documentation: “Route Cloud Storage events to GKE”
• Compute Engine works with GKE From the official documentation: “For example, Google Kubernetes Engine (GKE) can cause usage in Compute Engine.”
• Compute Engine works with Security Command Center From the official documentation: “After you activate Security Command Center, it starts to analyze, or scan, your resources for Compute Engine and other Google Cloud services.”
• Gemini Enterprise Agent Platform depends on Artifact Registry From the official documentation: “Certain tasks in Agent Platform require that you use additional Google Cloud products besides Agent Platform. For example, in most cases, you must use Cloud Storage and Artifact Registry when you create a custom training pipeline.”
• Gemini Enterprise Agent Platform depends on Cloud Storage From the official documentation: “Certain tasks in Agent Platform require that you use additional Google Cloud products besides Agent Platform. For example, in most cases, you must use Cloud Storage and Artifact Registry when you create a custom training pipeline.”
• Gemini Enterprise Agent Platform depends on Compute Engine From the official documentation: “Agent Platform trains your models by using Compute Engine resources.”
• Gemini Enterprise Agent Platform is an alternative to GKE From the official documentation: “You can deploy supported Hugging Face models in Gemini Enterprise Agent Platform or Google Kubernetes Engine (GKE).”
• Gemini Enterprise Agent Platform depends on Identity and Access Management From the official documentation: “Agent Platform uses IAM to manage access to resources.”