SaaS Security Administrator's Guide
    : Begin Scanning a Google Drive App
    Focus
    Download PDF
    Focus
    1. Home
    2. SaaS Security
    3. SaaS Security Administrator's Guide
    4. Data Security
    5. Secure Sanctioned SaaS Apps on Data Security
    6. Add Cloud Apps to Data Security
    7. Begin Scanning a Google Drive App
    Download PDF

    SaaS Security Administrator's Guide

    Begin Scanning a Google Drive App

    Table of Contents

    Begin Scanning a Google Drive App

    Add your Google Drive app to Data Security to begin scanning and monitoring assets for possible security risks.
    Data Security 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 Data Security 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 Data Security and assign a Super admin role.
    • Add the Google Drive app to Google Marketplace and Data Security.
    • Grant Google Drive API access to Data Security.
    Ensure that the Super Admin account added to the Strata Cloud Manager for onboarding Google Drive app has logged in at least once into the Strata Cloud Manager. Only then will the account be enabled. Onboarding will fail if this account has never logged into the Strata Cloud Manager.
    Support for automated remediation capabilities varies by SaaS application.
    Whether files are individually owned and shared (My Drive) or belong to members in a team (Shared Drives), Data Security scans and protects the assets because your end users can share data externally from Shared Drives 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 Data Security 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 Data Security to monitor the sharing of assets.
    1. Verify that your Google Drive administrator account is assigned Super admin role.
    2. Ensure that the Google Drive administrator account’s domain matches the existing domain on Data Security.
    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 Google Workspace Marketplace and log out of Google Marketplace to ensure that you're 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 same email address of the Google Drive administrator to Data Security and assign a Superuser role.
    6. Next step: Proceed to Add Google Drive App.

    Add Google Drive App

    In order for Data Security to scan assets, you must consent to specific permissions during adding the Google Drive app.
    1. To add the Google Drive app, go to Data SecurityApplicationsAdd ApplicationGoogle Drive .
    2. Before you begin: As indicated in the onscreen instruction 1, Prepare To Add Google Drive App.
    3. To onboard your Google Drive app, use Domain wide delegation and skip to Step 5 OR perform the following steps.
    4. Follow the onscreen instruction 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.
        Don't go to the link provided. Doing so aborts the onboarding process. If you inadvertently click the redirect link, simply repeat the process starting with Add Google Drive App.
      2. Click Continue to proceed with the Domain wide install process.
      3. Review and Accept the requested permissions.
        Data Security requires these permissions to scan your assets on Google Drive. A new browser window opens in the foreground.
      4. Click Done.
    5. Follow the onscreen instruction 3: Connect to Google Drive Account.
      After you enter the Google Drive admin email, the Google Drive app is installed.
      Data Security 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 Data Security. For example, if you added one Google Drive app, the name displays as Google Drive 1 .
      The Global Administrator role is required only for the onboarding process. After successful onboarding, you can downgrade the account from the Global Administrator role to a normal user role in the Google Admin Console. Additionally, you can also delete the account used to onboard Google Drive. However, if you delete the account, you cannot perform the Admin Quarantine function.
    6. Next step: Proceed to Selective Scanning on Google Drive App.

    Troubleshooting Onboarding for Google Drive App

    The validation work flow is currently not available in FedRAMP Moderate. Instead, validation will be confirmed by user activity.
    To ensure that your app has onboarded correctly without any issues in authentication or permissions, Data Security performs validation checks between the onboarding and scanning process. You can start scanning only after a successful validation. For Google Drive, the following three validations happen:
    • App Authentication
    • User Permission
    • Validating Permissions
    After the validation is successful, Data Security displays the sample data assets and sample user activities.
    If the App Authentication, User Permission, or Validating Permissions checks fail, try the following:
    1. Ensure you have administrator permissions.
    2. Check if Palo Alto Networks application is listed in the list of Google Workspace Marketplace Apps. Following are the app names for specific regions:
      • India region: NG CASB Gdrive IN
      • Australia region: Palo Alto Networks Gdrive- Aus
      • Japan region: Palo Alto Networks Gdrive- JP
      • UK region: Palo Alto Networks Gdrive- UK
      • Europe region: Prisma SaaS by Palo Alto Networks
      • Asia Pacific region: Prisma SaaS by Palo Alto Networks (Asia Pacific)
      • VPC region: Prisma SaaS by Palo Alto Networks
      • FEDM region: Palo Alto Networks-SaaS Security Gdrive-FEDM
    Handling Errors
    To understand your error messages and ways to resolve them, see:
    The other 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 Data Security.
    Make sure your Google account is super admin on Data Security 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.
    Don't log out of Data Security. Instead, open Data Security 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 in the 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 Data Security 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 Data Security.
    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 Data Security.
    If the issue persists, contact SaaS Security Technical Support.

    Fix Google Drive User Activities Monitoring Issues

    If user activities for Google Drive don't display in Data Security, contact SaaS Security Technical Support to initiate appropriate troubleshooting steps. However, if requested do so by Data Security Technical Support due to permissions issues, remove the API client access from Google, then authenticate the Google app to enable the access again.
    1. Open a web browser and log in to admin.google.com.
    2. Select Google Workspace Marketplace appsApps list.
    3. Click on Prisma SaaS by Palo Alto Networks in the list.
    4. Select Data AccessOAuth Scopes
    5. Select Revoke access.

    Selective Scanning on Google Drive App

    Customizations include modifying a Google Drive app name and specifying OUs.
    1. (Optional) Give a descriptive name to this app instance.
      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're managing.
      3. (Optional) Enter the Organizational Units for OU scanning.
        OU scanning on Google Drive is distinct from group‑based selective scanning, which is for supported cloud apps that use Azure Active Directory Services. However, the use cases are the same. Ensure that you have completed the following three steps before performing selective scanning:
        1. Add an organizational unit
        2. Move users to an organizational unit
        3. Make someone else the owner of your file
        You can enter multiple OUs including the OU name and sub-OU:
        • /—Top level of a newly added Google App
        • blank—Top level of an existing Google App
        • /Asia—A child OU of the top-level OU
        • /Asia/China—China is a child OU of the Asia OU
        • /Asia/India, /Europe—India is a child OU of the Asia OU and Europe is a child OU of the top-level OU
        For example, your domain is companydomain.com and you want to scan three OUs—finance, operations, and marking and social media OUs. Enter the OUs as a comma-separated list: /finance,/operations,/marketing/socialmedia. If you leave this field blank, all units are scanned.
        Backward scans and forward scans detect OU assets by querying the OUs for users, then querying for each user’s file ownership. A file is ignored if it exists in a folder that is owned by an OU user even if the file is owned by a non-OU user. However, if file ownership is subsequently changed to the OU user then the incremental scan discovers the file. The forward scan detects any changes to the OU configuration, including OUs that you add or delete in the OU scanning configuration or users who you add, move, or delete from OUs on Google Drive.
        If you are using Strata Cloud Manager, the Google Organizational Units cannot be edited once the app has started scanning as seen in the following screen shot.
    2. Next step: Proceed to Identify Risks.

    Identify Risks

    When you add a new cloud app and enable scanning, Data Security 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. Monitor the scan results.
      During the discovery phase, Data Security 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 the 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.

    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 Data Security, 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, Data Security displays Delete in the Activity log.
    Google API reported the action as a Delete when actually Google did in fact Move the file. Data Security displays in the Activity Log what the 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 Data Security indicates External.
    For Google shared drives, Data Security analyzes a file’s direct collaborators and the drive’s members. If one of the members is external, Data Security assigns an External exposure level.
    This behavior is expected and by design.

    Create Domain Wide Delegation

    You need domain wide delegation to make API calls to Google and fetch user data. To implement domain wide delegation, perform the following steps.
    Domain wide delegation is applicable only for Australia, UK, Japan, and India regions.
    1. Log in to the Google Admin Console as a super user and select SecurityAccess and data controlAPI controlsMANAGE DOMAIN WIDE DELEGATIONAdd new.
    2. Enter your client ID that is applicable for your region.
      • AU: 117916877802214783504
      • UK: 110579143651113261020
      • IN: 101485368660522582034
      • JP: 105441676635767149048
      • FEDM: 107464171233791181403
    3. Enter the following comma-delimited OAuth scopes and click AUTHORIZE.
      • https://www.googleapis.com/auth/userinfo.email
      • https://www.googleapis.com/auth/userinfo.profile
      • https://www.googleapis.com/auth/admin.directory.group
      • https://www.googleapis.com/auth/admin.directory.group.member
      • https://www.googleapis.com/auth/admin.directory.user
      • https://www.googleapis.com/auth/admin.directory.user.readonly
      • https://www.googleapis.com/auth/admin.directory.user.security
      • https://www.googleapis.com/auth/admin.reports.audit.readonly
      • https://www.googleapis.com/auth/drive
      • https://www.googleapis.com/auth/drive.appdata
      • https://www.googleapis.com/auth/drive.apps.readonly
      • https://www.googleapis.com/auth/drive.metadata.readonly

    © 2024 Palo Alto Networks, Inc. All rights reserved.