<?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 Re: F5 Security Breach in Threats</title>
    <link>https://community.isc2.org/t5/Threats/F5-Security-Breach/m-p/85021#M1724</link>
    <description>&lt;P&gt;What seems to have occurred is that someone got into F5's internal documents, and the worry is they can use that info to craft attacks against F5 devices. The fact that F5 has released mitigating patches tells me that somewhere in those documents may be things like API keys or other configuration-type info that could lead to&amp;nbsp; elevated access to the devices. However, the between-the-lines seems to say the stolen information by itself shouldn't cause a compromise.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Maybe that is part of the shoulder-shrug to all this is that there is not an actual attack (yet) tied to this breach.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 24 Oct 2025 13:53:43 GMT</pubDate>
    <dc:creator>JoePete</dc:creator>
    <dc:date>2025-10-24T13:53:43Z</dc:date>
    <item>
      <title>F5 Security Breach</title>
      <link>https://community.isc2.org/t5/Threats/F5-Security-Breach/m-p/84997#M1723</link>
      <description>&lt;P&gt;I'm surprised I've not seen this mentioned on here at all, so if you weren't aware, F5 announced it had suffered a major security breach last week:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://my.f5.com/manage/s/article/K000154696" target="_blank" rel="noopener"&gt;https://my.f5.com/manage/s/article/K000154696&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Their CEO posted this on LinkedIn a little while ago:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="image" style="width: 546px;"&gt;&lt;img src="https://community.isc2.org/t5/image/serverpage/image-id/10275iBB981445CCF6BECD/image-size/large?v=v2&amp;amp;px=999" role="button" title="image" alt="image" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Which in turn includes a link to a blog post from their CISO:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.f5.com/company/blog/lessons-we-are-learning-from-our-security-incident" target="_blank" rel="noopener"&gt;https://www.f5.com/company/blog/lessons-we-are-learning-from-our-security-incident&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here's CISA's emergency directive on the subject:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cisa.gov/news-events/directives/ed-26-01-mitigate-vulnerabilities-f5-devices" target="_blank" rel="noopener"&gt;https://www.cisa.gov/news-events/directives/ed-26-01-mitigate-vulnerabilities-f5-devices&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are folks just not using F5 anymore, so not really interested in this?&lt;/P&gt;</description>
      <pubDate>Thu, 23 Oct 2025 15:59:02 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Threats/F5-Security-Breach/m-p/84997#M1723</guid>
      <dc:creator>AlecTrevelyan</dc:creator>
      <dc:date>2025-10-23T15:59:02Z</dc:date>
    </item>
    <item>
      <title>Re: F5 Security Breach</title>
      <link>https://community.isc2.org/t5/Threats/F5-Security-Breach/m-p/85021#M1724</link>
      <description>&lt;P&gt;What seems to have occurred is that someone got into F5's internal documents, and the worry is they can use that info to craft attacks against F5 devices. The fact that F5 has released mitigating patches tells me that somewhere in those documents may be things like API keys or other configuration-type info that could lead to&amp;nbsp; elevated access to the devices. However, the between-the-lines seems to say the stolen information by itself shouldn't cause a compromise.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Maybe that is part of the shoulder-shrug to all this is that there is not an actual attack (yet) tied to this breach.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Oct 2025 13:53:43 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Threats/F5-Security-Breach/m-p/85021#M1724</guid>
      <dc:creator>JoePete</dc:creator>
      <dc:date>2025-10-24T13:53:43Z</dc:date>
    </item>
  </channel>
</rss>

