Defensive Gap Analysis¶
Executive Summary
Synthesis of threat actor deep-dives across all nation-state and cybercrime categories reveals a consistent pattern: defenders have strong coverage at endpoint execution and known-malware-signature phases but critical blind spots in living-off-the-land (LOTL) detection, edge device monitoring, identity-based attacks, encrypted traffic analysis, OT/ICS visibility, and multi-stage attack correlation. These gaps persist not because technology is unavailable but because attacker techniques exploit the seams between security product categories. The six structural gaps identified here map directly to the highest-priority market opportunities in Underserved Areas and the most acute practitioner frustrations in Pain Points.
Cross-Segment Defensive Coverage Matrix¶
The following matrix maps kill chain phases against major security product segments, rating coverage based on the actual defensive capabilities observed against real-world attacker techniques documented in the Threat Actor deep-dives.
| Kill Chain Phase | Endpoint | Network | Cloud | Identity | SIEM/SOAR | OT/IoT | Threat Intel | |
|---|---|---|---|---|---|---|---|---|
| Reconnaissance | Weak | Partial | Weak | Weak | Weak | Partial | Weak | Strong |
| Weaponization | Weak | Weak | Weak | Weak | Weak | Weak | Weak | Strong |
| Delivery (Phishing) | Partial | Partial | Weak | Weak | Strong | Partial | Weak | Partial |
| Delivery (Edge Exploit) | Weak | Partial | Partial | Weak | Weak | Partial | Weak | Partial |
| Initial Access (Valid Accounts) | Weak | Weak | Partial | Partial | Weak | Partial | Weak | Weak |
| Execution (Malware) | Strong | Partial | Partial | Weak | Partial | Partial | Weak | Strong |
| Execution (LOTL) | Partial | Weak | Weak | Weak | Weak | Partial | Weak | Weak |
| Persistence | Strong | Weak | Partial | Partial | Weak | Partial | Weak | Partial |
| Privilege Escalation | Strong | Weak | Partial | Partial | Weak | Partial | Weak | Weak |
| Lateral Movement | Partial | Partial | Partial | Partial | Weak | Partial | Weak | Weak |
| Collection & Exfiltration | Partial | Partial | Partial | Weak | Weak | Partial | Weak | Partial |
| C2 Communication | Partial | Partial | Weak | Weak | Weak | Partial | Weak | Strong |
| Impact (Ransomware/Wiper) | Strong | Weak | Partial | Weak | Weak | Partial | Weak | Partial |
Key takeaway: Endpoint products dominate coverage for malware execution, persistence, and privilege escalation --- the phases where file-based indicators and behavioral rules are well-understood. Coverage drops sharply for LOTL execution, edge device delivery, valid account abuse, and encrypted C2 --- the phases where modern adversaries concentrate their tradecraft.
The Attacker Advantage
Nation-state actors and sophisticated ransomware operators have systematically shifted their tradecraft toward the weakest columns in this matrix. Volt Typhoon's exclusive use of LOTL techniques, APT29's OAuth token abuse, and the ransomware ecosystem's reliance on edge device CVEs are not coincidences --- they are rational responses to defender investments. Attackers read vendor marketing too, and they route around advertised capabilities.
Defensive Coverage Visualization¶
flowchart LR
subgraph strong["Strong Coverage"]
direction TB
A["Endpoint Malware\nDetection"]
B["Email Phishing\nFiltering"]
C["Known Signature\nMatching"]
D["Ransomware\nPrevention"]
end
subgraph partial["Partial Coverage"]
direction TB
E["Lateral Movement\nDetection"]
F["Cloud Workload\nMonitoring"]
G["Data Exfiltration\nPrevention"]
H["Privilege Escalation\nDetection"]
end
subgraph weak["Weak Coverage --- Critical Gaps"]
direction TB
I["LOTL / Fileless\nDetection"]
J["Edge Device\nMonitoring"]
K["Identity-Based\nAttack Detection"]
L["Encrypted C2\nAnalysis"]
M["OT/ICS\nVisibility"]
N["Multi-Stage\nCorrelation"]
end
strong --> partial --> weak
style strong fill:#2e7d32,color:#fff
style partial fill:#f9a825,color:#000
style weak fill:#c62828,color:#fff The pattern is clear: defenders are strongest where attacks are most visible (file-based malware, email phishing) and weakest where attacks blend into normal operations (LOTL, valid credentials, encrypted channels). Sophisticated actors have shifted their tradecraft accordingly.
This asymmetry has a compounding effect: as defenders invest more in the "strong" categories (better endpoint protection, more advanced email filtering), attackers shift further toward the "weak" categories --- creating an arms race that widens the gap rather than closing it. Closing the structural gaps requires fundamentally different detection approaches, not incremental improvements to existing product categories.
Deep-Dive: Six Structural Defensive Gaps¶
The following sections examine each gap in detail: what makes detection hard, which threat actors exploit it, and where market opportunities exist. These gaps were identified by cross-referencing attacker TTPs documented in the Threat Actor deep-dives against the defensive capabilities analyzed in the 14 segment deep-dives.
1. Living-off-the-Land (LOTL) Detection Gap¶
The Hardest Problem in Detection Engineering
Attackers who use only legitimate system tools --- PowerShell, cmd.exe, WMI, certutil, mshta, rundll32 --- generate activity indistinguishable from routine administration. This is not a tooling failure; it is a fundamental signal-to-noise problem that current detection architectures struggle to solve.
The challenge: Every invocation of powershell.exe or wmic by an attacker looks identical at the process level to the same invocation by an IT administrator. EDR products detect known-bad command-line patterns (e.g., encoded PowerShell, AMSI bypass strings), but sophisticated actors --- particularly Chinese threat actors --- deliberately avoid these signatures. They use standard administrative commands executed in standard ways, differing from legitimate use only in intent and context --- attributes that are extremely difficult to capture in detection rules.
The MITRE ATT&CK framework documents dozens of techniques that rely on built-in OS utilities: T1059 (Command and Scripting Interpreter), T1047 (WMI), T1218 (System Binary Proxy Execution), and T1053 (Scheduled Task/Job) among the most prevalent.
Which actors rely on LOTL:
- China / Volt Typhoon: The defining LOTL operation. Volt Typhoon achieved multi-year persistence in US critical infrastructure using almost exclusively native Windows tools, avoiding custom malware entirely (CISA Advisory AA24-038A).
- Russia / APT28 (Fancy Bear): Combines custom implants with LOTL for post-exploitation movement (Mandiant APT28 Report, 2023).
- Ransomware affiliates: Pre-encryption reconnaissance and lateral movement frequently relies on PsExec, WMI, RDP, and native scripting.
Why current EDR struggles: Behavioral baselines require extensive tuning per environment. Most organizations lack the detection engineering resources to build and maintain LOTL-specific analytics. CrowdStrike, SentinelOne, and Microsoft Defender all offer LOTL-related detections, but false positive rates remain high enough that many SOC teams disable or deprioritize these rules.
Scale of the problem: Microsoft's own telemetry shows that PowerShell executes billions of times per day across enterprise environments. Even a 0.1% false positive rate on PowerShell-based detections generates thousands of alerts daily in a large organization --- well above the threshold where SOC analysts can investigate each one.
Market Opportunity: Behavioral Analytics and UEBA
User and entity behavior analytics (UEBA) --- particularly solutions that baseline per-user, per-endpoint tool usage and flag contextual anomalies --- represent the most direct counter to LOTL techniques. Vendors that can reduce false positive rates below 5% for LOTL detections while maintaining recall above 80% will capture significant enterprise demand. The broader opportunity includes AI-driven behavioral modeling that learns what "normal administration" looks like for each environment rather than relying on static signatures.
2. Edge Device Blind Spot¶
The Unmonitored Perimeter
Routers, VPN concentrators, firewalls, load balancers, and IoT gateways cannot run EDR agents. These devices are managed via vendor-proprietary interfaces, run embedded operating systems (often Linux-derived with limited observability), and receive firmware updates infrequently. Attackers who compromise an edge device operate in a detection vacuum.
The scope of the problem: Edge devices are the first thing an external attacker touches --- and often the last thing a defender monitors. The average enterprise network contains hundreds to thousands of edge devices across dozens of vendors and firmware versions. Firmware-level implants can survive reboots and factory resets. Integrity verification tools are nascent or nonexistent for most device families. Even basic logging is inconsistent --- many edge devices generate syslog output in non-standard formats that SIEM platforms struggle to parse effectively.
Which actors exploit this:
- China / Volt Typhoon: Extensively targeted Ivanti Connect Secure, Fortinet FortiGate, Sophos firewalls, and Cisco routers for initial access and persistence (CISA AA24-038A).
- Iran: APT groups exploited VPN appliance vulnerabilities (Pulse Secure / Ivanti) for access to government and defense networks (CISA AA21-321A).
- Initial Access Brokers: Mass-scan for edge CVEs (Citrix Bleed, Fortinet CVE-2023-27997, Ivanti CVE-2024-21887) within hours of public disclosure, selling access to ransomware operators.
- Ransomware operators: Citrix Bleed (CVE-2023-4966) and Fortinet vulnerabilities were among the top initial access vectors in 2023--2024 ransomware campaigns (Mandiant M-Trends 2024).
The supply chain dimension: Edge device vendors themselves are part of the problem. Firmware update cycles are slow (quarterly at best), end-of-life devices remain deployed for years after vendor support ends, and vulnerability disclosure coordination between device vendors and defenders is inconsistent. Organizations often cannot patch edge devices without scheduling maintenance windows that impact availability.
Market Opportunity: Firmware Integrity and Network-Based Detection
Two complementary opportunities exist: (1) firmware integrity monitoring --- continuous verification that edge device firmware and configurations have not been tampered with, analogous to file integrity monitoring for servers; and (2) network-based behavioral detection --- monitoring traffic patterns to/from edge devices for anomalous C2 callbacks, unexpected protocol usage, or configuration changes. Eclypsium has early traction in firmware security; the broader market remains nascent. A third emerging approach is virtual patching at the network layer --- IPS rules that block exploitation of known edge device CVEs without requiring the device itself to be patched.
3. Identity-Based Attack Gap¶
Valid Credentials Defeat Perimeter Defenses
When an attacker authenticates with stolen, phished, or brute-forced credentials, every perimeter control --- firewalls, email gateways, WAFs --- is irrelevant. The attacker is the user. MITRE ATT&CK technique T1078 (Valid Accounts) appears in virtually every threat actor profile because it works universally.
Attack surface breadth:
- Credential theft: Infostealers (Raccoon, RedLine, Lumma) harvest credentials at industrial scale. Billions of credentials circulate on dark web markets and Telegram channels (SpyCloud 2024 Identity Exposure Report).
- OAuth / token abuse: Russia / SVR (APT29) specializes in abusing OAuth tokens and application consent flows in Microsoft 365 and Azure AD environments, bypassing MFA entirely (Microsoft Threat Intelligence, Jan 2024).
- Password spraying at scale: Iran conducts massive password spray campaigns against enterprise VPNs and cloud services.
- MFA fatigue / bypass: Scattered Spider and other ransomware affiliates use MFA fatigue (push notification bombing) and SIM swapping to defeat second-factor authentication.
- Service principal abuse: Cloud-native attacks increasingly target service accounts, managed identities, and API keys that lack MFA entirely.
Why current defenses fall short: Identity and Access Management (IAM) products focus on provisioning and authentication --- ensuring the right users get the right access. They are not designed to detect post-authentication abuse: an attacker using valid credentials who behaves abnormally after login. SIEM/SOAR can correlate identity events but requires extensive custom detection engineering.
The non-human identity explosion: Machine identities (service accounts, API keys, certificates, managed identities) outnumber human identities by an estimated 45:1 in enterprise environments. These non-human identities typically lack MFA, have overly broad permissions, and are rarely rotated. Cloud-native attacks increasingly target service principals and workload identities that are invisible to traditional identity governance. See Underserved Areas for the non-human identity market gap analysis.
The cloud identity sprawl problem: A typical enterprise has identities across Active Directory, Entra ID (Azure AD), Okta, AWS IAM, GCP IAM, and dozens of SaaS applications. No single tool provides unified visibility across all identity providers. Attackers exploit this fragmentation --- compromising a credential in one identity provider and using it to access resources governed by another, crossing the visibility boundary between security tools.
Market Opportunity: Identity Threat Detection and Response (ITDR)
ITDR --- real-time monitoring of identity infrastructure (Active Directory, Entra ID, Okta) for signs of compromise, credential misuse, and privilege abuse --- is the fastest-growing category addressing this gap. Gartner named ITDR a top security trend in 2023. Key capabilities include AD attack path analysis, token theft detection, and service account behavior monitoring. Vendors include CrowdStrike (Falcon Identity), Semperis, Silverfort, and Oort (acquired by Cisco). The market remains fragmented with room for platform consolidation.
4. Encrypted Traffic Analysis Gap¶
C2 Hidden in Plain Sight
Over 90% of web traffic is now encrypted with TLS. Attackers route command-and-control (C2) traffic over HTTPS to legitimate cloud services --- blending perfectly with normal enterprise traffic. Traditional network security appliances that rely on payload inspection are increasingly blind.
The scale of encrypted C2: According to Google Transparency Report data, over 95% of web traffic traversing Google's network is encrypted. Enterprise environments mirror this proportion. A C2 beacon making HTTPS requests to a cloud-hosted endpoint every 30 minutes is statistically invisible in an organization generating millions of HTTPS sessions per day.
Compounding factors:
- TLS 1.3: Encrypts the certificate handshake (via Encrypted Client Hello / ECH), eliminating a key metadata source that defenders previously used for passive inspection.
- DNS-over-HTTPS (DoH): Moves DNS resolution into encrypted HTTPS channels, neutralizing DNS-based C2 detection and threat intelligence feeds that rely on DNS visibility.
- Cloud service abuse: Actors use legitimate services (Azure Blob Storage, Google Drive, Slack, Notion, Cloudflare Workers) for C2 --- the destination domains are indistinguishable from normal business traffic. APT29 (Russia) and APT41 (China) both use cloud-hosted C2 extensively.
- Domain fronting / CDN abuse: Traffic appears directed at a trusted CDN (e.g., Cloudflare, Fastly) but is routed to attacker infrastructure behind the same CDN.
Detection challenge: TLS inspection (break-and-inspect) introduces latency, breaks certificate pinning, raises privacy concerns, and is increasingly infeasible as ECH adoption grows. Organizations need detection methods that work on encrypted traffic metadata rather than decrypted payloads.
Regulatory pressure compounds the problem: GDPR and other privacy regulations limit the ability to decrypt employee traffic. Healthcare (HIPAA), financial services, and government environments face additional restrictions. The tension between security visibility and privacy compliance creates a structural barrier to traditional network monitoring approaches.
Market Opportunity: Encrypted Traffic Analysis (ETA)
Emerging approaches analyze encrypted traffic without decryption: JA3/JA4 TLS fingerprinting identifies C2 frameworks by their unique TLS handshake characteristics; flow metadata analysis detects beaconing patterns, unusual session durations, and data volume anomalies; certificate transparency monitoring identifies suspicious certificate issuance. Vendors with early traction include Vectra AI, ExtraHop, and Corelight. The market opportunity expands as TLS 1.3 and ECH make traditional inspection infeasible.
5. OT/ICS Visibility Gap¶
Critical Infrastructure's Detection Deficit
Operational technology environments --- power grids, water treatment, manufacturing, oil and gas --- run protocols (Modbus, DNP3, OPC UA) that were designed for reliability, not security. Most OT networks lack basic asset inventories, let alone behavioral monitoring or anomaly detection.
The IT/OT convergence risk: As OT environments connect to IT networks for remote monitoring, data analytics, and cloud integration, attack paths from IT to OT proliferate. An attacker with IT network access can pivot to OT systems through poorly segmented network boundaries, shared credentials, or historian servers that bridge both environments.
Which actors target OT:
- Russia / Sandworm: Deployed Industroyer/CrashOverride against Ukraine's power grid (2016) and Industroyer2 (2022). Sandworm has the most demonstrated capability for destructive OT attacks (ESET Industroyer2 Analysis, 2022).
- China / Volt Typhoon: Pre-positioned in US water, energy, and transportation infrastructure --- not for espionage but for potential wartime disruption of critical infrastructure OT systems (CISA AA24-038A).
- Hacktivist / state-adjacent groups: CyberAv3ngers (Iran-linked) targeted US water utility PLCs in late 2023, exploiting default credentials on Unitronics Vision series PLCs --- devices that were internet-facing with no authentication (CISA AA23-335A).
Legacy protocol risk: Industrial protocols like Modbus (designed in 1979) and DNP3 transmit commands in cleartext with no authentication. An attacker on the OT network can send arbitrary commands to PLCs and RTUs --- including commands that alter physical processes --- without needing credentials. Modern protocols like OPC UA offer encryption and authentication, but adoption is slow and backward compatibility requirements mean insecure protocols persist.
Detection maturity: Most OT environments operate at Level 0--1 detection maturity. Asset inventories are incomplete, network monitoring is limited to IT/OT boundary firewalls (if present), and OT-specific protocol analysis is rare. The SANS 2023 OT/ICS Cybersecurity Survey found that only 24% of organizations have dedicated OT security monitoring. See the OT/IoT Security segment for a detailed market analysis.
Market Opportunity: OT-Specific NDR and Asset Discovery
OT network detection and response (NDR) --- passive monitoring that understands industrial protocols and can detect anomalous commands without disrupting operations --- is a high-growth category. Dragos, Claroty, Nozomi Networks, and Armis lead the segment. Key gaps remain in Level 1/0 device monitoring (PLCs, RTUs, safety systems), OT-specific SOAR playbooks, and managed OT security services for organizations that lack in-house OT security expertise.
6. Multi-Stage Attack Correlation Gap¶
Attacks Span Weeks --- Defenses Think in Seconds
Sophisticated attacks unfold across days or weeks, traversing multiple systems, identities, and network segments. Each individual action may appear benign in isolation. The attacker's intent only becomes visible when events are correlated across the full kill chain --- but most security tools analyze events in isolation or within narrow time windows.
The alert fatigue connection: Enterprise SOCs face 10,000+ alerts per day. Studies consistently show 40--60% of alerts go uninvestigated (Ponemon Institute, 2023). When individual alerts lack context, analysts cannot distinguish a true multi-stage intrusion from background noise. This is the operational manifestation of the alert fatigue problem documented in Pain Points.
What is missing:
- Automated kill chain reconstruction: Given a suspicious event, automatically traverse related events backward and forward in time to reconstruct the full attack chain.
- Cross-tool correlation: Attacks cross EDR, NDR, IAM, cloud, and email boundaries. No single tool sees the whole picture, and SIEM/XDR correlation rules are brittle and require constant tuning.
- Long-horizon analysis: SIEM retention is often limited by cost (ingest-based pricing). Attacks with weeks-long dwell times may span multiple retention windows.
- Context enrichment: Raw telemetry (process started, network connection made, file accessed) lacks the business context needed to assess risk. An analyst seeing "PowerShell connected to Azure Blob Storage" cannot determine severity without knowing which user, what data, what time of day, and what baseline behavior looks like.
The dwell time reality: Mandiant's M-Trends 2024 report found a global median dwell time (time from compromise to detection) of 10 days. For espionage-motivated actors like Volt Typhoon, dwell times measured in months to years are documented. Detection systems optimized for real-time alerting are architecturally mismatched to threats that unfold over extended periods.
Market Opportunity: AI-Driven Attack Chain Correlation
The convergence of graph-based analytics, LLM-powered reasoning, and extended data retention creates an opening for automated threat hunting and attack reconstruction. Products that can ingest cross-tool telemetry, maintain weeks-to-months of context, and present analysts with complete attack narratives --- rather than isolated alerts --- address both the correlation gap and the alert fatigue crisis. XDR platforms (Palo Alto Cortex, Microsoft Sentinel, CrowdStrike Falcon) are moving in this direction, but purpose-built attack chain analysis tools remain an underserved niche. Key enabling technologies include knowledge graphs for entity relationship mapping, LLMs for natural-language incident summarization, and cost-effective long-term telemetry storage (data lakes replacing traditional SIEM ingest models).
Detection Maturity Model¶
The following table maps key attacker techniques to a five-level detection maturity model. Most organizations operate at Level 1--2, creating structural advantages for attackers who use techniques requiring Level 3+ defenses.
The maturity levels are:
- Level 0 (None): No detection capability for this technique
- Level 1 (Basic): Signature or rule-based detection with high false positive rates
- Level 2 (Intermediate): Tuned detections with some behavioral analysis
- Level 3 (Advanced): Context-aware detection with low false positive rates and active threat hunting
- Level 4 (Optimized): Continuous validation, automated response, and proactive defense
| Technique | Level 0 (None) | Level 1 (Basic) | Level 2 (Intermediate) | Level 3 (Advanced) | Level 4 (Optimized) | Typical Org Level |
|---|---|---|---|---|---|---|
| Known malware (signatures) | No AV deployed | Signature AV | Next-gen AV/EDR | ML-based detection with tuning | Continuous red team validation | Level 2 |
| Phishing delivery | No email filtering | Basic spam filter | Secure email gateway (SEG) | SEG + sandboxing + link rewrite | SEG + AI content analysis + user reporting | Level 2 |
| LOTL / fileless execution | No visibility | Basic process logging | EDR with LOTL rules (noisy) | Tuned LOTL analytics + UEBA | Per-user behavioral baselines | Level 1 |
| Edge device compromise | No monitoring | Vendor syslog to SIEM | Firmware version tracking | Firmware integrity verification | Continuous config + firmware attestation | Level 0--1 |
| Valid account abuse (T1078) | No identity monitoring | Failed login alerts | Impossible travel / anomaly rules | ITDR with AD attack path analysis | Continuous identity posture + adaptive auth | Level 1 |
| Encrypted C2 (HTTPS) | No TLS inspection | TLS break-and-inspect (partial) | JA3 fingerprinting | Flow metadata + beaconing detection | Full ETA with certificate transparency | Level 1 |
| Lateral movement | No east-west visibility | Basic firewall logging | NDR + microsegmentation | Deception (honeypots/honeytokens) | Zero trust verified per-request | Level 1--2 |
| OT protocol abuse | No OT monitoring | IT/OT boundary firewall | Passive OT NDR (asset discovery) | Protocol-aware anomaly detection | OT-specific SOAR + threat hunting | Level 0--1 |
| Data exfiltration | No DLP | Endpoint DLP (keyword rules) | Network DLP + CASB | ML-based data classification + DLP | Integrated DLP across all channels | Level 1--2 |
| Multi-stage correlation | No SIEM | SIEM with basic correlation rules | XDR with cross-source correlation | AI-driven attack chain analysis | Automated hunting + narrative generation | Level 1 |
The Maturity Gap Is the Market Gap
The distance between where most organizations are (Level 1--2) and where they need to be to counter modern threats (Level 3--4) represents the core demand driver for the cybersecurity market. Products that can move organizations from Level 1 to Level 3 without requiring proportional increases in headcount or expertise will capture outsized market share.
Gap-to-Opportunity Summary¶
The following table maps each defensive gap to the primary threat actors exploiting it, the security product categories most affected, and the emerging solutions addressing it. Market maturity ratings reflect the current state of vendor solutions addressing each gap:
- Nascent: Few vendors, no established category, limited enterprise adoption
- Early: Emerging vendor category, growing awareness, limited production deployments
- Growing: Established vendor competition, increasing enterprise adoption, analyst coverage
| Defensive Gap | Primary Threat Actors | Affected Product Categories | Emerging Solutions | Market Maturity |
|---|---|---|---|---|
| LOTL detection | China (Volt Typhoon), Russia (APT28), Ransomware affiliates | Endpoint, SIEM/SOAR | UEBA, AI behavioral analytics, per-user baselines | Early |
| Edge device blind spot | China (Volt Typhoon), IABs, Iran, Ransomware | Network, Vuln/ASM | Firmware integrity, network behavioral detection, virtual patching | Nascent |
| Identity-based attacks | Russia (APT29), Iran, Ransomware (Scattered Spider) | Identity, Cloud | ITDR, adaptive authentication, token theft detection | Growing |
| Encrypted traffic | Russia (APT29), China (APT41), Ransomware C2 | Network, SIEM/SOAR | JA3/JA4 fingerprinting, flow metadata analysis, ETA | Early |
| OT/ICS visibility | Russia (Sandworm), China (Volt Typhoon), Iran (CyberAv3ngers) | OT/IoT | OT NDR, passive asset discovery, protocol-aware detection | Growing |
| Multi-stage correlation | All advanced actors | SIEM/SOAR, MDR/MSSP | AI attack chain analysis, graph analytics, automated hunting | Early |
Implications¶
For Product Builders¶
The six gaps identified above represent the highest-value product opportunities in cybersecurity:
- LOTL/behavioral detection that reduces false positives below analyst fatigue thresholds
- Edge device integrity monitoring --- a near-greenfield category
- ITDR for post-authentication identity threat detection
- Encrypted traffic analysis that works without payload decryption
- OT-native detection that understands industrial protocols
- AI-driven attack chain correlation that reconstructs multi-stage campaigns
The common thread across all six gaps: the hardest problems are context problems, not signature problems. Products that can deliver environmental context --- "is this normal for this user, this device, this network?" --- at scale and with low false positive rates will define the next generation of defensive tooling.
Cross-reference: Underserved Areas for market sizing and competitive density analysis; Emerging Tech for enabling technologies.
For Investors¶
Defensive spending is shifting toward the gaps documented here. Categories with the strongest growth tailwinds:
- ITDR: Fastest-growing subcategory within identity security, driven by the credential epidemic and cloud identity sprawl
- OT/ICS security: Regulatory mandates (NIS2, NERC CIP, TSA directives) force spending regardless of budget cycles
- XDR / attack correlation: Platform consolidation trend aligns with the multi-stage correlation gap
- Edge device security: Smallest existing vendor base relative to the severity of the threat
Acquisition signals: Recent M&A activity validates these gap categories. CrowdStrike's acquisitions in identity security, Palo Alto's investments in OT visibility, and Cisco's acquisition of Oort (ITDR) all track the gaps identified here. Early-stage startups in edge device security and encrypted traffic analysis represent potential acquisition targets for platform vendors seeking to close coverage gaps.
Spending trajectory by gap:
| Gap Category | Current Spending Trend | 3-Year Outlook | Key Growth Drivers |
|---|---|---|---|
| LOTL / Behavioral Analytics | Moderate growth | High | AI/ML maturation, Volt Typhoon awareness |
| Edge Device Security | Low base, accelerating | Very High | Ivanti/Fortinet breach wave, regulatory pressure |
| ITDR | High growth | Very High | Credential epidemic, cloud identity sprawl |
| Encrypted Traffic Analysis | Low base, steady | High | TLS 1.3 adoption, DoH proliferation |
| OT/ICS Security | Moderate growth | High | NIS2, NERC CIP, nation-state OT targeting |
| Attack Chain Correlation | Moderate growth | High | Platform consolidation, AI capabilities |
Knowledge Gap
Precise market sizing for several of these subcategories (particularly LOTL-specific behavioral analytics and firmware integrity monitoring) is not well-established by analyst firms as of early 2026. Estimates vary significantly depending on category definitions.
For Practitioners¶
Detection investments yielding the highest ROI given current threat patterns:
- Identity monitoring: Deploy ITDR or, at minimum, enable Azure AD / Entra ID risk-based conditional access and monitor OAuth consent grants. The identity vector is the most exploited and least monitored.
- Edge device hardening: Implement firmware update discipline, disable unnecessary management interfaces, and forward edge device logs to SIEM. Low cost, high impact.
- LOTL detection tuning: Invest in detection engineering for the top 10 LOTL binaries (PowerShell, cmd, WMI, certutil, mshta, rundll32, regsvr32, bitsadmin, msiexec, schtasks). Environment-specific baselines beat generic rules.
- Network segmentation: Microsegmentation limits lateral movement and buys time for detection. The most cost-effective control against ransomware propagation.
- Deception technology: Honeytokens and honeypots are low-noise, high-signal detection mechanisms. A fake credential that triggers an alert when used has a near-zero false positive rate --- any use is malicious by definition. Underdeployed relative to efficacy.
Prioritization Framework
Not all gaps are equally urgent for every organization. Prioritize based on your threat model: if you face nation-state risk, focus on LOTL, edge devices, and identity. If ransomware is the primary concern, prioritize edge device patching, identity monitoring, and network segmentation. If you operate critical infrastructure, OT visibility is non-negotiable. The Threat Actor deep-dives provide the context needed to map your industry vertical to the most relevant actor profiles and, by extension, the most relevant gaps.
Key Takeaways¶
-
Defenders are fighting the last war. The security industry's strongest capabilities (signature-based malware detection, email filtering, endpoint protection) address attack techniques that sophisticated adversaries have already moved beyond.
-
The six gaps are interconnected. An attacker who enters via an edge device vulnerability (Gap 2), uses valid credentials (Gap 3), moves laterally with LOTL techniques (Gap 1), and exfiltrates over encrypted channels (Gap 4) crosses four defensive blind spots in a single campaign. Closing one gap without addressing the others provides limited protection.
-
Context is the missing ingredient. Every gap shares a common root cause: defenders lack the environmental context to distinguish malicious activity from legitimate operations. The next generation of security products must be context-native --- built around environmental baselines, identity correlation, and behavioral understanding rather than signatures and rules.
-
The market is responding, unevenly. ITDR and OT security have attracted significant vendor and investor attention. Edge device security and LOTL-specific analytics remain underserved relative to the severity of the threat. The most acute gap --- multi-stage attack correlation --- is being addressed primarily by platform vendors (XDR) rather than purpose-built solutions.
-
Organizations do not need to reach Level 4 everywhere. Pragmatic defenders should identify which gaps are most relevant to their threat model and focus on reaching Level 3 for those specific techniques. The Threat Actor deep-dives provide the threat modeling context needed to make that determination.
Sources¶
- CISA, "PRC State-Sponsored Actors Compromise and Maintain Persistent Access to U.S. Critical Infrastructure" (Advisory AA24-038A, Feb 2024): https://www.cisa.gov/news-events/cybersecurity-advisories/aa24-038a
- CISA, "IRGC-Affiliated Cyber Actors Exploit PLCs in Multiple Sectors" (Advisory AA23-335A, Dec 2023): https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-335a
- CISA, "Iranian Government-Sponsored APT Actors Exploiting Vulnerabilities" (Advisory AA21-321A, 2021): https://www.cisa.gov/news-events/cybersecurity-advisories/aa21-321a
- Mandiant, "M-Trends 2024 Special Report": https://www.mandiant.com/m-trends
- Microsoft Threat Intelligence, "Midnight Blizzard Guidance for Responders" (Jan 2024): https://www.microsoft.com/en-us/security/blog/2024/01/25/midnight-blizzard-guidance-for-responders-on-nation-state-attack/
- ESET, "Industroyer2: Industroyer Reloaded" (Apr 2022): https://www.eset.com/int/about/newsroom/press-releases/research/eset-research-finds-industroyer2-used-against-ukraine/
- SpyCloud, "2024 Identity Exposure Report": https://spycloud.com/resource/2024-identity-exposure-report/
- CrowdStrike, "2024 Global Threat Report": https://www.crowdstrike.com/global-threat-report/
- Ponemon Institute, "The State of Security Operations" (2023): https://www.ponemon.org/
- FBI Congressional Testimony, "The CCP Cyber Threat to the American Homeland" (Jan 2024): https://www.fbi.gov/news/testimony/the-ccp-cyber-threat-to-the-american-homeland-and-national-security
- SANS Institute, "2023 OT/ICS Cybersecurity Survey": https://www.sans.org/white-papers/sans-2023-ot-ics-cybersecurity-survey/
- Mandiant, "APT28 Targets Diplomatic Entities" (2023): https://www.mandiant.com/resources/blog/apt28-targets-diplomats
- Gartner, "Top Trends in Cybersecurity 2023" (identifying ITDR as a top trend): https://www.gartner.com/en/articles/top-trends-in-cybersecurity-2023
- Google Transparency Report, "HTTPS Encryption on the Web": https://transparencyreport.google.com/https/overview
- ODNI, "2024 Annual Threat Assessment of the U.S. Intelligence Community": https://www.dni.gov/files/ODNI/documents/assessments/ATA-2024-Unclassified-Report.pdf
Glossary¶
This glossary defines the acronyms and key terms used throughout the cybersecurity market research site. Use it as a quick reference when navigating segment analyses, pain-point discussions, and opportunity assessments.
A¶
| Term | Definition |
|---|---|
| ACL | Access Control List: rules determining which users/systems can access resources |
| APT | Advanced Persistent Threat: a prolonged, targeted cyberattack where an intruder gains and maintains unauthorized access |
| ASM | Attack Surface Management: continuous discovery, inventory, and risk assessment of an organization's external-facing assets |
| ASPM | Application Security Posture Management: unified visibility and risk management across the application lifecycle |
| AV | Antivirus: software designed to detect, prevent, and remove malware |
B¶
| Term | Definition |
|---|---|
| BAS | Breach and Attack Simulation: automated tools that simulate real-world attacks to test security controls |
| BEC | Business Email Compromise: a social-engineering attack targeting employees with access to company finances or data |
| BYOVD | Bring Your Own Vulnerable Driver: attack technique where adversaries load a legitimately signed but vulnerable kernel driver to disable security tools |
C¶
| Term | Definition |
|---|---|
| C2 | Command and Control: infrastructure used by attackers to communicate with compromised systems |
| CASB | Cloud Access Security Broker: a security policy enforcement point between cloud consumers and providers |
| CCPA | California Consumer Privacy Act: California state law granting consumers rights over their personal data |
| CIAM | Customer Identity and Access Management: managing and securing external customer identities and authentication |
| CIEM | Cloud Infrastructure Entitlement Management: managing identities and privileges in cloud environments |
| CTEM | Continuous Threat Exposure Management: a program for continuously assessing and prioritizing threat exposures |
| CNAPP | Cloud-Native Application Protection Platform: integrated security for cloud-native applications across the full lifecycle |
| CSPM | Cloud Security Posture Management: continuous monitoring of cloud infrastructure for misconfigurations and compliance risks |
| CWPP | Cloud Workload Protection Platform: security for workloads running in cloud environments (VMs, containers, serverless) |
| CVE | Common Vulnerabilities and Exposures: a standardized identifier for publicly known cybersecurity vulnerabilities |
D¶
| Term | Definition |
|---|---|
| DAST | Dynamic Application Security Testing: testing a running application for vulnerabilities by simulating attacks |
| DCS | Distributed Control System: a control system for managing industrial processes across multiple locations |
| DLP | Data Loss Prevention: tools and processes to prevent unauthorized data exfiltration or leakage |
| DORA | Digital Operational Resilience Act: EU regulation on ICT risk management for financial entities |
| DSPM | Data Security Posture Management: discovering, classifying, and protecting sensitive data across cloud environments |
E¶
| Term | Definition |
|---|---|
| EASM | External Attack Surface Management: discovering and monitoring internet-facing assets for exposures |
| EDR | Endpoint Detection and Response: tools that monitor endpoints for threats and provide investigation and response capabilities |
| EPP | Endpoint Protection Platform: integrated endpoint security combining prevention, detection, and response |
F/G¶
| Term | Definition |
|---|---|
| FAIR | Factor Analysis of Information Risk: a quantitative model for understanding, analyzing, and measuring information risk |
| GRC | Governance, Risk, and Compliance: integrated framework for aligning IT with business goals, managing risk, and meeting regulations |
| GDPR | General Data Protection Regulation: EU regulation on data protection and privacy for individuals |
H¶
| Term | Definition |
|---|---|
| HIPAA | Health Insurance Portability and Accountability Act: US law governing the privacy and security of health information |
I¶
| Term | Definition |
|---|---|
| IAB | Initial Access Broker: specialized cybercriminals who compromise networks and sell access to ransomware operators and other buyers |
| IAM | Identity and Access Management: framework for managing digital identities and controlling access to resources |
| ICS | Industrial Control System: control systems used in industrial production and critical infrastructure |
| IDS | Intrusion Detection System: a system that monitors network traffic for suspicious activity and alerts |
| ITDR | Identity Threat Detection and Response: detecting and responding to identity-based attacks and compromises |
| IoT | Internet of Things: network of physical devices embedded with sensors, software, and connectivity |
| IPS | Intrusion Prevention System: a system that monitors and actively blocks detected threats in network traffic |
L¶
| Term | Definition |
|---|---|
| LOLBin | Living Off the Land Binary: a legitimate system binary that can be abused by attackers for malicious purposes such as downloading payloads, executing code, or bypassing security controls |
| LOTL | Living Off the Land: attack technique using legitimate, pre-installed system tools and binaries rather than custom malware to evade detection |
M¶
| Term | Definition |
|---|---|
| MaaS | Malware-as-a-Service: cybercrime business model where malware developers sell or rent their tools to other criminals |
| MDR | Managed Detection and Response: outsourced security service providing 24/7 threat monitoring, detection, and response |
| MITRE ATT&CK | MITRE Adversarial Tactics, Techniques, and Common Knowledge: a knowledge base of adversary behaviors and techniques |
| MSSP | Managed Security Service Provider: a third-party provider offering outsourced monitoring and management of security devices |
| MFA | Multi-Factor Authentication: requiring two or more verification factors to gain access to a resource |
N¶
| Term | Definition |
|---|---|
| NDR | Network Detection and Response: detecting and responding to threats by analyzing network traffic patterns |
| NERC CIP | North American Electric Reliability Corporation Critical Infrastructure Protection: security standards for the electric grid |
| NGAV | Next-Generation Antivirus: advanced antivirus using behavioral analysis, AI, and machine learning beyond signature-based detection |
| NIS2 | Network and Information Systems Directive 2: updated EU directive on cybersecurity for essential and important entities |
| NIST CSF | National Institute of Standards and Technology Cybersecurity Framework: a voluntary framework for managing cybersecurity risk |
O¶
| Term | Definition |
|---|---|
| ORB | Operational Relay Box: compromised network devices (typically SOHO routers or IoT devices) used by threat actors as proxy infrastructure for command and control traffic |
| OT | Operational Technology: hardware and software that monitors and controls physical devices and processes |
| OWASP | Open Worldwide Application Security Project: a nonprofit focused on improving software security through open-source projects and guidance |
P¶
| Term | Definition |
|---|---|
| PAM | Privileged Access Management: securing, managing, and monitoring privileged accounts and access |
| PCI DSS | Payment Card Industry Data Security Standard: security standards for organizations that handle credit card data |
| PII | Personally Identifiable Information: any data that could identify a specific individual |
| PLC | Programmable Logic Controller: an industrial computer used to control manufacturing processes |
R¶
| Term | Definition |
|---|---|
| RaaS | Ransomware-as-a-Service: cybercrime business model where ransomware operators provide malware and infrastructure to affiliates who conduct attacks, splitting profits |
| RGB | Reconnaissance General Bureau: North Korea's primary intelligence agency responsible for clandestine operations including cyber operations |
S¶
| Term | Definition |
|---|---|
| SASE | Secure Access Service Edge: converged network and security-as-a-service architecture delivered from the cloud |
| SAST | Static Application Security Testing: analyzing source code for vulnerabilities without executing the application |
| SBOM | Software Bill of Materials: a formal inventory of components, libraries, and dependencies in a software product |
| SCA | Software Composition Analysis: identifying open-source components and known vulnerabilities in a codebase |
| SCADA | Supervisory Control and Data Acquisition: a system for monitoring and controlling industrial processes remotely |
| SD-WAN | Software-Defined Wide Area Network: a virtual WAN architecture that simplifies branch networking and optimizes traffic |
| SEG | Secure Email Gateway: a solution that filters inbound and outbound email to block threats and enforce policies |
| SIEM | Security Information and Event Management: aggregating and analyzing log data for threat detection and compliance |
| SOAR | Security Orchestration, Automation, and Response: tools that automate and coordinate security operations workflows |
| SOC | Security Operations Center: a centralized team and facility for monitoring, detecting, and responding to security incidents |
| SOX | Sarbanes-Oxley Act: US law mandating financial reporting and internal control requirements for public companies |
| SSE | Security Service Edge: the security component of SASE, delivering SWG, CASB, and ZTNA as cloud services |
| SWG | Secure Web Gateway: a solution that filters web traffic to enforce security policies and block threats |
T¶
| Term | Definition |
|---|---|
| TAM | Total Addressable Market: the total revenue opportunity available for a product or service |
| TCO | Total Cost of Ownership: the complete cost of acquiring, deploying, and operating a solution over its lifetime |
| TIP | Threat Intelligence Platform: a system for aggregating, correlating, and operationalizing threat intelligence data |
| TLS | Transport Layer Security: a cryptographic protocol that provides secure communication over a network |
| TTP | Tactics, Techniques, and Procedures: the patterns of behavior and methods used by threat actors to conduct cyber operations |
V¶
| Term | Definition |
|---|---|
| VM | Vulnerability Management: the ongoing process of identifying, evaluating, treating, and reporting security vulnerabilities |
X¶
| Term | Definition |
|---|---|
| XDR | Extended Detection and Response: unified threat detection and response across endpoints, network, cloud, and email |
Z¶
| Term | Definition |
|---|---|
| ZTNA | Zero Trust Network Access: a security model that grants access based on identity verification and least-privilege principles |