Join our Newsletter — 33% off our NHI Course
Threats, Abuse & Incident Response

Web Exfiltration

← Back to Glossary
By NHI Mgmt Group Updated November 16, 2026 Domain: Threats, Abuse & Incident Response

Web exfiltration is the unauthorised transfer of data from a system to a remote web destination. It usually happens through HTTP or HTTPS requests, often by malware, a compromised browser session, or a script that posts data out to an attacker-controlled endpoint, bypassing normal file transfer controls.

What Web Exfiltration Means in Practice

Web exfiltration is not just “data leaving the network”, it is data being pushed out through ordinary-looking web traffic. That matters because HTTP and HTTPS are usually permitted, heavily used, and hard to distinguish from legitimate business activity without content, destination, and behavioural inspection.

In practice, the technique often blends into normal browsing, software update traffic, API calls, form submissions, or browser-based workflows. A malicious script, injected page, compromised extension, or malware can turn a standard outbound request into a theft channel without needing a classic file transfer tool.

Why Web Traffic Is a Favoured Exfiltration Channel

Web channels are attractive because they are reliable, ubiquitous, and often allowed to traverse proxies, NAT, firewalls, and cloud egress paths. That gives an attacker a low-friction path for moving stolen data out of an environment while reducing the chance that simple perimeter controls will spot it.

Web exfiltration also supports staging and fragmentation. Data can be split across many requests, embedded in query strings, request bodies, cookies, headers, or uploaded form data, which makes the transfer appear like ordinary application usage rather than a bulk export.

The same logic applies to modern software and cloud estates. The more an environment depends on browser sessions, web apps, SaaS integrations, and API-driven workflows, the more a malicious outbound request can hide inside legitimate traffic patterns. ATT&CK Exfiltration Tactic is a useful map for understanding where web exfiltration sits in the wider data theft chain.

Common Web Exfiltration Patterns

Web exfiltration is not one single method. It commonly appears as direct posts to an attacker-controlled endpoint, encoded data in GET parameters, uploads to cloud or paste services, webhook abuse, or scripted transfers that mimic legitimate application requests. The specific pattern often reflects what the environment already permits.

When browser sessions are involved, the attacker may not need to steal a whole file at once. Sensitive fragments, session-bound data, rendered page content, or copied records can be transmitted incrementally over web requests, making the activity look like ordinary interaction rather than a dedicated transfer job.

T1567 Exfiltration Over Web Service is the closest ATT&CK technique family for many real-world cases, while Data Exfiltration Guide gives the broader detection and prevention context across web, cloud, and other channels.

Why Detection and Response Are Harder Than They Look

Web exfiltration is difficult because defenders must separate malicious outbound web activity from legitimate business traffic. The same proxy, TLS, DNS, browser, and SaaS telemetry that proves connectivity may not by itself reveal intent, so context such as destination reputation, request frequency, payload shape, user-agent anomalies, and unusual timing becomes critical.

Post-incident review should assume that web exfiltration may have involved more than one control failure. If a browser session, endpoint, script, or service account was compromised, the data theft path may also have included token theft, weak segmentation, absent egress policy, or a lack of alerting on unusual uploads.

For response work, it is often useful to start from the outbound request trail, then trace back to the originating host, account, session, and data set. Data Exfiltration Playbook is directly relevant because it focuses on confirming theft from logs, scoping what left, stopping the transfer, and deciding on follow-on actions.

How to Reduce Exposure Without Assuming the Channel Can Be Blocked

Web exfiltration is best treated as an egress-risk problem, not just a malware problem. Organisations usually need layered controls that reduce what can leave, reduce where it can go, and increase the chance that unusual outbound web behaviour is visible quickly enough to act on.

That means treating web destinations, upload paths, and browser-driven transfers as part of the data loss surface. M1057 Data Loss Prevention is relevant here because DLP is one of the main control families used to inspect or constrain outbound sensitive content, even though it will not catch every encrypted or well-disguised transfer.

For cloud and SaaS-heavy environments, the practical goal is not perfect prevention, but reducing blind spots around internet-facing upload paths, session abuse, and suspicious outbound destinations. T1567 Exfiltration Over Web Service and Data Exfiltration Playbook are both useful references for that control-and-response combination.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

MITRE ATT&CK addresses the attack and risk surface, while NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
MITRE ATT&CKT1567 — Exfiltration Over Web ServiceWeb exfiltration commonly uses web services as the theft path.
TA0010 — ExfiltrationWeb exfiltration is a data theft stage in the ATT&CK exfiltration tactic.
M1057 — Data Loss PreventionDLP is a core mitigation for outbound sensitive data over web channels.
Recommendation — Map outbound upload and webhook abuse to T1567 and monitor for unusual web transfer patterns. Correlate network and host telemetry to spot exfiltration before data leaves the environment. Apply M1057 controls to inspect, constrain, and alert on sensitive outbound web transfers.
NIST SP 800-53 Rev 5SI-4 — System MonitoringOutbound web exfiltration requires monitoring for anomalous network and endpoint behaviour.
AC-4 — Information Flow EnforcementWeb exfiltration is fundamentally an information flow control problem.
Recommendation — Use SI-4 to detect unusual outbound requests, destinations, and transfer patterns. Enforce AC-4 to restrict which data may leave to external web destinations.
CIS Controls v8CIS-8 — Audit Log ManagementDetection and forensics for web exfiltration depend on usable logs.
Recommendation — Centralise and retain logs needed to investigate suspicious outbound web transfers.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org