Privacy and forensics investigation process: The ERPINA protocol

Authors:
Giannakis Antoniou;Leon Sterling;Stefanos Gritzalis;Parampalli Udaya
Affiliations:
Department of Computer Science and Software Engineering, The University of Melbourne, 111 Barry Street, Carlton, Victoria 3053, Australia;Department of Computer Science and Software Engineering, The University of Melbourne, 111 Barry Street, Carlton, Victoria 3053, Australia;Department of Information and Communication Systems Engineering, University of the Aegean, Samos, 83200 Greece;Department of Computer Science and Software Engineering, The University of Melbourne, 111 Barry Street, Carlton, Victoria 3053, Australia
Venue:
Computer Standards & Interfaces
Year:
2008

Citing 3
Cited 2

Measures of retaining digital evidence to prosecute computer-based cyber-crimes

Computer Standards & Interfaces
PPINA – a forensic investigation protocol for privacy enhancing technologies

CMS'06 Proceedings of the 10th IFIP TC-6 TC-11 international conference on Communications and Multimedia Security
Advances in Onion Routing: Description and backtracing/investigation problems

Digital Investigation: The International Journal of Digital Forensics & Incident Response

Designing Information Systems Which Manage or Avoid Privacy Incidents

EuroISI '08 Proceedings of the 1st European Conference on Intelligence and Security Informatics
Safety Measures for Social Computing in Wiki Learning Environment

International Journal of Information Security and Privacy

Quantified Score

Hi-index	0.00

Visualization

Abstract

The rights of an Internet user acting anonymously conflicts with the rights of a Server victim identifying the malicious user. The ERPINA protocol, introduced in this paper, allows an honest user communicating anonymously with a Server through a PET, while the identity of a dishonest user is revealed. Prior research failed to distinguish objectively between an honest user and an attacker; and a reliable and objective distinguishing technique is lacking. The ERPINA protocol addresses the reliability issue efficiently by defining from the beginning of the communication what is considered as malicious and what is not.