<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>SuperPentest Blog</title>
  <link>https://superpentest.com/blog</link>
  <atom:link href="https://superpentest.com/feed.xml" rel="self" type="application/rss+xml"/>
  <description>Autonomous AI penetration testing — notes on reproduction-first security, AI/agent testing and compliance evidence.</description>
  <language>en</language>
  <item>
    <title>The vulnerability classes every pentest should cover in 2026 — SuperPentest</title>
    <link>https://superpentest.com/blog/vulnerability-classes-pentest-2026</link>
    <guid isPermaLink="true">https://superpentest.com/blog/vulnerability-classes-pentest-2026</guid>
    <pubDate>2026-10-27T09:00:00+00:00</pubDate>
    <description>A senior reference to the vulnerability classes a modern penetration test has to reach — access control, authentication, injection, API contracts, business logic, exposure and the new AI-agent surface — grouped, with a note on why signature scanners miss the harder members and why coverage only counts when it is tested honestly.</description>
  </item>
  <item>
    <title>What makes a trust page useful for auditors — SuperPentest</title>
    <link>https://superpentest.com/blog/trust-page-for-auditors</link>
    <guid isPermaLink="true">https://superpentest.com/blog/trust-page-for-auditors</guid>
    <pubDate>2026-10-27T09:00:00+00:00</pubDate>
    <description>A security trust page is read by auditors, buyers&#x27; security teams and vendor-risk reviewers — not by your marketing team. Here is what makes one actually useful: current test status and dates, a scope statement, shareable evidence instead of badges, a stated verification method, findings tracked to closure, and honest disclosure — versus the logo-wall page that proves nothing.</description>
  </item>
  <item>
    <title>From scope to evidence: a practical pentest roadmap — SuperPentest</title>
    <link>https://superpentest.com/blog/scope-to-evidence-pentest-roadmap</link>
    <guid isPermaLink="true">https://superpentest.com/blog/scope-to-evidence-pentest-roadmap</guid>
    <pubDate>2026-10-27T09:00:00+00:00</pubDate>
    <description>A field-tested roadmap for running a penetration test that ends in proof, not a PDF of maybes: how scope, rules of engagement, hypotheses, controlled tests, clean-session reproduction and hash-chained evidence fit together, stage by stage.</description>
  </item>
  <item>
    <title>Prompt injection and MCP security: an intro guide — SuperPentest</title>
    <link>https://superpentest.com/blog/prompt-injection-and-mcp-security-guide</link>
    <guid isPermaLink="true">https://superpentest.com/blog/prompt-injection-and-mcp-security-guide</guid>
    <pubDate>2026-10-27T09:00:00+00:00</pubDate>
    <description>A beginner-friendly, technically correct introduction to prompt injection and MCP security testing: direct vs indirect injection, why an agent&#x27;s tools turn an injection into an action, permission boundaries, how an over-permissioned MCP surface widens the blast radius, and how you test for it with a benign canary.</description>
  </item>
  <item>
    <title>Map pentest findings to OWASP, SOC 2, ISO 27001 and PCI DSS — SuperPentest</title>
    <link>https://superpentest.com/blog/map-findings-to-compliance-controls</link>
    <guid isPermaLink="true">https://superpentest.com/blog/map-findings-to-compliance-controls</guid>
    <pubDate>2026-10-27T09:00:00+00:00</pubDate>
    <description>Auditors do not want a list of bugs; they want each one tied to the control it exercises. Here is how a single finding maps across OWASP, SOC 2, ISO 27001 and PCI DSS at once — with correct, conservative example mappings and where people get them wrong.</description>
  </item>
  <item>
    <title>How to scope a pen test for web apps, APIs and AI agents — SuperPentest</title>
    <link>https://superpentest.com/blog/how-to-scope-a-penetration-test</link>
    <guid isPermaLink="true">https://superpentest.com/blog/how-to-scope-a-penetration-test</guid>
    <pubDate>2026-10-27T09:00:00+00:00</pubDate>
    <description>A practical guide to scoping a penetration test that actually covers your attack surface: the identities and tenants to supply, how web apps, APIs and AI-agent surfaces each change the scope, and the rules of engagement that keep it safe.</description>
  </item>
  <item>
    <title>Deep vs Standard: which pentest your security maturity needs — SuperPentest</title>
    <link>https://superpentest.com/blog/deep-vs-standard-pentest-plans</link>
    <guid isPermaLink="true">https://superpentest.com/blog/deep-vs-standard-pentest-plans</guid>
    <pubDate>2026-10-27T09:00:00+00:00</pubDate>
    <description>A decision guide, not a sales page: what a Standard coverage scan and a Deep assessment each actually cover, and which one fits your stage — first-ever pentest, an annual compliance requirement, or a continuous program.</description>
  </item>
</channel>
</rss>
