Sophos Device Encryption Administrator guide
Hirdetés
Hirdetés
Sophos Central Device
Encryption administrator guide
2
Contents
administrator guide
1 About Sophos Central Device Encryption
Sophos Central Device Encryption allows you to manage BitLocker Drive Encryption on Windows endpoints and FileVault encryption on Mac endpoints via Sophos Central. Encrypting hard disks keeps data safe, even when a device is lost or stolen.
This guide describes how to set up and use Device Encryption. It also covers how to retrieve your recovery key using the Self Service Portal. For details of the Sophos Central policy settings, alerts, and recovery via Sophos Central, see the Sophos Central Admin Help.
3
4
Sophos Central Device Encryption
2 Managing BitLocker Drive Encryption
This section describes the prerequisites for using BitLocker Drive Encryption on the Windows endpoints in your network, the various authentication modes available, and how they interact with the proprietary group policy settings.
2.1 Migrate to Sophos Central Device Encryption
If you are already using SafeGuard Enterprise with BitLocker Drive Encryption or Sophos Full
Disk Encryption this section describes how to migrate to Sophos Central Device Encryption. It covers:
■
■
■
SafeGuard Enterprise & BitLocker
SafeGuard Enterprise & Sophos Full Disk Encryption
For information on migrating Mac endpoints, see Migrate to Sophos Central Device Encryption
(page 12).
2.1.1 Migrate from SafeGuard Enterprise BitLocker
Note: If you are using BitLocker with SafeGuard Enterprise version 6.x or 7.x, we recommend that you upgrade to the newest version of SafeGuard Enterprise first.
If you are using SafeGuard Enterprise version 6.x or 7.x, you must decrypt the system disk following the steps in the SafeGuard Enterprise administrator help before you can migrate to
Sophos Central Device Encryption.
To migrate from a SafeGuard Enterprise BitLocker Client (version 8.0 or higher) to Sophos Central
Device Encryption:
1. Go to Control Panel > Uninstall a program and right-click Sophos SafeGuard Client.
2. Select Change from the right-click menu.
The Sophos SafeGuard Client Setup wizard opens.
3. Uninstall the BitLocker component.
Note: Removing the BitLocker component does not decrypt your volumes or files.
4. Install the Sophos Central Device Encryption software.
5. Make sure that a Sophos Central Device Encryption policy is assigned to the endpoint and activated.
You can now manage BitLocker using Sophos Central. You do not need to re-encrypt. Once you have applied a Sophos Central Device Encryption policy to the endpoint, the recovery key is renewed and sent to Sophos Central.
Note: File encryption functionality remains unchanged.
administrator guide
2.1.2 Migrate from Sophos Full Disk Encryption
To migrate from Sophos Full Disk Encryption:
1. Uninstall the Sophos SafeGuard Client software.
Encrypted volumes are decrypted automatically. Encrypted files remain encrypted.
2. Install the Sophos Central Device Encryption software.
3. Make sure that a Sophos Central Device Encryption policy is assigned to the endpoint and enabled.
4. Re-install the required Sophos File Encryption module (Synchronized Encryption or Location
Based File Encryption).
You can now manage BitLocker using Sophos Central. Once you have applied a Sophos Central
Device Encryption policy to the endpoint, encryption starts in the background and the recovery key is renewed and sent to Sophos Central.
2.2 Prepare Device Encryption
By default, most system drives are prepared for BitLocker. If this is not the case, Sophos Central
Device Encryption automatically runs the required Microsoft command line tool
BdeHdCfg.exe
to prepare the drive. This means that a separate BitLocker partition is created on the system drive.
During setup of Sophos Central Device Encryption, a message informs the user that a restart is required to prepare the system drive. The user can choose to restart the computer immediately or postpone the operation. Device Encryption can only start when the computer is restarted and the preparation of the system drive has been successful.
2.3 Device Encryption step by step
Before users can start:
■
The Sophos Central agent software must be installed on the endpoints.
■
■
A Device Encryption policy must be configured and enabled in Sophos Central .
Users must log on to their endpoints to have them connected to and synchronized with Sophos
Central.
■
The operating system must support BitLocker Drive Encryption. For more information, see
(page 5) and
Device Encryption system compatibility (page 6).
These instructions tell you what users will see and what they need to do:
1. If the TPM security hardware is not yet enabled, a BIOS action is triggered to enable it. This requires a restart. The user can restart immediately or postpone the restart.
During the restart, the user is prompted to enable the TPM. If the TPM cannot be enabled or the user does not respond, a message is displayed.
5
6
Sophos Central Device Encryption
2. If the TPM is active and enabled but not owned, the Sophos Central agent software automatically generates and sets TPM owner information. An alert is sent to Sophos Central if this fails.
3. If endorsement keys of the TPM are missing, the Sophos Central agent software automatically creates them. An alert is sent to Sophos Central if this fails.
Note: Not all manufacturers deliver TPM security hardware with preconfigured keys.
4. The user sees the Sophos Device Encryption dialog.
■
The dialog tells the user that a restart is necessary to enable encryption.
■
If the Sophos Central policy specifies Require startup authentication, the user has to define a PIN, passphrase, or USB key to protect the system drive. From now on, they will have to use this each time they log on. If
(page 8) is used, the encryption key for the system disk will be stored in the TPM.
Note: Users need to be careful when setting a passphrase. The pre-boot environment only supports the US-English keyboard layout. So if they set a PIN/passphrase now (in
Windows) with special characters, they might have to use different keys when they enter it to log on.
Note: The user can select Postpone to close the dialog. However, it will appear again next time the user logs on or when you change the encryption policy.
Note: You can see which users have not yet enabled encryption. Look in the Reports section in the Sophos Central Admin console.
5. When the user clicks Restart and Encrypt, the computer restarts and checks that Device
Encryption works.
Note: If the user cannot enter the correct PIN/passphrase, they can press the Esc key. The system boots normally since encryption has not been applied yet. The user is asked to try to enter the PIN/passphrase again after logon.
6. If the pre-boot test has been successful, the Sophos Central agent software starts encrypting the fixed disks. Encryption happens in the background, allowing users to work with their computer as usual.
Note: If the hardware test fails, the system reboots, encryption will not be enforced and an event will be sent to Sophos Central to notify you.
After the Sophos Central agent has encrypted the system volume, the encryption of the data volumes is started. Protection for these volumes is stored on the system volume, so that data volumes are available automatically after startup. This means that when a user logs on to their computer, the data volumes can be accessed without any further user interaction. Removable data volumes, for instance USB keys, are not encrypted.
2.4 Device Encryption system compatibility
The table below gives an overview of which protection types are supported on which platform.
The protection type applied depends on the Windows version and whether TPM security hardware is available. The number in brackets describes the priority of the specific protection type.
administrator guide
(*) When Require startup authentication is enabled, the installation of TPM-only protection is not possible and therefore TPM+PIN is the first priority.
TPM-only
TPM+PIN
-
-
Passphrase
-
USB key
ok (1)
Win 7 no TPM ok (1*) ok (2)
ok (3)
Win 7 with TPM
-
ok (1) ok (2)
Win 8 no TPM ok (1*) ok (2) ok (3) ok (4)
Win 8 with TPM
-
ok (1) ok (2)
≥Win 8.1
no TPM
≥Win 8.1
with TPM ok (1*) ok (2) ok (3) ok (4)
Note: When Windows FIPS Mode is enabled, BitLocker encryption is only supported on systems with Windows 8.1 or higher. For detailed information on BitLocker in FIPS mode on Windows 7, see https://support.microsoft.com/en-us/kb/2990184 .
Note: You can use encrypted hard drives with Sophos Central Device Encryption. For more information, see https://docs.microsoft.com/en-us/windows/device-security/encrypted-hard-drive .
2.5 Device Encryption authentication modes
You can use the Require startup authentication switch in the Device Encryption settings to control whether users need to authenticate when they log on to their computers. The authentication mode installed on the computers depends on the system, the
BitLocker group policy settings
endpoints:
■
■
(page 8)
■
■
(page 8)
(page 9)
On endpoints that are already encrypted with BitLocker, a message informs users about the required steps.
When you turn on Require startup authentication users are prompted to define a PIN / passphrase / USB key and click Apply. They will have to use this PIN / passphrase / USB key every time they start the computer after that. When you turn off Require startup authentication
TPM-only mode is applied automatically and no additional authentication is required. Users are informed that their computer will unlock the device automatically when it starts up.
Sophos Device Encryption can automatically configure the group policy object (GPO) so that all authentication modes are allowed, provided that the corresponding setting is set to not configured.
When you configure the setting manually, the software does not overwrite these definitions. For more information, see
BitLocker group policy settings
(page 9).
7
Sophos Central Device Encryption
Users can decide to postpone the installation of the authentication modes. In this case, no encryption takes place. Whenever a user logs back on to Windows or when you deploy a new encryption policy, the system prompts the user to restart the computer. After the restart, the authentication mode is installed and Device Encryption starts. Users will not be able to decrypt their devices after that.
2.5.1 TPM+PIN
The TPM+PIN mode uses the computer's TPM security hardware and a PIN as authentication.
Users have to enter this PIN in the Windows pre-boot environment every time the computer starts.
TPM+PIN requires a prepared TPM and the GPO settings of the system must allow the TPM+PIN mode.
If all conditions are met, the TPM+PIN setting dialog will be displayed and the user is prompted to define a PIN. The user can click Restart and Encrypt to immediately reboot the computer and start encryption.
If the GPO setting Allow enhanced PINs for startup is enabled, the PIN may include numbers, letters, and special characters. Otherwise, only numbers are allowed.
PINs for BitLocker are between 4 and 20 characters in length. You can define a higher minimum length through a group policy. The Sophos Central agent software sets the group policy to allow enhanced PINs. The dialog tells the user which characters may be entered and what minimum/maximum lengths are allowed.
Note: All users of a specific Windows computer need to use the same PIN to unlock the system disk. After that, they log on to the operating system with their individual credentials. Single sign-on is not supported for Windows computers.
2.5.2 Passphrase
For authentication at endpoints without TPM security hardware, a passphrase can be used. Users have to enter this passphrase in the Windows pre-boot environment every time the computer starts.
Passphrase protection requires Windows 8.0 or higher and the GPO settings of the system must allow the passphrase mode.
If all conditions are met, the passphrase setting dialog will be displayed and the user is prompted to define a passphrase of 8-100 characters in length. The user can click Restart and Encrypt to immediately reboot the computer and start encryption.
2.5.3 TPM-only
The TPM-only mode uses the computer's TPM security hardware without any PIN authentication.
This means that the user can start the computer without being prompted for a PIN in the Windows pre-boot environment.
TPM-only requires a prepared TPM and the Device Encryption policy setting Require startup
authentication must be disabled. Furthermore, the GPO settings of the system must allow
TPM-only protection.
8
administrator guide
If all conditions are met, the TPM-only protection installation dialog will be displayed. The user can click Restart and Encrypt to immediately restart the computer and start encryption.
2.5.4 USB key
The USB key mode uses a key stored on a USB flash drive for authentication. For every startup, the USB flash drive must be connected to the computer.
USB key protection is used on Windows 7 endpoints if no TPM is available or if it is disabled via
GPO.
The USB flash drive must be formatted with NTFS, FAT, or FAT32. The exFAT format is not supported. Furthermore, the USB flash drive must be writable.
If all conditions are met, the USB key protection installation dialog will be displayed and the user must select a connected USB flash drive that will be used to store the key.
The user can click Restart and Encrypt to immediately restart the computer and start encryption.
2.6 BitLocker group policy settings
Sophos Central defines some group policy settings automatically, so that administrators don't have to prepare computers for device encryption. If settings have already been defined by administrators, configured values will not be overwritten.
In the Local Group Policy Editor under Computer Configuration > Administrative Templates >
Windows Components > BitLocker Drive Encryption > Operating System Drives, you find the following policies:
Policy
Allow network unlock at startup
Setting Value set by
Sophos Central
Enabled
Comment
You can allow a pre-configured BitLocker network unlock to keep working after you have enabled Central Device Encryption.
To do this, switch on Allow network
unlock in the Device Encryption Policy.
Note: This feature may not be available for all customers yet.
Require additional authentication at startup
Allow BitLocker without a compatible TPM
Require additional authentication at startup
Configure TPM startup PIN
Checked This is set for Windows 8 if no TPM is available, to allow using a password on startup to unlock the system disk.
Allow startup PIN with TPM
If the Device Encryption policy setting
Require startup authentication is set and the system has a TPM, then this group policy setting will be set to allow protection of the system drive by TPM, with additionally asking the user for a PIN.
9
Sophos Central Device Encryption
Allow enhanced
PINs for startup n/a Enabled This is set to allow using alphanumeric
PINs to protect the system drive with TPM.
If this can't be set, only digits are allowed.
■
Encryption algorithm to be used: By default, Sophos Central Device Encryption uses AES-256.
There is a group policy setting that can be used to select AES-128.
■
PIN/password requirements: There are group policy settings that can be used to set a minimum
PIN/password length and to require complex passwords.
■
Encrypt all data or used space only: If the group policy for boot volumes and/or data volumes is set to require full data encryption, it overrides any Sophos Central policy that allows encryption of used space only.
Some group policy settings may conflict with Sophos Central so that encryption cannot be enabled.
In that case, an event is sent to Sophos Central.
■
Smart card required: If a group policy requires a smart card to be used for BitLocker, this is not supported by Sophos Central and generates an error event.
■
Encrypt all data or used space only: If the group policy for boot volumes and/or data volumes is set to encrypt used space only but Sophos Central policy requires full encryption, this generates an error event.
If you want to encrypt tablet devices (such as the MS Surface Pro) and use startup authentication, you need to enable the following group policy setting:
Enable use of BitLocker authentication requiring preboot keyboard input on slates
For more information, see Sophos knowledgebase article 125772 .
For more general information on BitLocker and TPM group policy settings, see technet.microsoft.com/en-us/library/jj679890.aspx
and technet.microsoft.com/en-us/library/jj679889.aspx
2.7 Limitations
Dynamic Disks
BitLocker does not support dynamic disks. The endpoints send an event to Sophos Central to notify you that encryption failed. This is because a system volume on a dynamic disk cannot be encrypted. Data volumes on dynamic disks are simply ignored.
Remote Desktop
When using a Windows endpoint through Remote Desktop that has the Sophos Central agent software installed, no dialogs are displayed and device encryption will NOT be enforced if an encryption policy is deployed. Enabling encryption would result in a reboot sequence to verify compatibility of the hardware. The user needs to be able to enter PIN / passphrase in the pre-boot environment and this cannot be done through Remote Desktop.
10
administrator guide
2.8 About decryption
You don't usually need to decrypt. If you need to exclude an encrypted endpoint from encryption you can do this by removing all of its users from the policy and then turning encryption off. In
Windows Explorer (on the endpoint), right-click on the system disk and select Manage BitLocker.
In the BitLocker Drive Encryption dialog, click Turn off BitLocker. Only a Windows Administrator can perform this operation.
If an encryption policy is applied and a user, with administrative privileges, attempts to manually decrypt their hard disk Sophos Central overrides the user's command and the disk will remain encrypted.
2.9 Recover Windows endpoints
If users forget their BitLocker PIN or password, they can regain access to their computer in two ways.
■
If the user was the last person to be logged into the computer, they can use the Sophos Self
Service Portal, see Retrieve recovery key via Self Service Portal
(page 18).
■
You can help them access their computer. These instructions tell you what the users will see and what they need to do. They must:
1. Restart the computer and press the Esc key in the BitLocker logon screen.
2. In the BitLocker recovery screen, find the Recovery Key ID.
3. Call the administrator and tell them the recovery key ID.
You can give them the recovery key. For help on retrieving a key for one of your users, see the Sophos Central Admin Help .
4. The user must enter the recovery key, then follow the on-screen instructions to create a new
PIN or password.
The instructions for creating a new PIN or password are displayed automatically and tell users what they need to do.
Note: This feature may not be available for all customers yet.
Users can access their computer again.
11
Sophos Central Device Encryption
3 Managing FileVault Encryption
Sophos Central Device Encryption for Mac manages the FileVault full disk encryption functionality on your Macs. Users only need their macOS login password to encrypt and access their data.
3.1 Migrate to Sophos Central Device Encryption (Mac)
If you want to use Sophos Central to manage Mac endpoints that are already encrypted with
FileVault, you need to apply a Sophos Central Device Encryption policy to these endpoints.
Note: If you are using FileVault with SafeGuard Enterprise, you must uninstall the Sophos
SafeGuard Device Encryption software first.
Before users can start:
■
The Sophos Central agent software must be installed on the endpoints.
■
■
A Device Encryption policy must be configured and enabled in Sophos Central .
Users must log on to their endpoints and have them connected to and synchronized with
Sophos Central.
Important: Without a connection to Sophos Central, the recovery key cannot be stored. If users restart their computer without the key safely stored and forget their password, they cannot access their computer. Recovery is not possible in this case.
These instructions tell you what users will see and what they need to do:
1. When users log on or when you apply a Sophos Central Device Encryption policy while the users are logged on, users are informed that Device Encryption has been set up to protect their computers.
2. To enable Sophos Central Device Encryption, users need to enter their login password and click Create key.
A new recovery key is created and stored centrally for recovery purposes. If there are other unencrypted internal disks, those disks are encrypted as well. You do not need a separate disk password for them.
3. If there are internal disks that are already encrypted with a disk password, users are prompted to enter the disk password and click Proceed.
The disk password is now managed by Sophos Central. The disk will be unlocked automatically during startup.
The endpoint is now managed by Sophos Central Device Encryption.
12
administrator guide
3.2 Device Encryption step by step (Mac)
Before users can start:
■
The Sophos Central agent software must be installed on the endpoints.
■
■
A Device Encryption policy must be configured and enabled in Sophos Central .
Users must log on to their endpoints and have them connected to and synchronized with
Sophos Central.
Important:
Without a connection to Sophos Central, the recovery key cannot be stored. If users restart their computer without the key safely stored and forget their password, they cannot access their computer. Recovery is not possible in this case.
These instructions tell you what the users will see and what they need to do. They must:
1. Enter their login password after starting their Mac. This enables Sophos Device Encryption.
2. Click either Encrypt to start the encryption of their system disk or Postpone to start the process later.
When users enter their login password and click Encrypt, the recovery key is stored both locally in the keychain and in Sophos Central.
On endpoints running macOS 10.13 or later, all existing users of an endpoint are added to
FileVault automatically. On endpoints running macOS 10.12 or earlier, each user needs to log
in separately to be added to FileVault. For more information, see Add new FileVault users
(page 13).
3. Click Restart when prompted to restart their computer and have the recovery key stored in
Sophos Central.
After the restart, the encryption of the system disk begins.
Note: If the recovery key could not be stored in Sophos Central, no restart notification is displayed. Users must not restart their computer until it was successfully stored.
When the system disk is encrypted, the internal data volumes are automatically encrypted.
Encrypted disks are automatically unlocked when the computer starts.
Notifications inform the users about the encryption status of the individual disks.
3.2.1 Add new FileVault users
If users are not added to FileVault automatically, these instructions tell you what the new users will see and what they need to do. They must:
1. Enter their login password and click Proceed.
Users can normally use their macOS login password to access their Mac and use FileVault.
2. If there is no recovery key stored in Sophos Central yet, new users must select an existing
FileVault user who can authorize this task.
13
Sophos Central Device Encryption
3. The existing FileVault user then needs to enter their login password and click Proceed.
New users can now use their macOS login password to access their Mac and use FileVault.
3.3 Recover Mac endpoints
If users forget their login password, there are several ways they can regain access to their computer.
■
If the user was the last person to be logged into the computer, they can use the Sophos Self
Service Portal, see Retrieve recovery key via Self Service Portal
(page 18).
■
■
Users can start their computer with an external Mac startup disk and then use Terminal commands to unlock the disk.
Users can start their computer in target disk mode and then use Terminal commands to unlock the disk.
■
Users can start their computer with macOS Recovery and then use Terminal commands to unlock the disk.
Note: For information on working with Terminal commands, see Unlock HFS+ volumes with
Terminal commands (page 15) and Unlock APFS volumes with Terminal commands
(page
15).
■
You can help users to regain access. These instructions tell you what the users will see and what they need to do. They must:
1. Switch on the endpoint computer and wait until the Recovery key ID is displayed.
Note: The recovery key ID is displayed only for a few minutes. To display it again, users must restart their computer.
2. Call the administrator and tell them the recovery key ID.
You can give them the recovery key. For help on retrieving a key for one of your users, see the Sophos Central Admin Help .
3. Click the question mark icon in the Password field.
A message is displayed.
4. Click the arrow icon next to the message to switch to the recovery key field.
5. Enter the recovery key, then follow the on-screen instructions to create a new password .
6. If prompted, click Create New Keychain.
Users can access their computer's startup volume again.
On endpoints running macOS 10.12 or earlier, a new recovery key will be created and stored in
Sophos Central. A recovery key can only be used once. If you need to recover a computer again later, you need to retrieve a new recovery key.
On endpoints running macOS 10.13 and Apple File System (APFS), no new recovery key is created. The existing recovery key remains valid.
14
administrator guide
3.3.1 Unlock HFS+ volumes with Terminal commands
You can use Terminal commands to unlock encrypted volumes. The commands in this section apply to endpoints running macOS 10.12 or earlier with volumes formatted with HFS+.
These instructions tell you what the users will see and what they need to do. They must:
1. Open the Terminal application and run diskutil corestorage list
.
A list of all connected volumes is displayed.
2. Search for the volume name (
LV Name
) they want to recover and note the
Logical Volume identification.
3. Call the administrator and ask for the recovery key using the
Logical Volume
identification as recovery key ID.
You give them the recovery key. For help on retrieving a key for one of your users, see the
Sophos Central Admin Help .
4. Enter the recovery key in the disk password dialog to unlock the disk.
Alternatively, users can use the command diskutil corestorage unlockVolume
and enter the recovery key in the Terminal application to unlock the disk.
The disk can now be accessed in Finder.
3.3.2 Unlock APFS volumes with Terminal commands
You can use Terminal commands to unlock encrypted volumes. The commands in this section apply to endpoints running macOS 10.13 and Apple File System (APFS).
These instructions tell you what the users will see and what they need to do. They must:
1. Open the Terminal application and run diskutil apfs list
A list of all connected volumes is displayed.
2. Search for the volume name they want to recover and note the volume identification, for example,
Volume disk1s1
.
3. Call the administrator and ask for the recovery key using the volume identification as recovery key ID.
You give them the recovery key. For help on retrieving a key for one of your users, see the
Sophos Central Admin Help .
4. Enter the recovery key in the disk password dialog to unlock the disk.
Alternatively, users can use the command diskutil apfs unlockVolume
and enter the recovery key in the Terminal application to unlock the disk.
The disk can now be accessed in Finder.
15
Sophos Central Device Encryption
16
3.3.3 Error: Failed to store the recovery key
In rare cases, the system may fail to store the recovery key locally (in the keychain) or in Sophos
Central. This means that the machine is not recoverable if users forget their password. To mitigate this risk, an error message with the recovery key is displayed and the user is prompted to make a copy of the recovery key.
The system will repeatedly attempt to store the recovery key in Sophos Central. As soon as this is successful, users are informed that a new recovery key is now managed by Sophos Central and that they can destroy their copy of the recovery key.
3.4 Accessing Device Encryption status (Mac)
Users can access information on the encryption status using the Sophos Device Encryption application. It is installed to the
Applications
directory and can be launched via Finder,
Launchpad or Spotlight.
The Sophos Device Encryption application provides the following information:
■
■
Policy status: The first line tells users whether or not their endpoint is managed by Sophos
Device Encryption.
User status: The second line tells users what they can and cannot do.
■
Disk status: A list of all internal disks is displayed. If the disk name is grayed out, the disk is currently not mounted. An icon next to the disk name indicates the status of the disk. The following statuses are available:
■
Green: The disk is fully encrypted and the recovery key is stored centrally.
■
■
■
Yellow: The disk is fully encrypted, but the recovery key is not stored in Sophos Central.
This may happen when Sophos Central is currently not reachable. If encryption of the disk is not required, the recovery key may not exist at all. This is usually the case when the disk is not managed by Sophos Central Device Encryption and it was encrypted using operating system tools.
Yellow + exclamation mark: The disk is fully encrypted, a policy exists which requires that the disk is encrypted, but there is no recovery key available.
Red: The disk is not encrypted, but a policy is active which requires that the disk must be encrypted.
■
■
■
Gray: The disk is not encrypted and the policy does not require encryption or there is no policy at all.
Status bar + Encrypting: The disk is currently being encrypted.
Status bar + Decrypting: The disk is currently being decrypted.
Note: If a user with administrative privileges on a Mac endpoint attempts to manually decrypt their hard disk with an encryption policy applied, Sophos Central cannot override this and the disk will be decrypted. When the decryption is complete the user is asked for their password to enable FileVault and the disk will be encrypted again.
■
Recovery status: At the bottom of the window, users are informed whether recovery keys are available for their disks.
administrator guide
Alternatively, you can access information on the Device Encryption status via a command line tool. The tool is installed to
/usr/local/bin/seadmin
. The following commands are available:
■
help
: Displays a list of available commands.
■
■
status
: Displays the last synchronization of the encryption software and the synchronization interval.
--device-encryption
: Displays the current encryption policy and the encryption and recovery status of all internal disks.
17
Sophos Central Device Encryption
4 Retrieve recovery key via Self Service
Portal
If users cannot log on to their computer (forgot BitLocker PIN, macOS password, etc.), they can use the Sophos Self Service Portal to retrieve a recovery key. With the recovery key, they can gain access to their computer's startup volume again.
Note: The recovery of non-startup volumes under Windows is not supported. For details about
recovering non-startup volumes on Mac, see Recover Mac endpoints
(page 14).
To enable users to recover their computers in the Self Service Portal, go to Sophos Central >
People > Users, select one or more users and click the Email Setup Link button. In the following dialog, select Sophos Central Self Service Welcome/Setup Email to email users an activation link. When users follow the instructions in the email, they can use the Sophos Self Service Portal to recover their computer.
To recover a startup volume, users have to do the following:
1. Log on to the Sophos Self Service Portal using another computer.
2. Go to the Device Encryption page.
A list of all computers where the user was the last one to be logged on is displayed. If someone else has logged on to a computer in the meantime, the user cannot regain access to this computer via the Self Service Portal.
3. Select a computer from the list and click the Retrieve button in the RECOVERY KEY column.
A dialog with the recovery key is displayed.
4. Start their own computer and go to the recovery page.
■
■
Windows: Press the Esc key to switch to the BitLocker recovery page.
Mac: Click the question mark icon in the Password field to switch to the FileVault recovery page.
5. Enter the recovery key.
Users can access their computer's startup volume again.
18
administrator guide
5 Further reading
General
■
FAQs: Sophos knowledgebase article 124819
Windows
■
BitLocker FAQ: technet.microsoft.com/en-us/library/hh831507.aspx
■
BitLocker Group Policy Settings: technet.microsoft.com/en-us/library/jj679890.aspx
■
TPM Fundamentals: technet.microsoft.com/en-us/library/jj889441.aspx
■
TPM Group Policy Settings: technet.microsoft.com/en-us/library/jj679889.aspx
■
Trusted Platform Module Administration Technical Overview: technet.microsoft.com/en-us/library/cc766159(v=WS.10).aspx
Mac
■
FileVault: https://support.apple.com/kb/PH25107?locale=en_US
■
■
■
Setup: https://support.apple.com/en-us/HT202385
Deployment: http://training.apple.com/pdf/WP_FileVault2.pdf
Recovery: https://support.apple.com/en-us/HT202860
19
Sophos Central Device Encryption
6 Technical support
You can find technical support for Sophos products in any of these ways:
■
Visit the Sophos Community at community.sophos.com/ and search for other users who are experiencing the same problem.
■
■
■
Visit the Sophos support knowledgebase at www.sophos.com/en-us/support.aspx
.
Download the product documentation at www.sophos.com/en-us/support/documentation.aspx
.
Open a ticket with our support team at https://secure2.sophos.com/support/contact-support/support-query.aspx
.
20
administrator guide
7 Legal notices
Copyright
©
2017 Sophos Limited. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise unless you are either a valid licensee where the documentation can be reproduced in accordance with the license terms or you otherwise have the prior permission in writing of the copyright owner.
Sophos, Sophos Anti-Virus and SafeGuard are registered trademarks of Sophos Limited, Sophos
Group and Utimaco Safeware AG, as applicable. All other product and company names mentioned are trademarks or registered trademarks of their respective owners.
Last update: 20170915
21
Letöltés
A nyilvános link frissítve
A csevegés nyilvános linkje frissítve lett. You may view and manage your chat links after registration here.
Dokumentum nyilvános linkje
Hirdetés
