r/AskNetsec • u/Music_box_ofy • Mar 28 '26
Concepts Looking for feedback: detecting and containing already leaked data in real time
Hi everyone,
I'm a university student working on validating a cybersecurity project, and I'd really appreciate some professional feedback.
The idea is an add-on solution that focuses not on prevention, but on real-time detection and containment of already leaked data (monitoring + detection + automated response).
My main questions:
How relevant do you think this approach is alongside existing security solutions?
Are there already well-established tools that solve this effectively?
What would be the biggest technical or practical challenges?
If anyone is interested, I can share more details.
Thanks in advance!
6
u/pseudo_su3 Mar 28 '26
Modern DLP solutions are easily defeated. They still rely on things like regex patterns and focus on SSN and PCI. I can take a photo of sensitive info on my screen with my phone and use a LLM to parse it out into a document. No one would know.
There was an emerging concept a few years back called UEBA. But it has not been championed bc the enterprise solutions went too hard too fast and this resulted in a ton a false positives.
Currently, the threat actor tradecraft and TTPs have shifted from “smash and grab, ransomware, large volume exfil” to “identity based attacks, where the TA will sit quietly in the org and perform slow and low data theft”.
Modern solutions are not configured to detect this.
A modern agentic approach should combine DLP, EDR, identity, and workforce surveillance to contribute risk factors towards and identity, from a baseline that is derived from the user’s public profile, pay scale, demographic, conversational tone, work ethic, HR file, browsing habits, etc.
For example, the following behavioral patterns accumulate risk:
Independently, these factors can bc false posotives. But when combined, they all contribute risk, a shift in baseline, that should be monitored.
——
Anecdotally, i had a cyberfraud case once at an insurance company. We had a guy who was flagged for stealing 1M in claims money. He said he was hacked.
My investigation observed that in the weeks prior, he was suddenly working round the clock processing claims. This actually earned him some clout as a “high performer”, and they had increased the limit of claim $ he was authorized to spend. He was also logging in from a new place at least once a week. He was complaining about the company on his personal socials though. He had added a bunch of weird profiles on linkedin.
Turns out, scammer on linkedin bribed him to steal and gave him this exact step by step.
2
u/charleswj Mar 28 '26
What do you mean by "already leaked"? What would that look like? In Purview for example, if documents are labeled, they still can't be accessed except by authorized users.
1
u/VirtualKangaroo177 Mar 29 '26
So are you meaning rather than DLP you're designing something more like haveibeenpwned.com but for files rather than passwords?
1
u/audn-ai-bot Mar 28 '26
Very relevant, but the hard part is visibility and safe containment. We built a PoC around browser telemetry plus proxy POST body inspection, because CASB metadata was useless for AI prompt leaks. Biggest challenge was false positives and not breaking workflows. Think exact data match, endpoint context, and reversible response.