Merge pull request #5168 from baardhermansen/patch-2

Update prepare-your-organization-for-bitlocker-planning-and-policies.md

windows/security/information-protection/bitlocker/prepare-your-organization-for-bitlocker-planning-and-policies.md

@@ -20,24 +20,14 @@ ms.date: 04/24/2019
 # Prepare your organization for BitLocker: Planning and policies
 
 **Applies to**
+
 - Windows 10
 
 This topic for the IT professional explains how can you plan your BitLocker deployment.
 
 When you design your BitLocker deployment strategy, define the appropriate policies and configuration requirements based on the business requirements of your organization. The following topics will help you collect information that you can use to frame your decision-making process about deploying and managing BitLocker systems.
 
--   [Audit your environment](#bkmk-audit)
+## Audit your environment
--   [Encryption keys and authentication](#bkk-encrypt)
--   [TPM hardware configurations](#bkmk-tpmconfigurations)
--   [Non-TPM hardware configurations](#bkmk-nontpm)
--   [Disk configuration considerations](#bkmk-disk)
--   [BitLocker provisioning](#bkmk-prov)
--   [Used Disk Space Only encryption](#bkk-used)
--   [Active Directory Domain Services considerations](#bkmk-addscons)
--   [FIPS support for recovery password protector](#bkmk-fipssupport)
--   [BitLocker Group Policy settings](bitlocker-group-policy-settings.md)
-
-## <a href="" id="bkmk-audit"></a>Audit your environment
 
 To plan your enterprise deployment of BitLocker, you must first understand your current environment. Conduct an informal audit to define your current policies, procedures, and hardware environment. Begin by reviewing your existing corporate security policies as they relate to disk encryption software. If your organization is not currently using disk encryption software, none of these policies will exist. If you are using disk encryption software, then you might need to modify your organization's policies to address the capabilities of BitLocker.
 
@@ -49,7 +39,7 @@ Use the following questions to help you document your organization's current dis
 4. What policies exist to control who in the organization has access to recovery data?
 5. What policies exist to control computer decommissioning or retirement?
 
-## <a href="" id="bkk-encrypt"></a>Encryption keys and authentication
+## Encryption keys and authentication
 
 BitLocker helps prevent unauthorized access to data on lost or stolen computers by:
 
@@ -101,7 +91,7 @@ If there are areas of your organization where data residing on user computers is
 
 The protection differences provided by multifactor authentication methods cannot be easily quantified. Consider each authentication method's impact on Helpdesk support, user education, user productivity, and automated systems management processes.
 
-## <a href="" id="bkmk-tpmconfigurations"></a>TPM hardware configurations
+## TPM hardware configurations
 
 In your deployment plan, identify what TPM-based hardware platforms will be supported. Document the hardware models from an OEM of your choice, so that their configurations can be tested and supported. TPM hardware requires special consideration during all aspects of planning and deployment.
 
@@ -117,7 +107,7 @@ An endorsement key can be created at various points in the TPM’s lifecycle, bu
 
 For more information about the TPM and the TCG, see the Trusted Computing Group: Trusted Platform Module (TPM) Specifications (<https://go.microsoft.com/fwlink/p/?linkid=69584>).
 
-## <a href="" id="bkmk-nontpm"></a>Non-TPM hardware configurations
+## Non-TPM hardware configurations
 
 Devices that do not include a TPM can still be protected by drive encryption. Windows To Go workspaces can be BitLocker protected using a startup password and PCs without a TPM can use a startup key.
 
@@ -129,7 +119,7 @@ Use the following questions to identify issues that might affect your deployment
 
 Test your individual hardware platforms with the BitLocker system check option while you are enabling BitLocker. The system check will ensure that BitLocker can read the recovery information from a USB device and encryption keys correctly before it encrypts the volume. CD and DVD drives cannot act as a block storage device and cannot be used to store the BitLocker recovery material.
 
-## <a href="" id="bkmk-disk"></a>Disk configuration considerations
+## Disk configuration considerations
 
 To function correctly, BitLocker requires a specific disk configuration. BitLocker requires two partitions that meet the following requirements:
 
@@ -142,7 +132,7 @@ Windows Recovery Environment (Windows RE) is an extensible recovery platform tha
 
 Windows RE can also be used from boot media other than the local hard disk. If you choose not to install Windows RE on the local hard disk of BitLocker-enabled computers, you can use alternate boot methods, such as Windows Deployment Services, CD-ROM, or USB flash drive, for recovery.
 
-## <a href="" id="bkmk-prov"></a>BitLocker provisioning
+## BitLocker provisioning
 
 In Windows Vista and Windows 7, BitLocker was provisioned post installation for system and data volumes through either the manage-bde command line interface or the Control Panel user interface. With newer operating systems, BitLocker can be easily provisioned before the operating system is installed. Preprovisioning requires that the computer have a TPM.
 
@@ -152,7 +142,7 @@ When using the control panel options, administrators can choose to **Turn on Bit
 
 Administrators can enable BitLocker prior to operating system deployment from the Windows Pre-installation Environment (WinPE). This is done with a randomly generated clear key protector applied to the formatted volume and encrypting the volume prior to running the Windows setup process. If the encryption uses the Used Disk Space Only option this step takes only a few seconds and so incorporates well into regular deployment processes.
 
-## <a href="" id="bkk-used"></a>Used Disk Space Only encryption
+## Used Disk Space Only encryption
 
 The BitLocker Setup wizard provides administrators the ability to choose the Used Disk Space Only or Full encryption method when enabling BitLocker for a volume. Administrators can use the new BitLocker Group Policy setting to enforce either Used Disk Space Only or Full disk encryption.
 
@@ -162,7 +152,7 @@ Used Disk Space Only means that only the portion of the drive that contains data
 
 Full drive encryption means that the entire drive will be encrypted, regardless of whether data is stored on it or not. This is useful for drives that have been repurposed and may contain data remnants from their previous use.
 
-## <a href="" id="bkmk-addscons"></a>Active Directory Domain Services considerations
+## Active Directory Domain Services considerations
 
 BitLocker integrates with Active Directory Domain Services (AD DS) to provide centralized key management. By default, no recovery information is backed up to Active Directory. Administrators can configure the following Group Policy setting for each drive type to enable backup of BitLocker recovery information:
 
@@ -180,11 +170,12 @@ The following recovery data is saved for each computer object:
 
     With this key package and the recovery password, you will be able decrypt portions of a BitLocker-protected volume if the disk is severely damaged. Each key package will only work with the volume it was created on, which can be identified by the corresponding volume ID.
 
-## <a href="" id="bkmk-fipssupport"></a>FIPS support for recovery password protector
+## FIPS support for recovery password protector
 
 Functionality introduced in Windows Server 2012 R2 and Windows 8.1, allows BitLocker to be fully functional in FIPS mode.
 
->**Note:**  The United States Federal Information Processing Standard (FIPS) defines security and interoperability requirements for computer systems that are used by the U.S. federal government. The FIPS 140 standard defines approved cryptographic algorithms. The FIPS 140 standard also sets forth requirements for key generation and for key management. The National Institute of Standards and Technology (NIST) uses the Cryptographic Module Validation Program (CMVP) to determine whether a particular implementation of a cryptographic algorithm is compliant with the FIPS 140 standard. An implementation of a cryptographic algorithm is considered FIPS 140-compliant only if it has been submitted for and has passed NIST validation. An algorithm that has not been submitted cannot be considered FIPS-compliant even if the implementation produces identical data as a validated implementation of the same algorithm. 
+> [!NOTE]
+> The United States Federal Information Processing Standard (FIPS) defines security and interoperability requirements for computer systems that are used by the U.S. federal government. The FIPS 140 standard defines approved cryptographic algorithms. The FIPS 140 standard also sets forth requirements for key generation and for key management. The National Institute of Standards and Technology (NIST) uses the Cryptographic Module Validation Program (CMVP) to determine whether a particular implementation of a cryptographic algorithm is compliant with the FIPS 140 standard. An implementation of a cryptographic algorithm is considered FIPS 140-compliant only if it has been submitted for and has passed NIST validation. An algorithm that has not been submitted cannot be considered FIPS-compliant even if the implementation produces identical data as a validated implementation of the same algorithm.
 
 Prior to these supported versions of Windows, when Windows was in FIPS mode, BitLocker prevented the creation or use of recovery passwords and instead forced the user to use recovery keys. For more information about these issues, see the support article [kb947249](https://support.microsoft.com/kb/947249).