<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DevSecOps on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/devsecops/</link><description>Recent content in DevSecOps on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 22 Jun 2023 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/devsecops/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker and Containers (7): Security — Running Containers Without Giving Away the Keys</title><link>https://www.chenk.top/en/docker-containers/07-security-and-best-practices/</link><pubDate>Thu, 22 Jun 2023 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/docker-containers/07-security-and-best-practices/</guid><description>&lt;p>Docker&amp;rsquo;s default configuration prioritizes convenience over security. Containers run as root, have access to a broad set of Linux capabilities, and can write to their entire filesystem. This is fine for development but dangerous for production. A container escape vulnerability in a root-privileged container means an attacker can take over the host. Let&amp;rsquo;s fix that.&lt;/p>
&lt;hr>
&lt;h2 id="the-threat-model" class="heading-anchor">The Threat Model&lt;a href="#the-threat-model" class="heading-link" aria-label="Permalink to this section" title="Copy link to this section">#&lt;/a>
&lt;/h2>&lt;p>Before securing your setup, understand what you&amp;rsquo;re defending against:&lt;/p></description></item></channel></rss>