mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 10:23:37 +00:00
Merge branch 'master' into v-smandalika-vl-rlb-4457208
This commit is contained in:
@ -18,14 +18,14 @@ ms.date: 02/28/2019
|
||||
ms.custom: bitlocker
|
||||
---
|
||||
|
||||
# BCD settings and BitLocker
|
||||
# Boot Configuration Data settings and BitLocker
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
|
||||
This topic for IT professionals describes the BCD settings that are used by BitLocker.
|
||||
This topic for IT professionals describes the Boot Configuration Data (BCD) settings that are used by BitLocker.
|
||||
|
||||
When protecting data at rest on an operating system volume, during the boot process BitLocker verifies that the security sensitive boot configuration data (BCD) settings have not changed since BitLocker was last enabled, resumed, or recovered.
|
||||
When protecting data at rest on an operating system volume, during the boot process BitLocker verifies that the security sensitive BCD settings have not changed since BitLocker was last enabled, resumed, or recovered.
|
||||
|
||||
## BitLocker and BCD Settings
|
||||
|
||||
|
@ -28,7 +28,7 @@ This topic for the IT professional explains how BitLocker features can be used t
|
||||
|
||||
## Using BitLocker to encrypt volumes
|
||||
|
||||
BitLocker provides full volume encryption (FVE) for operating system volumes, as well as fixed and removable data volumes. To support fully encrypted operating system volumes, BitLocker uses an unencrypted system volume for the files required to boot, decrypt, and load the operating system. This volume is automatically created during a new installation of both client and server operating systems.
|
||||
BitLocker provides full volume encryption (FVE) for operating system volumes, as well as fixed and removable data drives. To support fully encrypted operating system drives, BitLocker uses an unencrypted system partition for the files required to boot, decrypt, and load the operating system. This volume is automatically created during a new installation of both client and server operating systems.
|
||||
|
||||
In the event that the drive was prepared as a single contiguous space, BitLocker requires a new volume to hold the boot files. BdeHdCfg.exe can create these volumes.
|
||||
|
||||
|
@ -43,7 +43,7 @@ Before Windows starts, you must rely on security features implemented as part of
|
||||
|
||||
### Trusted Platform Module
|
||||
|
||||
A TPM is a microchip designed to provide basic security-related functions, primarily involving encryption keys.
|
||||
A trusted platform module (TPM) is a microchip designed to provide basic security-related functions, primarily involving encryption keys.
|
||||
On some platforms, TPM can alternatively be implemented as a part of secure firmware.
|
||||
BitLocker binds encryption keys with the TPM to ensure that a computer has not been tampered with while the system was offline.
|
||||
For more info about TPM, see [Trusted Platform Module](https://docs.microsoft.com/windows/device-security/tpm/trusted-platform-module-overview).
|
||||
@ -126,7 +126,7 @@ For SBP-2 and 1394 (a.k.a. Firewire), refer to the “SBP-2 Mitigation” sectio
|
||||
|
||||
## Attack countermeasures
|
||||
|
||||
This section covers countermeasures for specific types attacks.
|
||||
This section covers countermeasures for specific types of attacks.
|
||||
|
||||
### Bootkits and rootkits
|
||||
|
||||
@ -162,7 +162,7 @@ The following sections cover mitigations for different types of attackers.
|
||||
|
||||
Physical access may be limited by a form factor that does not expose buses and memory.
|
||||
For example, there are no external DMA-capable ports, no exposed screws to open the chassis, and memory is soldered to the mainboard.
|
||||
This attacker of opportunity does not use destructive methods or sophisticated forensics hardware/software.
|
||||
This attacker of opportunity does not use destructive methods or sophisticated forensics hardware/software.
|
||||
|
||||
Mitigation:
|
||||
- Pre-boot authentication set to TPM only (the default)
|
||||
@ -172,7 +172,7 @@ Mitigation:
|
||||
Targeted attack with plenty of time; this attacker will open the case, will solder, and will use sophisticated hardware or software.
|
||||
|
||||
Mitigation:
|
||||
- Pre-boot authentication set to TPM with a PIN protector (with a sophisticated alphanumeric PIN to help the TPM anti-hammering mitigation).
|
||||
- Pre-boot authentication set to TPM with a PIN protector (with a sophisticated alphanumeric PIN [enhanced pin] to help the TPM anti-hammering mitigation).
|
||||
|
||||
-And-
|
||||
|
||||
|
@ -23,7 +23,7 @@ ms.custom: bitlocker
|
||||
- Windows 10
|
||||
|
||||
This topic explains how BitLocker Device Encryption can help protect data on devices running Windows 10.
|
||||
For a general overview and list of topics about BitLocker, see [BitLocker](bitlocker-overview.md).
|
||||
For a general overview and list of topics about BitLocker, see [BitLocker](bitlocker-overview.md).
|
||||
|
||||
When users travel, their organization’s confidential data goes with them. Wherever confidential data is stored, it must be protected against unauthorized access. Windows has a long history of providing at-rest data-protection solutions that guard against nefarious attackers, beginning with the Encrypting File System in the Windows 2000 operating system. More recently, BitLocker has provided encryption for full drives and portable drives. Windows consistently improves data protection by improving existing options and by providing new strategies.
|
||||
|
||||
|
@ -593,7 +593,7 @@ After you've decided where your protected apps can access enterprise data on you
|
||||
|
||||
**Use Azure RMS for WIP.** Determines whether WIP uses [Microsoft Azure Rights Management](https://products.office.com/business/microsoft-azure-rights-management) to apply EFS encryption to files that are copied from Windows 10 to USB or other removable drives so they can be securely shared amongst employees. In other words, WIP uses Azure Rights Management "machinery" to apply EFS encryption to files when they are copied to removable drives. You must already have Azure Rights Management set up. The EFS file encryption key is protected by the RMS template’s license. Only users with permission to that template will be able to read it from the removable drive. WIP can also integrate with Azure RMS by using the **AllowAzureRMSForEDP** and the **RMSTemplateIDForEDP** MDM settings in the [EnterpriseDataProtection CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/enterprisedataprotection-csp).
|
||||
|
||||
- **On.** Protects files that are copied to a removable drive. You can enter a TemplateID GUID to specify who can access the Azure Rights Management protected files, and for how long. The RMS template is only applied to the files on removable media, and is only used for access control—it doesn’t actually apply Azure Information Protection to the files. Curly braces {} are required around the RMS Template ID, but they are removed after you save the policy.
|
||||
- **On.** Protects files that are copied to a removable drive. You can enter a TemplateID GUID to specify who can access the Azure Rights Management protected files, and for how long. The RMS template is only applied to the files on removable media, and is only used for access control—it doesn’t actually apply Azure Information Protection to the files.
|
||||
|
||||
If you don’t specify an [RMS template](https://docs.microsoft.com/information-protection/deploy-use/configure-custom-templates), it’s a regular EFS file using a default RMS template that all users can access.
|
||||
|
||||
|
@ -73,6 +73,8 @@ Microsoft has made a concerted effort to enlighten several of our more popular a
|
||||
|
||||
- Microsoft Remote Desktop
|
||||
|
||||
- Microsoft To Do
|
||||
|
||||
> [!NOTE]
|
||||
> Microsoft Visio, Microsoft Office Access, Microsoft Project, and Microsoft Publisher are not enlightened apps and need to be exempted from WIP policy. If they are allowed, there is a risk of data loss. For example, if a device is workplace-joined and managed and the user leaves the company, metadata files that the apps rely on remain encrypted and the apps stop functioning.
|
||||
|
||||
@ -113,6 +115,7 @@ You can add any or all of the enlightened Microsoft apps to your allowed apps li
|
||||
| Microsoft Paint | **Publisher:** `O=Microsoft Corporation, L=Redmond, S=Washington, C=US`<br>**Binary Name:** mspaint.exe<br>**App Type:** Desktop app |
|
||||
| Microsoft Remote Desktop | **Publisher:** `O=Microsoft Corporation, L=Redmond, S=Washington, C=US`<br>**Binary Name:** mstsc.exe<br>**App Type:** Desktop app |
|
||||
| Microsoft MAPI Repair Tool | **Publisher:** `O=Microsoft Corporation, L=Redmond, S=Washington, C=US`<br>**Binary Name:** fixmapi.exe<br>**App Type:** Desktop app |
|
||||
| Microsoft To Do | **Publisher:** `O=Microsoft Corporation, L=Redmond, S=Washington, C=US`<br>**Product Name:** Microsoft.Todos<br>**App Type:** Store app |
|
||||
|
||||
>[!NOTE]
|
||||
>Help to make this topic better by providing us with edits, additions, and feedback. For info about how to contribute to this topic, see [Editing Windows IT professional documentation](https://github.com/Microsoft/windows-itpro-docs/blob/master/CONTRIBUTING.md).
|
||||
|
Reference in New Issue
Block a user