<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Asset-Discovery on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/asset-discovery/</link>
    <description>Recent content in Asset-Discovery on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 14 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/asset-discovery/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Attack Surface Management: Sn1per vs Natlas vs xingrin (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-14-self-hosted-attack-surface-management-sn1per-natlas-xingrin-guide/</link>
      <pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-14-self-hosted-attack-surface-management-sn1per-natlas-xingrin-guide/</guid>
      <description>&lt;p&gt;Attack surface management (ASM) has become a critical security practice as organizations expand their digital footprints across cloud infrastructure, SaaS platforms, and remote endpoints. Unlike traditional vulnerability scanners that focus on known CVEs, ASM platforms continuously discover, catalog, and assess every externally-facing asset — domains, subdomains, IP addresses, cloud resources, and exposed services — giving security teams a complete picture of their attack surface from an adversary&amp;rsquo;s perspective.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
