GCP Vertex AI TensorBoard Without CMEK
This resource is encrypted with a Google-managed key, so access to the data cannot be revoked independently and key custody cannot be evidenced to an auditor.
Free to start. No card. The playground just needs your work email.
Google Cloud
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Encrypt Vertex AI resource with a customer-managed key.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Vertex AI TensorBoards on Google Cloud
- The fix, by hand
- Create/identify a Cloud KMS key in the resource's region.
- Recreate the resource with
encryptionSpec.kmsKeyNameset to that key. - Grant the Vertex AI service agent the Cloud KMS CryptoKey Encrypter/Decrypter role.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1348- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.