Designing Information Systems Which Manage or Avoid Privacy Incidents

Authors:
Giannakis Antoniou;Lynn Batten;Udaya Parampalli
Affiliations:
The University of Melbourne, Department of Computer Science and Software Engineering,;School of Information Technology, Deakin University,;The University of Melbourne, Department of Computer Science and Software Engineering,
Venue:
EuroISI '08 Proceedings of the 1st European Conference on Intelligence and Security Informatics
Year:
2008

Citing 8
Cited 1

E-P3P privacy policies and privacy authorization

Proceedings of the 2002 ACM workshop on Privacy in the Electronic Society
The session token protocol for forensics and traceback

ACM Transactions on Information and System Security (TISSEC)
Tracking cyberstalkers: a cryptographic approach

ACM SIGCAS Computers and Society
Tor: the second-generation onion router

SSYM'04 Proceedings of the 13th conference on USENIX Security Symposium - Volume 13
Privacy and forensics investigation process: The ERPINA protocol

Computer Standards & Interfaces
Specifying and implementing privacy-preserving cryptographic protocols

International Journal of Information Security
Revocable anonymity

ETRICS'06 Proceedings of the 2006 international conference on Emerging Trends in Information and Communication Security
Trust, privacy and security in e-business: requirements and solutions

PCI'05 Proceedings of the 10th Panhellenic conference on Advances in Informatics

E-commerce: protecting purchaser privacy to enforce trust

Electronic Commerce Research

Quantified Score

Hi-index	0.00

Visualization

Abstract

In this paper, we consider an information system (IS) to be a set of technologies together with a set of rules about those technologies. An IS is considered to be prone to a privacy incident if it does not fully protect the private information of a user or if a dishonest user can take advantage of the privacy protection offered by the IS. This work identifies the potential privacy incidents that may occur in an IS, and proposes a framework, the MAPI Framework (Manage or Avoid Privacy Incidents), which designs IS to manage or avoid privacy incidents. The MAPI Framework can also be used for evaluating IS by identifying the missing or inappropriate technologies which may lead to privacy incidents.