<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dns on microsegment.io</title>
    <link>https://microsegment.io/tags/dns/</link>
    <description>Recent content in Dns on microsegment.io</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 10 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://microsegment.io/tags/dns/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A DNS Allowlist Is Not a Workload Containment Policy</title>
      <link>https://microsegment.io/post/2026-11-10-dns-allowlist-is-not-workload-containment/</link>
      <pubDate>Tue, 10 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-11-10-dns-allowlist-is-not-workload-containment/</guid>
      <description>&lt;p&gt;The server can resolve only approved names. Can it still connect to an unrelated database by address?&lt;/p&gt;&#xA;&lt;p&gt;Those are different questions. A containment review needs answers to both.&lt;/p&gt;&#xA;&lt;p&gt;DNS policy belongs in a microsegmentation design. It should not quietly become the whole design.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-useful-shift-in-dns-security&#34;&gt;The Useful Shift In DNS Security&lt;/h2&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.nist.gov/news-events/news/2026/03/secure-domain-name-system-dns-deployment-guide-final-publication&#34;&gt;NIST published SP 800-81r3 in March 2026&lt;/a&gt;. Its guidance treats DNS as more than infrastructure plumbing: DNS can support Zero Trust policy enforcement and provide information for access decisions. The publication also addresses authoritative and recursive DNS security.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
