2019 IEEE International Conference on Service-Oriented System Engineering (SOSE) 2019
DOI: 10.1109/sose.2019.00032
|View full text |Cite
|
Sign up to set email alerts
|

Container-Based Module Isolation for Cloud Services

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
5
0

Year Published

2019
2019
2022
2022

Publication Types

Select...
5
3
1

Relationship

0
9

Authors

Journals

citations
Cited by 13 publications
(5 citation statements)
references
References 21 publications
0
5
0
Order By: Relevance
“…The access control policies are composed of user ID, container ID, and container based image layer directory. Finally, user access control handling rejects unauthorized access towards the container image layer by examining the I/O of the user's file [20]. The event over the container image accessing is performed using the container platform, and another kind of access is rejected.…”
Section: Security Threat Towards the Container Imagementioning
confidence: 99%
“…The access control policies are composed of user ID, container ID, and container based image layer directory. Finally, user access control handling rejects unauthorized access towards the container image layer by examining the I/O of the user's file [20]. The event over the container image accessing is performed using the container platform, and another kind of access is rejected.…”
Section: Security Threat Towards the Container Imagementioning
confidence: 99%
“…As is well known, the container engine protects the execution environment of the container. A container engine uses namespaces and cgroups to individually apply environmental variables, resources, and process management for application during a container operation to ensure an independent operating environment [26].…”
Section: Security Environment Analysis Of Container Platform a mentioning
confidence: 99%
“…Despite its advantages, container-based virtualization possesses a major drawback: if a container image (We used image, container image, and Docker image inter-changeably in this article) contains security vulnerabilities, all mircoservice components related to this image are in a high risk state [ 4 ]. Malicious parties now frequently exploit vulnerable images to gain control of the entire microservice architecture [ 5 ].…”
Section: Introductionmentioning
confidence: 99%