Overview

The Dasera platform supports onboarding, connecting to, and scanning Data Stores across your GCP Projects.  These actions require programmatic access to connect to & scan the Data Stores, including assigning specific GCP IAM roles & API permissions.  

Below are the high-level steps for setting up the Dasera platform to scan your GCP infrastructure.

Set Up Your Dasera Instance

The Dasera platform supports several hosting options, including:

• Dasera-hosted tenants managed by us; or
• An instance you self-host within any major cloud provider, such as AWS, Azure, or GCP.

If you plan on self-hosting Dasera within GCP, you can install your instance using our Installing Dasera on GCP instructions.

Note that your Dasera instance does not need to be hosted within GCP in order to scan GCP Data Stores.  Please visit these other articles to learn about alternative hosting options:

• Installing Dasera using AWS CloudFormation 
• Launching Dasera on AWS with Terraform 
• Manually Launching on Azure 

Onboard Your GCP Infrastructure

The Dasera platform supports connecting with and scanning your GCP infrastructure.  These actions require the following configurations:

• Setting up a dedicated GCP service account and assigning specific GCP IAM roles & API permissions, using the Configuring GCP Service Accounts article.
• Once the service account setup is complete, you can create a connection between Dasera and your GCP infrastructure using the Configuring GCP Infrastructure article.

Connect Your GCP Data Stores

Regardless of where your Dasera application is hosted, the Dasera platform supports identifying and connecting with Data Stores we discover within your GCP infrastructure.  

To learn how to connect to your GCP Data Stores and initiate the Dasera platform’s scanning & analysis activities, please visit our GCP Data Store Support within Dasera article.