Disk Encryption

Cortex XDR provides full visibility into encrypted Windows and Mac endpoints that were encrypted using BitLocker and FileVault, respectively. Additionally, you can apply Cortex XDR Disk Encryption rule on the endpoints by creating disk encryption rules and policies that leverage BitLocker and FileVault capabilities.
Before you start applying disk encryption policy rules, ensure you meet the following requirements and refer to these known limitations:
Requirement / Limitation
Windows
Mac
Endpoint Pre-requisites
  • The endpoint is running a Microsoft Windows version that supports BitLocker.
  • The endpoint is within the organization network domain.
  • The endpoint is running a Cortex XDR agent 7.1 or later release
  • To allow the agent to encrypt the endpoint, Trusted Platform Module (TPM) must be supported and enabled on the endpoint.
  • To allow the agent to access the encryption recovery key backup, Active Directory Domain Services must be enabled on the endpoint.
  • The endpoint is running a macOS version that supports FileVault.
  • The endpoint is running a Cortex XDR agent 7.2 or later release.
Disk Encryption Scope
You can enforce XDR disk encryption policy rules only on the Operating System volume.
  • You can enforce XDR disk encryption policy rules only on the Operating System volume.
  • The Cortex XDR Disk Encryption profile for Mac can encrypt the endpoint disk, however it cannot decrypt it. After you disable the Cortex XDR policy rule on the endpoint, you can decrypt the endpoint manually.
Other
Group Policy configuration:
  • Make sure the GPO configuration applying to the endpoint enables
    Save BitLocker recovery information to AD DS for operating system drives
    .
  • Make sure your Cortex XDR disk encryption policy does not conflict with the GPO configuration to
    Choose drive encryption method and cipher strength
    .
  • Provide a FileVaultMaster certificate / institutional recovery key (IRK) that is signed by a valid authority.
  • It can take the agent up to 5 minutes to report the disk encryption status to Cortex XDR if the endpoint was encrypted through Cortex XDR, and up to one hour if it was encrypted through another MDM.
  • In line with the operating system requirements, the Cortex XDR encryption profile will take place on the endpoint after the user logs off and back on, and approves the prompt to enable the endpoint encryption.
  • Palo Alto Networks recommends you do not apply an encryption enforcement from another MDM on the endpoint together with the Cortex XDR encryption profile.
Follow this high-level workflow to deploy the Cortex XDR disk encryption in your network:

Monitor the Endpoint Encryption Status in Cortex XDR

You can monitor the
Encryption Status
of an endpoint in the new
Endpoints
Disk Encryption Visibility
table. For each endpoint, the table lists both system and custom drives that were encrypted.
disk-encryption-visibility.png
The following table describes both the default and additional optional fields that you can view in the
Disk Encryption Visibility
table per endpoint. The fields are in alphabetical order.
Field
Description
Encryption Status
The endpoint encryption status can be:
  • Applying Policy
    —Indicates that the Cortex XDR disk encryption policy is in the process of being applied on the endpoint.
  • Compliant
    —Indicates that the Cortex XDR agent encryption status on the endpoint is compliant with the Cortex XDR disk encryption policy.
  • Not Compliant
    —Indicates that the Cortex XDR agent encryption status on the endpoint is not compliant with the Cortex XDR disk encryption policy.
  • Not Configured
    —Indicates that no disk encryption rules are configured on the endpoint.
  • Not Supported
    —Indicates that the operating system running on the endpoint is not supported by Cortex XDR.
  • Unmanaged
    —Indicates that the endpoint encryption is not managed by Cortex XDR.
Endpoint ID
Unique ID assigned by Cortex XDR that identifies the endpoint.
Endpoint Name
Hostname of the endpoint.
Endpoint Status
The status of the endpoint. For more details, see View Details About an Endpoint.
IP Address
Last known IPv4 or IPv6 address of the endpoint.
Last Reported
Date and time of the last change in the agent’s status. For more details, see View Details About an Endpoint.
MAC Address
The MAC address of the endpoint.
Operating System
The platform running on the endpoint.
OS Version
Name of the operating system version running on the endpoint.
Volume Status
Lists all the disks on the endpoint along with the status per volume,
Decrypted
or
Encrypted
. For Windows endpoints, Cortex XDR includes the encryption method.
You can also monitor the endpoint
Encryption Status
in your
Endpoint Administration
table. If the
Encryption Status
is missing from the table, add it.

Configure a Disk Encryption Profile

  1. Log in to Cortex XDR.
    Go to
    Endpoints
    Policy Management
    Extensions Profiles
    and select
    + New Profile
    . Choose the
    Platform
    and select
    Disk Encryption
    . Click
    Next
    .
    disk-encryption-profile.png
  2. Fill-in the general information for the new profile.
    Assign a name and an optional description to the profile.
  3. Enable disk encryption.
    To enable the Cortex XDR agent to apply disk encryption rules using the operating system disk encryption capabilities,
    Enable
    the
    Use disk encryption
    option.
  4. Configure
    Encryption details
    .
    • For Windows:
      • Encrypt or decrypt the system drives.
      • Encrypt the entire disk or only the used disk space.
    • For Mac:
      Inline with the operating system requirements, when the Cortex XDR agent attempts to enforce an encryption profile on an endpoint, the endpoint user is required to enter the login password. Limit the number of login attempts to one or three. Otherwise, if you do not force log in attempts, the user can continuously dismiss the operating system pop-up and the Cortex XDR agent will never encrypt the endpoint.
  5. (
    Windows only
    ) Specify the
    Encryption methods
    per operating system.
    For each operating system (Windows 7, Windows 8-10, Windows 10 (1511) and above), select the encryption method from the corresponding list.
    You must select the same encryption method configured by the Microsoft Windows Group Policy in your organization for the target endpoints. Otherwise, if you select a different encryption method than the one already applied through the Windows Group Policy, Cortex XDR will display errors.
  6. (
    Mac only
    ) Upload the FileVaultMaster certificate.
    To enable the Cortex XDR agent encrypt your endpoint, or to help users who forgot their password to decrypt the endpoint, you must upload to Cortex XDR the FileVaultMaster certificate / institutional recovery key (IRK). You must ensure the key is signed by a valid authority and upload a CER file only.
  7. Save your profile.
    When you’re done,
    Create
    your disk encryption profile.

Apply Disk Encryption Profile to Your Endpoints

After you defined the required disk encryption profiles, you must configure the Protection Policies and enforce them on your endpoints. Cortex XDR applies Protection policies on endpoints from top to bottom, as you’ve ordered them on the page. The first policy that matches the endpoint is applied. If no policies match, the default policy that enables all communication to and form the endpoint is applied.
  1. Log in to Cortex XDR.
    Go to
    Endpoints
    Policy Management
    Extensions Policy Rules
    +New policy
    .
  2. Configure settings for the disk encryption policy.
    1. Assign a policy name and optional description.
      The platform will automatically be assigned to Windows.
    2. Assign the disk encryption profile you want to use in this rule.
    3. If desired, assign
      Device Configuration
      and/or
      Device Exceptions
      profiles and/or
      Host Firewall
      profiles. If none are assigned, the default profiles will be applied.
    4. Click
      Next
      .
    5. Select the target endpoints on which to enforce the policy.
      Use filters or manual endpoint selection to define the exact target endpoints of the policy rules.
    6. Click
      Done
      .
    Alternatively, you can associate the disk encryption profile to an existing policy. Right-click the policy and select
    Edit
    . Select the
    Disk Encryption
    profile and click
    Next
    . If needed, you can edit other settings in the rule (such as target endpoints, description, etc.) When you’re done, click
    Done
  3. Configure policy hierarchy.
    Drag and drop the policies in the desired order of execution.
  4. Save
    the policy hierarchy.
    After the policy is saved and applied to the agents, Cortex XDR enforces the disk encryption policies on your environment.

Recommended For You