From 81f0cd135f377fa95c55b52fef31cd37184e71e6 Mon Sep 17 00:00:00 2001 From: Iaan D'Souza-Wiltshire Date: Sat, 26 Aug 2017 01:55:26 -0700 Subject: [PATCH] update with sample xml link --- .../import-export-exploit-protection-emet-xml.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/windows/threat-protection/windows-defender-exploit-guard/import-export-exploit-protection-emet-xml.md b/windows/threat-protection/windows-defender-exploit-guard/import-export-exploit-protection-emet-xml.md index 9a979c73d6..d97fe0df4f 100644 --- a/windows/threat-protection/windows-defender-exploit-guard/import-export-exploit-protection-emet-xml.md +++ b/windows/threat-protection/windows-defender-exploit-guard/import-export-exploit-protection-emet-xml.md @@ -51,6 +51,8 @@ You can also convert and import an existing EMET configuration XML file into an This topic describes how to create a configuration file and deploy it across your network, and how to convert an EMET configuration. +The [Exploit Guard Evaluation Package](#) contains a sample configuration file (name *ProcessMitigation-Selfhost-v4.xml* that you can use to see how the XML structure looks. The sample file also contains settings that have been converted from an EMET configuration. You can open the file in a text editor (such as Notepad) or import it directly into Exploit Protection and then review the settings in the Windows Defender Security Center app, as described further in this topic. + ## Create and export a configuration file