mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-18 20:03:40 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into vs-10574249
This commit is contained in:
LizRoss
@ -51,6 +51,7 @@
|
||||
## [Upgrade to Windows 10 with the Microsoft Deployment Toolkit](upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md)
|
||||
## [Upgrade to Windows 10 with System Center Configuration Manager](upgrade-to-windows-10-with-system-center-configuraton-manager.md)
|
||||
## [Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md)
|
||||
## [Convert MBR partition to GPT](mbr-to-gpt.md)
|
||||
## [Configure a PXE server to load Windows PE](configure-a-pxe-server-to-load-windows-pe.md)
|
||||
## [Windows 10 upgrade paths](windows-10-upgrade-paths.md)
|
||||
## [Windows 10 edition upgrade](windows-10-edition-upgrades.md)
|
||||
|
||||
@ -11,6 +11,11 @@ author: greg-lindsay
|
||||
# Change history for Deploy Windows 10
|
||||
This topic lists new and updated topics in the [Deploy Windows 10](index.md) documentation for [Windows 10 and Windows 10 Mobile](../index.md).
|
||||
|
||||
## March 2017
|
||||
| New or changed topic | Description |
|
||||
|----------------------|-------------|
|
||||
| [Convert MBR partition to GPT](mbr-to-gpt.md) | New |
|
||||
|
||||
## February 2017
|
||||
| New or changed topic | Description |
|
||||
|----------------------|-------------|
|
||||
|
||||
BIN
windows/deploy/images/mbr2gpt-volume.PNG
Normal file
BIN
windows/deploy/images/mbr2gpt-volume.PNG
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 16 KiB |
BIN
windows/deploy/images/mbr2gpt-workflow.png
Normal file
BIN
windows/deploy/images/mbr2gpt-workflow.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 28 KiB |
@ -24,6 +24,7 @@ Learn about deploying Windows 10 for IT professionals.
|
||||
|[Upgrade to Windows 10 with the Microsoft Deployment Toolkit](upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md) |The simplest path to upgrade PCs that are currently running Windows 7, Windows 8, or Windows 8.1 to Windows 10 is through an in-place upgrade. You can use a Microsoft Deployment Toolkit (MDT) 2013 Update 2 task sequence to completely automate the process. |
|
||||
|[Upgrade to Windows 10 with System Center Configuration Manager](upgrade-to-windows-10-with-system-center-configuraton-manager.md) |The simplest path to upgrade PCs currently running Windows 7, Windows 8, or Windows 8.1 to Windows 10 is through an in-place upgrade. You can use a System Center Configuration Manager task sequence to completely automate the process. |
|
||||
|[Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md) |This topic provides a brief introduction to Windows 10 installation processes, and provides resolution procedures that IT administrators can use to resolve issues with Windows 10 upgrade. |
|
||||
|[Convert MBR partition to GPT](mbr-to-gpt.md) |This topic provides detailed instructions for using the MBR2GPT partition conversion tool. |
|
||||
|[Configure a PXE server to load Windows PE](configure-a-pxe-server-to-load-windows-pe.md) |This guide describes how to configure a PXE server to load Windows PE by booting a client computer from the network. |
|
||||
|[Windows 10 edition upgrade](windows-10-edition-upgrades.md) |With Windows 10, you can quickly upgrade from one edition of Windows 10 to another, provided the upgrade path is supported. |
|
||||
| [Provisioning packages for Windows 10](provisioning-packages.md) | Learn how to use the Windows Imaging and Configuration Designer (ICD) and provisioning packages to easily configure multiple devices. |
|
||||
|
||||
384
windows/deploy/mbr-to-gpt.md
Normal file
384
windows/deploy/mbr-to-gpt.md
Normal file
@ -0,0 +1,384 @@
|
||||
---
|
||||
title: MBR2GPT
|
||||
description: How to use the MBR2GPT tool to convert MBR partitions to GPT
|
||||
keywords: deploy, troubleshoot, windows, 10, upgrade, partition, mbr, gpt
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: greg-lindsay
|
||||
localizationpriority: high
|
||||
---
|
||||
|
||||
# MBR2GPT.EXE
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
|
||||
## Summary
|
||||
|
||||
**MBR2GPT.EXE** converts a disk from Master Boot Record (MBR) to GUID Partition Table (GPT) partition style without modifying or deleting data on the disk. The tool is designed to be run from a Windows Preinstallation Environment (Windows PE) command prompt, but can also be run from the full Windows 10 operating system (OS).
|
||||
|
||||
You can use MBR2GPT to perform the following:
|
||||
|
||||
- \[Within the Windows PE environment\]: Convert any attached MBR-formatted disk to GPT, including the system disk.
|
||||
- \[From within the currently running OS\]: Convert any attached MBR-formatted disk to GPT, including the system disk.
|
||||
|
||||
>MBR2GPT is available in Windows 10 version 1703, also known as Windows 10 Creator's Update, and later versions.
|
||||
>The tool is available in both the full OS environment and Windows PE.
|
||||
|
||||
You can use MBR2GPT to convert an MBR disk with BitLocker-encrypted volumes as long as protection has been suspended. To resume BitLocker after conversion, you will need to delete the existing protectors and recreate them.
|
||||
|
||||
The MBR2GPT tool can convert operating system disks that have earlier versions of Windows installed, such as Windows 10 versions 1507, 1511, and 1607. However, you must run the tool while booted into Windows 10 version 1703 or later, and perform an offline conversion.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>After the disk has been converted to GPT partition style, the firmware must be reconfigured to boot in UEFI mode. <BR>Make sure that your device supports UEFI before attempting to convert the disk.
|
||||
|
||||
## Syntax
|
||||
|
||||
<table style="font-family:consolas;font-size:12px" >
|
||||
<TR><TD>MBR2GPT /validate|convert [/disk:\<diskNumber\>] [/logs:\<logDirectory\>] [/map:\<source\>=\<destination\>] [/allowFullOS]
|
||||
</TABLE>
|
||||
|
||||
### Options
|
||||
|
||||
| Option | Description |
|
||||
|----|-------------|
|
||||
|/validate| Instructs MBR2GPT.exe to perform only the disk validation steps and report whether the disk is eligible for conversion. |
|
||||
|/convert| Instructs MBR2GPT.exe to perform the disk validation and to proceed with the conversion if all validation tests pass. |
|
||||
|/disk:\<diskNumber\>| Specifies the disk number of the disk to be converted to GPT. If not specified, the system disk is used. The mechanism used is the same as that used by the diskpart.exe tool **SELECT DISK SYSTEM** command.|
|
||||
|/logs:\<logDirectory\>| Specifies the directory where MBR2GPT.exe logs should be written. If not specified, **%windir%** is used. If specified, the directory must already exist, it will not be automatically created or overwritten.|
|
||||
|/map:\<source\>=\<destination\>| Specifies additional partition type mappings between MBR and GPT. The MBR partition number is specified in decimal notation, not hexidecimal. The GPT GUID can contain brackets, for example: **/map:42={af9b60a0-1431-4f62-bc68-3311714a69ad}**. Multiple /map options can be specified if multiple mappings are required. |
|
||||
|/allowFullOS| By default, MBR2GPT.exe is blocked unless it is run from Windows PE. This option overrides this block and enables disk conversion while running in the full Windows environment.|
|
||||
|
||||
## Examples
|
||||
|
||||
### Validation example
|
||||
|
||||
In the following example, disk 0 is validated for conversion. Errors and warnings are logged to the default location, **%windir%**.
|
||||
|
||||
```
|
||||
X:\>mbr2gpt /validate /disk:0
|
||||
MBR2GPT: Attempting to validate disk 0
|
||||
MBR2GPT: Retrieving layout of disk
|
||||
MBR2GPT: Validating layout, disk sector size is: 512
|
||||
MBR2GPT: Validation completed successfully
|
||||
```
|
||||
|
||||
### Conversion example
|
||||
|
||||
In the following example:
|
||||
|
||||
1. The current disk partition layout is displayed prior to conversion - three partitions are present on the MBR disk (disk 0): a system reserved partition, a Windows partition, and a recovery partition. A DVD-ROM is also present as volume 0.
|
||||
2. The OS volume is selected, partitions are listed, and partition details are displayed for the OS partition. The [MBR partition type](https://msdn.microsoft.com/library/windows/desktop/aa363990.aspx) is **07** corresponding to the installable file system (IFS) type.
|
||||
2. The MBR2GPT tool is used to convert disk 0.
|
||||
3. The DISKPART tool displays that disk 0 is now using the GPT format.
|
||||
4. The new disk layout is displayed - four partitions are present on the GPT disk: three are identical to the previous partitions and one is the new EFI system partition (volume 3).
|
||||
5. The OS volume is selected again, and detail displays that it has been converted to the [GPT partition type](https://msdn.microsoft.com/library/windows/desktop/aa365449.aspx) of **ebd0a0a2-b9e5-4433-87c0-68b6b72699c7** corresponding to the **PARTITION_BASIC_DATA_GUID** type.
|
||||
|
||||
>As noted in the output from the MBR2GPT tool, you must make changes to the computer firmware so that the new EFI system partition will boot properly.
|
||||
|
||||
```
|
||||
DISKPART> list volume
|
||||
|
||||
Volume ### Ltr Label Fs Type Size Status Info
|
||||
---------- --- ----------- ----- ---------- ------- --------- --------
|
||||
Volume 0 F CENA_X64FRE UDF DVD-ROM 4027 MB Healthy
|
||||
Volume 1 C System Rese NTFS Partition 499 MB Healthy
|
||||
Volume 2 D Windows NTFS Partition 58 GB Healthy
|
||||
Volume 3 E Recovery NTFS Partition 612 MB Healthy Hidden
|
||||
|
||||
DISKPART> select volume 2
|
||||
|
||||
Volume 2 is the selected volume.
|
||||
|
||||
DISKPART> list partition
|
||||
|
||||
Partition ### Type Size Offset
|
||||
------------- ---------------- ------- -------
|
||||
Partition 1 Primary 499 MB 1024 KB
|
||||
* Partition 2 Primary 58 GB 500 MB
|
||||
Partition 3 Recovery 612 MB 59 GB
|
||||
|
||||
DISKPART> detail partition
|
||||
|
||||
Partition 2
|
||||
Type : 07
|
||||
Hidden: No
|
||||
Active: No
|
||||
Offset in Bytes: 524288000
|
||||
|
||||
Volume ### Ltr Label Fs Type Size Status Info
|
||||
---------- --- ----------- ----- ---------- ------- --------- --------
|
||||
* Volume 2 D Windows NTFS Partition 58 GB Healthy
|
||||
|
||||
DISKPART> exit
|
||||
|
||||
Leaving DiskPart...
|
||||
|
||||
X:\>mbr2gpt /convert /disk:0
|
||||
|
||||
MBR2GPT will now attempt to convert disk 0.
|
||||
If conversion is successful the disk can only be booted in GPT mode.
|
||||
These changes cannot be undone!
|
||||
|
||||
MBR2GPT: Attempting to convert disk 0
|
||||
MBR2GPT: Retrieving layout of disk
|
||||
MBR2GPT: Validating layout, disk sector size is: 512 bytes
|
||||
MBR2GPT: Trying to shrink the system partition
|
||||
MBR2GPT: Trying to shrink the OS partition
|
||||
MBR2GPT: Creating the EFI system partition
|
||||
MBR2GPT: Installing the new boot files
|
||||
MBR2GPT: Performing the layout conversion
|
||||
MBR2GPT: Migrating default boot entry
|
||||
MBR2GPT: Adding recovery boot entry
|
||||
MBR2GPT: Fixing drive letter mapping
|
||||
MBR2GPT: Conversion completed successfully
|
||||
MBR2GPT: Before the new system can boot properly you need to switch the firmware to boot to UEFI mode!
|
||||
|
||||
X:\>diskpart
|
||||
|
||||
Microsoft DiskPart version 10.0.15048.0
|
||||
|
||||
Copyright (C) Microsoft Corporation.
|
||||
On computer: MININT-K71F13N
|
||||
|
||||
DISKPART> list disk
|
||||
|
||||
Disk ### Status Size Free Dyn Gpt
|
||||
-------- ------------- ------- ------- --- ---
|
||||
Disk 0 Online 60 GB 0 B *
|
||||
|
||||
DISKPART> select disk 0
|
||||
|
||||
Disk 0 is now the selected disk.
|
||||
|
||||
DISKPART> list volume
|
||||
|
||||
Volume ### Ltr Label Fs Type Size Status Info
|
||||
---------- --- ----------- ----- ---------- ------- --------- --------
|
||||
Volume 0 F CENA_X64FRE UDF DVD-ROM 4027 MB Healthy
|
||||
Volume 1 D Windows NTFS Partition 58 GB Healthy
|
||||
Volume 2 C System Rese NTFS Partition 499 MB Healthy Hidden
|
||||
Volume 3 FAT32 Partition 100 MB Healthy Hidden
|
||||
Volume 4 E Recovery NTFS Partition 612 MB Healthy Hidden
|
||||
|
||||
DISKPART> select volume 1
|
||||
|
||||
Volume 1 is the selected volume.
|
||||
|
||||
DISKPART> list partition
|
||||
|
||||
Partition ### Type Size Offset
|
||||
------------- ---------------- ------- -------
|
||||
Partition 1 Recovery 499 MB 1024 KB
|
||||
* Partition 2 Primary 58 GB 500 MB
|
||||
Partition 4 System 100 MB 59 GB
|
||||
Partition 3 Recovery 612 MB 59 GB
|
||||
|
||||
DISKPART> detail partition
|
||||
|
||||
Partition 2
|
||||
Type : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
|
||||
Hidden : No
|
||||
Required: No
|
||||
Attrib : 0000000000000000
|
||||
Offset in Bytes: 524288000
|
||||
|
||||
Volume ### Ltr Label Fs Type Size Status Info
|
||||
---------- --- ----------- ----- ---------- ------- --------- --------
|
||||
* Volume 1 D Windows NTFS Partition 58 GB Healthy
|
||||
|
||||
```
|
||||
|
||||
## Specifications
|
||||
|
||||
### Disk conversion workflow
|
||||
|
||||
The following steps illustrate high-level phases of the MBR-to-GPT conversion process:
|
||||
|
||||
1. Disk validation is performed.
|
||||
2. The disk is repartitioned to create an EFI system partition (ESP) if one does not already exist.
|
||||
3. UEFI boot files are installed to the ESP.
|
||||
4. GPT metatdata and layout information is applied.
|
||||
5. The boot configuration data (BCD) store is updated.
|
||||
6. Drive letter assignments are restored.
|
||||
|
||||
### Disk validation
|
||||
|
||||
Before any change to the disk is made, MBR2GPT validates the layout and geometry of the selected disk to ensure that:
|
||||
- The disk is currently using MBR
|
||||
- There is enough space not occupied by partitions to store the primary and secondary GPTs:
|
||||
- 16KB + 2 sectors at the front of the disk
|
||||
- 16KB + 1 sector at the end of the disk
|
||||
- There are at most 3 primary partitions in the MBR partition table
|
||||
- One of the partitions is set as active and is the system partition
|
||||
- The BCD store on the system partition contains a default OS entry pointing to an OS partition
|
||||
- The volume IDs can retrieved for each volume which has a drive letter assigned
|
||||
- All partitions on the disk are of MBR types recognized by Windows or has a mapping specified using the /map command-line option
|
||||
|
||||
If any of these checks fails, the conversion will not proceed and an error will be returned.
|
||||
|
||||
### Creating an EFI system partition
|
||||
|
||||
For Windows to remain bootable after the conversion, an EFI system partition (ESP) must be in place. MBR2GPT creates the ESP using the following rules:
|
||||
|
||||
1. The existing MBR system partition is reused if it meets these requirements:
|
||||
a. It is not also the OS or Windows Recovery Environment partition
|
||||
b. It is at least 100MB (or 260MB for 4K sector size disks) in size
|
||||
c. It is less than or equal to 1GB in size. This is a safety precaution to ensure it is not a data partition.
|
||||
d. If the conversion is being performed from the full OS, the disk being converted is not the system disk.
|
||||
2. If the existing MBR system partition cannot be reused, a new ESP is created by shrinking the OS partition. This new partition has a size of 100MB (or 260MB for 4K sector size disks) and is formatted FAT32.
|
||||
|
||||
If the existing MBR system partition is not reused for the ESP, it is no longer used by the boot process after the conversion. Other partitions are not modified.
|
||||
|
||||
### Partition type mapping and partition attributes
|
||||
|
||||
Since GPT partitions use a different set of type IDs than MBR partitions, each partition on the converted disk must be assigned a new type ID. The partition type mapping follows these rules:
|
||||
|
||||
1. The ESP is always set to partition type PARTITION_SYSTEM_GUID (c12a7328-f81f-11d2-ba4b-00a0c93ec93b).
|
||||
2. If an MBR partition is of a type that matches one of the entries specified in the /map switch, the specified GPT partition type ID is used.
|
||||
3. If the MBR partition is of type 0x27, the partition is converted to a GPT partition of type PARTITION_MSFT_RECOVERY_GUID (de94bba4-06d1-4d40-a16a-bfd50179d6ac).
|
||||
4. All other MBR partitions recognized by Windows are converted to GPT partitions of type PARTITION_BASIC_DATA_GUID (ebd0a0a2-b9e5-4433-87c0-68b6b72699c7).
|
||||
|
||||
In addition to applying the correct partition types, partitions of type PARTITION_MSFT_RECOVERY_GUID also have the following GPT attributes set:
|
||||
- GPT_ATTRIBUTE_PLATFORM_REQUIRED (0x0000000000000001)
|
||||
- GPT_BASIC_DATA_ATTRIBUTE_NO_DRIVE_LETTER (0x8000000000000000)
|
||||
|
||||
For more information about partition types, see:
|
||||
- [GPT partition types](https://msdn.microsoft.com/library/windows/desktop/aa365449.aspx)
|
||||
- [MBR partition types](https://msdn.microsoft.com/library/windows/desktop/aa363990.aspx)
|
||||
|
||||
|
||||
### Persisting drive letter assignments
|
||||
|
||||
The conversion tool will attempt to remap all drive letter assignment information contained in the registry that correspond to the volumes of the converted disk. If a drive letter assignment cannot be restored, an error will be displayed at the console and in the log, so that you can manually perform the correct assignment of the drive letter. **Important**: this code runs after the layout conversion has taken place, so the operation cannot be undone at this stage.
|
||||
|
||||
The conversion tool will obtain volume unique ID data before and after the layout conversion, organizing this information into a lookup table. It will then iterate through all the entries in **HKLM\SYSTEM\MountedDevices**, and for each entry do the following:
|
||||
|
||||
1. Check if the unique ID corresponds to any of the unique IDs for any of the volumes that are part of the converted disk.
|
||||
2. If found, set the value to be the new unique ID, obtained after the layout conversion.
|
||||
3. If the new unique ID cannot be set and the value name starts with \DosDevices, issue a console and log warning about the need for manual intervention in properly restoring the drive letter assignment.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
The tool will display status information in its output. Both validation and conversion are clear if any errors are encountered. For example, if one or more partitions do not translate properly, this is displayed and the conversion not performed. To view more detail about any errors that are encountered, see the associated [log files](#logs).
|
||||
|
||||
### Logs
|
||||
|
||||
Four log files are created by the MBR2GPT tool:
|
||||
|
||||
- diagerr.xml
|
||||
- diagwrn.xml
|
||||
- setupact.log
|
||||
- setuperr.log
|
||||
|
||||
These files contain errors and warnings encountered during disk validation and conversion. Information in these files can be helpful in diagnosing problems with the tool. The setupact.log and setuperr.log files will have the most detailed information about disk layouts, processes, and other information pertaining to disk validation and conversion. Note: The setupact*.log files are different than the Windows Setup files that are found in the %Windir%\Panther directory.
|
||||
|
||||
The default location for all these log files in Windows PE is **%windir%**.
|
||||
|
||||
### Interactive help
|
||||
|
||||
To view a list of options available when using the tool, type **mbr2gpt /?**
|
||||
|
||||
The following text is displayed:
|
||||
|
||||
```
|
||||
|
||||
C:\> mbr2gpt /?
|
||||
|
||||
Converts a disk from MBR to GPT partitioning without modifying or deleting data on the disk.
|
||||
|
||||
MBR2GPT.exe /validate|convert [/disk:<diskNumber>] [/logs:<logDirectory>] [/map:<source>=<destination>] [/allowFullOS]
|
||||
|
||||
Where:
|
||||
|
||||
/validate
|
||||
- Validates that the selected disk can be converted
|
||||
without performing the actual conversion.
|
||||
|
||||
/convert
|
||||
- Validates that the selected disk can be converted
|
||||
and performs the actual conversion.
|
||||
|
||||
/disk:<diskNumber>
|
||||
- Specifies the disk number of the disk to be processed.
|
||||
If not specified, the system disk is processed.
|
||||
|
||||
/logs:<logDirectory>
|
||||
- Specifies the directory for logging. By default logs
|
||||
are created in the %windir% directory.
|
||||
|
||||
/map:<source>=<destination>
|
||||
- Specifies the GPT partition type to be used for a
|
||||
given MBR partition type not recognized by Windows.
|
||||
Multiple /map switches are allowed.
|
||||
|
||||
/allowFullOS
|
||||
- Allows the tool to be used from the full Windows
|
||||
environment. By default, this tool can only be used
|
||||
from the Windows Preinstallation Environment.
|
||||
|
||||
```
|
||||
|
||||
### Return codes
|
||||
|
||||
MBR2GPT has the following associated return codes:
|
||||
|
||||
| Return code | Description |
|
||||
|----|-------------|
|
||||
|0| Conversion completed successfully.|
|
||||
|1| Conversion was canceled by the user.|
|
||||
|2| Conversion failed due to an internal error.|
|
||||
|3| Conversion failed due to an initialization error.|
|
||||
|4| Conversion failed due to invalid command-line parameters. |
|
||||
|5| Conversion failed due to error reading the geometry and layout of the selected disk.|
|
||||
|6| Conversion failed because one or more volumes on the disk is encrypted.|
|
||||
|7| Conversion failed because the geometry and layout of the selected disk do not meet requirements.|
|
||||
|8| Conversion failed due to error while creating the EFI system partition.|
|
||||
|9| Conversion failed due to error installing boot files.|
|
||||
|10| Conversion failed due to error while applying GPT layout.|
|
||||
|100| Conversion to GPT layout succeeded, but some boot configuration data entries could not be restored.|
|
||||
|
||||
|
||||
### Determining the partition type
|
||||
|
||||
You can type the following command at a Windows PowerShell prompt to display the disk number and partition type. Example output is also shown:
|
||||
|
||||
|
||||
```
|
||||
PS C:\> Get-Disk | ft -Auto
|
||||
|
||||
Number Friendly Name Serial Number HealthStatus OperationalStatus Total Size Partition Style
|
||||
------ ------------- ------------- ------------ ----------------- ---------- ---------------
|
||||
0 MTFDDAK256MAM-1K1 13050928F47C Healthy Online 238.47 GB MBR
|
||||
1 ST1000DM003-1ER162 Z4Y3GD8F Healthy Online 931.51 GB GPT
|
||||
```
|
||||
|
||||
You can also view the partition type of a disk by opening the Disk Management tool, right-clicking the disk number, clicking **Properties**, and then clicking the **Volumes** tab. See the following example:
|
||||
|
||||
|
||||
|
||||
|
||||
If Windows PowerShell and Disk Management are not available, such as when you are using Windows PE, you can determine the partition type at a command prompt with the diskpart tool. To determine the partition style, type **diskpart** and then type **list disk**. See the following example:
|
||||
|
||||
```
|
||||
DISKPART> list disk
|
||||
|
||||
Disk ### Status Size Free Dyn Gpt
|
||||
-------- ------------- ------- ------- --- ---
|
||||
Disk 0 Online 238 GB 0 B
|
||||
Disk 1 Online 931 GB 0 B *
|
||||
```
|
||||
|
||||
In this example, Disk 0 is formatted with the MBR partition style, and Disk 1 is formatted using GPT.
|
||||
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
[Using MBR2GPT with Configuration Manager OSD](https://miketerrill.net/tag/mbr2gpt/)
|
||||
<BR>[Windows 10 Enterprise system requirements](https://technet.microsoft.com/en-us/windows/dn798752.aspx)
|
||||
<BR>[Windows 10 Specifications](https://www.microsoft.com/en-us/windows/Windows-10-specifications)
|
||||
<BR>[Windows 10 IT pro forums](https://social.technet.microsoft.com/Forums/en-US/home?category=Windows10ITPro)
|
||||
52
windows/keep-secure/code/example.ps1
Normal file
52
windows/keep-secure/code/example.ps1
Normal file
@ -0,0 +1,52 @@
|
||||
$tenantId = '{Your Tenant ID}'
|
||||
$clientId = '{Your Client ID}'
|
||||
$clientSecret = '{Your Client Secret}'
|
||||
|
||||
$authUrl = "https://login.windows.net/{0}/oauth2/token" -f $tenantId
|
||||
|
||||
$tokenPayload = @{
|
||||
"resource"='https://graph.windows.net'
|
||||
"client_id" = $clientId
|
||||
"client_secret" = $clientSecret
|
||||
"grant_type"='client_credentials'}
|
||||
|
||||
$response = Invoke-RestMethod $authUrl -Method Post -Body $tokenPayload
|
||||
$token = $response.access_token
|
||||
|
||||
$headers = @{
|
||||
"Content-Type"="application/json"
|
||||
"Accept"="application/json"
|
||||
"Authorization"="Bearer {0}" -f $token }
|
||||
|
||||
$apiBaseUrl = "https://ti.securitycenter.windows.com/V1.0/"
|
||||
|
||||
$alertDefinitions =
|
||||
(Invoke-RestMethod ("{0}AlertDefinitions" -f $apiBaseUrl) -Method Get -Headers $headers).value
|
||||
|
||||
$alertDefinitionPayload = @{
|
||||
"Name"= "The Alert's Name"
|
||||
"Severity"= "Low"
|
||||
"InternalDescription"= "An internal description of the Alert"
|
||||
"Title"= "The Title"
|
||||
"UxDescription"= "Description of the alerts"
|
||||
"RecommendedAction"= "The alert's recommended action"
|
||||
"Category"= "Trojan"
|
||||
"Enabled"= "true"}
|
||||
|
||||
$alertDefinition =
|
||||
Invoke-RestMethod ("{0}AlertDefinitions" -f $apiBaseUrl) `
|
||||
-Method Post -Headers $headers -Body ($alertDefinitionPayload | ConvertTo-Json)
|
||||
|
||||
$alertDefinitionId = $alertDefinition.Id
|
||||
|
||||
$iocPayload = @{
|
||||
"Type"="Sha1"
|
||||
"Value"="dead1111eeaabbccddeeaabbccddee11ffffffff"
|
||||
"DetectionFunction"="Equals"
|
||||
"Enabled"="true"
|
||||
"AlertDefinition@odata.bind"="AlertDefinitions({0})" -f $alertDefinitionId }
|
||||
|
||||
|
||||
$ioc =
|
||||
Invoke-RestMethod ("{0}IndicatorsOfCompromise" -f $apiBaseUrl) `
|
||||
-Method Post -Headers $headers -Body ($iocPayload | ConvertTo-Json)
|
||||
53
windows/keep-secure/code/example.py
Normal file
53
windows/keep-secure/code/example.py
Normal file
@ -0,0 +1,53 @@
|
||||
import json
|
||||
import requests
|
||||
from pprint import pprint
|
||||
|
||||
tenant_id="{your tenant ID}"
|
||||
client_id="{your client ID}"
|
||||
client_secret="{your client secret}"
|
||||
|
||||
auth_url = "https://login.windows.net/{0}/oauth2/token".format(tenant_id)
|
||||
|
||||
payload = {"resource": "https://graph.windows.net",
|
||||
"client_id": client_id,
|
||||
"client_secret": client_secret,
|
||||
"grant_type": "client_credentials"}
|
||||
|
||||
response = requests.post(auth_url, payload)
|
||||
token = json.loads(response.text)["access_token"]
|
||||
|
||||
with requests.Session() as session:
|
||||
session.headers = {
|
||||
'Authorization': 'Bearer {}'.format(token),
|
||||
'Content-Type': 'application/json',
|
||||
'Accept': 'application/json'}
|
||||
|
||||
response = session.get("https://ti.securitycenter.windows.com/V1.0/AlertDefinitions")
|
||||
pprint(json.loads(response.text))
|
||||
|
||||
alert_definition = {"Name": "The alert's name",
|
||||
"Severity": "Low",
|
||||
"InternalDescription": "An internal description of the alert",
|
||||
"Title": "The Title",
|
||||
"UxDescription": "Description of the alerts",
|
||||
"RecommendedAction": "The alert's recommended action",
|
||||
"Category": "Trojan",
|
||||
"Enabled": True}
|
||||
|
||||
response = session.post(
|
||||
"https://ti.securitycenter.windows.com/V1.0/AlertDefinitions",
|
||||
json=alert_definition)
|
||||
|
||||
alert_definition_id = json.loads(response.text)["Id"]
|
||||
|
||||
ioc = {'Type': "Sha1",
|
||||
'Value': "dead1111eeaabbccddeeaabbccddee11ffffffff",
|
||||
'DetectionFunction': "Equals",
|
||||
'Enabled': True,
|
||||
"AlertDefinition@odata.bind": "AlertDefinitions({0})".format(alert_definition_id)}
|
||||
|
||||
response = session.post(
|
||||
"https://ti.securitycenter.windows.com/V1.0/IndicatorsOfCompromise",
|
||||
json=ioc)
|
||||
|
||||
pprint(json.loads(response.text))
|
||||
@ -40,12 +40,10 @@ Here's a high-level overview on how the LSA is isolated by using virtualization-
|
||||
|
||||
## Requirements
|
||||
|
||||
For Credential Guard to provide protections, the computers you are protecting must meet certain baseline hardware, firmware, and software requirements which we will refer to as [Hardware and software requirements](#hardware-and-software-requirements). Additionally Credential Guard blocks specific authentication capabilities, so applications which require blocked capabilities will break. We will refer to this as [Application requirements](#application-requirements). Beyond that, computers can meet additional hardware and firmware requirements, and receive additional protection—those computers will be more hardened against certain threats. To keep this section brief, those will be in [Security Considerations](#security-considerations).
|
||||
For Credential Guard to provide protections, the computers you are protecting must meet certain baseline hardware, firmware, and software requirements which we will refer to as [Hardware and software requirements](#hardware-and-software-requirements). Additionally Credential Guard blocks specific authentication capabilities, so applications which require blocked capabilities will break. We will refer to this as [Application requirements](#application-requirements). Beyond that, computers can meet additional hardware and firmware qualifications, and receive additional protection—those computers will be more hardened against certain threats. To keep this section brief, those will be in [Security Considerations](#security-considerations).
|
||||
|
||||
### Hardware and software requirements
|
||||
|
||||
To deploy Credential Guard, the computers you are protecting must meet certain baseline hardware, firmware, and software requirements. Beyond that, computers can meet additional hardware and firmware requirements, and receive additional protection—those computers will be more hardened against certain threats.
|
||||
|
||||
To provide basic protection against OS level attempts to read Credential Manager domain credentials, NTLM and Kerberos derived credentials, Credential Manager uses:
|
||||
- Support for Virtualization-based security (required)
|
||||
- TPM 2.0 either discrete or firmware (preferred - provides binding to hardware)
|
||||
@ -82,14 +80,15 @@ Applications may cause performance issues when they attempt to hook the isolated
|
||||
|
||||
### Security considerations
|
||||
|
||||
The following tables provide more information about the hardware, firmware, and software required for deployment of Credential Guard. The tables describe baseline protections, plus protections for improved security that are associated with hardware and firmware options available in 2015, available in 2016, and announced as options for 2017.
|
||||
All computers that meet baseline protections for hardware, firmware, and software can use Credential Guard.
|
||||
Computers that meet additional qualifications can provide additional protections to further reduce the attack surface.
|
||||
The following tables describe baseline protections, plus protections for improved security that are associated with hardware and firmware options available in 2015, 2016, and 2017.
|
||||
|
||||
> [!NOTE]
|
||||
> Beginning with Windows 10, version 1607, Trusted Platform Module (TPM 2.0) must be enabled by default on new computers. This requirement is not restated in the tables that follow.<br>
|
||||
> If you are an OEM, see the requirements information at [PC OEM requirements for Device Guard and Credential Guard](https://msdn.microsoft.com/library/windows/hardware/mt767514.aspx).<br>
|
||||
> Starting in Widows 10, 1607, TPM 2.0 is required.
|
||||
> Beginning with Windows 10, version 1607, Trusted Platform Module (TPM 2.0) must be enabled by default on new computers. <br>
|
||||
> If you are an OEM, see [PC OEM requirements for Device Guard and Credential Guard](https://msdn.microsoft.com/library/windows/hardware/mt767514.aspx).<br>
|
||||
|
||||
#### Baseline protection recommendations
|
||||
#### Baseline protections
|
||||
|
||||
|Baseline Protections | Description |
|
||||
|---------------------------------------------|----------------------------------------------------|
|
||||
@ -101,9 +100,9 @@ The following tables provide more information about the hardware, firmware, and
|
||||
| Software: Qualified **Windows operating system** | **Requirement**: Windows 10 Enterprise, Windows 10 Education, Windows Server 2016, or Windows 10 IoT Enterprise<br><blockquote><p><strong>Important:</strong><br> Windows Server 2016 running as a domain controller does not support Credential Guard. Only Device Guard is supported in this configuration.</p></blockquote><br>**Security benefits**: Support for VBS and for management features that simplify configuration of Credential Guard. |
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The preceding table lists requirements for baseline protections. The following tables list requirements for improved security. You can use Credential Guard with hardware, firmware, and software that support baseline protections, even if they do not support protections for improved security. However, we strongly recommend meeting the requirements for improved security to significantly strengthen the level of security that Credential Guard can provide.
|
||||
> The following tables list additional qualifications for improved security. We strongly recommend meeting the additional qualifications to significantly strengthen the level of security that Credential Guard can provide.
|
||||
|
||||
#### 2015 Additional Security Recommendations (starting with Windows 10, version 1507, and Windows Server 2016, Technical Preview 4)
|
||||
#### 2015 Additional security qualifications starting with Windows 10, version 1507, and Windows Server 2016 Technical Preview 4
|
||||
|
||||
| Protections for Improved Security | Description |
|
||||
|---------------------------------------------|----------------------------------------------------|
|
||||
@ -113,10 +112,10 @@ The following tables provide more information about the hardware, firmware, and
|
||||
|
||||
<br>
|
||||
|
||||
#### 2016 Additional Security Recommendations (starting with Windows 10, version 1607, and Windows Server 2016)
|
||||
#### 2016 Additional security qualifications starting with Windows 10, version 1607, and Windows Server 2016
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The following tables list requirements for improved security, beyond the level of protection described in the preceding tables. You can use Credential Guard with hardware, firmware, and software that do not support the following protections for improved security. As your systems meet more requirements, more protections become available to them.
|
||||
> The following tables list additional qualifications for improved security. Systems that meet these additional qualifications can provide more protections.
|
||||
|
||||
| Protections for Improved Security | Description |
|
||||
|---------------------------------------------|----------------------------------------------------|
|
||||
@ -126,9 +125,9 @@ The following tables provide more information about the hardware, firmware, and
|
||||
|
||||
<br>
|
||||
|
||||
#### 2017 Additional security requirements starting with Windows 10, version 1703
|
||||
#### 2017 Additional security qualifications starting with Windows 10, version 1703
|
||||
|
||||
The following table lists requirements for Windows 10, version 1703, which are in addition to all preceding requirements.
|
||||
The following table lists qualifications for Windows 10, version 1703, which are in addition to all preceding qualifications.
|
||||
|
||||
| Protection for Improved Security | Description |
|
||||
|---------------------------------------------|----------------------------------------------------|
|
||||
|
||||
@ -347,11 +347,13 @@ These parameters are compatible with the [OData V4 query language](http://docs.o
|
||||
|
||||
## Code examples
|
||||
The following articles provide detailed code examples that demonstrate how to use the custom threat intelligence API in several programming languages:
|
||||
- PowerShell code examples
|
||||
- Python code examples
|
||||
- [PowerShell code examples](powershell-example-code-windows-defender-advanced-threat-protection.md)
|
||||
- [Python code examples](python-example-code-windows-defender-advanced-threat-protection.md)
|
||||
|
||||
|
||||
## Related topics
|
||||
- [Understand threat intelligence](threat-indicator-concepts-windows-defender-advanced-threat-protection.md)
|
||||
- [Understand threat intelligence concepts](threat-indicator-concepts-windows-defender-advanced-threat-protection.md)
|
||||
- [Enable the custom threat intelligence application](enable-custom-ti-windows-defender-advanced-threat-protection.md)
|
||||
- [PowerShell code examples](powershell-example-code-windows-defender-advanced-threat-protection.md)
|
||||
- [Python code examples](python-example-code-windows-defender-advanced-threat-protection.md)
|
||||
- [Troubleshoot custom threat intelligence issues](troubleshoot-custom-ti-windows-defender-advanced-threat-protection.md)
|
||||
|
||||
@ -40,6 +40,8 @@ Before you can create custom threat intelligence (TI) using REST API, you'll nee
|
||||
You’ll need to use the access token in the Authorization header when doing REST API calls.
|
||||
|
||||
## Related topics
|
||||
- [Understand threat intelligence](threat-indicator-concepts-windows-defender-advanced-threat-protection.md)
|
||||
- [Create custom threat intelligence](custom-ti-api-windows-defender-advanced-threat-protection.md)
|
||||
- [Understand threat intelligence concepts](threat-indicator-concepts-windows-defender-advanced-threat-protection.md)
|
||||
- [Create custom threat intelligence alerts](custom-ti-api-windows-defender-advanced-threat-protection.md)
|
||||
- [PowerShell code examples](powershell-example-code-windows-defender-advanced-threat-protection.md)
|
||||
- [Python code examples](python-example-code-windows-defender-advanced-threat-protection.md)
|
||||
- [Troubleshoot custom threat intelligence issues](troubleshoot-custom-ti-windows-defender-advanced-threat-protection.md)
|
||||
|
||||
@ -50,10 +50,10 @@ This status indicates that there's limited communication between the machine and
|
||||
|
||||
The following suggested actions can help fix issues related to a misconfigured machine with impaired communication:
|
||||
|
||||
- [Ensure the endpoint has Internet connection](troubleshoot-onboarding-windows-defender-advanced-threat-protection.md#ensure-the-endpoint-has-an-internet-connection)
|
||||
- [Ensure the endpoint has Internet connection](troubleshoot-onboarding-windows-defender-advanced-threat-protection.md#ensure-the-endpoint-has-an-internet-connection)</br>
|
||||
The Window Defender ATP sensor requires Microsoft Windows HTTP (WinHTTP) to report sensor data and communicate with the Windows Defender ATP service.
|
||||
|
||||
- Verify client connectivity to Windows Defender ATP service URLs</br>
|
||||
- [Verify client connectivity to Windows Defender ATP service URLs](configure-proxy-internet-windows-defender-advanced-threat-protection.md#verify-client-connectivity-to-windows-defender-atp-service-urls)</br>
|
||||
Verify the proxy configuration completed successfully, that WinHTTP can discover and communicate through the proxy server in your environment, and that the proxy server allows traffic to the Windows Defender ATP service URLs.
|
||||
|
||||
If you took corrective actions and the machine status is still misconfigured, [open a support ticket](http://go.microsoft.com/fwlink/?LinkID=761093&clcid=0x409).
|
||||
@ -62,16 +62,16 @@ If you took corrective actions and the machine status is still misconfigured, [o
|
||||
A misconfigured machine with status ‘No sensor data’ has communication with the service but can only report partial sensor data.
|
||||
Follow theses actions to correct known issues related to a misconfigured machine with status ‘Impaired communication’:
|
||||
|
||||
- [Ensure the endpoint has Internet connection](troubleshoot-onboarding-windows-defender-advanced-threat-protection.md#ensure-the-endpoint-has-an-internet-connection)
|
||||
- [Ensure the endpoint has Internet connection](troubleshoot-onboarding-windows-defender-advanced-threat-protection.md#ensure-the-endpoint-has-an-internet-connection)</br>
|
||||
The Window Defender ATP sensor requires Microsoft Windows HTTP (WinHTTP) to report sensor data and communicate with the Windows Defender ATP service.
|
||||
|
||||
- Verify client connectivity to Windows Defender ATP service URLs</br>
|
||||
- [Verify client connectivity to Windows Defender ATP service URLs](configure-proxy-internet-windows-defender-advanced-threat-protection.md#verify-client-connectivity-to-windows-defender-atp-service-urls)</br>
|
||||
Verify the proxy configuration completed successfully, that WinHTTP can discover and communicate through the proxy server in your environment, and that the proxy server allows traffic to the Windows Defender ATP service URLs.
|
||||
|
||||
- [Ensure the telemetry and diagnostics service is enabled](troubleshoot-onboarding-windows-defender-advanced-threat-protection.md#ensure-the-telemetry-and-diagnostics-service-is-enabled)
|
||||
- [Ensure the telemetry and diagnostics service is enabled](troubleshoot-onboarding-windows-defender-advanced-threat-protection.md#ensure-the-telemetry-and-diagnostics-service-is-enabled)</br>
|
||||
If the endpoints aren't reporting correctly, you might need to check that the Windows 10 telemetry and diagnostics service is set to automatically start and is running on the endpoint.
|
||||
|
||||
- [Ensure that Windows Defender is not disabled by policy](troubleshoot-onboarding-windows-defender-advanced-threat-protection.md#ensure-that-windows-defender-is-not-disabled-by-a-policy)
|
||||
- [Ensure that Windows Defender is not disabled by policy](troubleshoot-onboarding-windows-defender-advanced-threat-protection.md#ensure-that-windows-defender-is-not-disabled-by-a-policy)</br>
|
||||
If your endpoints are running a third-party antimalware client, the Windows Defender ATP agent needs the Windows Defender Early Launch Antimalware (ELAM) driver to be enabled.
|
||||
|
||||
If you took corrective actions and the machine status is still misconfigured, [open a support ticket](http://go.microsoft.com/fwlink/?LinkID=761093&clcid=0x409).
|
||||
|
||||
@ -72,7 +72,7 @@ Imagine that someone is looking over your shoulder as you get money from an ATM
|
||||
|
||||
Windows Hello helps protect user identities and user credentials. Because the user doesn't enter a password (except during provisioning), it helps circumvent phishing and brute force attacks. It also helps prevent server breaches because Windows Hello credentials are an asymmetric key pair, which helps prevent replay attacks when these keys are protected by TPMs.
|
||||
|
||||
For customers using a hybrid Active Directory and Azure Active Directorye environment, Windows Hello also enables Windows 10 Mobile devices to be used as [a remote credential](hello-prepare-people-to-use.md#bmk-remote) when signing into Windows 10 PCs. During the sign-in process, the Windows 10 PC can connect using Bluetooth to access Windows Hello on the user’s Windows 10 Mobile device. Because users carry their phone with them, Windows Hello makes implementing two-factor authentication across the enterprise less costly and complex than other solutions.
|
||||
For customers using a hybrid Active Directory and Azure Active Directory environment, Windows Hello also enables Windows 10 Mobile devices to be used as [a remote credential](hello-prepare-people-to-use.md#bmk-remote) when signing into Windows 10 PCs. During the sign-in process, the Windows 10 PC can connect using Bluetooth to access Windows Hello on the user’s Windows 10 Mobile device. Because users carry their phone with them, Windows Hello makes implementing two-factor authentication across the enterprise less costly and complex than other solutions.
|
||||
|
||||
> [!NOTE]
|
||||
> Phone sign-in is currently limited to select Technology Adoption Program (TAP) participants.
|
||||
|
||||
@ -40,7 +40,7 @@ When you investigate a specific machine, you'll see:
|
||||
|
||||
|
||||
|
||||
The machine details, total logged on users and machine reporting sections display various attributes about the machine. You’ll see details such as machine name, health status, actions you can take on the machine. For more information on how to take action on a machine, see [Take response action on a machine](respond-machine-alerts-windows-defender-advanced-threat-protection.md).
|
||||
The machine details, total logged on users and machine reporting sections display various attributes about the machine. You’ll see details such as machine name, health state, actions you can take on the machine. For more information on how to take action on a machine, see [Take response action on a machine](respond-machine-alerts-windows-defender-advanced-threat-protection.md).
|
||||
|
||||
You'll also see other information such as domain, operating system (OS), total logged on users and who frequently and less frequently logged on, IP address, and how long it's been reporting sensor data to the Windows Defender ATP service.
|
||||
|
||||
|
||||
@ -26,88 +26,54 @@ localizationpriority: high
|
||||
This article provides PowerShell code examples for using the custom threat intelligence API.
|
||||
|
||||
These code examples demonstrate the following tasks:
|
||||
- [Obtain an Azure AD access token](#obtain-an-azure-ad-access-token)
|
||||
- [Create headers](#create-headers)
|
||||
- [Create calls to the custom threat intelligence API](#create-calls-to-the-custom-threat-intelligence-api)
|
||||
- [Create a new alert definition](#create-a-new-alert-definition)
|
||||
- [Create a new indicator of compromise](#create-a-new-indicator-of-compromise)
|
||||
- [Obtain an Azure AD access token](#token)
|
||||
- [Create headers](#headers)
|
||||
- [Create calls to the custom threat intelligence API](#calls)
|
||||
- [Create a new alert definition](#alert-definition)
|
||||
- [Create a new indicator of compromise](#ioc)
|
||||
|
||||
## Obtain an Azure AD access token
|
||||
<span id="token" />
|
||||
## Step 1: Obtain an Azure AD access token
|
||||
The following example demonstrates how to obtain an Azure AD access token that you can use to call methods in the custom threat intelligence API. After you obtain a token, you have 60 minutes to use this token in calls to the custom threat intelligence API before the token expires. After the token expires, you can generate a new token.
|
||||
|
||||
Replace the *tenant\_id*, *client_id*, and *client_secret* values with the ones you got from **Preferences settings** page in the portal:
|
||||
Replace the *tenantid*, *clientid*, and *clientSecret* values with the ones you got from **Preferences settings** page in the portal:
|
||||
|
||||
```
|
||||
[!code[CustomTIAPI](./code/example.ps1#L1-L14)]
|
||||
|
||||
$tenantId = '{Your Tenant ID}
|
||||
$clientId = '{Your Client ID}'
|
||||
$clientSecret = '{Your Client Secret}'
|
||||
<span id="header" />
|
||||
## Step 2: Create headers used for the requests with the API
|
||||
Use the following code to create the headers used for the requests with the API:
|
||||
|
||||
$authUrl = "https://login.windows.net/{0}/oauth2/token" -f $tenantId
|
||||
[!code[CustomTIAPI](./code/example.ps1#L16-L19)]
|
||||
|
||||
$tokenPayload = @{
|
||||
"resource"='https://graph.windows.net'
|
||||
"client_id" = $clientId
|
||||
"client_secret" = $clientSecret
|
||||
"grant_type"='client_credentials'}
|
||||
<span id="calls" />
|
||||
## Step 3: Create calls to the custom threat intelligence API
|
||||
After creating the headers, you can now create calls to the API. The following example demonstrates how you can view all the alert definition entities:
|
||||
|
||||
$response = Invoke-RestMethod $authUrl -Method Post -Body $tokenPayload
|
||||
$token = $response.access_token
|
||||
[!code[CustomTIAPI](./code/example.ps1#L21-L24)]
|
||||
|
||||
```
|
||||
The response is empty on initial use of the API.
|
||||
|
||||
## Create headers
|
||||
The following example demonstrates how to create headers used for the requests with the API.
|
||||
<span id="alert-definition" />
|
||||
## Step 4: Create a new alert definition
|
||||
The following example demonstrates how you to create a new alert definition.
|
||||
|
||||
```
|
||||
$headers = @{}
|
||||
$headers.Add("Content-Type", "application/json")
|
||||
$headers.Add("Accept", "application/json")
|
||||
$headers.Add("Authorization", "Bearer {0}" -f $token)
|
||||
[!code[CustomTIAPI](./code/example.ps1#L26-L39)]
|
||||
|
||||
```
|
||||
<span id="ioc" />
|
||||
## Step 5: Create a new indicator of compromise
|
||||
You can now use the alert ID obtained from creating a new alert definition to create a new indicator of compromise.
|
||||
|
||||
## Create calls to the custom threat intelligence API
|
||||
The following example demonstrates how to view all alert definition entities by creating a call to the API.
|
||||
[!code[CustomTIAPI](./code/example.ps1#L43-L53)]
|
||||
|
||||
```
|
||||
$apiBaseUrl = "https://ti.securitycenter.windows.com/V1.0/"
|
||||
$alertDefinitions =
|
||||
(Invoke-RestMethod ("{0}AlertDefinitions" -f $apiBaseUrl) -Method Get -Headers $headers).value
|
||||
```
|
||||
## Complete code
|
||||
You can use the complete code to create calls to the API.
|
||||
|
||||
If this is the first time to use the API, the response is empty.
|
||||
[!code[CustomTIAPI](./code/example.ps1#L1-L53)]
|
||||
|
||||
## Create a new alert definition
|
||||
The following example shows how to create a new alert definition.
|
||||
|
||||
```
|
||||
$alertDefinitionPayload = @{
|
||||
"Name"= "The Alert's Name"
|
||||
"Severity"= "Low"
|
||||
"InternalDescription"= "An internal description of the Alert"
|
||||
"Title"= "The Title"
|
||||
"UxDescription"= "Description of the alerts"
|
||||
"RecommendedAction"= "The alert's recommended action"
|
||||
"Category"= "Trojan"
|
||||
"Enabled"= "true"}
|
||||
|
||||
|
||||
$alertDefinition =
|
||||
Invoke-RestMethod ("{0}AlertDefinitions" -f $apiBaseUrl) -Method Post -Headers $headers -Body ($alertDefinitionPayload | ConvertTo-Json)
|
||||
```
|
||||
|
||||
## Create a new indicator of compromise
|
||||
The following example shows how to use the alert ID obtained from creating a new alert definition to create a new indicator of compromise.
|
||||
|
||||
```
|
||||
$iocPayload = @{
|
||||
"Type"="Sha1"
|
||||
"Value"="dead1111eeaabbccddeeaabbccddee11ffffffff"
|
||||
"DetectionFunction"="Equals"
|
||||
"Enabled"="true"
|
||||
"AlertDefinition@odata.bind"="AlertDefinitions({0})" -f $alertDefinitionId }
|
||||
|
||||
|
||||
$ioc = Invoke-RestMethod ("{0}IndicatorsOfCompromise" -f $apiBaseUrl) -Method Post -Headers $headers -Body ($iocPayload | ConvertTo-Json)
|
||||
```
|
||||
## Related topics
|
||||
- [Understand threat intelligence concepts](threat-indicator-concepts-windows-defender-advanced-threat-protection.md)
|
||||
- [Enable the custom threat intelligence application](enable-custom-ti-windows-defender-advanced-threat-protection.md)
|
||||
- [Create custom threat intelligence alerts](custom-ti-api-windows-defender-advanced-threat-protection.md)
|
||||
- [Python code examples](python-example-code-windows-defender-advanced-threat-protection.md)
|
||||
- [Troubleshoot custom threat intelligence issues](troubleshoot-custom-ti-windows-defender-advanced-threat-protection.md)
|
||||
|
||||
@ -34,18 +34,18 @@ For more information, see [Turn on the preview experience](preview-settings-wind
|
||||
## Preview features
|
||||
The following features are included in the preview release:
|
||||
|
||||
- [Take response actions on a machine](respond-machine-alerts-windows-defender-advanced-threat-protection.md) - Take action on machine related alerts to quickly respond to detected attacks by isolating machines or collecting an investigation package.
|
||||
- [Take response actions on a machine](respond-machine-alerts-windows-defender-advanced-threat-protection.md) - Quickly respond to detected attacks by isolating machines or collecting an investigation package.
|
||||
- [Isolate machines from the network](respond-machine-alerts-windows-defender-advanced-threat-protection.md#isolate-machines-from-the-network)
|
||||
- [Undo machine isolation](respond-machine-alerts-windows-defender-advanced-threat-protection.md#undo-machine-isolation)
|
||||
- [Collect investigation package](respond-machine-alerts-windows-defender-advanced-threat-protection.md#collect-investigation-package-from-machines)
|
||||
|
||||
- [Take response actions on a file](respond-file-alerts-windows-defender-advanced-threat-protection.md) - Take action on file related alerts to quickly respond to detected attacks by stopping and quarantining files or blocking a file.
|
||||
- [Take response actions on a file](respond-file-alerts-windows-defender-advanced-threat-protection.md) - Quickly respond to detected attacks by stopping and quarantining files or blocking a file.
|
||||
- [Stop and quarantine files in your network](respond-file-alerts-windows-defender-advanced-threat-protection.md#stop-and-quarantine-files-in-your-network)
|
||||
- [Remove file from quarantine](respond-file-alerts-windows-defender-advanced-threat-protection.md#remove-file-from-quarantine)
|
||||
- [Block files in your network](respond-file-alerts-windows-defender-advanced-threat-protection.md#block-files-in-your-network)
|
||||
|
||||
- [Check sensor status](check-sensor-status-windows-defender-advanced-threat-protection.md) - Check an endpoint's ability to provide sensor data and communicate with the Windows Defender ATP service and fix sensor issues if you identify problematic machines.
|
||||
- [Check sensor health state](check-sensor-status-windows-defender-advanced-threat-protection.md) - Check an endpoint's ability to provide sensor data and communicate with the Windows Defender ATP service and fix known issues.
|
||||
- [Fix unhealthy sensors](fix-unhealhty-sensors-windows-defender-advanced-threat-protection.md)
|
||||
|
||||
>[!NOTE]
|
||||
> All response features require machines to be on the latest Windows 10 Insider Preview build and above.
|
||||
> All response actions require machines to be on the latest Windows 10 Insider Preview build.
|
||||
|
||||
@ -27,95 +27,55 @@ localizationpriority: high
|
||||
You must [install](http://docs.python-requests.org/en/master/user/install/#install) the "[requests](http://docs.python-requests.org/en/master/)" python library.
|
||||
|
||||
These code examples demonstrate the following tasks:
|
||||
- [Obtain an Azure AD access token](#obtain-an-azure-ad-access-token)
|
||||
- [Create request session object](#create-a-request's-session-object)
|
||||
- [Create calls to the custom threat intelligence API](#create-calls-to-the-custom-threat-intelligence-api)
|
||||
- [Create a new alert definition](#create-a-new-alert-definition)
|
||||
- [Create a new indicator of compromise](#create-a-new-indicator-of-compromise)
|
||||
- [Obtain an Azure AD access token](#token)
|
||||
- [Create request session object](#session-object)
|
||||
- [Create calls to the custom threat intelligence API](#calls)
|
||||
- [Create a new alert definition](#alert-definition)
|
||||
- [Create a new indicator of compromise](#ioc)
|
||||
|
||||
## Obtain an Azure AD access token
|
||||
<span id="token" />
|
||||
## Step 1: Obtain an Azure AD access token
|
||||
The following example demonstrates how to obtain an Azure AD access token that you can use to call methods in the custom threat intelligence API. After you obtain a token, you have 60 minutes to use this token in calls to the custom threat intelligence API before the token expires. After the token expires, you can generate a new token.
|
||||
|
||||
Replace the *tenant\_id*, *client_id*, and *client_secret* values with the ones you got from **Preferences settings** page in the portal:
|
||||
|
||||
```
|
||||
|
||||
import json
|
||||
import requests
|
||||
from pprint import pprint
|
||||
|
||||
tenant_id="{your tenant ID}"
|
||||
client_id="{your client ID"
|
||||
client_secret="{your client secret}"
|
||||
|
||||
full_auth_url = r"https://login.windows.net/{0}/oauth2/token".format(tenant_id)
|
||||
|
||||
payload = {"resource": "https://graph.windows.net",
|
||||
"client_id": client_id,
|
||||
"client_secret": client_secret,
|
||||
"grant_type": "client_credentials"}
|
||||
[!code[CustomTIAPI](./code/example.py#L1-L17)]
|
||||
|
||||
|
||||
response = requests.post(full_auth_url, payload)
|
||||
token = json.loads(response.text)["access_token"]
|
||||
```
|
||||
|
||||
## Create request session object
|
||||
<span id="session-object" />
|
||||
## Step 2: Create request session object
|
||||
Add HTTP headers to the session object, including the Authorization header with the token that was obtained.
|
||||
|
||||
```
|
||||
with requests.Session() as session:
|
||||
session.headers = {
|
||||
'Authorization': 'Bearer {}'.format(token),
|
||||
'Content-Type': 'application/json',
|
||||
'Accept': 'application/json'}
|
||||
```
|
||||
[!code[CustomTIAPI](./code/example.py#L19-L23)]
|
||||
|
||||
## Create calls to the custom threat intelligence API
|
||||
The following example shows how to view all of the alert definition entities by creating a call to the API.
|
||||
<span id="calls" />
|
||||
## Step 3: Create calls to the custom threat intelligence API
|
||||
After adding HTTP headers to the session object, you can now create calls to the API. The following example demonstrates how you can view all the alert definition entities:
|
||||
|
||||
>[!NOTE]
|
||||
> All code is still within the ```with``` statement with the same indention level.
|
||||
[!code[CustomTIAPI](./code/example.py#L25-L26)]
|
||||
|
||||
```json
|
||||
The response is empty on initial use of the API.
|
||||
|
||||
response = session.get("https://ti.securitycenter.windows.com/V1.0/AlertDefinitions")
|
||||
pprint(json.loads(response.text))
|
||||
```
|
||||
<span id="alert-definition" />
|
||||
## Step 4: Create a new alert definition
|
||||
The following example demonstrates how you to create a new alert definition.
|
||||
|
||||
If this is the first time to use the API, the response is empty.
|
||||
[!code[CustomTIAPI](./code/example.py#L28-L39)]
|
||||
|
||||
## Create a new alert definition
|
||||
The following example shows how to create a new alert definition.
|
||||
<span id="ioc" />
|
||||
## Step 5: Create a new indicator of compromise
|
||||
You can now use the alert ID obtained from creating a new alert definition to create a new indicator of compromise.
|
||||
|
||||
```
|
||||
[!code[CustomTIAPI](./code/example.py#L41-L51)]
|
||||
|
||||
alert_definition = {"Name": "The Alert's Name",
|
||||
"Severity": "Low",
|
||||
"InternalDescription": "An internal description of the Alert",
|
||||
"Title": "The Title",
|
||||
"UxDescription": "Description of the alerts",
|
||||
"RecommendedAction": "The alert's recommended action",
|
||||
"Category": "Trojan",
|
||||
"Enabled": True}
|
||||
## Complete code
|
||||
You can use the complete code to create calls to the API.
|
||||
|
||||
response = session.post(
|
||||
"https://ti.securitycenter.windows.com/V1.0/AlertDefinitions",
|
||||
json=alert_definition)
|
||||
```
|
||||
[!code[CustomTIAPI](./code/example.py#L1-L51)]
|
||||
|
||||
## Create a new indicator of compromise
|
||||
The following example shows how to use the alert ID obtained from creating a new alert definition to create a new indicator of compromise.
|
||||
|
||||
```
|
||||
alert_definition_id = json.loads(response.text)["Id"]
|
||||
ioc = {'Type': "Sha1",
|
||||
'Value': "dead1111eeaabbccddeeaabbccddee11ffffffff",
|
||||
'DetectionFunction': "Equals",
|
||||
'Enabled': True,
|
||||
"AlertDefinition@odata.bind": "AlertDefinitions({0})".format(alert_definition_id)}
|
||||
|
||||
response = session.post(
|
||||
"https://ti.securitycenter.windows.com/V1.0/IndicatorsOfCompromise",
|
||||
json=ioc)
|
||||
```
|
||||
## Related topics
|
||||
- [Understand threat intelligence](threat-indicator-concepts-windows-defender-advanced-threat-protection.md)
|
||||
- [Create custom threat intelligence alerts](custom-ti-api-windows-defender-advanced-threat-protection.md)
|
||||
- [Enable the custom threat intelligence application](enable-custom-ti-windows-defender-advanced-threat-protection.md)
|
||||
- [PowerShell code examples](powershell-example-code-windows-defender-advanced-threat-protection.md)
|
||||
- [Troubleshoot custom threat intelligence issues](troubleshoot-custom-ti-windows-defender-advanced-threat-protection.md)
|
||||
|
||||
@ -39,9 +39,9 @@ You can deploy Device Guard in phases, and plan these phases in relation to the
|
||||
> [!WARNING]
|
||||
> Virtualization-based protection of code integrity may be incompatible with some devices and applications. We strongly recommend testing this configuration in your lab before enabling virtualization-based protection of code integrity on production systems. Failure to do so may result in unexpected failures up to and including data loss or a blue screen error (also called a stop error).
|
||||
|
||||
The following tables provide more information about the hardware, firmware, and software required for deployment of various Device Guard features. The tables describe baseline protections, plus protections for improved security that are associated with hardware and firmware options available in 2015, available in 2016, and announced as options for 2017.
|
||||
The following tables provide more information about the hardware, firmware, and software required for deployment of various Device Guard features. The tables describe baseline protections, plus protections for improved security that are associated with hardware and firmware options available in 2015, 2016, and 2017.
|
||||
|
||||
> **Notes**
|
||||
> **Notes**<br>
|
||||
> • To understand the requirements in the following tables, you will need to be familiar with the main features in Device Guard: configurable code integrity policies, virtualization-based security (VBS), and Universal Extensible Firmware Interface (UEFI) Secure Boot. For information about these features, see [How Device Guard features help protect against threats](introduction-to-device-guard-virtualization-based-security-and-code-integrity-policies.md#how-device-guard-features-help-protect-against-threats).<br>
|
||||
> • Beginning with Windows 10, version 1607, Trusted Platform Module (TPM 2.0) must be enabled by default on new computers.
|
||||
|
||||
|
||||
@ -23,7 +23,7 @@ localizationpriority: high
|
||||
|
||||
<span style="color:#ED1C24;">[Some information relates to pre–released product, which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.]</span>
|
||||
|
||||
You can take action on file related alerts to quickly respond to detected attacks by stopping and quarantining files or blocking a file. After taking action on files, you can check activity details on the Action center.
|
||||
Quickly respond to detected attacks by stopping and quarantining files or blocking a file. After taking action on files, you can check activity details on the Action center.
|
||||
|
||||
>[!NOTE]
|
||||
> These response actions are only available for machines on Windows 10, version 1703.
|
||||
|
||||
@ -23,7 +23,7 @@ localizationpriority: high
|
||||
|
||||
<span style="color:#ED1C24;">[Some information relates to pre-released product, which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.]</span>
|
||||
|
||||
You can take action on machine related alerts to quickly respond to detected attacks by isolating machines or collecting an investigation package. After taking action on machines, you can check activity details on the Action center.
|
||||
Quickly respond to detected attacks by isolating machines or collecting an investigation package. After taking action on machines, you can check activity details on the Action center.
|
||||
|
||||
>[!NOTE]
|
||||
> These response actions are only available for machines on Windows 10, version 1703.
|
||||
|
||||
@ -11,7 +11,7 @@ author: mjcaparas
|
||||
localizationpriority: high
|
||||
---
|
||||
|
||||
# Understand threat indicators
|
||||
# Understand threat intelligence concepts
|
||||
|
||||
**Applies to:**
|
||||
|
||||
@ -49,5 +49,7 @@ IOCs have a many-to-one relationship with alert definitions such that an alert d
|
||||
|
||||
## Related topic
|
||||
- [Enable the custom threat intelligence application](enable-custom-ti-windows-defender-advanced-threat-protection.md)
|
||||
- [Create custom threat indicators using REST API](custom-ti-api-windows-defender-advanced-threat-protection.md)
|
||||
- [Create custom threat intelligence alerts](custom-ti-api-windows-defender-advanced-threat-protection.md)
|
||||
- [PowerShell code examples](powershell-example-code-windows-defender-advanced-threat-protection.md)
|
||||
- [Python code examples](python-example-code-windows-defender-advanced-threat-protection.md)
|
||||
- [Troubleshoot custom threat intelligence issues](troubleshoot-custom-ti-windows-defender-advanced-threat-protection.md)
|
||||
|
||||
@ -44,3 +44,11 @@ If your client secret expires or if you've misplaced the copy provided when you
|
||||
6. Click **Save**. The key value is displayed.
|
||||
|
||||
7. Copy the value and save it in a safe place.
|
||||
|
||||
|
||||
## Related topics
|
||||
- [Understand threat intelligence](threat-indicator-concepts-windows-defender-advanced-threat-protection.md)
|
||||
- [Enable the custom threat intelligence application](enable-custom-ti-windows-defender-advanced-threat-protection.md)
|
||||
- [Create custom threat intelligence](custom-ti-api-windows-defender-advanced-threat-protection.md)
|
||||
- [PowerShell code examples](powershell-example-code-windows-defender-advanced-threat-protection.md)
|
||||
- [Python code examples](python-example-code-windows-defender-advanced-threat-protection.md)
|
||||
|
||||
Reference in New Issue
Block a user