StrongestLayer Threat Research · Evasion Taxonomy v1.0

Attacks have a goal. Evasion has a method.

A formal catalog of 36 email evasion techniques across 5 categories, organized by which detection capability each technique defeats. Twenty-two are dataset-validated against StrongestLayer's Dec 2025 to Feb 2026 detection corpus; fourteen are literature-validated from public threat research. Companion to the Email Attack Taxonomy + Simulator: that one classifies the goal, this one classifies the bypass.
36 techniques
5 categories
3 tiers
April 2026

Three tiers of architectural defeat depth.

Tier reflects the defender's structural position against a technique, independent of attacker effort. A simple Voice Channel Pivot is Tier 3 because no email-text-scanning paradigm can detect what happens after the call connects. A complex multi-stage redirect chain may be Tier 2 because it is, in principle, traceable with sufficient compute. The tier is a procurement question, not a difficulty rating.

Tier 3
Structural Blind Spot
Detection is architecturally impossible within the email-text-scanning paradigm. No amount of capability addition closes the gap; resolution requires capability the SEG does not possess.
Resolution: Off-platform telemetry, behavioral reasoning, mobile / endpoint integration.
Tier 2
Practically Defeated
Detection is theoretically possible but the technique specifically blocks or degrades automated analysis. The detector is being detected and routed around.
Resolution: Deeper detonation, time-of-click execution, cloak-aware infrastructure.
Tier 1
Cost-Prohibitive
The signal is recognizable but blocking it produces unacceptable false positives because the same vocabulary or infrastructure carries legitimate business email at high volume.
Resolution: Workflow context, intent reasoning, sender-graph correlation.
14
Tier 3 techniques (39%)
15
Tier 2 techniques (42%)
7
Tier 1 techniques (19%)
Why hybrid naming

Each technique gets one canonical name. Some are intent-named (Sandbox Detonation Gate, Authentication Alignment Evasion, Authority Impersonation): the safeguard bypassed is the diagnostic feature. Others are behavior-named (Voice Channel Pivot, QR Code Mobile Pivot, HTML Smuggling): the mechanic is distinctive enough to anchor analysis on its own. The rule is what a SOC analyst would type into a search bar first.

Organized by what the technique defeats.

Each category is defined by the detection capability it primarily defeats, not by what the technique looks like superficially. Many techniques chain across categories in real campaigns; the taxonomy classifies the technique, not the campaign.

CS · Channel-Shift

Move exploitation off the email plane

Phone, mobile, calendar, collaboration platform, encrypted messenger. Once the conversation leaves email, post-delivery remediation cannot follow.
Defeats: Post-delivery monitoring
DT · Delivery Trust

Arrive through trusted infrastructure

Compromised accounts, lookalike domains, legitimate ESPs, OAuth consent. Reputation filtering cannot distinguish attacker from legitimate sender.
Defeats: Sender reputation + auth
SE · Scanner Evasion

Detect the detector

CAPTCHA gates, multi-hop chains, time-of-click drift, AiTM proxies, geofencing, user-agent cloaking. Stop or degrade automated analysis before it reaches the payload.
Defeats: Sandbox + URL detonation
PC · Payload Concealment

Encode beyond text scanning

QR codes, image-based text, HTML smuggling, SVG scripts, encrypted attachments, cloud-file LOTS hosting. Hide the malicious signal in a representation the parser cannot read.
Defeats: Content scanning
CE · Cognitive Exploitation

Look like legitimate business mail

Authority impersonation, brand spoofing, financial pretexting, notification format trust, internal self-impersonation, thread hijacking. Vocabulary identical to legitimate mail.
Defeats: Semantic intent classification

36 techniques. Click any cell for full detail.

Each cell shows the canonical ID, name, naming axis (intent / behavior), tier badge, and source tag. OBS = dataset-validated against the Dec 2025 to Feb 2026 StrongestLayer corpus. LIT = literature-validated from public threat research. Use the search box or filter chips to narrow.

MITRE ATT&CK and vendor terminology mapping.

Each StrongestLayer technique maps to the closest MITRE ATT&CK technique or sub-technique, plus aliases used by other vendors and research teams. Use this matrix when reading a third-party advisory and trying to locate the corresponding technique in this taxonomy.

IDCanonical NameMITRE ATT&CKCommon Aliases

One taxonomy, three audiences.

If you are a SOC analyst

The taxonomy is a search index. Open this page, type a technique name or symptom into the search box, and the matching cell opens. Each detail panel includes the MITRE mapping and common combinations so you can pivot to threat-hunt rules, ATT&CK Navigator layers, or your own alert pipeline.

If you are a CISO or architecture lead

The categories and tiers are the conversation. "We have addressed Tier 1 across all categories and Tier 2 in three of five" is a substantive maturity statement. Use the matrix in vendor evaluations to ask which techniques does the architecture you are evaluating ever close, by design, not just what features does it ship.

If you are a vendor or research team

The IDs (EV-CS-001, EV-DT-006, etc.) are stable references. Cite them in coverage claims and detection-rule documentation. Renaming a canonical name in a future revision will not break ID-based references. The cross-reference matrix is the bridge to MITRE and to other vendor taxonomies; submit corrections to the StrongestLayer threat research team.

What this taxonomy is not

It is not a complete enumeration of every email evasion ever observed. It is a working catalog at v1.0 of the techniques most relevant to enterprise defenders today, expected to evolve quarterly. It is not a scoring system; the ICE (Indicators of Coordinated Evasion) framework is the scoring layer that operates on top of this taxonomy. It is not a buying guide; tier and category answer architectural questions, not vendor questions.