<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
 xmlns:content="http://purl.org/rss/1.0/modules/content/"
 xmlns:wfw="http://wellformedweb.org/CommentAPI/"
 xmlns:dc="http://purl.org/dc/elements/1.1/"
 xmlns:atom="http://www.w3.org/2005/Atom"
 xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
 xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
 >

<channel>
 <title>7ASecurity Blog</title>
 <atom:link href="https://7asecurity.com/blog/feed/" rel="self" type="application/rss+xml" />
 <link>https://7asecurity.com/blog/</link>
 <description>7ASecurity Blog With Cybersecurity Tips and Tools</description>
 <lastBuildDate>Fri, 17 Jul 2026 07:39:13 +0000</lastBuildDate>
 <language>en-US</language>
 <sy:updatePeriod>
 hourly </sy:updatePeriod>
 <sy:updateFrequency>
 1 </sy:updateFrequency>


<image>
 <url>https://7asecurity.com/blog/contents/uploads/2019/06/favicon.ico</url>
 <title>7ASecurity Blog</title>
 <link>https://7asecurity.com/blog/</link>
 <width>32</width>
 <height>32</height>
</image> 
 <item>
  <title>How WPA3 Personal Transition Affects Internal Security Risk</title>
  <link>https://7asecurity.com/blog/2026/07/wpa3-transition-security-risk/</link>

  <dc:creator><![CDATA[Admin]]></dc:creator>
  <pubDate>Fri, 17 Jul 2026 07:39:10 +0000</pubDate>
    <category><![CDATA[Blog]]></category>
  <category><![CDATA[internal penetration testing]]></category>
  <category><![CDATA[IoT Security]]></category>
  <category><![CDATA[Network Security]]></category>
  <category><![CDATA[Network Segmentation]]></category>
  <category><![CDATA[offensive security]]></category>
  <category><![CDATA[Wi-Fi Security]]></category>
  <category><![CDATA[Wireless Security]]></category>
  <category><![CDATA[WPA2]]></category>
  <category><![CDATA[WPA3]]></category>
  <category><![CDATA[WPA3 Transition Mode]]></category>


     <description><![CDATA[<p>WPA3 Personal Transition Mode lets WPA2 and WPA3 devices connect to the same SSID during migration. It solves a real compatibility problem, but it keeps WPA2-era risk in play. Treat it as a time-limited bridge, not the target state. Document why it exists, isolate legacy devices, use strong passphrases, review PMF behaviour, and move trusted &#8230;</p>
<p>The post <a rel="nofollow" href="https://7asecurity.com/blog/2026/07/wpa3-transition-security-risk/">How WPA3 Personal Transition Affects Internal Security Risk</a> appeared first on <a rel="nofollow" href="https://7asecurity.com/blog/">7ASecurity Blog</a>.</p>
]]></description>



   </item>
  <item>
  <title>Don&#039;t Let jQuery 3.5.1 Vulnerabilities Panic Your Risk Team</title>
  <link>https://7asecurity.com/blog/2026/07/jquery-3-5-1-vulnerabilities/</link>

  <dc:creator><![CDATA[Admin]]></dc:creator>
  <pubDate>Fri, 17 Jul 2026 07:18:30 +0000</pubDate>
    <category><![CDATA[Blog]]></category>
  <category><![CDATA[Application Security]]></category>
  <category><![CDATA[Code Audit]]></category>
  <category><![CDATA[Cross-Site Scripting]]></category>
  <category><![CDATA[DOM Manipulation]]></category>
  <category><![CDATA[False Positives]]></category>
  <category><![CDATA[jQuery 3.5.1]]></category>
  <category><![CDATA[jQuery Vulnerabilities]]></category>
  <category><![CDATA[Vulnerability Scanners]]></category>
  <category><![CDATA[web application penetration testing]]></category>
  <category><![CDATA[XSS]]></category>


     <description><![CDATA[<p>Searches for jQuery 3.5.1 vulnerabilities often mix up older jQuery XSS issues with scanner noise. The major 2020 DOM manipulation flaws, CVE-2020-11022 and CVE-2020-11023, affected versions before 3.5.0. jQuery 3.5.1 followed 3.5.0 and kept those fixes while addressing a regression. Teams should still check loaded versions, old bundled copies, plugins, unsafe DOM insertion, and output &#8230;</p>
<p>The post <a rel="nofollow" href="https://7asecurity.com/blog/2026/07/jquery-3-5-1-vulnerabilities/">Don&#039;t Let jQuery 3.5.1 Vulnerabilities Panic Your Risk Team</a> appeared first on <a rel="nofollow" href="https://7asecurity.com/blog/">7ASecurity Blog</a>.</p>
]]></description>



   </item>
  <item>
  <title>BOFs Explained: Protecting Your Network From Stealthy Attacks</title>
  <link>https://7asecurity.com/blog/2026/07/bofs-explained-protecting-your-network-from-stealthy-attacks/</link>

  <dc:creator><![CDATA[Admin]]></dc:creator>
  <pubDate>Fri, 10 Jul 2026 09:58:41 +0000</pubDate>
    <category><![CDATA[Blog]]></category>
  <category><![CDATA[Beacon Object Files]]></category>
  <category><![CDATA[BOFs]]></category>
  <category><![CDATA[Cobalt Strike]]></category>
  <category><![CDATA[Endpoint Security]]></category>
  <category><![CDATA[offensive security]]></category>
  <category><![CDATA[Penetration Testing]]></category>
  <category><![CDATA[Post-Exploitation]]></category>
  <category><![CDATA[Red Teaming]]></category>
  <category><![CDATA[Security Testing]]></category>
  <category><![CDATA[Threat Detection]]></category>


     <description><![CDATA[<p>BOFs, or Beacon Object Files, are small compiled C object files that Cobalt Strike can load and run inside an existing Beacon process. They extend Beacon with focused post-exploitation tasks without creating a separate executable for each action. For defenders, BOFs matter because they change detection trade-offs. You need to look at behaviour, memory, API &#8230;</p>
<p>The post <a rel="nofollow" href="https://7asecurity.com/blog/2026/07/bofs-explained-protecting-your-network-from-stealthy-attacks/">BOFs Explained: Protecting Your Network From Stealthy Attacks</a> appeared first on <a rel="nofollow" href="https://7asecurity.com/blog/">7ASecurity Blog</a>.</p>
]]></description>



   </item>
  <item>
  <title>Don&#039;t Let a Misconfigured Cache DB Ruin Your Application</title>
  <link>https://7asecurity.com/blog/2026/07/misconfigured-cache-database/</link>

  <dc:creator><![CDATA[Admin]]></dc:creator>
  <pubDate>Fri, 10 Jul 2026 09:56:06 +0000</pubDate>
    <category><![CDATA[Blog]]></category>
  <category><![CDATA[Application Security]]></category>
  <category><![CDATA[Cache DB]]></category>
  <category><![CDATA[Cache Poisoning]]></category>
  <category><![CDATA[Cache Security]]></category>
  <category><![CDATA[cloud security]]></category>
  <category><![CDATA[In-Memory Store]]></category>
  <category><![CDATA[Memcached]]></category>
  <category><![CDATA[Penetration Testing]]></category>
  <category><![CDATA[Redis]]></category>
  <category><![CDATA[Web Cache Deception]]></category>


     <description><![CDATA[<p>A cache DB is a common search term for a cache layer, cache store, or in-memory data store. It keeps frequently used data close to the application to reduce latency and load. The security risk is simple: cached data still counts. Sessions, tokens, user records, API responses, authorisation state, browser cache files, and mobile cache &#8230;</p>
<p>The post <a rel="nofollow" href="https://7asecurity.com/blog/2026/07/misconfigured-cache-database/">Don&#039;t Let a Misconfigured Cache DB Ruin Your Application</a> appeared first on <a rel="nofollow" href="https://7asecurity.com/blog/">7ASecurity Blog</a>.</p>
]]></description>



   </item>
  <item>
  <title>Super Tanks lightweight threat model by 7ASecurity</title>
  <link>https://7asecurity.com/blog/2026/07/super-tanks-lightweight-threat-model-7asecurity/</link>

  <dc:creator><![CDATA[Admin]]></dc:creator>
  <pubDate>Fri, 03 Jul 2026 11:23:34 +0000</pubDate>
    <category><![CDATA[Blog]]></category>
  <category><![CDATA[7ASecurity]]></category>
  <category><![CDATA[agentic AI]]></category>
  <category><![CDATA[AI security]]></category>
  <category><![CDATA[AI-agent governance]]></category>
  <category><![CDATA[auditability]]></category>
  <category><![CDATA[autonomous agents]]></category>
  <category><![CDATA[code quarantine]]></category>
  <category><![CDATA[defense in depth]]></category>
  <category><![CDATA[gateway enforcement]]></category>
  <category><![CDATA[hardening]]></category>
  <category><![CDATA[lightweight threat model]]></category>
  <category><![CDATA[Open Source Security]]></category>
  <category><![CDATA[OWASP Agentic Top 10]]></category>
  <category><![CDATA[SAFE_MODE]]></category>
  <category><![CDATA[STRIDE]]></category>
  <category><![CDATA[Super Tanks]]></category>
  <category><![CDATA[Threat Model]]></category>


     <description><![CDATA[<p>7ASecurity publishes a lightweight threat model for Super Tanks, highlighting its defense-in-depth AI-agent governance architecture and practical hardening guidance for safer autonomous-agent operations.</p>
<p>The post <a rel="nofollow" href="https://7asecurity.com/blog/2026/07/super-tanks-lightweight-threat-model-7asecurity/">Super Tanks lightweight threat model by 7ASecurity</a> appeared first on <a rel="nofollow" href="https://7asecurity.com/blog/">7ASecurity Blog</a>.</p>
]]></description>



   </item>
  <item>
  <title>P2PE vs E2EE: Stop Guessing and Start Securing Your App</title>
  <link>https://7asecurity.com/blog/2026/07/p2pe-vs-e2ee-encryption-comparison/</link>

  <dc:creator><![CDATA[Admin]]></dc:creator>
  <pubDate>Fri, 03 Jul 2026 07:53:16 +0000</pubDate>
    <category><![CDATA[Blog]]></category>
  <category><![CDATA[Application Security]]></category>
  <category><![CDATA[Cryptography]]></category>
  <category><![CDATA[data protection]]></category>
  <category><![CDATA[E2EE]]></category>
  <category><![CDATA[end-to-end encryption]]></category>
  <category><![CDATA[P2PE]]></category>
  <category><![CDATA[Payment Security]]></category>
  <category><![CDATA[PCI Compliance]]></category>
  <category><![CDATA[Penetration Testing]]></category>
  <category><![CDATA[Point-to-Point Encryption]]></category>


     <description><![CDATA[<p>P2PE vs E2EE compares two different encryption models. P2PE protects payment card data from the point of interaction to a secure decryption environment. E2EE protects content between communicating endpoints so intermediaries mustn’t read the plaintext. One isn’t universally better. The right model depends on the data flow, endpoint trust, key handling, compliance context, and where &#8230;</p>
<p>The post <a rel="nofollow" href="https://7asecurity.com/blog/2026/07/p2pe-vs-e2ee-encryption-comparison/">P2PE vs E2EE: Stop Guessing and Start Securing Your App</a> appeared first on <a rel="nofollow" href="https://7asecurity.com/blog/">7ASecurity Blog</a>.</p>
]]></description>



   </item>
  <item>
  <title>PCI Vulnerability Management: Find, Fix, Verify Cyber Risks</title>
  <link>https://7asecurity.com/blog/2026/06/pci-vulnerability-management-find-fix-verify-cyber-risks/</link>

  <dc:creator><![CDATA[Admin]]></dc:creator>
  <pubDate>Fri, 26 Jun 2026 11:54:43 +0000</pubDate>
    <category><![CDATA[Blog]]></category>
  <category><![CDATA[ASV Scans]]></category>
  <category><![CDATA[Code Audit]]></category>
  <category><![CDATA[Compliance Security]]></category>
  <category><![CDATA[information security]]></category>
  <category><![CDATA[Payment Security]]></category>
  <category><![CDATA[PCI DSS]]></category>
  <category><![CDATA[PCI Vulnerability Management]]></category>
  <category><![CDATA[Penetration Testing]]></category>
  <category><![CDATA[Security Remediation]]></category>
  <category><![CDATA[vulnerability management]]></category>


     <description><![CDATA[<p>PCI vulnerability management is the process of finding, prioritising, fixing, and verifying weaknesses that affect payment environments. It supports PCI DSS v4.0.1, but it requires more than a scan schedule. Teams need asset scope, recurring scans, penetration testing, remediation ownership, and fix verification. Patching is only part of the answer. Teams need proof that the &#8230;</p>
<p>The post <a rel="nofollow" href="https://7asecurity.com/blog/2026/06/pci-vulnerability-management-find-fix-verify-cyber-risks/">PCI Vulnerability Management: Find, Fix, Verify Cyber Risks</a> appeared first on <a rel="nofollow" href="https://7asecurity.com/blog/">7ASecurity Blog</a>.</p>
]]></description>



   </item>
  <item>
  <title>KEDA audit by 7ASecurity</title>
  <link>https://7asecurity.com/blog/2026/06/keda-security-audit-7asecurity/</link>

  <dc:creator><![CDATA[Admin]]></dc:creator>
  <pubDate>Fri, 26 Jun 2026 10:22:34 +0000</pubDate>
    <category><![CDATA[Blog]]></category>
  <category><![CDATA[admission webhook]]></category>
  <category><![CDATA[authentication]]></category>
  <category><![CDATA[Cloud Native Computing Foundation]]></category>
  <category><![CDATA[CNCF]]></category>
  <category><![CDATA[code review]]></category>
  <category><![CDATA[event-driven autoscaling]]></category>
  <category><![CDATA[hardening]]></category>
  <category><![CDATA[KEDA]]></category>
  <category><![CDATA[Kubernetes]]></category>
  <category><![CDATA[Kubernetes autoscaling]]></category>
  <category><![CDATA[Kubernetes Security]]></category>
  <category><![CDATA[metrics server]]></category>
  <category><![CDATA[open source]]></category>
  <category><![CDATA[OSTIF]]></category>
  <category><![CDATA[RBAC]]></category>
  <category><![CDATA[secret handling]]></category>
  <category><![CDATA[Security Audit]]></category>
  <category><![CDATA[SLSA]]></category>
  <category><![CDATA[supply chain security]]></category>
  <category><![CDATA[whitebox pentest]]></category>


     <description><![CDATA[<p>7ASecurity shares results of a KEDA security audit: 15 security-impact findings (4 high), 5 hardening recommendations, SLSA supply-chain review, and future security guidance.</p>
<p>The post <a rel="nofollow" href="https://7asecurity.com/blog/2026/06/keda-security-audit-7asecurity/">KEDA audit by 7ASecurity</a> appeared first on <a rel="nofollow" href="https://7asecurity.com/blog/">7ASecurity Blog</a>.</p>
]]></description>



   </item>
  <item>
  <title>The Security Guide To WebDAV Servers And Exposed Methods</title>
  <link>https://7asecurity.com/blog/2026/06/webdav-security-guide/</link>

  <dc:creator><![CDATA[Admin]]></dc:creator>
  <pubDate>Fri, 19 Jun 2026 08:42:05 +0000</pubDate>
    <category><![CDATA[Blog]]></category>
  <category><![CDATA[Access Control]]></category>
  <category><![CDATA[Attack Surface]]></category>
  <category><![CDATA[external penetration testing]]></category>
  <category><![CDATA[HTTP Methods]]></category>
  <category><![CDATA[information security]]></category>
  <category><![CDATA[Network Security]]></category>
  <category><![CDATA[Threat Detection]]></category>
  <category><![CDATA[web application penetration testing]]></category>
  <category><![CDATA[Web Distributed Authoring and Versioning]]></category>
  <category><![CDATA[WebDAV server]]></category>


     <description><![CDATA[<p>What Is a WebDAV Server? How It Works, Use Cases, and Security Risks A WebDAV server lets users access and manage files over HTTP or HTTPS. It supports remote workflows such as document editing, collaboration, and legacy publishing. Now, WebDAV isn’t automatically unsafe. It becomes a risk when exposed methods, weak authentication, broad permissions, or &#8230;</p>
<p>The post <a rel="nofollow" href="https://7asecurity.com/blog/2026/06/webdav-security-guide/">The Security Guide To WebDAV Servers And Exposed Methods</a> appeared first on <a rel="nofollow" href="https://7asecurity.com/blog/">7ASecurity Blog</a>.</p>
]]></description>



   </item>
  <item>
  <title>Iframe XSS: postMessage, CSP, Sandboxing, &#038; Clickjacking</title>
  <link>https://7asecurity.com/blog/2026/06/iframe-xss-security/</link>

  <dc:creator><![CDATA[Admin]]></dc:creator>
  <pubDate>Fri, 19 Jun 2026 08:18:21 +0000</pubDate>
    <category><![CDATA[Blog]]></category>
  <category><![CDATA[Application Security]]></category>
  <category><![CDATA[Browser Security]]></category>
  <category><![CDATA[Clickjacking]]></category>
  <category><![CDATA[Code Audit]]></category>
  <category><![CDATA[Content Security Policy]]></category>
  <category><![CDATA[DOM XSS]]></category>
  <category><![CDATA[Iframe XSS]]></category>
  <category><![CDATA[postMessage Security]]></category>
  <category><![CDATA[Sandboxing]]></category>
  <category><![CDATA[web application penetration testing]]></category>


     <description><![CDATA[<p>Iframe XSS Explained: Trust Boundaries, Messages, and Embedded Content Iframe XSS isn’t one single bug class. It can refer to XSS inside framed content, unsafe srcdoc, user-controlled iframe sources, weak postMessage handling, over-trusted widgets, or parent pages that trust child frames too much. The fix starts with trust boundaries: control iframe sources, sandbox untrusted content, &#8230;</p>
<p>The post <a rel="nofollow" href="https://7asecurity.com/blog/2026/06/iframe-xss-security/">Iframe XSS: postMessage, CSP, Sandboxing, &#038; Clickjacking</a> appeared first on <a rel="nofollow" href="https://7asecurity.com/blog/">7ASecurity Blog</a>.</p>
]]></description>



   </item>
 </channel>
</rss>
