<?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: TCP and UDP portscans in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/tcp-and-udp-portscans/m-p/5335505#M1123015</link>
    <description>&lt;P&gt;Balaji&lt;/P&gt;&lt;P&gt;Thanks for the response. An example of this is one of my hosts did a portscan when accessing google.com. I can see the Intrusion event for this. Maybe my port scan detection is misconfigured?&lt;/P&gt;&lt;P&gt;Your thoughts?&lt;/P&gt;</description>
    <pubDate>Thu, 02 Oct 2025 17:07:39 GMT</pubDate>
    <dc:creator>ethutchinson</dc:creator>
    <dc:date>2025-10-02T17:07:39Z</dc:date>
    <item>
      <title>TCP and UDP portscans</title>
      <link>https://community.cisco.com/t5/network-security/tcp-and-udp-portscans/m-p/5335394#M1123010</link>
      <description>&lt;P&gt;I have two FTD 1140ns managed by an FMCv. Both are running 7.6.2. I enabled portscannig in detection mode some time ago. I noticed quite a few of my local IP addresses scanning out to Outside (public) addresses. I know this is a nubie type of question but is this normal behavior? I can understand the inside IP addresses scanning because of the OS, programs installed, etc.and I can know I can ignore outgoing scans from these internal subnets. Could this amount of portscans be pointing to an issue?&lt;/P&gt;&lt;P&gt;Any ideas or am I overthinking this.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Oct 2025 12:24:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-and-udp-portscans/m-p/5335394#M1123010</guid>
      <dc:creator>ethutchinson</dc:creator>
      <dc:date>2025-10-02T12:24:48Z</dc:date>
    </item>
    <item>
      <title>Re: TCP and UDP portscans</title>
      <link>https://community.cisco.com/t5/network-security/tcp-and-udp-portscans/m-p/5335471#M1123014</link>
      <description>&lt;P&gt;Why would an internal IP scan the internet world? This looks suspicious until you have a security team investigating any issues or scanning for requirements.&lt;/P&gt;
&lt;P&gt;If not, you need to examine the endpoint; why is it scanning over the internet?&lt;/P&gt;
&lt;P&gt;Even if local scanning takes place, they should only use RFC 1918 addresses for scanning, not the Internet range.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Oct 2025 15:09:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-and-udp-portscans/m-p/5335471#M1123014</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2025-10-02T15:09:33Z</dc:date>
    </item>
    <item>
      <title>Re: TCP and UDP portscans</title>
      <link>https://community.cisco.com/t5/network-security/tcp-and-udp-portscans/m-p/5335505#M1123015</link>
      <description>&lt;P&gt;Balaji&lt;/P&gt;&lt;P&gt;Thanks for the response. An example of this is one of my hosts did a portscan when accessing google.com. I can see the Intrusion event for this. Maybe my port scan detection is misconfigured?&lt;/P&gt;&lt;P&gt;Your thoughts?&lt;/P&gt;</description>
      <pubDate>Thu, 02 Oct 2025 17:07:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-and-udp-portscans/m-p/5335505#M1123015</guid>
      <dc:creator>ethutchinson</dc:creator>
      <dc:date>2025-10-02T17:07:39Z</dc:date>
    </item>
    <item>
      <title>Re: TCP and UDP portscans</title>
      <link>https://community.cisco.com/t5/network-security/tcp-and-udp-portscans/m-p/5335529#M1123019</link>
      <description>&lt;P&gt;not sure we need to know more information and how this was configured.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Oct 2025 18:06:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-and-udp-portscans/m-p/5335529#M1123019</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2025-10-02T18:06:06Z</dc:date>
    </item>
  </channel>
</rss>

