Journal article
Investigating the leakage of sensitive personal and organisational information in email headers
- Abstract:
- Email is undoubtedly the most used communications mechanism in society today. Within business alone, it is estimated that 100 billion emails are sent and received daily across the world. While the security and privacy of email has been of concern to enterprises and individuals for decades, this has predominately been focused on protecting against malicious content in incoming emails and explicit data exfiltration, rather than inadvertent leaks in outgoing emails. In this paper, we consider this topic of outgoing emails and unintentional information leakage to better appreciate the security and privacy concerns related to the simple activity of sending an email. Specifically, our research seeks to investigate the extent to which potentially sensitive information could be leaked, in even blank emails, by considering the metadata that is a natural part of email headers. Through findings from a user-based experiment, we demonstrate that there is a noteworthy level of exposure of organisational and personal identity information, much of which can be further used by an attacker for reconnaissance or develop a more targeted and sophisticated attack.
- Publication status:
- Published
- Peer review status:
- Peer reviewed
Actions
Access Document
- Files:
-
-
(Preview, Version of record, pdf, 331.3KB, Terms of use)
-
Authors
- Publisher:
- Journal of Internet Services and Information Security
- Journal:
- Journal of Internet Services and Information Security More from this journal
- Volume:
- 5
- Issue:
- 1
- Pages:
- 70-84
- Publication date:
- 2015-02-01
- Edition:
- Publisher's version
- EISSN:
-
2182-2077
- ISSN:
-
2182-2069
- Language:
-
English
- Keywords:
- Subjects:
- UUID:
-
uuid:f019a0eb-d00c-4076-88ad-e7c196432fb4
- Local pid:
-
ora:10470
- Deposit date:
-
2015-03-09
- ARK identifier:
Terms of use
- Copyright holder:
- Jason RC Nurse et al
- Copyright date:
- 2015
If you are the owner of this record, you can report an update to it here: Report update to this record