feat(cloud-security): add Vertex AI as a GCP Cloud Tests service#3038
Merged
Conversation
Surfaces GCP Vertex AI / Workbench security findings under a dedicated "Vertex AI" service instead of the generic "Security Command Center" bucket. - gcp-security.service.ts: add `vertex-ai` to SERVICE_NAMES; detect it from `aiplatform.googleapis.com` / `notebooks.googleapis.com` (GCP_API_TO_SERVICE) so its findings pass the enabled-services filter; and group findings by resource-type host (resolveGcpServiceId) — checking the authoritative resource type before the SCC category, since Google names AI detector categories inconsistently. Falls back to the category map, then the SCC bucket, so no finding is ever dropped. - integration-platform GCP manifest: add the Vertex AI service entry (the Services-tab catalog), with a description noting it requires SCC Premium / Enterprise. - ServiceCard: Vertex AI icon. - Tests: resolveGcpServiceId resource-type precedence + fallbacks. Notes: - Detection-gated: invisible to orgs not using Vertex AI. - A Vertex-AI org on SCC Standard will see the service with no findings (SCC doesn't scan Vertex AI on Standard) — the card description states the tier requirement. - Not yet verified against a live Vertex AI finding (no test org); mapping is built defensively on resource type, which is the stable SCC field. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
|
🎉 This PR is included in version 3.71.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds Vertex AI as a first-class service in GCP Cloud Tests. Today, GCP Cloud Tests only surface findings from Google's Security Command Center (SCC), and any finding we don't explicitly map falls into a generic "Security Command Center" bucket. This PR groups GCP Vertex AI / Workbench findings under a dedicated "Vertex AI" service.
Requested by a customer ("heavy Gemini users") who asked whether Vertex AI is covered.
What changed
gcp-security.service.tsSERVICE_NAMES: addvertex-ai → "Vertex AI".GCP_API_TO_SERVICE: detectvertex-aifromaiplatform.googleapis.com/notebooks.googleapis.com— required so its findings pass the enabled-services filter (the scan drops findings whose service isn't in the enabled set).resolveGcpServiceId(category, resourceType, resourceName): group by the resource-type host (e.g.aiplatform.googleapis.com/*) before the SCC category. Google names AI detector categories inconsistently across resources (Dataset/Model/Endpoint/Workbench; CMEK/access/policy), so resource type is the robust, authoritative signal. Falls back to the category map, then the SCC bucket — nothing is ever dropped.ServiceCard.tsx: Vertex AI icon.resolveGcpServiceIdresource-type precedence + fallbacks.Behavior / caveats (honest)
aiplatformAPI isn't enabled → not detected).generativelanguage) is a separate product not covered by SCC on any tier — out of scope.resource.typefield rather than guessed category strings, so it's defensive — but a real finding is the final proof.Tests
gcp-security.service.spec.ts: 6 new cases forresolveGcpServiceId(incl. resource-type precedence over category, and fallbacks). Full GCP spec green; changed files typecheck clean.🤖 Generated with Claude Code
Summary by cubic
Adds Vertex AI as a first-class GCP Cloud Tests service so Vertex AI and Workbench findings are grouped under “Vertex AI” instead of the generic Security Command Center bucket.
vertex-aiservice; detectaiplatform.googleapis.comandnotebooks.googleapis.com.resolveGcpServiceIdto prefer resource-type host over SCC category; falls back to category, then Security Command Center. Also matches onresourceNameifresource.typeis missing.ServiceCard.tsx.resourceNamefallback, and non-AI fallbacks.Written for commit 84fdac5. Summary will update on new commits.