Here is an open-source UI which can access/view/create/modify all of these Windows 10 process mitigations via IFEO registry settings. This tool is portable and does not require the use of the ProcessMitigations PowerShell module. This portable app allows you to set per-process mitigations. Therefore any process that starts, as long as it is setup here, will have the selected process mitigations enforced within the process without the need for the individual developers of other software having to set certain flags (DEP, for example) during binary compilation. The program itself is only a GUI for setting process mitigations in the registry "via IFEO registry settings". After mitigations have been set, Windows "is taking over" and enforcing them. (When your application starts, OS will look for specific registry values under that reg key, and act accordingly - #) You have to rely on "cryptic" events from the Windows Event Viewer (if it is logged at all) GFlagsX is more about making OS built-in security features more easily accessible. Part of a "Living Off The Land" or "Defending Off The Land" type of strategy. Source (w/ screenshot): https://twitter.com/zodiacon/status/861238433687228417 Link: https://github.com/zodiacon/GflagsX/releases Warning: Under certain unknown conditions and settings, some might experience BSODs in your systems. Take a snapshot or make system image prior making use of GFlagsX please. Use it at your own risk. Note by @WildByDesign : We should note that this would still likely work with Windows 8 and whatever other versions of Windows that utilize the IFEO MitigationOptions keys (https://theryuu.github.io/ifeo-mitigationoptions.txt). That is the most informative details I've ever found with regard to the IFEO mitigation options. It also explains in detail what each mitigation does and the possible options. Although some of that is getting outdated, but still good info. For example, dev Pavel for GFlagsX does different numbers for SEHOP, combining with DEP and such in the same bit number. I thought he was wrong at first, but then I realized he is the main author for Windows Internals books then I realized I have no reason to question him. But then I checked the ProcessMitigations PowerShell tool and it applies the same way. So GFlagsX is entirely correct with the numbers even though I thought it was wrong initially. But apparently both methods work. I believe that more mitigation options bit numbers will be created for when RS3 is released for the EAF, EAF+, IAT, ROP, etc. mitigations coming over from EMET. They ran out of bit number space within Windows so they created a new key somewhere. But anyway, Pavel will add it too as it gets closer. Credits for supplying infos to create this first post: @WildByDesign For finding the source code and creating compilations accordingly. @mood for his always invaluable input.