Skip to main content

Who is this article for?

Incydr
Code42 for Enterprise
CrashPlan for Enterprise
CrashPlan for Small Business

Incydr, yes.

CrashPlan for Enterprise, no.

Code42 for Enterprise, yes.

CrashPlan for Small Business, no.

This article applies to Code42 cloud environments.

HOME
GETTING STARTED
RELEASE NOTES
FAQs
APIs
SYSTEM STATUS
Code42 Support

Introduction to adding data sources

Overview

To help protect you from data loss, you can use Code42 to monitor files moving to and from data sources such as cloud services (for example, Box, Google Drive, and OneDrive), or attachments sent through email services (such as Office 365 Outlook). You can also connect other systems or workflows to Code42 via automated integrations, speeding the process for detecting, investigating, and responding to insider risks. 

This article provides a brief introduction to adding data sources and configuring automated integrations.  

Considerations

  • You can register a Google Workspace (formerly G Suite) or Microsoft 365 account in a single Code42 environment only:
    • Once as a cloud service, to monitor file movement in Google Drive or OneDrive locations
    • Once as an email service, to monitor file attachments emailed from Gmail or Office 365 Outlook accounts
    You cannot register the same account as more than one cloud or email service. For example, you cannot register a Google Drive cloud service scoped to your Accounting users and a second Google Drive cloud service scoped to Development users when they belong to the same Google Workspace account.
  • You can only register a Google Workspace or Microsoft 365 account for one Code42 environment at a time. For example, you cannot register a OneDrive cloud service in one Code42 environment and an Office 365 DLP email service in another Code42 environment when both belong to the same Microsoft 365 account.
  • You can register two (or more) unique Google Workspace or Microsoft 365 accounts as long as these accounts are not associated in any way.
  • Code42 only monitors one domain in a Google Workspace account even though multiple domains may exist in that account. Code42 monitors only the domain associated with the administrator email address that was used to register the Google Drive or Gmail data source.
  • Data sources are not available in the Code42 federal environment.

Before you begin

Before you can add cloud or email services, you must enable File Metadata Collection.

Code42 automated integrations require setup from Code42 Professional Services. Contact your Customer Success Manager (CSM) to engage the Code42 Professional Services team and get started. 

Add cloud or email services

You can add cloud services and email services in the Code42 console from Investigation > Data Sources.

Cloud services

When you add a cloud service as a data source, we monitor the service to capture when a user: 

  • Creates a file
  • Shares a file
  • Deletes a file
  • Modifies a file

The following cloud services are available to add:

Email services

When you add an email service as a data source, we monitor the service to capture file and message information about the attachments that users have emailed to recipients. 

Configure automated integrations 

Code42 automated integrations require setup from Code42 Professional Services. Once Code42 Professional Services adds your automated integrations, they appear on the Data Sources screen. See Configure automated integrations for instructions on next steps. 

After adding cloud or email services

Once you add a cloud service or email service, file information collected from that service is available in Code42 and can be searched in Forensic Search, included in alert rules and notifications, and displayed on the Risk Exposure dashboard and in the User Profile.

If you want to stop collecting data from a cloud or email service, deauthorize it. 

After configuring automated integrations

The ways you can automate workflows depend on the systems you choose to integrate Code42 with. See Configure automated integrations for sample use cases, or contact your Customer Success Manager (CSM) for more information.