Skip to content

fix: doc for gcp org level integration#212

Merged
ehsandeep merged 2 commits intomainfrom
docs/gcp-org-permissions-platform
Mar 3, 2026
Merged

fix: doc for gcp org level integration#212
ehsandeep merged 2 commits intomainfrom
docs/gcp-org-permissions-platform

Conversation

@girish-cheedala
Copy link
Contributor

@girish-cheedala girish-cheedala commented Mar 2, 2026

  • we will need additional permission ( on resources ) at org level for aggregation to happen.
  • Add project Ids optional field to integration docs
  • Add gcloud cmd for getting project list

@neo-by-projectdiscovery-dev
Copy link

neo-by-projectdiscovery-dev bot commented Mar 2, 2026

Neo - PR Security Review

No security issues found

Highlights

  • Updates GCP organization-level permission documentation to include resource-specific roles (Compute Viewer, DNS Reader, Storage Bucket Viewer, Cloud Run Viewer, Cloud Functions Viewer, Kubernetes Engine Viewer)
  • Documents 10 total read-only roles required for organization-level GCP asset aggregation
  • Uses placeholder values (YOUR_PROJECT_ID, YOUR_ORG_ID) instead of real credentials

Comment @neo help for available commands. · Open in Neo

@ehsandeep ehsandeep merged commit fe460b4 into main Mar 3, 2026
5 checks passed
@ehsandeep ehsandeep deleted the docs/gcp-org-permissions-platform branch March 3, 2026 18:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants