<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Advanced DNS Security vs. DNS Security in Advanced DNS Security  Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/advanced-dns-security/advanced-dns-security-vs-dns-security/m-p/589027#M5</link>
    <description>&lt;P&gt;Good day,&lt;/P&gt;
&lt;P&gt;i apologize in advance if i'm posting in the wrong place...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;i've read the docs but i have some clarifications:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. What exactly can Advanced DNS Security do that DNS Security cannot?&amp;nbsp; It's implied that plain DNS Security cannot detect misconfigured or hijacked domains.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2. Does it detect when users try to connect to a misconfigured/hijacked domain, or does it detect if *my* organization's DNS domain has been hijacked or is misconfigured? Or both?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;3. Would you consider these as must-have features, or just for specific setups?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 07 Jun 2024 01:39:57 GMT</pubDate>
    <dc:creator>itassetbenilde</dc:creator>
    <dc:date>2024-06-07T01:39:57Z</dc:date>
    <item>
      <title>Advanced DNS Security vs. DNS Security</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-dns-security/advanced-dns-security-vs-dns-security/m-p/589027#M5</link>
      <description>&lt;P&gt;Good day,&lt;/P&gt;
&lt;P&gt;i apologize in advance if i'm posting in the wrong place...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;i've read the docs but i have some clarifications:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. What exactly can Advanced DNS Security do that DNS Security cannot?&amp;nbsp; It's implied that plain DNS Security cannot detect misconfigured or hijacked domains.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2. Does it detect when users try to connect to a misconfigured/hijacked domain, or does it detect if *my* organization's DNS domain has been hijacked or is misconfigured? Or both?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;3. Would you consider these as must-have features, or just for specific setups?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jun 2024 01:39:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-dns-security/advanced-dns-security-vs-dns-security/m-p/589027#M5</guid>
      <dc:creator>itassetbenilde</dc:creator>
      <dc:date>2024-06-07T01:39:57Z</dc:date>
    </item>
    <item>
      <title>Re: Advanced DNS Security vs. DNS Security</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-dns-security/advanced-dns-security-vs-dns-security/m-p/589054#M6</link>
      <description>&lt;P&gt;1. regular DNS security works somewhat like URL filtering where it categorizes a record's FQDN as good or bad&lt;/P&gt;
&lt;P&gt;A-DNS will go a little further and also inspect the record itself to see if there are any markers that could indicate a problem:&lt;/P&gt;
&lt;P&gt;one example is zone dangling, which allows for the takeover of a 'forgotten' subdomain record. a "common" example is when an org has set up a record pointing to a cloud resource which gets decommissioned at some point without removing the record. a bad actor could try to forge the resource so now that dns record points to their resource&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2. security is applied to sessions passing through the firewall, it does not proactively monitor your domain (except if you request a record for your own domain so the payload of the request is inspected)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;3. security in layers: it's certainly a nice to have&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jun 2024 07:42:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-dns-security/advanced-dns-security-vs-dns-security/m-p/589054#M6</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2024-06-07T07:42:45Z</dc:date>
    </item>
  </channel>
</rss>

