<?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 Thanks for your reply! in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ports-vulnerability-scan/m-p/2522311#M921771</link>
    <description>&lt;P&gt;Thanks for your reply!&lt;/P&gt;</description>
    <pubDate>Wed, 03 Jun 2015 15:56:46 GMT</pubDate>
    <dc:creator>gvega0009</dc:creator>
    <dc:date>2015-06-03T15:56:46Z</dc:date>
    <item>
      <title>ports (vulnerability scan)</title>
      <link>https://community.cisco.com/t5/network-security/ports-vulnerability-scan/m-p/2522308#M921768</link>
      <description>&lt;P&gt;I ran a vulnerability scan on a 2960 switch and some "ports" (I don't even know if this is the right way to call them) showed being open or that needed to be reviewed. I really need to know what they are and if I need to keep them or need to get rid of them. How do you disable "ports" (I am not talking about the actual ports on the switch ex. gig1/0/1) on&amp;nbsp;a cisco switch? The ports are 4786 tcp, 67 udp, 161 udp, 162 udp, 1975 udp, 2228 udp, and 49688 udp.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 13:18:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ports-vulnerability-scan/m-p/2522308#M921768</guid>
      <dc:creator>gvega0009</dc:creator>
      <dc:date>2020-02-21T13:18:09Z</dc:date>
    </item>
    <item>
      <title>udp/67 is bootp (used by DHCP</title>
      <link>https://community.cisco.com/t5/network-security/ports-vulnerability-scan/m-p/2522309#M921769</link>
      <description>&lt;P&gt;udp/67 is bootp (used by DHCP). The switch listens on that port if it is either a DHCP server itself or is setup to provide "ip helper" service which is used to translate local segment end users broadcasts to a unicast packet which is then forwarded to your DHCP server elsewhere.&lt;/P&gt;&lt;P&gt;udp 161 and 162 are used by SNMP. Best practice has SNMP restricted to SNMP v3 (with authentication and privacy or encryption) and an access-list applied to define your permitted SNMP servers.&lt;/P&gt;&lt;P&gt;The high numbered ports are usually a sign that the device (or a user session on it) is logged into something remotely and that's the random port is selected from the &amp;gt;1024 range (sometimes known as "ephemeral" ports since they come and go somewhat at random)&amp;nbsp;to use as its source port. As long as the session is open, the devices will be "listening" on that port for replies.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Good&amp;nbsp;&lt;A href="http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers"&gt;link for port number reference&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Oct 2014 21:48:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ports-vulnerability-scan/m-p/2522309#M921769</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2014-10-06T21:48:56Z</dc:date>
    </item>
    <item>
      <title>The most effective way to</title>
      <link>https://community.cisco.com/t5/network-security/ports-vulnerability-scan/m-p/2522310#M921770</link>
      <description>&lt;P&gt;The most effective way to disable those ports is on a firewall.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Oct 2014 22:06:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ports-vulnerability-scan/m-p/2522310#M921770</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2014-10-06T22:06:15Z</dc:date>
    </item>
    <item>
      <title>Thanks for your reply!</title>
      <link>https://community.cisco.com/t5/network-security/ports-vulnerability-scan/m-p/2522311#M921771</link>
      <description>&lt;P&gt;Thanks for your reply!&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jun 2015 15:56:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ports-vulnerability-scan/m-p/2522311#M921771</guid>
      <dc:creator>gvega0009</dc:creator>
      <dc:date>2015-06-03T15:56:46Z</dc:date>
    </item>
    <item>
      <title>Thanks for your reply!</title>
      <link>https://community.cisco.com/t5/network-security/ports-vulnerability-scan/m-p/2522312#M921772</link>
      <description>&lt;P&gt;Thanks for your reply!&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jun 2015 15:57:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ports-vulnerability-scan/m-p/2522312#M921772</guid>
      <dc:creator>gvega0009</dc:creator>
      <dc:date>2015-06-03T15:57:02Z</dc:date>
    </item>
    <item>
      <title>You're welcome.Please rate or</title>
      <link>https://community.cisco.com/t5/network-security/ports-vulnerability-scan/m-p/2522313#M921774</link>
      <description>&lt;P&gt;You're welcome.&lt;/P&gt;&lt;P&gt;Please rate or mark correct if it answers your question.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jun 2015 15:58:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ports-vulnerability-scan/m-p/2522313#M921774</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2015-06-03T15:58:47Z</dc:date>
    </item>
  </channel>
</rss>

