build-time scanning

Related topics

• build-time scanning is part of Artifact guard From the official documentation: “Artifact guard enforces vulnerability policies across three main stages of your container lifecycle: - **Build-time scanning**: Integrates directly into CI/CD platforms (such as Cloud Build, GitHub Actions, and Jenkins) to scan containers as they are built.”
• build-time scanning works with Cloud Build From the official documentation: “**Build-time scanning**: Integrates directly into CI/CD platforms (such as Cloud Build, GitHub Actions, and Jenkins) to scan containers as they are built.”
• Cloud Build works with GKE From the official documentation: “Remove the permission granted to Cloud Build to connect to GKE.”
• Artifact guard secures 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.”
• 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).”
• 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 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 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.”