Prisma Cloud GCP agentless scan fails with 403 compute.zones.list - apply the permissions template

Not specified by the original author.

TL;DR

Per Prisma Cloud community guidance: paste the service-account JSON (not a token) and apply the permissions template, or scans fail with 403.

Steps

1. Per Prisma Cloud community guidance: paste the service-account JSON (not a token) and apply the permissions template, or scans fail with 403.

When to use

You are seeing this: Paste the full contents of the service account JSON key file into the service account field, and leave the API token field empty. Use this skill when you run into "Prisma Cloud GCP agentless scan fails with 403 compute.zones.list - apply the permissions template".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Problem: Setting up GCP agentless scanning in the Prisma Cloud Compute console. Paste the full contents of the service account JSON key file into the service account field, and leave the API token field empty. When the scan runs, "failed to create account clients ... Error 403: Required compute.zones.list permission" means the downloaded permissions template was never applied to the service account - apply it in GCP IAM, then retry the scan.

Verified resolution: Per Prisma Cloud community guidance: paste the service-account JSON (not a token) and apply the permissions template, or scans fail with 403.

Source URL: https://live.paloaltonetworks.com/t5/prisma-cloud-discussions/gcp-agentless-scanning-setup/m-p/525318/highlight/true