Allow Code42 access to Google Drive

Step 1: Connect Code42 to Google Drive

1. Sign in to the Code42 console.
2. Add a cloud storage data connection:
   1. Select Administration > Integrations > Data Connections. 
   2. Click Add data connection.
      The Add data connection panel opens.
   3. From Data connection, select Google Drive under Cloud storage.
      Note the Client ID and OAuth scopes details that appear near the bottom of the panel. You enter this information into the Google Admin console later in this procedure.
   4. Enter a display name. This display name must be unique.
      
3. Authorize the Code42 app in Google:
   1. Go to your Google Admin console and log in using your Google Workspace administrator username and password.
      Requires Super Admin role
      This email address must be associated with a Google Workspace administrator that has the Super Admin role.
   2. Go to Security > Access and data control > API controls. 
   3. Click Manage domain wide delegation in the Domain wide delegation panel.
   4. On the Domain-wide delegation page, click Add new next to API clients.
   5. In the Add a new client ID dialog box:
      • Copy the Client ID from the Code42 console and paste it in the Client ID field.
      • Copy the OAuth scopes from the Code42 console and paste it in the in the OAuth scopes (comma-delimited) field.
   6. Click Authorize.
      The Code42 cloud storage data connection is added to the API clients table.

Step 2: Add users

1. Return to the Code42 console.
2. In the Add data connection panel, select I've completed these steps under Complete these steps in Google Workspace and then click Continue.
   The Add Users panel appears.
   
3. Select one of the following options:
   • All: Monitors all Google Drive users in your environment, including any drives owned by suspended users.
   • Specific users: Monitors only the Google Drive users you designate.
     1. Click Upload .CSV file.
     2. Select a .csv file containing a list of only those Google Drive users you want to monitor. For details, see Upload a .csv file listing Google Drive users below.
   • Specific groups: Monitors only the users in Google Drive groups you designate.
     1. Click Upload .CSV file.
     2. Select a .csv file containing a list of Google Drive groups whose users you want to monitor. For details, see Upload a .csv file listing Google Drive groups below.
   Monitoring of shared drives is dependent on in-scope users
   Code42 monitors a shared drive only when at least one of its members is also a monitored user. During initial indexing, Code42 scans the shared drives in your Google Drive environment to identify their members. Code42 then determines which of those members are also users that are monitored by the Code42 connection. (You identify the members that are in scope for Code42 monitoring when you authorize its connection to your Google Drive environment.) If no members of that shared drive are users that are monitored, Code42 does not monitor that shared drive.

Step 3: Verify the setup

1. In the Add data connection dialog, click Continue.
   The Verify panel appears.
   
2. Enter the Google Workspace username that you used earlier to log in to the Google Admin console.
   Requires Super Admin role
   This email address must be associated with a Google Workspace administrator that has the Super Admin role.
3. Click Authorize.
   Google Drive is added as a data connection, and Code42 begins the initial indexing process.

Next steps

Once you have added Google Drive as a data connection, learn more about:

• Common use cases for investigating incidents with Forensic Search
• How to use Forensic Search
• Adding trusted domains to easily identify when files are shared with users not on your list of approved domains.

Upload a .csv file listing Google Drive users

To get a list of Google Drive users, see Google Workspace Admin Help. Create a .csv file from this list that contains only the users you want to monitor. Code42 reads usernames from column headers labeled Email Address [Required], Email Address, or Emailsin the .csv file. If these columns contain any entries that aren't email addresses, the upload produces an error.

Click to download an example of users identified by email address.

Upload a .csv file listing Google Drive groups

To create a Google Drive group, see the Google Workspace Learning Center. After your Google Drive groups are set up, create a .csv file that contains only the groups you want to monitor. In this file, use column headers to identify either the name or the email addresses of those groups.

• Code42 reads the names of groups from the column header labeledGroup Name or Groups. Specify the names of the groups exactly as they appear in the Google Admin console.
• Code42 reads a list of email addresses associated with a group from the column header labeled Email or Email Address. In the .csv file, specify the email address associated with each group.

Click to download an example of groups identified by email address.

If the .csv file does not contain at least one of these column headers, the upload produces an error.

Code42 looks for users associated with Google Drive groups as follows:

• When a group's name or email address is provided, Code42 attempts to look up users associated with that group name or group email address.
• If the group includes another group name or email address (a "nested" group), Code42 looks up users associated with that nested group as well.
• If the group name or email address cannot be found, Code42 proceeds to the next entry in the .csv file. Code42 looks for that group or email address again every 24 hours.

As users are added and removed from the monitored groups, Code42 detects these changes within 24 hours and adjusts monitoring of user drives accordingly.

Users that are removed from monitored groups have their event history preserved so that it remains searchable in Forensic Search. When an unmonitored user in your Code42 organization shares a file with a monitored user, the events associated with that file are not captured because the unmonitored user is the owner of the file.

Permissions your Google Workspace administrator needs

For more information, see Data connection is not sending security data below.

Permissions the Code42 service account needs

As a service account, Code42 uses delegated domain-wide authority to collect file events from Google Drive. A file event is any activity observed for a file, such as creating, modifying, sharing, renaming, moving, or deleting a file. To see this file activity, Code42 requires access to your Google Drive environment.

In the configuration steps above, Code42 provides the following scopes for you to enter in your Google Admin console:

Copy to clipboardCopied!

https://www.googleapis.com/auth/drive.readonly
https://www.googleapis.com/auth/admin.directory.user.readonly
https://www.googleapis.com/auth/admin.directory.group.readonly
https://www.googleapis.com/auth/admin.directory.customer.readonly
https://www.googleapis.com/auth/admin.reports.audit.readonly
https://www.googleapis.com/auth/admin.reports.usage.readonly

Configuring these scopes in the Google Admin console gives the Code42 API client delegated domain-wide authority to your Google Drive environment, and follows Google's recommendation for allowing service accounts to read content from user drives. Because of this authority, audit logs of your Google Workspace environment may show the Code42 Cloud Service account impersonating the owner of each user drive in order to read its contents.

Issues occurring during authorization

Other issues