How do I install the Memory Prtctn Dep Aslr skill?

Run npx skillmds@latest add undermybelt/memory-prtctn-dep-aslr in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Memory Prtctn Dep Aslr safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Memory Prtctn Dep Aslr?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Memory Prtctn Dep Aslr free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Memory Prtctn Dep Aslr?

undermybelt (@undermybelt) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Memory Prtctn Dep Aslr by undermybelt

Name: Memory Prtctn Dep Aslr
Author: undermybelt

Memory Prtctn Dep Aslr

Implements memory protection mechanisms including DEP (Data Execution Prevention), ASLR (Address Space Layout Randomization), CFG (Control Flow Guard), and other exploit mitigations to prevent memory corruption attacks. Use when hardening endpoints against buffer overflow exploits, ROP chains, and code injection. Activates for requests involving memory protection, exploit mitigation, DEP, ASLR, or CFG configuration.

undermybelt Updated Sep 17, 2026

File contents

Implementing Memory Protection with DEP and ASLR

When to Use

Use this skill when hardening endpoints against memory-based exploits by configuring DEP, ASLR, CFG, and Windows Exploit Protection system-wide and per-application mitigations.

Prerequisites

Windows 10/11 or Windows Server 2016+ with administrative privileges
Group Policy management access for enterprise-wide deployment
Understanding of memory corruption attack techniques (buffer overflow, ROP chains)
Test environment for validating application compatibility with exploit mitigations

Workflow

Step 1: Configure System-Level Mitigations

# Enable system-wide DEP (Data Execution Prevention)
# Boot configuration: OptIn (default), OptOut (recommended), AlwaysOn
bcdedit /set nx AlwaysOn

# Verify ASLR status (enabled by default on modern Windows)
Get-ProcessMitigation -System
# MandatoryASLR, BottomUpASLR, HighEntropyASLR should be ON

# Enable all system-level mitigations
Set-ProcessMitigation -System -Enable DEP,SEHOP,ForceRelocateImages,BottomUp,HighEntropy

Step 2: Configure Per-Application Mitigations

# Harden high-risk applications (browsers, Office, PDF readers)
Set-ProcessMitigation -Name "WINWORD.EXE" -Enable DEP,SEHOP,ForceRelocateImages,CFG,StrictHandle
Set-ProcessMitigation -Name "EXCEL.EXE" -Enable DEP,SEHOP,ForceRelocateImages,CFG,StrictHandle
Set-ProcessMitigation -Name "AcroRd32.exe" -Enable DEP,SEHOP,ForceRelocateImages,CFG
Set-ProcessMitigation -Name "chrome.exe" -Enable DEP,CFG,ForceRelocateImages
Set-ProcessMitigation -Name "msedge.exe" -Enable DEP,CFG,ForceRelocateImages

# Export configuration for deployment
Get-ProcessMitigation -RegistryConfigFilePath "C:\exploit_protection.xml"
# Deploy via Intune or GPO

Step 3: Deploy via Intune/GPO

Intune: Endpoint Security → Attack Surface Reduction → Exploit Protection
  Import exploit_protection.xml template

GPO: Computer Configuration → Admin Templates → Windows Components
  → Windows Defender Exploit Guard → Exploit Protection
  → "Use a common set of exploit protection settings" → Enabled
  → Point to XML file on network share

Key Concepts

Term	Definition
DEP	Marks memory pages as non-executable to prevent shellcode execution in data regions
ASLR	Randomizes memory addresses of loaded modules to defeat hardcoded ROP gadgets
CFG	Validates indirect call targets at runtime to prevent control flow hijacking
SEHOP	Validates SEH chain integrity to prevent SEH-based exploitation

Tools & Systems

Windows Exploit Protection: Built-in per-process mitigation management
EMET (legacy): Enhanced Mitigation Experience Toolkit (predecessor, now deprecated)
ProcessMitigations PowerShell: Get/Set-ProcessMitigation cmdlets

Common Pitfalls

DEP compatibility: Legacy 32-bit applications may crash with DEP AlwaysOn. Use OptOut with exceptions.
Mandatory ASLR breaking apps: Some applications are not ASLR-compatible. Test before enforcing ForceRelocateImages.
CFG limited to compiled-in support: CFG only works for applications compiled with /guard:cf. Cannot be retroactively applied.

---name: memory-prtctn-dep-aslrdescription: Implements memory protection mechanisms including DEP (Data Execution Prevention), ASLR (Address Space Layout Randomization), CFG (Control Flow Guard), and other exploit mitigations to prevent memory corruption attacks. Use when hardening endpoints against buffer overflow exploits, ROP chains, and code injection. Activates for requests involving memory protection, exploit mitigation, DEP, ASLR, or CFG configuration.license: Apache-2.0---# Implementing Memory Protection with DEP and ASLR## When to UseUse this skill when hardening endpoints against memory-based exploits by configuring DEP, ASLR, CFG, and Windows Exploit Protection system-wide and per-application mitigations.## Prerequisites- Windows 10/11 or Windows Server 2016+ with administrative privileges- Group Policy management access for enterprise-wide deployment- Understanding of memory corruption attack techniques (buffer overflow, ROP chains)- Test environment for validating application compatibility with exploit mitigations## Workflow### Step 1: Configure System-Level Mitigations```powershell# Enable system-wide DEP (Data Execution Prevention)# Boot configuration: OptIn (default), OptOut (recommended), AlwaysOnbcdedit /set nx AlwaysOn# Verify ASLR status (enabled by default on modern Windows)Get-ProcessMitigation -System# MandatoryASLR, BottomUpASLR, HighEntropyASLR should be ON# Enable all system-level mitigationsSet-ProcessMitigation -System -Enable DEP,SEHOP,ForceRelocateImages,BottomUp,HighEntropy```### Step 2: Configure Per-Application Mitigations```powershell# Harden high-risk applications (browsers, Office, PDF readers)Set-ProcessMitigation -Name "WINWORD.EXE" -Enable DEP,SEHOP,ForceRelocateImages,CFG,StrictHandleSet-ProcessMitigation -Name "EXCEL.EXE" -Enable DEP,SEHOP,ForceRelocateImages,CFG,StrictHandleSet-ProcessMitigation -Name "AcroRd32.exe" -Enable DEP,SEHOP,ForceRelocateImages,CFGSet-ProcessMitigation -Name "chrome.exe" -Enable DEP,CFG,ForceRelocateImagesSet-ProcessMitigation -Name "msedge.exe" -Enable DEP,CFG,ForceRelocateImages# Export configuration for deploymentGet-ProcessMitigation -RegistryConfigFilePath "C:\exploit_protection.xml"# Deploy via Intune or GPO```### Step 3: Deploy via Intune/GPO```Intune: Endpoint Security → Attack Surface Reduction → Exploit Protection Import exploit_protection.xml templateGPO: Computer Configuration → Admin Templates → Windows Components → Windows Defender Exploit Guard → Exploit Protection → "Use a common set of exploit protection settings" → Enabled → Point to XML file on network share```## Key Concepts| Term | Definition ||------|-----------|| **DEP** | Marks memory pages as non-executable to prevent shellcode execution in data regions || **ASLR** | Randomizes memory addresses of loaded modules to defeat hardcoded ROP gadgets || **CFG** | Validates indirect call targets at runtime to prevent control flow hijacking || **SEHOP** | Validates SEH chain integrity to prevent SEH-based exploitation |## Tools & Systems- **Windows Exploit Protection**: Built-in per-process mitigation management- **EMET (legacy)**: Enhanced Mitigation Experience Toolkit (predecessor, now deprecated)- **ProcessMitigations PowerShell**: Get/Set-ProcessMitigation cmdlets## Common Pitfalls- **DEP compatibility**: Legacy 32-bit applications may crash with DEP AlwaysOn. Use OptOut with exceptions.- **Mandatory ASLR breaking apps**: Some applications are not ASLR-compatible. Test before enforcing ForceRelocateImages.- **CFG limited to compiled-in support**: CFG only works for applications compiled with /guard:cf. Cannot be retroactively applied.

Frequently asked questions