<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://elvis.hcw.ac.at/wiki/index.php?action=history&amp;feed=atom&amp;title=Docker_Security</id>
	<title>Docker Security - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://elvis.hcw.ac.at/wiki/index.php?action=history&amp;feed=atom&amp;title=Docker_Security"/>
	<link rel="alternate" type="text/html" href="https://elvis.hcw.ac.at/wiki/index.php?title=Docker_Security&amp;action=history"/>
	<updated>2026-09-10T21:00:50Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.41.5</generator>
	<entry>
		<id>https://elvis.hcw.ac.at/wiki/index.php?title=Docker_Security&amp;diff=13686&amp;oldid=prev</id>
		<title>KHnidek: Created page with &quot;&lt;span id=&quot;docker-security&quot;&gt;&lt;/span&gt; = Docker Security =  &amp;quot;It works on my computer.&amp;quot; - A statement that is becoming less important with the advent and introduction of containerisation.  This is one of the main reasons for the massive upswing in container technologies   &lt;span id=&quot;virtualization-techniques&quot;&gt;&lt;/span&gt; == 1. Virtualization Techniques ==  * &#039;&#039;&#039;Container-Based&#039;&#039;&#039;: Efficient, lightweight solutions using OS isolation. * &#039;&#039;&#039;Hypervisor-Based&#039;&#039;&#039;: Strong isola...&quot;</title>
		<link rel="alternate" type="text/html" href="https://elvis.hcw.ac.at/wiki/index.php?title=Docker_Security&amp;diff=13686&amp;oldid=prev"/>
		<updated>2024-01-07T09:43:15Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;&amp;lt;span id=&amp;quot;docker-security&amp;quot;&amp;gt;&amp;lt;/span&amp;gt; = Docker Security =  &amp;quot;It works on my computer.&amp;quot; - A statement that is becoming less important with the advent and introduction of containerisation.  This is one of the main reasons for the massive upswing in container technologies   &amp;lt;span id=&amp;quot;virtualization-techniques&amp;quot;&amp;gt;&amp;lt;/span&amp;gt; == 1. Virtualization Techniques ==  * &amp;#039;&amp;#039;&amp;#039;Container-Based&amp;#039;&amp;#039;&amp;#039;: Efficient, lightweight solutions using OS isolation. * &amp;#039;&amp;#039;&amp;#039;Hypervisor-Based&amp;#039;&amp;#039;&amp;#039;: Strong isola...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;&amp;lt;span id=&amp;quot;docker-security&amp;quot;&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
= Docker Security =&lt;br /&gt;
&lt;br /&gt;
&amp;amp;quot;It works on my computer.&amp;amp;quot; - A statement that is becoming less important with the advent and introduction of containerisation. &lt;br /&gt;
This is one of the main reasons for the massive upswing in container technologies&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span id=&amp;quot;virtualization-techniques&amp;quot;&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
== 1. Virtualization Techniques ==&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Container-Based&amp;#039;&amp;#039;&amp;#039;: Efficient, lightweight solutions using OS isolation.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Hypervisor-Based&amp;#039;&amp;#039;&amp;#039;: Strong isolation with VMs, but more resource-intensive.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span id=&amp;quot;docker-overview&amp;quot;&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
== 2. Docker Overview ==&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Client-Server Model&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
** &amp;#039;&amp;#039;&amp;#039;Docker daemon&amp;#039;&amp;#039;&amp;#039; (&amp;lt;code&amp;gt;dockerd&amp;lt;/code&amp;gt;): Manages containers, images, networks.&lt;br /&gt;
** &amp;#039;&amp;#039;&amp;#039;Docker client&amp;#039;&amp;#039;&amp;#039; (&amp;lt;code&amp;gt;docker run/pull&amp;lt;/code&amp;gt;): User interface for Docker.&lt;br /&gt;
** &amp;#039;&amp;#039;&amp;#039;Docker registries&amp;#039;&amp;#039;&amp;#039; (&amp;lt;code&amp;gt;docker push/pull&amp;lt;/code&amp;gt;): Repositories for Docker images.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span id=&amp;quot;docker-commands-security-implications&amp;quot;&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
== 3. Docker Commands &amp;amp;amp; Security Implications ==&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;User Group Modification&amp;#039;&amp;#039;&amp;#039;: &amp;lt;code&amp;gt;sudo usermod -aG docker [user]&amp;lt;/code&amp;gt;&lt;br /&gt;
** Grants Docker group access.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Mounting Host Filesystem&amp;#039;&amp;#039;&amp;#039;: &amp;lt;code&amp;gt;docker run -v /:/privesc -it [image] /bin/bash&amp;lt;/code&amp;gt;&lt;br /&gt;
** Poses a security risk.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Altering Sudoers&amp;#039;&amp;#039;&amp;#039;: &amp;lt;code&amp;gt;echo “[user] ALL=(ALL) NOPASSWD: ALL” &amp;amp;gt;&amp;amp;gt; /privesc/etc/sudoers&amp;lt;/code&amp;gt;&lt;br /&gt;
** Affects host’s security.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span id=&amp;quot;security-threats-and-practices&amp;quot;&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
== 4. Security Threats and Practices ==&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Basic Commands for Monitoring and Cleanup&amp;#039;&amp;#039;&amp;#039;:&lt;br /&gt;
** List all containers: &amp;lt;code&amp;gt;docker ps -a&amp;lt;/code&amp;gt;&lt;br /&gt;
** Inspect a container: &amp;lt;code&amp;gt;docker inspect [id]&amp;lt;/code&amp;gt;&lt;br /&gt;
** Remove a container: &amp;lt;code&amp;gt;docker rm [id]&amp;lt;/code&amp;gt;&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Prevention Techniques&amp;#039;&amp;#039;&amp;#039;:&lt;br /&gt;
** Run as non-root: &amp;lt;code&amp;gt;docker run --name [app] -u [user]&amp;lt;/code&amp;gt;&lt;br /&gt;
** Read-only volumes: &amp;lt;code&amp;gt;docker run -v /:/privesc:ro -it debian /bin/bash&amp;lt;/code&amp;gt;&lt;br /&gt;
** Limit resources: &amp;lt;code&amp;gt;docker run --cpus=0.5 --memory=128m&amp;lt;/code&amp;gt;&lt;br /&gt;
** Network segregation: &amp;lt;code&amp;gt;docker network create, docker network rm&amp;lt;/code&amp;gt;&lt;br /&gt;
** Secure Dockerfile practices: Audit with &amp;lt;code&amp;gt;grep&amp;lt;/code&amp;gt;.&lt;br /&gt;
** Image inspection: &amp;lt;code&amp;gt;docker image inspect&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;docker image history&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span id=&amp;quot;references&amp;quot;&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
* Bui, Thanh. “Analysis of Docker Security.” &amp;#039;&amp;#039;ArXiv&amp;#039;&amp;#039;, 2015. [https://api.semanticscholar.org/CorpusID:14908430 Link]&lt;br /&gt;
* Polop, Carlos. “Docker Breakout/Privilege Escalation.” [https://book.hacktricks.xyz/linux-hardening/privilege-escalation/docker-security/docker-breakout-privilege-escalation Link]. Accessed 19-10-2023.&lt;br /&gt;
* Docker Inc. “Docker Overview | Docker Docs.” [https://docs.docker.com/get-started/overview/ Link]. Accessed 7-09-2023.&lt;br /&gt;
* Segura, Thomas. “Docker Security Best Practices.” [https://blog.gitguardian.com/how-to-improve-your-docker-containers-security-cheat-sheet/ Link]. Accessed 3-10-2023.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Documentation]]&lt;/div&gt;</summary>
		<author><name>KHnidek</name></author>
	</entry>
</feed>