2020
DOI: 10.1016/j.procs.2020.07.025
|View full text |Cite
|
Sign up to set email alerts
|

A review of native container security for running applications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
14
0

Year Published

2021
2021
2023
2023

Publication Types

Select...
7
1

Relationship

0
8

Authors

Journals

citations
Cited by 22 publications
(14 citation statements)
references
References 11 publications
0
14
0
Order By: Relevance
“…With the help of a risk library, there are many methods proposed to deal with image-security issues on container-based clouds. The most popular methods take uses of Linux features (i.e., CGroup and Capabilities) to isolate the hardware resource, and to divide the privileges, respectively [ 21 ]. They provide the general security protection of the storage and networking for containers.…”
Section: Related Workmentioning
confidence: 99%
“…With the help of a risk library, there are many methods proposed to deal with image-security issues on container-based clouds. The most popular methods take uses of Linux features (i.e., CGroup and Capabilities) to isolate the hardware resource, and to divide the privileges, respectively [ 21 ]. They provide the general security protection of the storage and networking for containers.…”
Section: Related Workmentioning
confidence: 99%
“…Software based mechanism are based on either Linux Security Features (LSFs) or Linux Security Modules (LSMs). These Linux kernel features include the solutions using the namespaces, Control Groups (CGroups), Capabilities Dropping and Computation Mode (Seccomp) [61], [63]. Hardware-based protection can be…”
Section: ) Security Solutions For Virtualized Edgementioning
confidence: 99%
“…Wist et al [166] scanned 2,500 Docker Hub images, mapped their vulnerabilities using the Common Vulnerability Scoring System (CVSS), and compared the vulnerabilities across the types of images, the types of scripting languages, and packages. In another research, Flauzac et al [63] reviewed the native containers security by conducting a static comparison of 6 container runtime solutions, namely LXC (Linux Containers), LXD (an open-source container management extension for LXC), Singularity, Docker (runc), Kata-containers (kata-runtime) and gVisor(runsc), in terms of their abilities to isolate system resources such as storage, network, processor, and memory. However, this is carried out in the container's default and standalone state and therefore does not reflect a real operating environment that is used by a container.…”
Section: Vulnerability Analysismentioning
confidence: 99%
“…Enhancement of container engine security In this paper, we use Docker as the representative container engine for security survey as it is the most popular and pervasively used by enterprises and businesses. However, a couple of reports state that an alternative container engine called Kata 13 container which is developed by IBM and Hyper.sh can offer better security isolation while maintaining efficiency and performance and it has a strong reference customer in the form of Baidu AI Cloud [97], [63], [94]. Therefore, another direction of study is a comprehensive comparison of the security and performance between Kata container and Docker container and investigate the possibility of a Docker substitute or areas for Docker's security enhancements.…”
Section: Future Research Directionsmentioning
confidence: 99%
See 1 more Smart Citation