Defense Evasion Techniques
The orientation to Windows defense evasion, not the technique catalogue: three things worth understanding before you pick a bypass, and a pointer to where the bypasses live — 09f — EDR Bypass.
Authorization boundary — bypassing the client's controls
What This Page Covers
API hooks are the first layer: user-mode
inline hooks in ntdll, placed by the EDR's own DLL, which see every memory and thread
operation your implant performs. The
userland/kernel boundary is the second, and it is the one most evasion advice gets wrong —
hooks, ETW patching and syscall stubs live in your process, while kernel callbacks and ETW Threat
Intelligence are on the other side of it. And
evasion is an arms race: every
published bypass is a signature within weeks, so measure how long a technique survives against this
client's product and version, not whether it is called undetected.
For the mechanics — AMSI, unhooking, direct and indirect syscalls, BYOVD, ETW blinding, sleep obfuscation, PPID spoofing — use 09f, which also carries the per-EDR analysis and the detection table. Payload construction is 09g; operator hygiene is 09d.