2020 IEEE International Conference on Big Data (Big Data) 2020
DOI: 10.1109/bigdata50022.2020.9377815
|View full text |Cite
|
Sign up to set email alerts
|

Highly-Scalable Container Integrity Monitoring for Large-Scale Kubernetes Cluster

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2021
2021
2023
2023

Publication Types

Select...
4
3

Relationship

2
5

Authors

Journals

citations
Cited by 7 publications
(2 citation statements)
references
References 8 publications
0
2
0
Order By: Relevance
“…In file integrity protection, monitoring system changes is a major approach, and is used to detect changes and determine whether they are anomalous. Jin et al [27] and Zlatkovski et al [33] proposed an approach to detect mutations on the basis of rules and Kitahara et al [28] proposed a mechanism to filter out default behavioral events in containers and detect mutation events that are anomalous. Commercial products for file integrity protection also exist, for instance, Solarwinds's Security Event Manager [21], Qualys's File Integrity Monitoring [23], Trustwave's Endpoint Protection [22], and Tripwire [24].…”
Section: Related Workmentioning
confidence: 99%
“…In file integrity protection, monitoring system changes is a major approach, and is used to detect changes and determine whether they are anomalous. Jin et al [27] and Zlatkovski et al [33] proposed an approach to detect mutations on the basis of rules and Kitahara et al [28] proposed a mechanism to filter out default behavioral events in containers and detect mutation events that are anomalous. Commercial products for file integrity protection also exist, for instance, Solarwinds's Security Event Manager [21], Qualys's File Integrity Monitoring [23], Trustwave's Endpoint Protection [22], and Tripwire [24].…”
Section: Related Workmentioning
confidence: 99%
“…In this paper, we propose a novel approach for highly scalable container integrity monitoring using system call monitoring [8]. We do not rely on any predefined allowlist configuration, i.e., no prior knowledge about container image for creating container.…”
Section: Introductionmentioning
confidence: 99%