Proceedings 2019 Network and Distributed System Security Symposium 2019
DOI: 10.14722/ndss.2019.23349
|View full text |Cite
|
Sign up to set email alerts
|

NoDoze: Combatting Threat Alert Fatigue with Automated Provenance Triage

Abstract: Large enterprises are increasingly relying on threat detection softwares (e.g., Intrusion Detection Systems) to allow them to spot suspicious activities. These softwares generate alerts which must be investigated by cyber analysts to figure out if they are true attacks. Unfortunately, in practice, there are more alerts than cyber analysts can properly investigate. This leads to a "threat alert fatigue" or information overload problem where cyber analysts miss true attack alerts in the noise of false alarms.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
120
0

Year Published

2019
2019
2021
2021

Publication Types

Select...
5
2

Relationship

2
5

Authors

Journals

citations
Cited by 162 publications
(151 citation statements)
references
References 35 publications
(50 reference statements)
0
120
0
Order By: Relevance
“…It connects causally-related events in the graph, even when those events are separated by a long time period. Thus, even though systems under APT attack usually behave similarly to unattacked systems, the richer contextual information in provenance allows for better separation of benign and malicious events [55].…”
Section: Introductionmentioning
confidence: 99%
“…It connects causally-related events in the graph, even when those events are separated by a long time period. Thus, even though systems under APT attack usually behave similarly to unattacked systems, the richer contextual information in provenance allows for better separation of benign and malicious events [55].…”
Section: Introductionmentioning
confidence: 99%
“…We make the following assumptions about our system. Similar with existing provenance-based systems [56], [73], [30], [74], [89], [55], we assume the underlying OS and the provenance tracker are in our trusted computing base (TCB). We assume the attacker cannot manipulate or delete the provenance record, i.e., log integrity is maintained at all time.…”
Section: Threat Model and Assumptionsmentioning
confidence: 99%
“…System Entity and System Event. Similar with [56], [39], [43], we consider the following three types of system entities: processes, files and network connections (i.e., sockets). A system event e = (src, dst, rel, time) models the interaction between two system entities, where src is the source entity, dst is the destination entity, rel is the relation between them (e.g., a process writes a file), and time is the timestamp when the event happened.…”
Section: A Definitionsmentioning
confidence: 99%
See 2 more Smart Citations