<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Att&amp;ck on microsegment.io</title>
    <link>https://microsegment.io/tags/attck/</link>
    <description>Recent content in Att&amp;ck on microsegment.io</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 14 Apr 2020 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://microsegment.io/tags/attck/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Thoughts on the Attack matrix for Kubernetes</title>
      <link>https://microsegment.io/2020/04/14/thoughts-on-the-attack-matrix-for-kubernetes/</link>
      <pubDate>Tue, 14 Apr 2020 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/2020/04/14/thoughts-on-the-attack-matrix-for-kubernetes/</guid>
      <description>&lt;h1 id=&#34;introduction&#34;&gt;Introduction&lt;/h1&gt;&#xA;&lt;p&gt;In a recent blog post Yossi Weizman talks about the &lt;a href=&#34;https://www.microsoft.com/security/blog/2020/04/02/attack-matrix-kubernetes/&#34;&gt;Attack matrix for&#xA;Kubernetes&lt;/a&gt;&#xA;and i had a couple of thoughts about it. As Yossi rightly says, Kubernetes is&#xA;becoming a vital part in the compute stack of many companies. What i hear in my&#xA;network and during sessions with IT security teams is that they face new&#xA;challenges with Kubernetes-based orchestration platforms. The container&#xA;platforms are also perceived like a black box for traditional networking and IT&#xA;security folks, so it makes sense to understand the security risks that are&#xA;inherent to those platforms first.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
