<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Container vulnerabilities and attack path ? in Prisma Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/prisma-cloud-discussions/container-vulnerabilities-and-attack-path/m-p/554197#M1007</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;when using attack path policies involving vulnerabilities such as&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"Azure Virtual Machine publicly exposed with critical or high vulnerabilities and Run command execution permissions"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"Azure Virtual Machine publicly exposed with critical or high vulnerabilities and data destruction permissions"&lt;/P&gt;
&lt;P&gt;"AWS EC2 instance publicly exposed with critical or high vulnerabilities and privilege escalation permission via PassRole &amp;amp; Glue permissions"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Does Prisma takes into account containers vulnerabilities as well ?&lt;/P&gt;
&lt;P&gt;The rational behind is: with most payloads being containerized, vulnerabilities to be used for initial access will likely be within a container, on the other hand lateral movement may require breaking the containment which is likely detectable from the host.&lt;/P&gt;</description>
    <pubDate>Thu, 17 Aug 2023 16:56:33 GMT</pubDate>
    <dc:creator>JVANDEWOESTYNE</dc:creator>
    <dc:date>2023-08-17T16:56:33Z</dc:date>
    <item>
      <title>Container vulnerabilities and attack path ?</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-cloud-discussions/container-vulnerabilities-and-attack-path/m-p/554197#M1007</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;when using attack path policies involving vulnerabilities such as&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"Azure Virtual Machine publicly exposed with critical or high vulnerabilities and Run command execution permissions"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"Azure Virtual Machine publicly exposed with critical or high vulnerabilities and data destruction permissions"&lt;/P&gt;
&lt;P&gt;"AWS EC2 instance publicly exposed with critical or high vulnerabilities and privilege escalation permission via PassRole &amp;amp; Glue permissions"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Does Prisma takes into account containers vulnerabilities as well ?&lt;/P&gt;
&lt;P&gt;The rational behind is: with most payloads being containerized, vulnerabilities to be used for initial access will likely be within a container, on the other hand lateral movement may require breaking the containment which is likely detectable from the host.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Aug 2023 16:56:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-cloud-discussions/container-vulnerabilities-and-attack-path/m-p/554197#M1007</guid>
      <dc:creator>JVANDEWOESTYNE</dc:creator>
      <dc:date>2023-08-17T16:56:33Z</dc:date>
    </item>
    <item>
      <title>Re: Container vulnerabilities and attack path ?</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-cloud-discussions/container-vulnerabilities-and-attack-path/m-p/554231#M1008</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for posting the question. The container vulnerabilities are currently not included in attack path policies but they are in the roadmap.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Yash Boravelli&lt;/P&gt;</description>
      <pubDate>Thu, 17 Aug 2023 22:59:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-cloud-discussions/container-vulnerabilities-and-attack-path/m-p/554231#M1008</guid>
      <dc:creator>yboravelli</dc:creator>
      <dc:date>2023-08-17T22:59:16Z</dc:date>
    </item>
  </channel>
</rss>

