Home / Knowledge hub / Data exfiltration
Knowledge hub
Data exfiltration
Quietly copying data out of your systems to somewhere the attacker controls.
What it means
Data exfiltration is the unauthorised copying of data out of your systems to a place the attacker controls. It is usually the last step of an intrusion: get in, find what is valuable, collect it, and move it out. MITRE ATT&CK lists exfiltration as its own stage, after collection.
The idea that makes it click: stealing data is only as hard as getting it past your boundaries. An attacker with access may send it over a normal web connection, tuck it into DNS requests, upload it to a cloud storage account or pull it out slowly through your own API. It often looks like ordinary traffic.
Why it matters
Exfiltration is the moment an incident becomes a data breach. Before it, the attacker has access. After it, your customers' records exist somewhere you cannot reach or delete. That triggers duties to notify regulators and customers, and the harm cannot be undone.
Detection is often late because the copying looks legitimate. A single account pulling thousands of records through an API, or an export feature used at three in the morning, may not stand out unless you are watching for it. Short log retention also removes the evidence of what left.
How it shows up
Routes include a large export or report endpoint, an API that returns whole collections, cloud storage copied to an outside account, email forwarding rules, removable media and tunnelling over DNS or other allowed protocols. In an application, a flaw such as BOLA or a missing limit lets one account page through everyone's data, which counts as exfiltration through your front door.
Reduce the room to move: limit what each account can read, set rate limits and size caps on exports, restrict outbound traffic with egress filtering, alert on unusual volume, and use data loss prevention on sensitive stores. Test the app for ways one account can read in bulk.
Questions people ask
Data exfiltration, answered
What is the difference between a data breach and exfiltration?
A breach is any unauthorised access to data. Exfiltration is the specific act of copying it out.
Some breaches never involve exfiltration, for example when data is only viewed or deleted. Others, like leaving storage open, can mean it is copied by anyone who finds it.
How do attackers exfiltrate data without being noticed?
They use normal-looking channels such as HTTPS to a cloud service, small amounts over a long time, or encoded data inside DNS queries.
Blending in is the point, so you watch behaviour and volume, not just known bad addresses.
Can rate limiting prevent exfiltration?
It slows bulk copying through your own API and gives you time to notice. It does not stop a patient attacker or one with legitimate bulk access.
Pair it with alerts and tight limits on what each account can read.
What logs help investigate exfiltration?
Application access logs, API logs with account and record identifiers, outbound network logs, cloud storage access logs and sign-in records.
You need them kept long enough and unaltered. See the page on log retention.
How do we test for it?
Check whether an ordinary account can read other accounts' records in bulk, whether exports have size and frequency limits, and whether outbound traffic is restricted.
A test should try to move real data and show you what got out.
Sources
Where this comes from
Related
Terms that sit next to this one
Data breach
Information you hold ends up somewhere it should not be.
Egress filtering
Limiting what your servers may connect out to, which blunts data theft.
Data loss prevention
Tools and rules that stop sensitive data leaving where it should stay.
BOLA
An API returns a record just because you asked for it by number.
Rate limiting
Capping how often something can be attempted, per user or per address.
Could one account read it all?
We check whether one signed-in account can page through another's records or pull data in bulk, and each finding carries the request and response that showed it. Book a pilot on one app.
Or start with a $199 pilot on one application: thirty days, success criteria agreed before day one, credited against the annual if you convert.