<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Infrastructure Security on Nalar</title>
    <link>https://nalar.dev/tags/infrastructure-security/</link>
    <description>Recent content in Infrastructure Security on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 15 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/infrastructure-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>NSEC3 Trades DNSSEC Name Exposure for Operational Cost</title>
      <link>https://nalar.dev/nsec3-trades-dnssec-name-exposure-for-operational-cost/</link>
      <pubDate>Tue, 15 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/nsec3-trades-dnssec-name-exposure-for-operational-cost/</guid>
      <description>&lt;h1 id=&#34;nsec3-trades-dnssec-name-exposure-for-operational-cost&#34;&gt;NSEC3 Trades DNSSEC Name Exposure for Operational Cost&lt;/h1&gt;&#xA;&lt;p&gt;A signed DNS zone has to authenticate absence as well as presence. When a resolver asks for a name that does not exist, a DNSSEC-validating resolver needs cryptographic evidence that the negative answer was not forged by an intermediary. The original NSEC mechanism supplies that evidence by linking existing names in canonical order.&lt;/p&gt;&#xA;&lt;p&gt;That design has a side effect: the links expose names. Following NSEC records can reveal much of a zone even when ordinary DNS queries do not provide an enumeration interface.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
