TL;DR
This paper examines privacy risks in continuous event data publishing for process mining, demonstrating how correspondence attacks can degrade privacy protections and analyzing real-life logs to assess vulnerability.
Contribution
It identifies and analyzes correspondence attacks against group-based privacy preservation in continuous event data publishing for process mining.
Findings
Correspondence attacks can significantly reduce privacy guarantees.
Real-life event logs show vulnerability to these attacks.
Privacy degradation is quantifiable using anonymity indicators.
Abstract
Process mining enables organizations to discover and analyze their actual processes using event data. Event data can be extracted from any information system supporting operational processes, e.g., SAP. Whereas the data inside such systems is protected using access control mechanisms, the extracted event data contain sensitive information that needs to be protected. This creates a new risk and a possible inhibitor for applying process mining. Therefore, privacy issues in process mining become increasingly important. Several privacy preservation techniques have been introduced to mitigate possible attacks against static event data published only once. However, to keep the process mining results up-to-date, event data need to be published continuously. For example, a new log is created at the end of each week. In this paper, we elaborate on the attacks which can be launched against…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Code & Models
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
