Begin Scanning a Google Drive App

Add your Google Drive app to SaaS Security API to begin scanning and monitoring assets for possible security risks.
SaaS Security API supports both My Drive and Shared Drives. Files in My Drive are individually owned whereas files in Shared Drives belong to members of a team. Groups in a team are not supported.
To connect a Google Drive app to SaaS Security API and begin scanning assets, you need to:
  • Ensure that you have a Google Drive admin account with Super Admin role.
  • Add the Google Drive admin account to SaaS Security API and assign a Super Admin role.
  • Add the Google Drive app to Google Marketplace and SaaS Security API.
  • Grant Google Drive API access to SaaS Security API.
For information on which automated remediation capabilities SaaS Security API supports with Google Drive, refer to Supported Applications with Remediation.
Whether files are individually owned and shared (My Drive) or belong to members in a team (Shared Drives), SaaS Security API scans and protects the assets because your end users can share data externally from Shared Drives just as easily as they can from My Drive.

Prepare To Add Google Drive App

Google’s default Super Admin role provides the necessary communication between SaaS Security API and the Google Drive app.
  • Read, write, and relocate assets in the app.
  • API access. API access provides visibility into the assets in Google Drive and allows SaaS Security API to monitor the sharing of assets.
  1. Verify that your Google Drive administrator account is assigned Super Admin role.
  2. Google Drive administrator account’s domain matches the existing domain on SaaS Security API.
  3. (
    Recommended
    ) Add your Google Drive domain as an internal domain.
  4. Log in to Google Marketplace using an account with Super Admin role permissions.
    1. Go to https://gsuite.google.com/marketplace and log out of Google Marketplace to ensure that you are not logged in as a user other than an account with Super Admin role permissions.
    2. Log in again to Google Marketplace using an account that has Super Admin role permissions.
  5. Add the email address of the Google Drive administrator to SaaS Security API and assign a Super Admin role.
  6. Next Step
    : Proceed to Add Google Drive App.

Add Google Drive App

In order for SaaS Security API to scan assets, you must consent to specific permissions during the course of adding the Google Drive app.
  1. From the
    Dashboard
    , select
    Add a Cloud App
    .
  2. Select
    Google Drive
    to launch the install.
  3. Before you begin
    : As indicated in the on-screen instructions in Step 2, Prepare To Add Google Drive App.
  4. Follow the on-screen instructions in Step 2:
    Go to Google Marketplace
    . Afterward, the
    Domain Install
    button is replaced by a disabled
    Uninstall
    button with a message that reads
    Please uninstall app for domain in Admin Console
    . This behavior is expected.
    1. Select
      Domain Install
      on the Google Marketplace page.
      Do not go to the link provided. Doing so aborts the onboarding process. If you inadvertently click the redirect link, simply repeat the process starting with launching the install.
    2. Click
      Continue
      to proceed with the
      Domain wide install
      process.
    3. Review and
      Accept
      the requested permissions.
      SaaS Security API requires these permissions to scan your assets on Google Drive. A new browser window opens in the foreground.
    4. Click
      Done
      .
  5. Follow the on-screen instructions in Step 3:
    Connect to Google Drive Account
    .
    After you enter the Google Drive admin email, you are redirected to
    Cloud Apps and Scan Settings
    on SaaS Security API. A message displays in a banner and the Google Drive:
    App installed
    .
    SaaS Security API adds the new Google Drive app to the Cloud Apps list as
    Google Drive
     n, where n is the number of Google Drive app instances that you connected to SaaS Security API. For example, if you added one Google Drive app, the name displays as
    Google Drive 1
    . You’ll specify a descriptive name soon.
  6. Next Step
    : Proceed to Customize Google Drive App.

Customize Google Drive App

Customizations include modifying Google Drive app name and assigning incident reviewer, OUs, and a Google Remediation account.
  1. (
    Optional
    ) Give a descriptive name to this app instance and specify an incident reviewer.
    1. Select the Google Drive n link on the Cloud Apps list.
    2. Enter a descriptive
      Name
      to differentiate this instance of Google Drive from other instances you are managing.
    3. Specify an
      Incident Reviewer Account
      . Use this setting with caution. The account you provide becomes a collaborator on all risks — even private files.
    4. (
      Optional
      ) Enter the
      Organizational Units
      to scan.
      You can enter multiple OUs including the OU name and sub-OU. For example, your domain is companydomain.com and you want to selectively scan three OUs—finance, operations, and marking/socialmedia OUs. Enter the OUs as a comma-separated list:
      /finance,/operations,/marketing/socialmedia
      . If you leave this field blank, all units are scanned.
  2. Set up a Google Remediation account.
    1. Select
      Settings
      , and select the corresponding Google Drive app.
    2. Enter an email address for the
      Google Remediation Account
      . This account grants access to all assets (files and folders) in the corresponding Google Drive account.
  3. Click
    Done
    to save your changes.
  4. Next Step
    : Proceed to Identify Risks.

Identify Risks

When you add a new cloud app and enable scanning, SaaS Security API automatically scans the cloud app against the default data patterns and displays the match occurrences. You can take action now to improve your scan results and identify risks.
  1. Start scanning the new Google Drive app for risks.
  2. During the discovery phase, SaaS Security API scans files and matches them against enabled default policy rules.
    Verify that your default policy rules are effective. If the results don’t capture all risks or you see false positives, proceed to the next step.
  3. (
    Optional
    ) Modify match criteria for existing policy rules.
  4. (
    Optional
    ) Add new policy rules.
    Consider the business use of your app, then identify risks unique to your enterprise. As necessary, add new:
  5. (
    Optional
    ) Configure or edit a data pattern.
    You can Configure Data Patterns to identify specific strings of text, characters, words, or patterns to make it possible to find all instances of text that match a data pattern you specify.
  6. Next Step
    : Proceed to Fix Google Drive App Onboarding Issues, if necessary.

Fix Google Drive App Onboarding Issues

The most common issues related to onboarding a Google Drive app are as follows:
Symptom
Explanation
Solution
When you click
Connect to Google Drive Account
(Step 3 of Install page), you receive an authentication error.
The Google account doesn’t have sufficient permissions to authenticate and access all the assets within Google Drive.
Make sure your Google account is an administrator with default super admin role or applicable custom role with the permission outlined in Prepare To Add Google Drive App.
When you click
Connect to Google Drive Account
(Step 3 of Install page), you receive a login error:
This email must be added as a Super Admin
The Google account doesn’t have an administrator account in SaaS Security API.
Make sure your Google account is super admin on SaaS Security API as outlined in Prepare To Add Google Drive App.
.
When you a click
Connect to Google Drive Account
(Step 3 of Install page), you’re redirected to a product landing page and the Google Drive app doesn’t appear in the Cloud Apps list.
Cached files are preventing the correct redirect.
Do not log out of SaaS Security API. Instead, open SaaS Security API in an incognito window. Repeat relaunch the Install page and click on
Connect to Google Drive Account
(Step 3) again. The Google Drive app now appears in the Cloud app list.
When click on
Go to Google Marketplace
(Step 2 of Install page), an
Please uninstall app for domain in Admin Console
message displays.
This problem usually occurs if you previously installed the app and deleted it from SaaS Security API but did not delete it from Google Marketplace.
Delete the app from the Google Marketplace, then you’ll be able to Add Google Drive App in SaaS Security API.
This problem occurs if you complete Step 2 of Install page and either abort your install or forget to click
Connect to Google Drive Account
(Step 3 of Install page).
If the Google Marketplace page is open in the same browser and session that you used when you initially added the Google Drive app, simply click
Connect to Google Drive Account
.
Otherwise, delete the Google Drive app from the Google Marketplace and repeat the Google Drive app onboarding process in SaaS Security API.

Fix Google Drive Monitoring Issues

If user activities for Google Drive do not display in SaaS Security API , contact SaaS Security Technical Support to initiate appropriate troubleshooting steps. However, if requested do so by SaaS Security API Technical Support due to permissions issues, remove the API client access from Google, then authenticate the Google app again to re-enable access.
  1. Open a web browser and log in to
    admin.google.com
    .
  2. Navigate to
    Manage API client access
    (located in
    Security
    Advanced Settings
    ).
  3. Scroll to find the list of
    Prisma SaaS
    (now SaaS Security API) clients.
  4. Click
    Remove
    .

Google Drive App Behaviors

The most common behaviors related to Google Drive app are as follows:
Symptom
Explanation
Solution
When you view a Goggle Drive asset in SaaS Security API, the
Created
date indicates a more current date than the
Last Updated
date.
lastModified
(
Last Updated
) is the date that the file is modified locally by the user and the
createDate
(
Created
) is the date that the file is uploaded (aka cloud-created) in Google Drive.
This behavior is expected due to how the Google Drive API determines timestamps.
When a user moves a file from Shared Drives to My Drive or vice versa, SaaS Security API displays
Delete
in the Activity log.
Google API reported the action as a
Delete
when actually Google did in fact
Move
the file. SaaS Security API displays in the Activity Log what Google API reports.
No known solution at this time. We communicate with our Google partner on an ongoing basis regarding its API.
Some files are shared with internal users, but SaaS Security API indicates
External
.
For Google shared drives, SaaS Security API analyzes a file’s direct collaborators and the drive’s members. If one of the members is external, SaaS Security API assigns an
External
exposure level.
This behavior is expected and by design.

Recommended For You