2000
DOI: 10.1007/3-540-39945-3_3
|View full text |Cite
|
Sign up to set email alerts
|

Transaction-Based Pseudonyms in Audit Data for Privacy Respecting Intrusion Detection

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
27
0

Year Published

2001
2001
2016
2016

Publication Types

Select...
6
2

Relationship

0
8

Authors

Journals

citations
Cited by 24 publications
(27 citation statements)
references
References 4 publications
0
27
0
Order By: Relevance
“…In the registration phase, the encryptions are done under the public key belonging to a set of so called audit officers 6 inside the organization, e.g. in the emergency management organization:…”
Section: Registration and Generation Of Pseudonymsmentioning
confidence: 99%
See 1 more Smart Citation
“…In the registration phase, the encryptions are done under the public key belonging to a set of so called audit officers 6 inside the organization, e.g. in the emergency management organization:…”
Section: Registration and Generation Of Pseudonymsmentioning
confidence: 99%
“…Research in this direction is about finding efficient mechanisms and models of operations. Biskup et al propose to use transaction pseudonyms [6] in audit logs and a secret sharing method for the re-identification [5] in case a threshold of detected inappropriate actions is exceeded in the analysis. These concepts are applied within traditional computer security domains like Unix audit logs.…”
Section: Privacy-respecting Audit Log Analysismentioning
confidence: 99%
“…It was not until 1997 when Sobirey et al first suggested using pseudonyms for privacyenhanced intrusion detection of syslogs [24]. From 2000-2002, Biskup and Flegel extended this work in a series of papers [2], [3], [9].…”
Section: Related Workmentioning
confidence: 99%
“…warning, error, emergencies). 3 In addition to pattern-matching syslog entries for known attack signatures, other examples of suspicious activity found in system syslogs include critical events (system reboots), unsuccessful login attempts, storage overload when a log fills its allocated disk space, and cessation of logging messages (may indicate the logging process has either been deleted or a Trojan logging process installed).…”
Section: Introductionmentioning
confidence: 99%
“…Existing approaches for pseudonymization [13,12,20] have several drawbacks that pose a major threat to the privacy and confidentiality of stored patient data. Others have not yet been realized for the field of patient related privacy issues [2,5,6,7]. In this paper, we propose a new architecture for the pseudonymization of medical data that provides the following contributions:…”
Section: Introductionmentioning
confidence: 99%