(408) 800-2536 support@dasera.com

Welcome to Dasera's Knowledge Base

You will find your answers here!

    Sorry, we didn't find any relevant articles for you.

    Send us your queries using the form below and we will get back to you with a solution.

    Onboarding GCP Projects Manually

    Table of Contents

    Overview Instructions

    Overview

    Dasera supports onboarding, connecting to, and scanning across your GCP Projects, either individual projects or those which participate within a GCP Organization. These actions require programmatic access to connect to & scan the Data Stores, including assigning specific IAM roles & API permissions. 

    Instructions

    The specific steps to follow depend on whether your GCP Project is a member of an organization or stands alone as an individual project. These steps will include actions you need to perform within the GCP Console. Click the tab below which corresponds to the project setup in question:

    GCP Organization

    Create Google Service Account

    Begin by configuring a service account which will be dedicated to the Dasera application's use. 

    These steps only need to be performed once on any single member GCP Project.

    Excerpt: GCP: Onboarding: Service Account

    More information about GCP's BigQuery IAM roles is available here. Click this lin

    More information about GCP's BigQuery IAM roles is available here.

    1. Click this link to log into your GCP IAM Console, which will navigate you to IAM & Admin > Service Accounts screen.
    2. Using the GCP project selector, navigate to the project for which you’d like to create the service account.
    3. Click the CREATE SERVICE ACCOUNT button (circled below).

    1. In the Service account details section, complete the following fields:
    Field Value
    Service account name Any value; it is recommended to include "Dasera" in the name, to make it easier to identify
    Service account description Any value
    1. Click the CREATE AND CONTINUE button.
    1. Click the DONE button to complete creating the service account.

    Add Custom IAM Roles

    Dasera Service Usage Role

    Dasera requires permission to specific Google APIs i.e. Cloud SQL Admin API, Cloud Data Catalog API, BigQuery API, and Cloud Resource Manager API to perform its scanning & discovery activities. A custom role needs to be created to automatically enable these APIs for all the projects under an organization during onboarding.

    The following steps need to be performed to create this custom role

    1. Click this link to log into your GCP IAM Console, which will navigate you to IAM & Admin > Roles screen.
    2. Click the CREATE ROLE button.
    3. Complete the following fields:
    Field Value
    Title

    Dasera Service Usage
    ID CustomRoleXXX, where XXX could be any numeric
    1. Click “Add Permissions” and type "Service Usage Admin" and select serviceusage.services.enable in the modal as shown below and click Add.

    1. To scan and classify data in Google Cloud Storage buckets, you must also add the following permissions:
      1. Filter permission list by Storage Admin role.
      2. Select the permissions shown in the image below. 
    storage.buckets.get
storage.buckets.getIamPolicy
storage.buckets.list
storage.buckets.listEffectiveTags
storage.buckets.listTagBindings
storage.multipartUploads.list
storage.multipartUploads.listParts
storage.objects.get
storage.objects.list
    1. Click the CREATE button to complete.

    Dasera BigQuery Connection User Role

    Dasera requires a specific Bigquery custom role to be defined and applied to the service account for a seamless connection to the Bigquery data stores. Repeat the steps as above in the IAM & Admin > Roles screen to create the role.

    Field Value
    Title

    Dasera BigQuery Connection User
    ID CustomRoleXXX, where XXX could be any numeric

    Click “Add Permissions” and type "BigQuery Connection User" and select all the permissions in the modal as shown below and click Add followed by CREATE button to complete.

    Note that the BigQuery API must be enabled for each GCP Project for which you'll connect a BigQuery data store:

    1. Visit the specific API page
    2. Click ENABLE

    1. Once enabled, you will see the following:

     

    Elevate Service Account to Organization Principal

    1. Using the GCP project selector, navigate to your organization.
    2. Within the GCP IAM Console, click the GRANT ACCESS button.
    3. In the Add principals section, search for & add the service account you created above.
    4. In the Assign roles section, configure the service account's organization access by assigning the following GCP IAM roles:
      • Dasera Service Usage (as created in Add Custom IAM Role section)
      • Dasera BigQuery Connection User (as created in Add Custom IAM Role section)
      • Cloud Spanner Viewer
      • Cloud Spanner Database Reader
      • Cloud SQL Admin (must be included to use Snapshot Scan with Cloud SQL data stores)
      • Cloud SQL Client
      • Cloud SQL Viewer
      • BigQuery Data Viewer
      • BigQuery Job User
      • BigQuery Metadata Viewer
      • BigQuery Read Session User
      • BigQuery Resource Viewer
      • Data Catalog Viewer
      • Organization Viewer
      • Pub/Sub Admin (must be included to send notifications via Google Pub/Sub)

    Click the SAVE button to complete the grant.

    Generate Google Service Key

    Excerpt: GCP: Onboarding: Service Key

     

    Once the Dasera-specific service account has been created, you can generate and download a service key, which the Dasera platform will use for connecting with your GCP infrastructure.

    1. Click this link to log into your GCP IAM Console, which will navigate you to IAM & Admin.
    2. Within the GCP IAM Console, click on the project for which you created the above service account
    3. Select the service account's details by either:
      1. Clicking its Email hyperlink; or
      2. Under the Actions column, click the three-dot icon to display the sub-menu, then select Manage Details.
    4. Click on the KEYS tab.
    1. Click the ADD KEYS button.
    2. In the displayed dropdown list, select “Create new key”.
    1. On the next screen, ensure that "Key type" equals "JSON".
    2. Click the CREATE button to download the JSON Key File to your local machine. This file will be used in the Create a Dasera Infrastructure Connection section below

    Create Dasera Infrastructure Connection

    Once a GCP Organization is connected, every member project will be automatically onboarded within the Dasera application, including members added in the future.

    Excerpt: GCP: Onboarding: Infrastructure Connection 1

     

    At this point, your configuration of GCP infrastructure is complete, and it can now be onboarded to the Dasera application. 

    1. Log into your Dasera instance.
    2. Navigate to Administration > Infrastructure Connections.
    3. Select the GCP tab.
    4. Click the Add Infrastructure button.
    5. The Add Infrastructure modal is displayed.
    6. In the JSON Key File field, upload the JSON key you created above.
    7. Enter the following additional values:

    Field Value
    I want to onboard a GCP Organization
    Organization Name Any value (this is used to identify your Infrastructure Connection within the Dasera UI).
    Organization ID Your GCP Organization ID, which can be found within the GCP Console under the IAM & Admin > Manage Resources screen.
    1. Confirm your desired organization defaults, which set the corresponding values for member projects when they are onboarded (you can change your choices at anytime):

    Excerpt: GCP: Onboarding: Infrastructure Connection 2

     

    Setting Details When Enabled
    Auto-Discovery Dasera will discover Data Stores within a GCP Project. To learn more, please visit our Data Store Inventory article.
    Ingest the Policy Tag Taxonomy Any GCP Policy Taxonomies associated with a GCP Project will be imported. To learn more, please visit our Data Tags article.
    1. Click the Acknowledge button. 

    At this point, we recommend that you permanently delete your local copy of the JSON Key File, to prevent any unauthorized use.

     

    Dasera will next verify the connection, onboard your project(s), and kick off the initial discovery of Data Stores.  Once you've completed onboarding GCP Projects, the GCP Infrastructure Connections screen will resemble the following.  Blank Organization Name values indicate individual GCP projects outside of any organization.

     
     

    Individual GCP Project

    You will repeat these steps for each individual GCP Project you wish to onboard within the Dasera application.

     

    Create Google Service Account

    Begin by configuring a Google service account which will be dedicated to Dasera's use.

    Excerpt: GCP: Onboarding: Service Account

    More information about GCP's BigQuery IAM roles is available here. Click this lin

    More information about GCP's BigQuery IAM roles is available here.

    1. Click this link to log into your GCP IAM Console, which will navigate you to IAM & Admin > Service Accounts screen.
    2. Using the GCP project selector, navigate to the project for which you’d like to create the service account.
    3. Click the CREATE SERVICE ACCOUNT button (circled below).

    1. In the Service account details section, complete the following fields:
    Field Value
    Service account name Any value; it is recommended to include "Dasera" in the name, to make it easier to identify
    Service account description Any value
    1. Click the CREATE AND CONTINUE button.

    Click the DONE button to complete creating the service account

    Add Custom IAM Roles

    Dasera Service Usage Role

    Dasera requires permission to specific Google APIs i.e. Cloud SQL Admin API,Cloud Data Catalog API and Cloud Resource Manager API to perform its scanning & discovery activities. A custom role needs to be created  to automatically enable these APIs for all the projects under an organization at the time of onboarding.

    Following  steps need to be performed to create this custom roles

    1. Click this link to log into your GCP IAM Console, which will navigate you to IAM & Admin > Roles screen.
    2. Click the CREATE ROLE button.
    3. Complete the following fields:
    Field Value
    Title

    Dasera Service Usage
    ID CustomRoleXXX, where XXX could be any numeric
    1. Click “Add Permissions” and type "Service Usage Admin" and select serviceusage.services.enable in the modal as shown below and click Add.

    1. To scan and classify data in Google Cloud Storage buckets, you must also add the following permissions:
      1. Filter permission list by Storage Admin role.
      2. Select the permissions shown in the image below. 
    storage.buckets.get
storage.buckets.getIamPolicy
storage.buckets.list
storage.buckets.listEffectiveTags
storage.buckets.listTagBindings
storage.multipartUploads.list
storage.multipartUploads.listParts
storage.objects.get
storage.objects.list
    1. Click the CREATE button to complete.

    Bigquery Connection user Role

    Dasera requires a specific Bigquery custom role to be defined and applied to the service account for a seamless connection to the Bigquery data stores. Repeat the steps as above in the IAM & Admin > Roles screen to create this role.

    Field Value
    Title

    Dasera BigQuery Connection User
    ID CustomRoleXXX, where XXX could be any numeric

    Click “Add Permissions” and type "BigQuery Connection User" and select all the  permissions in the  modal as shown below and click Add followed by CREATE button to complete.

    1. In the Grant this service account access to project section, configure the service account's project access by granting the following GCP IAM roles:
      • Dasera Service Usage (as created in Add Custom IAM Role section)
      • Dasera BigQuery Connection User (as created in Add Custom IAM Role section)
      • Cloud Spanner Viewer
      • Cloud Spanner Database Reader
      • Cloud SQL Admin (must be included to use Snapshot Scan with Cloud SQL data stores)
      • Cloud SQL Client
      • Cloud SQL Viewer
      • BigQuery Data Viewer
      • BigQuery Job User
      • BigQuery Metadata Viewer
      • BigQuery Read Session User
      • BigQuery Resource Viewer
      • Data Catalog Viewer
      • Pub/Sub Admin (must be included to send notifications via Google Pub/Sub)
    1. Click the CONTINUE button.
    2. Click the DONE button to complete creating the service account.

    Generate Google Service Key

    Excerpt: GCP: Onboarding: Service Key

     

    Once the Dasera-specific service account has been created, you can generate and download a service key, which the Dasera platform will use for connecting with your GCP infrastructure.

    1. Click this link to log into your GCP IAM Console, which will navigate you to IAM & Admin.
    2. Within the GCP IAM Console, click on the project for which you created the above service account
    3. Select the service account's details by either:
      1. Clicking its Email hyperlink; or
      2. Under the Actions column, click the three-dot icon to display the sub-menu, then select Manage Details.
    4. Click on the KEYS tab.
    1. Click the ADD KEYS button.
    2. In the displayed dropdown list, select “Create new key”.
    1. On the next screen, ensure that "Key type" equals "JSON".
    2. Click the CREATE button to download the JSON Key File to your local machine. This file will be used in the Create a Dasera Infrastructure Connection section below

    Create Dasera Infrastructure Connection

    Excerpt: GCP: Onboarding: Infrastructure Connection 1

     

    At this point, your configuration of GCP infrastructure is complete, and it can now be onboarded to the Dasera application. 

    1. Log into your Dasera instance.
    2. Navigate to Administration > Infrastructure Connections.
    3. Select the GCP tab.
    4. Click the Add Infrastructure button.
    5. The Add Infrastructure modal is displayed.
    6. In the JSON Key File field, upload the JSON key you created above.
    7. Enter the following additional values:
    Field Value
    I want to onboard a GCP Project
    Project Name Any value (this is used to identify your Infrastructure Connection within the Dasera UI).
    1. Confirm your desired GCP Project settings (you can change your choices at anytime):

    Excerpt: GCP: Onboarding: Infrastructure Connection 2

    Setting Details When Enabled Auto-Discovery Dasera will discover Data Stores with

    Setting Details When Enabled
    Auto-Discovery Dasera will discover Data Stores within a GCP Project. To learn more, please visit our Data Store Inventory article.
    Ingest the Policy Tag Taxonomy Any GCP Policy Taxonomies associated with a GCP Project will be imported. To learn more, please visit our Data Tags article.
    1. Click the Acknowledge button. 

    At this point, we recommend that you permanently delete your local copy of the JSON Key File, to prevent any unauthorized use.

     

    Dasera will next verify the connection, onboard your project(s), and kick off the initial discovery of Data Stores.  Once you've completed onboarding GCP Projects, the GCP Infrastructure Connections screen will resemble the following.  Blank Organization Name values indicate individual GCP projects outside of any organization.

     
     

     

    Was this article helpful?

    Recently Updated

    Still can't find what you are looking for?

    Contact Support