Skip to content
Connection Guide

Connect Google Cloud Security Command Center Without Breaking the Audit Trail

Use this guide to connect Google Cloud Security Command Center or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryCloud Security
Checklist2 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect Google Cloud Security Command Center and make sure the first collection lands cleanly.

  1. 1
    Create a dedicated GCP service account and grant the narrowest Security Command Center findings-viewer access that covers the in-scope projects.
  2. 2
    Store service_account_json and project_ids; validate by listing one page of SCC findings for each configured project.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

service_account_json

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.