Skip to main content
Code42 Support

Activate Compliance Settings

Available in:

  • CrashPlan PRO
    • Standard
    • Premium
    • Enterprise
Applies to:

Overview

The Compliance Settings feature makes it easy to configure a variety of settings all at once to support compliance with regulations such as HIPAA, FISMA, and GLBA. This article includes considerations for using Compliance Settings and instructions for activating the feature.

About Compliance Settings

Instead of manually configuring individual settings to support a compliant Code42 environment, click a single button to activate Compliance Settings and make the changes automatically. Because Compliance Settings is a permanent change, activate it once and know the organization's settings will stay in a compliance-supporting state, without the need to continuously monitor or update the settings in the administration console.

Activating Compliance Settings:

Considerations

Review the following significant considerations before continuing.

Legal

If you are subject to HIPAA regulations, you must obtain a Business Associate Agreement before your Code42 environment can be seen as fully supporting HIPAA compliance.

Compatibility

Compliance Settings is incompatible with the Legal Hold web app, File Search web app, and Security Center, which means you can no longer collect data for a legal hold, search for user files or pattern-matching, or monitor users' file activity. To continue using these features, you must manually configure settings to support compliance.

Security

Compliance Settings upgrade the security level for the organization to archive key password, which means users can restore files only from their Code42 apps, and they are required to enter their archive key passwords to do so. Therefore, administrators cannot perform web restores, and the CrashPlan mobile app is disabled.

Move users

  • If you move a user out of a Compliance Settings organization, the user's backup archive expires immediately, and a new backup starts.
    Code42 environments fully hosted in the Code42 cloud: You must contact Code42 for Enterprise support to move the user out of a Compliance Settings organization.
  • If you move a new user into a Compliance Settings organization, the user's relevant settings are updated automatically.

Before you begin

If you have an on-premises authority server, you must upgrade the Code42 app on all user devices to version 4.8 or 5.4 or later before enabling Compliance Settings. Upgrading Code42 apps ensures that users are prompted to create archive key passwords the next time they sign in to their Code42 apps.

Upgrade your Code42 apps
If your users use SSO and you fail to upgrade their Code42 apps to version 4.8 or 5.4 or later, the users' archive key passwords are set to random, unknowable values, and the users' data are unrecoverable.

Step 1: Disable indexing

You must disable indexing for the organization in which you activate Compliance Settings. This action disables search for data that was previously indexed, and it prevents indexing going forward.

Disable indexing

  1. Sign in to the administration console.
  2. Go to Organizations.
  3. Select an organization.
  4. From the action menu, choose Edit.
    The Organization Settings dialog appears.
  5. Select Indexing.
    If you don't see the Indexing tab, it is not enabled for your Code42 environment. Skip to step 2 below.
  6. Deselect Inherit settings from parent.
  7. Deselect Index all archives in this organization.
  8. Click Save.

Step 2: Disable endpoint monitoring

You must disable endpoint monitoring for the organization in which you activate Compliance Settings. This action removes the ability to monitor users' file movements.

Disable endpoint monitoring

  1. Sign in to the administration console.
  2. Go to Organizations.
  3. Select an organization.
  4. From the action menu, choose Edit.
    The Organization Settings dialog appears.
  5. Select Endpoint Monitoring.
    If you don't see the Endpoint Monitoring tab, it is not enabled for your Code42 environment. Skip to step 3 below.
  6. Deselect Inherit settings from parent.
  7. Deselect all the boxes under Detection Types.
  8. Click Save.

Step 3: Activate Compliance Settings

After you upgrade your Code42 apps, disable indexing, and disable endpoint monitoring, activate Compliance Settings for one or more organizations.

  • Child organizations inherit the activated Compliance Settings.
  • Sibling and parent organizations are not affected.
Activate for child organizations
If your Code42 environment is in the Code42 cloud, you cannot enable Compliance Settings for your top-level organization. Activate Compliance Settings for one or more child organizations instead.

Activate compliance settings

  1. Sign in to the administration console.
  2. Go to Organizations.
  3. Select an organization.
  4. From the action menu, choose Edit.
    The Organization Settings dialog appears.
  5. Next to Compliance Settings in the upper right corner, click Activate.
    A confirmation message appears highlighting the changes to the organization's settings.
  6. Read through the information.
  7. Type ACTIVATE, and select I understand this is permanent and irreversible.
  8. Click Activate.

External resources

For a detailed explanation of HIPAA requirements, please reference the following resources from the U.S. Department of Health & Human Services:

  • Was this article helpful?