Jump to Content
Secberus DocumentationHomeGuidesTerms & ConceptsAPI DocumentationPush APIRelease NotesStatus
HomeGuidesAPI ReferenceRelease Notes
v12.12.2

HomeGuidesTerms & ConceptsAPI DocumentationPush APIRelease NotesStatusSecberus Documentation
Guides
v12.12.2
Required Permissions
All
Pages
Start typing to search…

Getting Started

  • What is Secberus?
  • Data Collection Process
  • Terms and Concepts

Support

  • Support

Platform Setup

  • Organizations
  • User Management
    • Custom Roles
    • Available Attributes
    • API Action Permissions
  • AWS Data Source
    • AWS IAM Role
    • AWS IAM User
    • AWS Resources Collected
    • Required Permissions
  • Azure Data Source
    • Azure Resources Collected
    • Required Permissions
  • GCP Data Source
    • GCP Resources Collected
    • Required Permissions
    • Troubleshooting
  • Okta Data Source
  • Cloudflare Data Source
  • Integrations
    • Archer IRM Integration
    • Email Integration
    • Jira Integration
    • Slack Integration
    • ServiceNow Integration
    • Splunk Integration
    • Sumo Logic Integration
  • Authentication
  • API Documentation

Frameworks

  • Frameworks
  • Viewing Framework Compliance
  • Creating Frameworks
  • Modifying Frameworks
  • Deleting Frameworks

Reporting

  • Scheduled Reports
  • Export Data

Workflows

  • Workflows Overview
  • Create Workflows

Data Explorer

  • Overview
  • Tables
  • Views
  • Running Queries
  • A.I. Assistant

Policies

  • Creating Policies
  • Modifying Policies
  • Policy Exceptions
  • Managing Policy Coverage

PUSH API

  • Overview
  • Authentication
  • Custom Client Development
  • Generic Client
Powered by 

Required Permissions

In order for Secberus to collect the data it needs from your GCP project, the data source needs the following roles:

  1. The Viewer Role
  2. A custom role with the storage.buckets.getIamPolicy permission added

Updated 20 days ago


GCP Resources Collected
Troubleshooting