Skip to content

The 97 Google Cloud security checks Black Cat runs

Black Cat SSPM evaluates 97 security policies against your Google Cloud configuration on every scan, classifies each finding by risk, and provides remediation steps. Browse them by topic below.

How to connect Google Cloud — what access Black Cat needs, and why.

Identity, MFA & sign-in (4)

Access control & privilege (30)

Logging & audit (9)

Network security (5)

Configuration hardening (45)

Other checks (4)

severity: critical Public Storage Bucket fix difficulty: medium #

Remove public access from GCP Storage buckets and use signed URLs for controlled access

  1. Navigate to GCP Console > Cloud Storage > Buckets
  2. Select the public bucket
  3. Remove allUsers and allAuthenticatedUsers from bucket permissions
  4. Use signed URLs or IAM conditions for controlled access

Vendor docs ↗

Satisfies: ISO 27001:2022 A.8.27 SOC 2 Type II CC8.1 CIS Controls v8 CIS-16.1 NIST CSF 2.0 PR.DS-01 GDPR (SaaS Security) GDPR-44.1 HIPAA (SaaS Security) HIPAA-308.a4 NIS2 Directive NIS2-21.a.3 DORA (SaaS Security) DORA-9.12

severity: critical BigQuery Dataset Public Access fix difficulty: easy #

Remove allUsers and allAuthenticatedUsers access entries from the BigQuery dataset (CIS 7.1)

  1. Navigate to GCP Console > BigQuery
  2. Select the flagged dataset
  3. Click Sharing > Permissions
  4. Remove any entries granting access to allUsers or allAuthenticatedUsers
  5. Save changes

Vendor docs ↗

Satisfies: ISO 27001:2022 A.5.15 SOC 2 Type II CC6.1 CIS Controls v8 CIS-16.1 NIST CSF 2.0 PR.DS-01 NIS2 Directive NIS2-21.a.3 DORA (SaaS Security) DORA-9.11

severity: high SSL Policy Weak TLS Version fix difficulty: medium #

Update the SSL policy to require TLS 1.2 minimum and use MODERN or RESTRICTED profile (CIS 3.9)

  1. Navigate to GCP Console > Network Security > SSL Policies
  2. Select the flagged SSL policy
  3. Set minimum TLS version to TLS 1.2
  4. Change profile to MODERN or RESTRICTED
  5. Save and verify affected target proxies

Vendor docs ↗

Satisfies: ISO 27001:2022 A.8.24 SOC 2 Type II CC6.6 CIS Controls v8 CIS-03.10 NIST CSF 2.0 PR.DS-02 NIS2 Directive NIS2-21.h DORA (SaaS Security) DORA-9.7

severity: high Cloud Function Plaintext Secrets in Environment fix difficulty: medium #

Move secrets from plaintext environment variables to Secret Manager references (CIS 1.17)

  1. Identify environment variables containing secrets (API keys, tokens, passwords)
  2. Store each secret in GCP Secret Manager
  3. Navigate to GCP Console > Cloud Functions
  4. Edit the function and replace plaintext env vars with Secret Manager references
  5. Deploy the updated function and verify functionality

Vendor docs ↗

Satisfies: ISO 27001:2022 A.8.9 SOC 2 Type II CC8.1 CIS Controls v8 CIS-16.1 NIST CSF 2.0 PR.IP NIS2 Directive NIS2-21.e.3 DORA (SaaS Security) DORA-9.8

The information on this page is provided for general informational purposes and is believed to be accurate as of its most recent update. Product names, logos, and trademarks are the property of their respective owners and are used for identification purposes only; their use does not imply any affiliation with or endorsement by those owners. Descriptions of third-party applications and of compliance frameworks are based on publicly available documentation and may change over time.

See these checks run on your stack

Start a free 14-day trial — no credit card required.

Start Free Trial