This document includes the best practices and guidelines for agents and applications such when running generative AI workloads on Google Cloud.
Configure vulnerability scanning for artifacts
| Google control ID | AR-CO-6.2 |
|---|---|
| Implementation | Required |
| Description | Use Artifact Analysis or another tool to scan for vulnerabilities in images and packages within Artifact Registry. If you use a third-party scanning tool, you must deploy these tools correctly to scan Artifact Registry for vulnerabilities in images and packages. |
| Applicable products |
|
| Path | serviceusage.getservice |
| Operator | = |
| Value |
|
| Related NIST-800-53 controls |
|
| Related CRI profile controls |
|
| Related information |
Define permitted private pools
| Google control ID | CBD-CO-6.1 |
|---|---|
| Implementation | Required |
| Description | The Use one of the following formats to define an allowed or denied list of Worker Pools:
|
| Applicable products |
|
| Path | constraints/cloudbuild.allowedWorkerPools |
| Operator | = |
| Type | String |
| Related NIST-800-53 controls |
|
| Related CRI profile controls |
|
| Related information |
Define which external services can invoke build triggers
| Google control ID | CBD-CO-6.2 |
|---|---|
| Implementation | Required |
| Description | The |
| Applicable products |
|
| Path | constraints/cloudbuild.allowedIntegrations |
| Operator | = |
| Type | List |
| Related NIST-800-53 controls |
|
| Related CRI profile controls |
|
| Related information |
Create cleanup policies for artifacts
| Google control ID | AR-CO-6.1 |
|---|---|
| Implementation | Recommended based on use case |
| Description | Cleanup policies are useful if you store many versions of your artifacts but only need to keep specific versions that you release to production. Create separate cleanup policies for deleting artifacts and retaining artifacts. |
| Applicable products |
|
| Related NIST-800-53 controls |
|
| Related CRI profile controls |
|
| Related information |