Skip to content

GCP

Cloud platforms. Cloud Audit Logs and Security Command Center findings.

Status: available now - you connect this yourself

This source is live in the console. Create the read-only credential below, connect it on its card in Integrate -> Sources, and your dedicated instance starts collecting.

What SheerSight reads

SheerSight reads two Google Cloud feeds:

  • Cloud Audit Logs (Admin Activity and Data Access), and
  • Security Command Center findings (optional).

That feed powers detections such as an IAM policy change, a firewall change, a service account key created, a logging sink deleted, secret access, high-severity SCC findings, an active SCC threat, and a data-access burst.

It is read-only.

What you'll need

  • A GCP user who can create a service account and grant roles on the project, and, if you want Security Command Center findings, on the organization.
  • Permission to create a service account key. Newer Google Cloud organizations block this by default with the iam.disableServiceAccountKeyCreation organization policy constraint. If key creation is blocked for you, ask your organization administrator before you continue.
  • Your dedicated instance enrolled.

Turn on the Google Cloud prerequisites

In the project you will monitor:

  1. Enable the APIs. In APIs & Services -> Library, make sure Cloud Logging API is enabled, and enable Security Command Center API if you want findings. Without an enabled API, Google returns a permission error (HTTP 403) even when the roles are right. Google counts the API calls against the project that owns the service account, so create the service account in this same project (the next section does) or enable the APIs in the project it lives in.
  2. Turn on Data Access audit logs for the services you want covered, in IAM & Admin -> Audit Logs. Google leaves Data Access logs off for most services by default (BigQuery is the main exception), so those services produce no data-access events until you enable them. Admin Activity logs are always on. If you route Data Access logs to a custom log bucket, the service account also needs access to read that bucket's logs.
  3. For findings, make sure Security Command Center is activated for your organization.

Create the read-only credential

You create a service account with a JSON key and grant it read-only roles.

  1. In the Google Cloud console, go to IAM & Admin -> Service Accounts -> Create service account, in the project you will monitor. Name it sheersight-gcp.
  2. Grant it, at the project level, both of these roles:

    • Logs Viewer (roles/logging.viewer) for Admin Activity audit logs.
    • Private Logs Viewer (roles/logging.privateLogViewer) for Data Access audit logs.

    Logs Viewer alone cannot read Data Access logs, so both roles are needed. 3. Optional, for Security Command Center findings: grant it, at the organization level, Security Center Findings Viewer (roles/securitycenter.findingsViewer). Findings are an organization resource, so this role is granted on the organization, not the project. Skip this step if you do not want findings. 4. Open the service account -> Keys -> Add key -> Create new key -> JSON, and download the key. 5. Note the Project ID and, if you granted the organization role, your Organization ID.

Which Project ID

Use the short project ID from the project dashboard, such as my-project-123456: 6 to 30 lowercase letters, digits or hyphens, starting with a letter and not ending with a hyphen. It is not the project name or the project number. The Organization ID is the numeric organization id, digits only.

Connect it in SheerSight

In the console, open Integrate -> Sources -> GCP and fill in:

Field Value
Service account key JSON The entire key file from step 4, pasted as it is.
Project ID The project you granted the two logging roles on.
Organization ID Optional. Only for Security Command Center findings. Leave it blank to skip findings.

Enter an authenticator code if prompted, then press Connect. The key is encrypted in your browser before it is sent, and we never see it. Paste it only into the encrypted key field, never into chat or a support ticket. The service account email is read from the key file, so there is no separate email field.

Verify

  1. The relayed credentials entry moves from pending to applied.
  2. The GCP source badge moves from not connected to live.
  3. Audit-log events begin appearing, and matching detections start firing. Findings appear only if you gave an Organization ID.

Troubleshooting

  • Error: "The credential lacks a required permission/scope" (HTTP 403). The most common cause is a missing role. Check that the service account has both Logs Viewer and Private Logs Viewer on the project. Also check that the Cloud Logging API is enabled, and, if you use findings, the Security Command Center API too, on the project that owns the service account.
  • Audit logs but no findings. Confirm Security Center Findings Viewer is granted on the organization, that you entered the Organization ID, and that Security Command Center is activated.
  • Admin Activity events but no data-access events. Data Access audit logs are off by default for most services; turn them on under IAM & Admin -> Audit Logs.
  • No data. Re-check the Project ID and Organization ID, and that the key belongs to the service account you granted the roles to.
  • To change a value later, once the card has reported from your instance, fill in only the fields you are changing; blank fields keep their current value.

To check what a service account has been granted, an administrator can run these read-only commands (replace the placeholders). They print role names only:

gcloud projects get-iam-policy YOUR_PROJECT_ID --flatten="bindings[].members" --filter="bindings.members:serviceAccount:YOUR_SA_EMAIL" --format="value(bindings.role)"
gcloud services list --enabled --project YOUR_PROJECT_ID --filter="name:(logging.googleapis.com OR securitycenter.googleapis.com)" --format="value(name)"
gcloud organizations get-iam-policy YOUR_ORG_ID --flatten="bindings[].members" --filter="bindings.members:serviceAccount:YOUR_SA_EMAIL" --format="value(bindings.role)"

The first command lists project roles and the last lists organization roles, which is where Security Center Findings Viewer shows up.

What SheerSight can and cannot do

The roles are read-only. SheerSight cannot change GCP resources, IAM, firewall, or security settings, and it cannot dismiss findings or act in your project or organization. It only reads logs and findings.