<?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 Re: CSA issue with firewall rule in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/csa-issue-with-firewall-rule/m-p/1404017#M68180</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;oh, and you could do a specific rule for the opendns addresses where this is allowed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 17 Dec 2009 03:22:28 GMT</pubDate>
    <dc:creator>jan.nielsen</dc:creator>
    <dc:date>2009-12-17T03:22:28Z</dc:date>
    <item>
      <title>CSA issue with firewall rule</title>
      <link>https://community.cisco.com/t5/network-security/csa-issue-with-firewall-rule/m-p/1404015#M68178</link>
      <description>&lt;P&gt;I created a rule in CSA 6.0 that, by default, blocks any application on any machine being connected as a server.&amp;nbsp; On a DC we made an exception for the server to be connected on UDP 53 for DNS.&amp;nbsp; However, we are seeing the following messages below.&amp;nbsp; The port ranges from, so far, 30,000-65,000.&amp;nbsp; It seems odd that dns.exe would be accepting a connection as a server on all of those ports.&amp;nbsp; Has anyone seen this before or had this happen to them or is this normal?&amp;nbsp; Also, it is running OpenDNS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Jay&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13px; font-family: verdana,helvetica;"&gt;&lt;SPAN style="color: brown;"&gt;&lt;STRONG&gt;Audit: &lt;/STRONG&gt;&lt;/SPAN&gt;The process 'C:\WINDOWS\system32\dns.exe' (as user NT AUTHORITY\SYSTEM) attempted to accept a connection as a server on UDP port 61660 from 208.67.220.220 using interface Wired\HP NC7761 Gigabit Server Adapter. The operation would have been denied.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 11:50:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/csa-issue-with-firewall-rule/m-p/1404015#M68178</guid>
      <dc:creator>jasonsuplita</dc:creator>
      <dc:date>2019-03-10T11:50:59Z</dc:date>
    </item>
    <item>
      <title>Re: CSA issue with firewall rule</title>
      <link>https://community.cisco.com/t5/network-security/csa-issue-with-firewall-rule/m-p/1404016#M68179</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You are behind a hardware/appliance firewall right ? if so, that port should not be open, which tells me that this is an accept of a udp reply from opendns on a request the server made, and not an actual request from opendns to your server, cause all dns traffic works on port 53 tcp/udp as destination port.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Dec 2009 03:21:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/csa-issue-with-firewall-rule/m-p/1404016#M68179</guid>
      <dc:creator>jan.nielsen</dc:creator>
      <dc:date>2009-12-17T03:21:37Z</dc:date>
    </item>
    <item>
      <title>Re: CSA issue with firewall rule</title>
      <link>https://community.cisco.com/t5/network-security/csa-issue-with-firewall-rule/m-p/1404017#M68180</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;oh, and you could do a specific rule for the opendns addresses where this is allowed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Dec 2009 03:22:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/csa-issue-with-firewall-rule/m-p/1404017#M68180</guid>
      <dc:creator>jan.nielsen</dc:creator>
      <dc:date>2009-12-17T03:22:28Z</dc:date>
    </item>
  </channel>
</rss>

