Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Defence evasion is the MITRE ATT&CK tactic covering everything attackers do to avoid being detected or blocked: disabling tools, hiding in trusted processes, and erasing their own traces.

What Is Defence Evasion?
Defence evasion is the MITRE ATT&CK tactic, TA0005, that covers every technique an adversary uses to avoid being detected or blocked by security controls. It is the largest tactic in the framework by some distance, with more than forty parent techniques and a long list of sub-techniques beneath them, which tells you where attacker effort actually goes.
Unlike initial access or exfiltration, defence evasion is not a phase. It runs throughout the intrusion, alongside everything else. The same operator who is moving laterally is simultaneously choosing tools that do not touch disk, naming files to look ordinary, and deciding which logs to leave alone because clearing them would be noticed.
svchost.exe, placing it in a plausible directory, matching timestamps to neighbouring files, or signing it with a stolen or purchased certificate.rundll32, regsvr32, mshta, and msbuild, so that application control and process monitoring see a trusted executable. This overlaps heavily with living off the land.Most evasion techniques exploit features, not bugs. Signed Microsoft binaries that execute arbitrary code are doing what they were designed to do. Antivirus exclusions exist because real applications need them. Per-user registry precedence is a deliberate design choice. Patching is therefore not the answer, and the defensive response has to be structural.
Mapping your detection rules to ATT&CK techniques shows the gaps quickly, and defence evasion is usually the sparsest column. Adversary emulation — running specific techniques in a controlled way and checking what the SOC sees — turns that map from an assumption into evidence. This is the core of purple team work, and it tends to produce more improvement per day than any new tool.
Our SOC maturation services cover exactly this: measuring what your detections catch, what they miss, and what a competent operator would do to stay invisible.
No, it runs throughout. An operator applies evasion while gaining access, while moving laterally, while collecting data, and while maintaining persistence. Treating it as a separate phase leads to detection strategies that look for it at one point in the timeline. It is better understood as a constraint the attacker works under at every step.
Start with impairing defences and indicator removal, because both are rare in normal operation and therefore high fidelity. Alert on cleared security logs, new kernel driver services, antivirus exclusion changes, audit policy modification, and agents going unhealthy or silent. Add signed binary proxy execution next, tuned against your own baseline of legitimate administrative activity.
It raises the bar considerably, but it is also the thing attackers specifically target. Techniques exist to unhook its user-mode components, blind its telemetry sources, or kill it from the kernel using a vulnerable driver. Pair the product with centralised telemetry, tamper protection, health monitoring, and detections that fire when the agent itself stops reporting.
Map existing detection rules to MITRE ATT&CK techniques to see where the gaps are, then validate the map by actually running those techniques in a controlled adversary emulation exercise and checking what the SOC observed. Documentation routinely overstates coverage; emulation gives you evidence. Repeat it after significant tooling or configuration changes.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.