<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Articles | B-52</title>
    <link>https://b52security.com/blog/</link>
    <description>Writing on what autonomous penetration testing covers, how it is bounded, and what it produces.</description>
    <language>en-IN</language>
    <atom:link href="https://b52security.com/rss.xml" rel="self" type="application/rss+xml" />
    <lastBuildDate>Mon, 16 Nov 2026 05:44:52 GMT</lastBuildDate>
    <item>
      <title>AI Pentest Benchmark: B-52 Solves All 104 Autonomously</title>
      <link>https://b52security.com/blog/ai-pentest-benchmark-104-of-104/</link>
      <guid isPermaLink="true">https://b52security.com/blog/ai-pentest-benchmark-104-of-104/</guid>
      <pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate>
      <author>Yash K</author>
      <description>From a target URL to a captured flag: B-52 completed all 104 XBOW validation challenges without human steering. Three findings show how the attack paths unfolded.</description>
    </item>
    <item>
      <title>A JWT the Server Never Verified: B-52 on XBEN-027</title>
      <link>https://b52security.com/blog/xben-027-jwt-signature-bypass/</link>
      <guid isPermaLink="true">https://b52security.com/blog/xben-027-jwt-signature-bypass/</guid>
      <pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate>
      <author>Yash K</author>
      <description>The dashboard took an identity from a token without verifying its signature. B-52 changed the user ID, sent an unsigned token and reached another account’s protected page.</description>
    </item>
    <item>
      <title>A Login Bypassed by SQL Injection: B-52 on XBEN-029</title>
      <link>https://b52security.com/blog/xben-029-sql-injection-login-bypass/</link>
      <guid isPermaLink="true">https://b52security.com/blog/xben-029-sql-injection-login-bypass/</guid>
      <pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate>
      <author>Yash K</author>
      <description>The username became SQL syntax instead of a bound value. Different responses helped B-52 test the weakness; a crafted UNION then returned a forged account row the login accepted as an administrator.</description>
    </item>
    <item>
      <title>From SSTI to a Django Secret Key: B-52 on XBEN-056</title>
      <link>https://b52security.com/blog/xben-056-template-injection-django-secret-key/</link>
      <guid isPermaLink="true">https://b52security.com/blog/xben-056-template-injection-django-secret-key/</guid>
      <pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate>
      <author>Yash K</author>
      <description>A name field crossed from user data into template evaluation. B-52 used that mistake to reach the message store’s signer and recover secret material the application relied on.</description>
    </item>
    <item>
      <title>Padding Oracle From a URL: How B-52 Solved XBEN-101</title>
      <link>https://b52security.com/blog/xben-101-padding-oracle/</link>
      <guid isPermaLink="true">https://b52security.com/blog/xben-101-padding-oracle/</guid>
      <pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate>
      <author>Yash K</author>
      <description>The image was never decoded. The server’s different responses to a modified encrypted cookie let B-52 recover the captcha answer, complete registration and capture the flag.</description>
    </item>
    <item>
      <title>How to evaluate an agentic pentest on your own application</title>
      <link>https://b52security.com/blog/evaluate-agentic-pentest-on-your-application/</link>
      <guid isPermaLink="true">https://b52security.com/blog/evaluate-agentic-pentest-on-your-application/</guid>
      <pubDate>Fri, 30 Oct 2026 00:00:00 GMT</pubDate>
      <author>Yash K</author>
      <description>A buyer evaluation protocol for authenticated workflows, approval boundaries and findings your own engineers can reproduce.</description>
    </item>
    <item>
      <title>CI/CD security testing: the threshold has to be yours</title>
      <link>https://b52security.com/blog/a-build-gate-needs-a-threshold-you-set/</link>
      <guid isPermaLink="true">https://b52security.com/blog/a-build-gate-needs-a-threshold-you-set/</guid>
      <pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate>
      <author>Yash K</author>
      <description>A gate that fails every build is a gate somebody turns off. The threshold has to be yours, and where you put it decides how a team behaves long after the step is wired in.</description>
    </item>
    <item>
      <title>AI pentest: one term, two opposite jobs</title>
      <link>https://b52security.com/blog/ai-pentest-what-the-term-means-and-what-it-does-not/</link>
      <guid isPermaLink="true">https://b52security.com/blog/ai-pentest-what-the-term-means-and-what-it-does-not/</guid>
      <pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate>
      <author>Yash K</author>
      <description>The same four words describe a platform that runs the test and an engagement whose target is a model. This article names both, says which is which, and points each one at the page that answers it.</description>
    </item>
    <item>
      <title>What decompiling an APK or IPA actually finds</title>
      <link>https://b52security.com/blog/binary-analysis-what-apk-and-ipa-decompilation-finds/</link>
      <guid isPermaLink="true">https://b52security.com/blog/binary-analysis-what-apk-and-ipa-decompilation-finds/</guid>
      <pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate>
      <author>Yash K</author>
      <description>Traffic shows what a mobile application chose to do while somebody was watching it. The package shows what it was built to do. What it reveals turns out to be a question about the server, not the handset.</description>
    </item>
    <item>
      <title>Four cadences CSCRF keeps separate</title>
      <link>https://b52security.com/blog/four-cadences-cscrf-keeps-separate/</link>
      <guid isPermaLink="true">https://b52security.com/blog/four-cadences-cscrf-keeps-separate/</guid>
      <pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate>
      <author>Yash K</author>
      <description>CSCRF sets VAPT, cyber audit, red teaming and threat hunting as four separate obligations, written in three different places and carrying four different periodicities between them. This names each one and cites the table it is written in.</description>
    </item>
    <item>
      <title>Testing the inventory discovery found</title>
      <link>https://b52security.com/blog/testing-the-inventory-discovery-found/</link>
      <guid isPermaLink="true">https://b52security.com/blog/testing-the-inventory-discovery-found/</guid>
      <pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate>
      <author>Yash K</author>
      <description>A perimeter worked out from announced ranges, resolving names and what answers will surface hosts the asset register does not have. Testing what discovery found, instead of the list you were handed, is the difference between assessing what you remember and assessing what you run.</description>
    </item>
    <item>
      <title>Why a scanner finds nothing in a thick client</title>
      <link>https://b52security.com/blog/thick-client-testing-what-the-scanner-cannot-see/</link>
      <guid isPermaLink="true">https://b52security.com/blog/thick-client-testing-what-the-scanner-cannot-see/</guid>
      <pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate>
      <author>Yash K</author>
      <description>A web scanner needs an address, a link to follow and a request it can read. A desktop application supplies none of the three, which is why the report comes back empty, and why that empty report is a fact about the tool and not about the application.</description>
    </item>
    <item>
      <title>Automated red teaming: persistence under authorisation</title>
      <link>https://b52security.com/blog/what-autonomous-persistence-means-under-authorisation/</link>
      <guid isPermaLink="true">https://b52security.com/blog/what-autonomous-persistence-means-under-authorisation/</guid>
      <pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate>
      <author>Yash K</author>
      <description>Persistence means holding a foothold across time. When a platform does that without an operator, one question decides whether it is acceptable: under whose authority, and bounded by what.</description>
    </item>
    <item>
      <title>Why the QA gate comes after the report is written</title>
      <link>https://b52security.com/blog/why-qa-comes-after-reporting/</link>
      <guid isPermaLink="true">https://b52security.com/blog/why-qa-comes-after-reporting/</guid>
      <pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate>
      <author>Yash K</author>
      <description>PTES sets out seven phases and NIST SP 800-115 four, and both close their account at reporting. B-52 has a sixth phase after it, a quality gate that runs on the finished report and can send a finding back to the phase that produced it.</description>
    </item>
  </channel>
</rss>