$npx -y skills add SnailSploit/Claude-Red --skill offensive-windows-boundariesWhen this skill is active: 1. Load and apply the full methodology below as your operational checklist 2. Follow steps in order unless the user specifies otherwise 3. For each technique, consider applicability to the current target/context 4. Track which checklist items have been
| 1 | # SKILL: Week 7: Defeating Windows Security Boundaries |
| 2 | |
| 3 | ## Metadata |
| 4 | - **Skill Name**: windows-boundaries |
| 5 | - **Folder**: offensive-windows-boundaries |
| 6 | - **Source**: https://github.com/SnailSploit/offensive-checklist/blob/main/7-windows-boundaries.md |
| 7 | |
| 8 | ## Description |
| 9 | Windows security boundary taxonomy and attack surface enumeration: kernel/user boundary, sandbox boundaries (LPAC, AppContainer), COM/RPC boundaries, hypervisor boundary, trust level transitions. Use when planning privilege escalation paths, sandbox escapes, or understanding Windows security architecture. |
| 10 | |
| 11 | ## Trigger Phrases |
| 12 | Use this skill when the conversation involves any of: |
| 13 | `Windows boundaries, security boundary, kernel user boundary, sandbox escape, AppContainer, LPAC, COM boundary, RPC boundary, hypervisor, Hyper-V, privilege escalation, trust level` |
| 14 | |
| 15 | ## Instructions for Claude |
| 16 | |
| 17 | When this skill is active: |
| 18 | 1. Load and apply the full methodology below as your operational checklist |
| 19 | 2. Follow steps in order unless the user specifies otherwise |
| 20 | 3. For each technique, consider applicability to the current target/context |
| 21 | 4. Track which checklist items have been completed |
| 22 | 5. Suggest next steps based on findings |
| 23 | |
| 24 | --- |
| 25 | |
| 26 | ## Full Methodology |
| 27 | |
| 28 | # Week 7: Defeating Windows Security Boundaries |
| 29 | |
| 30 | ## Overview |
| 31 | |
| 32 | _created by AnotherOne from @Pwn3rzs Telegram channel_. |
| 33 | |
| 34 | Week 6 taught you how mitigations work defensively. |
| 35 | You'll learn to bypass the OS security _policies and features_ that prevent your code from running, your processes from accessing protected resources, and your actions from being logged. |
| 36 | This is distinct from Week 8, which teaches you how to bypass _exploit mitigations_ (DEP, ASLR, CFG) once your code is already running. |
| 37 | |
| 38 | > **Week 7 vs Week 8 - The Key Distinction**: |
| 39 | > |
| 40 | > - **Week 7** answers: _"Can my code execute at all?"_ - bypass AMSI, WDAC, ASR, AppContainers, integrity levels, PPL, ETW telemetry |
| 41 | > - **Week 8** answers: _"Can my exploit succeed?"_ - bypass DEP, ASLR, stack cookies, CFG/XFG, heap safe-unlinking |
| 42 | |
| 43 | **This Week's Focus**: |
| 44 | |
| 45 | - Offensive reconnaissance and mitigation fingerprinting |
| 46 | - AMSI bypass and script-based attack techniques |
| 47 | - Protected Process Light (PPL) exploitation |
| 48 | - Sandbox, integrity level, and AppContainer bypass |
| 49 | - WDAC and Attack Surface Reduction (ASR) bypass |
| 50 | - ETW manipulation and telemetry blinding |
| 51 | - Kernel driver interaction fundamentals (preparation for Week 11) |
| 52 | |
| 53 | **Prerequisites**: |
| 54 | |
| 55 | - Completed Week 6: Understanding Modern Windows Mitigations |
| 56 | - Week 5: Basic exploitation techniques (stack overflow, ROP, heap) |
| 57 | - Familiarity with WinDbg, x64dbg, and IDA/Ghidra |
| 58 | - C/C++, Python, and assembly knowledge |
| 59 | |
| 60 | ### Week 7 Deliverables |
| 61 | |
| 62 | By the end of this week, you should have completed: |
| 63 | |
| 64 | - [ ] **Recon Tool**: Built a mitigation fingerprinting tool |
| 65 | - [ ] **AMSI Bypass**: Implemented working AMSI bypass techniques |
| 66 | - [ ] **PPL Research**: Documented PPL bypass vectors |
| 67 | - [ ] **Sandbox Escape**: Bypassed AppContainer or integrity level restrictions |
| 68 | - [ ] **WDAC/ASR Bypass**: Demonstrated at least one WDAC and one ASR bypass |
| 69 | - [ ] **ETW Blinding**: Implemented ETW provider patching to suppress telemetry |
| 70 | - [ ] **Driver IOCTL Lab**: Loaded a test driver, sent an IOCTL, set a kernel breakpoint (Week 11 prep) |
| 71 | |
| 72 | ## Day 1: Offensive Reconnaissance & Mitigation Fingerprinting |
| 73 | |
| 74 | - **Goal**: Master target enumeration - fingerprint system and process mitigations to identify attack vectors. |
| 75 | - **Activities**: |
| 76 | - _Reading_: |
| 77 | - [Windows Exploit Protection](https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/exploit-protection-reference) - Official mitigation documentation |
| 78 | - [Process Mitigation Policies](https://learn.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-getprocessmitigationpolicy) |
| 79 | - [Override Process Mitigations via Policy](https://learn.microsoft.com/en-us/windows/security/operating-system-security/device-management/override-mitigation-options-for-app-related-security-policies) |
| 80 | - _Online Resources_: |
| 81 | - [DEFCON 27 - Exploiting Windows Exploit Mitigation for ROP Exploits](https://www.youtube.com/watch?v=gIJOtP1AC3A) |
| 82 | - [Sandbox Mitigations](https://troopers.de/media/filer_public/f6/07/f6076037-85e0-42b7-9a51-507986edafce/the_joy_of_sandbox_mitigations_export.pdf) |
| 83 | - [Offensive Windows Internals](https://github.com/matthieu-hackwitharts/Win32_Offensive_Cheatsheet) |
| 84 | - _Tool Setup_: |
| 85 | - Process Hacker / System Informer |
| 86 | - WinDbg Preview with mitigation inspection scripts |
| 87 | - PE-bear / pestudio for binary analysis |
| 88 | - _Exercise_: |
| 89 | - Build comprehensive mitigation scanner |
| 90 | - Enumerate all protected processes on target |
| 91 | - Identify legacy/unprotected binaries for exploitation |
| 92 | |
| 93 | ### Deliverables |
| 94 | |
| 95 | - [ ] Build a comprehensive mitigation scanner |
| 96 | - [ ] Fingerprint process-level protections remotely |
| 97 | - [ ] Identify unprotected/legacy binaries on target |
| 98 | - [ ] Map kernel mitigation status |
| 99 | |
| 100 | ### Target Mitigation Landscape |
| 101 | |
| 102 | ```text |
| 103 | ┌───────────────────────────────────────── |