Demo Data from EDBT 2026 / reviewers in the wild / expert
Tomás Navarro Múnera
dblp:407/8376
· DBLP profile ↗
1ranked-venue papers
0as first author
1since 2021 · last 2025
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Security and privacy · 1 · 1 since 2021
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Network and information security
1 paper |
Digital forensics and information hiding · 100% |
Topics — the 2 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Digital forensics and information hiding
attack investigation |
0.9 | 1 | 2025 | Connecting the Extra Dots (Contexts): Correlating External Information about Point of Interest for Attack Investigation · SP 2025 |
Digital forensics and information hiding › digital forensics
forensic analysis |
0.3 | 1 | 2025 | Connecting the Extra Dots (Contexts): Correlating External Information about Point of Interest for Attack Investigation · SP 2025 |
Methods — techniques the papers use, named apart from their topics
provenance analysis · 0.9graph pruning · 0.9
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2025 | Connecting the Extra Dots (Contexts): Correlating External Information about Point of Interest for Attack InvestigationabstractProvenance analysis is one of the go-to solutions today for human analysts to investigate security incidents. To assist analysts in managing the sheer size of provenance graphs, many pruning solutions have been proposed. Such solutions rely on graph-theory features, anomaly detection, and other techniques to identify nodes and edges that are irrelevant to the detected incident. Despite differences in their methodologies, those solutions typically share a common approach when it comes to the detected incident, i.e., they merely regard the incident as an abstract starting point, without tapping into it further. However, we observe that this may lead to missed opportunities for pruning, since the incident is typically associated with external information, e.g., knowledge about the exploit or the vulnerability, which may provide extra contextual insights for effective pruning. Based on such an observation, we propose Contexts, a solution that complements existing pruning approaches by leveraging external information about the incident. Specifically, the solution extracts contextual information from external sources, maps such information to provenance graph nodes, and then correlates those nodes to form a subgraph relevant to the incident. Our implementation and experiments based on real-world attacks demonstrate its effectiveness, e.g., working as the pre-processor of an existing pruning approach, it helps to reduce the false positives from more than 150k to less than ten, and as a standalone pruning solution, Contextsachieves 100% TPR for 19 out of 20 attacks, with an FPR below 0.6% for 16 out of 20 attacks. Finally, its real-world practicality is illustrated through a user study where 94.4% of participants agreed with its usefulness in attack investigation. Sareh Mohammadi, Hugo Kermabon-Bobinnec, Azadeh Tabiban, Lingyu Wang 0001, Tomás Navarro Múnera, Yosr Jarraya |
SP | 5 |