M1050: Exploit Protection
Deploy capabilities that detect, block, and mitigate conditions indicative of software exploits. These capabilities aim to prevent exploitation by addressing vulnerabilities, monitoring anomalous behaviors, and applying exploit-mitigation techniques to harden systems and software.
Operating System Exploit Protections:
- Use Case: Enable built-in exploit protection features provided by modern operating systems, such as Microsoft's Exploit Protection, which includes techniques like Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), and Control Flow Guard (CFG). - Implementation: Enforce DEP for all programs and enable ASLR to randomize memory addresses used by system and application processes. Windows: Configure Exploit Protection through the Windows Security app or deploy settings via Group Policy. `ExploitProtectionExportSettings.exe -path "exploit_settings.xml"` Linux: Use Kernel-level hardening features like SELinux, AppArmor, or GRSEC to enforce memory protections and prevent exploits.
Third-Party Endpoint Security:
- Use Case: Use endpoint protection tools with built-in exploit protection, such as enhanced memory protection, behavior monitoring, and real-time exploit detection. - Implementation: Deploy tools to detect and block exploitation attempts targeting unpatched software.
Virtual Patching: - Use Case: Use tools to implement virtual patches that mitigate vulnerabilities in applications or operating systems until official patches are applied. - Implementation: Use Intrusion Prevention System (IPS) to block exploitation attempts on known vulnerabilities in outdated applications.
Hardening Application Configurations:
- Use Case: Disable risky application features that can be exploited, such as macros in Microsoft Office or JScript in Internet Explorer. - Implementation: Configure Microsoft Office Group Policies to disable execution of macros in downloaded files.
Security context for executives and security teams
Exploit Protection is a prevention and hardening control category: it helps keep software flaws, risky application features, and unpatched systems from turning into compromise. Its business value is highest where patching cannot be immediate, where users handle shared or web-delivered content, and where public-facing or remote services could provide an entry point or path for lateral movement.
Executive priority
Treat M1050 as a resilience control, not a replacement for patching. Leaders should ask whether exploit mitigations are enforced, measured, and exception-managed across systems that matter most to operations: public-facing applications, client endpoints, remote services, credential-related systems, and shared content workflows. For audit and risk governance, require evidence of configured protections, compensating controls for delayed patches, and a process for retiring virtual patches once official fixes are applied.
Technical view
SOC, IR, and detection engineering teams should validate that exploit-protection controls are both configured and observable. The ATT&CK mitigation describes OS exploit protections such as DEP, ASLR, CFG, Windows Exploit Protection via Group Policy, Linux kernel hardening such as SELinux/AppArmor/GRSEC, third-party endpoint exploit prevention, IPS-based virtual patching, and hardening risky application features such as Office macros from downloaded files or JScript in Internet Explorer. Relationship context shows this mitigation is relevant to exploitation-driven initial access, execution, privilege escalation, lateral movement, stealth, and credential access techniques, including T1189, T1190, T1203, T1068, T1210, T1211, and T1212, plus some proxy-execution cases involving trusted binaries and applications.
Likely telemetry
- Exploit-protection configuration state and policy exports, such as Windows Exploit Protection settings or Group Policy evidence
- Endpoint security alerts for exploit behavior, memory protection violations, or blocked exploitation attempts
- Operating system hardening status and enforcement logs where SELinux, AppArmor, GRSEC, DEP, ASLR, or CFG are applicable
- IPS logs for virtual patch signatures and blocked attempts against known vulnerabilities
- Application hardening policy evidence, such as macro restrictions for downloaded Office files or disabled risky scripting features
Detection direction
- Because ATT&CK provides no official detection text for this mitigation, validate control effectiveness through configuration evidence, prevention logs, and controlled testing rather than assuming coverage.
- Tune alerts around exploit-prevention blocks, abnormal child processes from client applications, and suspicious use of trusted binaries while accounting for legitimate administrative and application behavior.
- Correlate IPS virtual patch events with vulnerability inventory so defenders can distinguish meaningful exposure reduction from noisy generic blocking.
- Check blind spots where protections are disabled by exception, not deployed to certain application classes, or not monitored by the SOC.
- For shared content and client-execution risk, confirm visibility into files opened from shared locations, browser/client application behavior, and policy enforcement for risky content features.
Mitigation priorities
- Prioritize official patching and vulnerability remediation first; use exploit protection and virtual patching as compensating controls when immediate patching is not feasible.
- Enforce built-in OS exploit protections and baseline configurations through central policy where supported.
- Apply kernel and application hardening controls appropriate to the environment, including restricting risky content features such as downloaded-file macros.
- Deploy and monitor endpoint exploit-prevention capabilities for systems exposed to client-side, privilege-escalation, or lateral-movement exploitation paths.
- Use IPS-based virtual patching for known vulnerable services while tracking ownership, expiration, and replacement with official fixes.
Additional notes and limits
M1050 is broad and control-oriented. Its defensive value depends on local asset criticality, vulnerability exposure, policy enforcement, and whether the SOC receives actionable prevention telemetry. The relationship set makes it especially relevant to exploitation used for initial access, execution, privilege escalation, lateral movement, stealth, and credential access.
The supplied ATT&CK object does not specify platforms or provide official detection guidance. Platform examples appear in the mitigation description and related techniques, so local validation is required before claiming coverage for any specific operating system, cloud service, identity provider, container, ESXi, or SaaS environment.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Exploit Protection
Deploy capabilities that detect, block, and mitigate conditions indicative of software exploits. These capabilities aim to prevent exploitation by addressing vulnerabilities, monitoring anomalous behaviors, and applying exploit-mitigation techniques to harden systems and software.
Operating System Exploit Protections:
- Use Case: Enable built-in exploit protection features provided by modern operating systems, such as Microsoft's Exploit Protection, which includes techniques like Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), and Control Flow Guard (CFG). - Implementation: Enforce DEP for all programs and enable ASLR to randomize memory addresses used by system and application processes. Windows: Configure Exploit Protection through the Windows Security app or deploy settings via Group Policy. `ExploitProtectionExportSettings.exe -path "exploit_settings.xml"` Linux: Use Kernel-level hardening features like SELinux, AppArmor, or GRSEC to enforce memory protections and prevent exploits.
Third-Party Endpoint Security:
- Use Case: Use endpoint protection tools with built-in exploit protection, such as enhanced memory protection, behavior monitoring, and real-time exploit detection. - Implementation: Deploy tools to detect and block exploitation attempts targeting unpatched software.
Virtual Patching: - Use Case: Use tools to implement virtual patches that mitigate vulnerabilities in applications or operating systems until official patches are applied. - Implementation: Use Intrusion Prevention System (IPS) to block exploitation attempts on known vulnerabilities in outdated applications.
Hardening Application Configurations:
- Use Case: Disable risky application features that can be exploited, such as macros in Microsoft Office or JScript in Internet Explorer. - Implementation: Configure Microsoft Office Group Policies to disable execution of macros in downloaded files.
How security teams should use this page
Treat this object as behavior context, not an attribution claim. Validate the related groups, software, data sources, and mitigations against official ATT&CK relationships and your own telemetry before making control-coverage decisions.
Techniques used
This mirrors the MITRE pattern of making group, software, campaign, and technique relationships scannable. Relationship notes come from mirrored ATT&CK relationship text when available.
| Domain | ID | Name | Relationship / procedure |
|---|---|---|---|
| Enterprise | T1212 | Exploitation for Credential Access | Security applications that look for behavior used during exploitation such as Windows Defender Exploit Guard (WDEG) and the Enhanced Mitigation Experience Toolkit (EMET) can be used to mitigate some exploitation behavior.[1] Control flow integrity checking is another way to potentially identify and stop a software exploit from occurring.[2] Many of these protections depend on the architecture and target application binary for compatibility and may not work for software targeted for defense evasion. |
| Enterprise | T1218.015 | Electron ApplicationsSub-technique | Microsoft's Enhanced Mitigation Experience Toolkit (EMET) Attack Surface Reduction (ASR) feature can be used to block methods of using trusted binaries to bypass application control. Ensure that Electron is updated to the latest version and critical vulnerabilities (such as nodeIntegration bypasses) are patched and cannot be exploited. |
| Enterprise | T1189 | Drive-by Compromise | Security applications that look for behavior used during exploitation such as Windows Defender Exploit Guard (WDEG) and the Enhanced Mitigation Experience Toolkit (EMET) can be used to mitigate some exploitation behavior.[1] Control flow integrity checking is another way to potentially identify and stop a software exploit from occurring.[2] Many of these protections depend on the architecture and target application binary for compatibility. |
| Enterprise | T1218 | System Binary Proxy Execution | Microsoft's Enhanced Mitigation Experience Toolkit (EMET) Attack Surface Reduction (ASR) feature can be used to block methods of using using trusted binaries to bypass application control. |
| Enterprise | T1210 | Exploitation of Remote Services | Security applications that look for behavior used during exploitation such as Windows Defender Exploit Guard (WDEG) and the Enhanced Mitigation Experience Toolkit (EMET) can be used to mitigate some exploitation behavior. [1] Control flow integrity checking is another way to potentially identify and stop a software exploit from occurring. [2] Many of these protections depend on the architecture and target application binary for compatibility and may not work for all software or services targeted. |
| Enterprise | T1068 | Exploitation for Privilege Escalation | Security applications that look for behavior used during exploitation such as Windows Defender Exploit Guard (WDEG) and the Enhanced Mitigation Experience Toolkit (EMET) can be used to mitigate some exploitation behavior. [1] Control flow integrity checking is another way to potentially identify and stop a software exploit from occurring. [2] Many of these protections depend on the architecture and target application binary for compatibility and may not work for software components targeted for privilege escalation. |
| Enterprise | T1211 | Exploitation for Stealth | Security applications that look for behavior used during exploitation such as Windows Defender Exploit Guard (WDEG) and the Enhanced Mitigation Experience Toolkit (EMET) can be used to mitigate some exploitation behavior. [1] Control flow integrity checking is another way to potentially identify and stop a software exploit from occurring. [2] Many of these protections depend on the architecture and target application binary for compatibility and may not work for software targeted for defense evasion. |
| Enterprise | T1203 | Exploitation for Client Execution | Security applications that look for behavior used during exploitation such as Windows Defender Exploit Guard (WDEG) and the Enhanced Mitigation Experience Toolkit (EMET) can be used to mitigate some exploitation behavior. [1] Control flow integrity checking is another way to potentially identify and stop a software exploit from occurring. [2] Many of these protections depend on the architecture and target application binary for compatibility. |
| Enterprise | T1190 | Exploit Public-Facing Application | Web Application Firewalls may be used to limit exposure of applications to prevent exploit traffic from reaching the application. |
| Enterprise | T1218.011 | Rundll32Sub-technique | Microsoft's Enhanced Mitigation Experience Toolkit (EMET) Attack Surface Reduction (ASR) feature can be used to block methods of using rundll32.exe to bypass application control. |
| Enterprise | T1218.010 | Regsvr32Sub-technique | Microsoft's Enhanced Mitigation Experience Toolkit (EMET) Attack Surface Reduction (ASR) feature can be used to block regsvr32.exe from being used to bypass application control. [3] Identify and block potentially malicious software executed through regsvr32 functionality by using application control [4] tools, like Windows Defender Application Control[5], AppLocker, [6] [7] or Software Restriction Policies [8] where appropriate. [9] |
| Enterprise | T1080 | Taint Shared Content | Use utilities that detect or mitigate common features used in exploitation, such as the Microsoft Enhanced Mitigation Experience Toolkit (EMET). |
All related ATT&CK context
Object version and sync metadata
The fields below describe the current mirrored snapshot. When Glexia retains multiple ATT&CK source imports, you can open the table to compare the same object across releases (hashes and MITRE timestamps). For MITRE’s own release notes and roadmap, see ATT&CK resources — Updates.
Imported snapshots across ATT&CK releases(1)
| Release | Bundle imported | Object version | Modified | Status | Raw hash |
|---|---|---|---|---|---|
| 19.1 | 1.2 | Current bundle | b1bbb31e775f… |
Mirrored ATT&CK source object
The raw object is retained through the mirrored ATT&CK source bundle and object hash. The raw endpoint returns the exact object from the mirrored bundle when available.
External references and citations
MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.
- [1]TechNet Moving Beyond EMET
Nunez, N. (2017, August 9). Moving Beyond EMET II – Windows Defender Exploit Guard. Retrieved March 12, 2018.
Open source URL - [2]Wikipedia Control Flow Integrity
Wikipedia. (2018, January 11). Control-flow integrity. Retrieved March 12, 2018.
Open source URL - [3]Secure Host Baseline EMET
National Security Agency. (2016, May 4). Secure Host Baseline EMET. Retrieved June 22, 2016.
Open source URL - [4]Beechey 2010
Beechey, J. (2010, December). Application Whitelisting: Panacea or Propaganda?. Retrieved November 18, 2014.
- [5]Microsoft Windows Defender Application Control
Gorzelany, A., Hall, J., Poggemeyer, L.. (2019, January 7). Windows Defender Application Control. Retrieved July 16, 2019.
Open source URL - [6]Windows Commands JPCERT
Tomonaga, S. (2016, January 26). Windows Commands Abused by Attackers. Retrieved February 2, 2016.
Open source URL - [7]NSA MS AppLocker
NSA Information Assurance Directorate. (2014, August). Application Whitelisting Using Microsoft AppLocker. Retrieved March 31, 2016.
Open source URL - [8]Corio 2008
Corio, C., & Sayana, D. P. (2008, June). Application Lockdown with Software Restriction Policies. Retrieved September 12, 2024.
Open source URL - [9]TechNet Applocker vs SRP
Microsoft. (2012, June 27). Using Software Restriction Policies and AppLocker Policies. Retrieved April 7, 2016.
Open source URL - [10]mitre-attackM1050Open source URL
- [11]mitre-attackM1050Open source URL
- [12]mitre-attackM1050Open source URL
- [13]TechNet Moving Beyond EMET
Nunez, N. (2017, August 9). Moving Beyond EMET II – Windows Defender Exploit Guard. Retrieved March 12, 2018.
Open source URL - [14]Wikipedia Control Flow Integrity
Wikipedia. (2018, January 11). Control-flow integrity. Retrieved March 12, 2018.
Open source URL - [15]TechNet Moving Beyond EMET
Nunez, N. (2017, August 9). Moving Beyond EMET II – Windows Defender Exploit Guard. Retrieved March 12, 2018.
Open source URL - [16]TechNet Moving Beyond EMET
Nunez, N. (2017, August 9). Moving Beyond EMET II – Windows Defender Exploit Guard. Retrieved March 12, 2018.
Open source URL - [17]Wikipedia Control Flow Integrity
Wikipedia. (2018, January 11). Control-flow integrity. Retrieved March 12, 2018.
Open source URL - [18]Wikipedia Control Flow Integrity
Wikipedia. (2018, January 11). Control-flow integrity. Retrieved March 12, 2018.
Open source URL - [19]TechNet Moving Beyond EMET
Nunez, N. (2017, August 9). Moving Beyond EMET II – Windows Defender Exploit Guard. Retrieved March 12, 2018.
Open source URL - [20]TechNet Moving Beyond EMET
Nunez, N. (2017, August 9). Moving Beyond EMET II – Windows Defender Exploit Guard. Retrieved March 12, 2018.
Open source URL - [21]Wikipedia Control Flow Integrity
Wikipedia. (2018, January 11). Control-flow integrity. Retrieved March 12, 2018.
Open source URL - [22]Wikipedia Control Flow Integrity
Wikipedia. (2018, January 11). Control-flow integrity. Retrieved March 12, 2018.
Open source URL - [23]TechNet Moving Beyond EMET
Nunez, N. (2017, August 9). Moving Beyond EMET II – Windows Defender Exploit Guard. Retrieved March 12, 2018.
Open source URL - [24]TechNet Moving Beyond EMET
Nunez, N. (2017, August 9). Moving Beyond EMET II – Windows Defender Exploit Guard. Retrieved March 12, 2018.
Open source URL - [25]Wikipedia Control Flow Integrity
Wikipedia. (2018, January 11). Control-flow integrity. Retrieved March 12, 2018.
Open source URL - [26]Wikipedia Control Flow Integrity
Wikipedia. (2018, January 11). Control-flow integrity. Retrieved March 12, 2018.
Open source URL - [27]TechNet Moving Beyond EMET
Nunez, N. (2017, August 9). Moving Beyond EMET II – Windows Defender Exploit Guard. Retrieved March 12, 2018.
Open source URL - [28]TechNet Moving Beyond EMET
Nunez, N. (2017, August 9). Moving Beyond EMET II – Windows Defender Exploit Guard. Retrieved March 12, 2018.
Open source URL - [29]Wikipedia Control Flow Integrity
Wikipedia. (2018, January 11). Control-flow integrity. Retrieved March 12, 2018.
Open source URL - [30]Wikipedia Control Flow Integrity
Wikipedia. (2018, January 11). Control-flow integrity. Retrieved March 12, 2018.
Open source URL - [31]TechNet Moving Beyond EMET
Nunez, N. (2017, August 9). Moving Beyond EMET II – Windows Defender Exploit Guard. Retrieved March 12, 2018.
Open source URL - [32]TechNet Moving Beyond EMET
Nunez, N. (2017, August 9). Moving Beyond EMET II – Windows Defender Exploit Guard. Retrieved March 12, 2018.
Open source URL - [33]Wikipedia Control Flow Integrity
Wikipedia. (2018, January 11). Control-flow integrity. Retrieved March 12, 2018.
Open source URL - [34]Wikipedia Control Flow Integrity
Wikipedia. (2018, January 11). Control-flow integrity. Retrieved March 12, 2018.
Open source URL - [35]Beechey 2010
Beechey, J. (2010, December). Application Whitelisting: Panacea or Propaganda?. Retrieved November 18, 2014.
- [36]Corio 2008
Corio, C., & Sayana, D. P. (2008, June). Application Lockdown with Software Restriction Policies. Retrieved September 12, 2024.
Open source URL - [37]Microsoft Windows Defender Application Control
Gorzelany, A., Hall, J., Poggemeyer, L.. (2019, January 7). Windows Defender Application Control. Retrieved July 16, 2019.
Open source URL - [38]NSA MS AppLocker
NSA Information Assurance Directorate. (2014, August). Application Whitelisting Using Microsoft AppLocker. Retrieved March 31, 2016.
Open source URL - [39]Secure Host Baseline EMET
National Security Agency. (2016, May 4). Secure Host Baseline EMET. Retrieved June 22, 2016.
Open source URL - [40]TechNet Applocker vs SRP
Microsoft. (2012, June 27). Using Software Restriction Policies and AppLocker Policies. Retrieved April 7, 2016.
Open source URL - [41]Windows Commands JPCERT
Tomonaga, S. (2016, January 26). Windows Commands Abused by Attackers. Retrieved February 2, 2016.
Open source URL
Source: MITRE ATT&CK®. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. MITRE ATT&CK and ATT&CK are registered trademarks of The MITRE Corporation. Glexia is not affiliated with or endorsed by MITRE.