<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[For users with public facing services: How does the current explosion of AI-discovered vulnerabilities affect your threat model and willingness to be public facing?]]></title><description><![CDATA[<p dir="auto">PHP, TLS, etc.. We appear to be facing a tsunami of vulnerabilities being discovered in record time. Further, the window to act on these vulnerabilities has basically closed to zero; hackers' tools now automatically fold the very latest vulnerabilities into their botnets within minutes/hours of discovery. I have always been extremely reluctant to expose any of my services - even with the latest and greatest security tools. My choice to stay totally within the confines of tailscale seems vindicated given this week's news. How are you all taking this?</p>
<p dir="auto"><a href="https://pwn.watch/" rel="nofollow ugc">https://pwn.watch/</a></p>
]]></description><link>https://forum.ieu.app/topic/2f653467-3b9c-46d8-895c-1d0435a6ac2b/for-users-with-public-facing-services-how-does-the-current-explosion-of-ai-discovered-vulnerabilities-affect-your-threat-model-and-willingness-to-be-public-facing</link><generator>RSS for Node</generator><lastBuildDate>Thu, 22 Oct 2026 23:10:58 GMT</lastBuildDate><atom:link href="https://forum.ieu.app/topic/2f653467-3b9c-46d8-895c-1d0435a6ac2b.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 22 Oct 2026 19:44:03 GMT</pubDate><ttl>60</ttl></channel></rss>