<?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: NMAP Probe - Expected Behaviors? in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5001013#M586556</link>
    <description>&lt;P&gt;i think i see what you're saying.&amp;nbsp; You're saying that i need to go to the attached and tell ISE if it sees something as "Microsoft-Workstation" that it then needs to do some sort of scan.&amp;nbsp; In this case i've told it to do an OS-scan.&amp;nbsp; this filed used to have NONE in it.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 19 Jan 2024 12:59:59 GMT</pubDate>
    <dc:creator>ryanbess</dc:creator>
    <dc:date>2024-01-19T12:59:59Z</dc:date>
    <item>
      <title>NMAP Probe - Expected Behaviors?</title>
      <link>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5000408#M586528</link>
      <description>&lt;P&gt;I'm running 3.2 patch 2.&amp;nbsp; I have the NMAP probe enabled (profiling configuration tab) and in General Settings i have "enable profiling service" enabled on the PSN.&amp;nbsp; What I'm not seeing is the PSN actually doing an NMAP scan on a device when it comes online.&amp;nbsp; I'm also letting it sit for sometime and still nothing.&amp;nbsp; The only time i see the NMAP scans doing anything is if i manually kick off a scan.&amp;nbsp; I know this because I'm running a PCAP and when i ping the endpoint from the PSN i see the ICMP packets making it to the client.&amp;nbsp; Is there something else i need to enable?&amp;nbsp; When should i expect to see ISE scan an endpoint?&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 03:01:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5000408#M586528</guid>
      <dc:creator>ryanbess</dc:creator>
      <dc:date>2024-01-19T03:01:36Z</dc:date>
    </item>
    <item>
      <title>Re: NMAP Probe - Expected Behaviors?</title>
      <link>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5000466#M586533</link>
      <description>&lt;P&gt;Have you configured an NMAP scan action for your relevant Profiling Policy as per the &lt;A href="https://community.cisco.com/t5/security-knowledge-base/ise-profiling-design-guide/ta-p/3739456#toc-hId-1651437215" target="_blank" rel="noopener"&gt;ISE Profiling Design Guide&lt;/A&gt;?&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 04:58:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5000466#M586533</guid>
      <dc:creator>Greg Gibbs</dc:creator>
      <dc:date>2024-01-19T04:58:28Z</dc:date>
    </item>
    <item>
      <title>Re: NMAP Probe - Expected Behaviors?</title>
      <link>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5000471#M586534</link>
      <description>&lt;P&gt;&lt;STRONG&gt;I think you need policy (profiling policy) to trigger NMAP for specific host/subnet&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;STRONG id="yui_3_17_2_1_1705640547816_672"&gt;Policy&amp;gt;Policy Elements&amp;gt;Results&amp;gt;Profiling&amp;gt;Network Scan (NMAP) Actions&lt;/STRONG&gt;&lt;BR /&gt;MHM&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 05:04:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5000471#M586534</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-01-19T05:04:36Z</dc:date>
    </item>
    <item>
      <title>Re: NMAP Probe - Expected Behaviors?</title>
      <link>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5000999#M586554</link>
      <description>&lt;P&gt;yes there are three&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 12:37:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5000999#M586554</guid>
      <dc:creator>ryanbess</dc:creator>
      <dc:date>2024-01-19T12:37:31Z</dc:date>
    </item>
    <item>
      <title>Re: NMAP Probe - Expected Behaviors?</title>
      <link>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5001000#M586555</link>
      <description>&lt;P&gt;Morning, yes they are there.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 12:38:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5001000#M586555</guid>
      <dc:creator>ryanbess</dc:creator>
      <dc:date>2024-01-19T12:38:08Z</dc:date>
    </item>
    <item>
      <title>Re: NMAP Probe - Expected Behaviors?</title>
      <link>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5001013#M586556</link>
      <description>&lt;P&gt;i think i see what you're saying.&amp;nbsp; You're saying that i need to go to the attached and tell ISE if it sees something as "Microsoft-Workstation" that it then needs to do some sort of scan.&amp;nbsp; In this case i've told it to do an OS-scan.&amp;nbsp; this filed used to have NONE in it.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 12:59:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5001013#M586556</guid>
      <dc:creator>ryanbess</dc:creator>
      <dc:date>2024-01-19T12:59:59Z</dc:date>
    </item>
    <item>
      <title>Re: NMAP Probe - Expected Behaviors?</title>
      <link>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5001027#M586557</link>
      <description>&lt;P&gt;sorry I confuse if was set and NMAP not work or now you set it ?&lt;BR /&gt;MHM&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 13:14:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5001027#M586557</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-01-19T13:14:56Z</dc:date>
    </item>
    <item>
      <title>Re: NMAP Probe - Expected Behaviors?</title>
      <link>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5001030#M586558</link>
      <description>&lt;P&gt;Nope.&amp;nbsp; Looks like there is more to the story.&amp;nbsp; Looks like ISE just doesn't do an NMAP scan even though there is an OS scan.&amp;nbsp; Looks like you need to go into the Profiler Policy list to tell it to do the OS-SCAN when in this case it sees the endpoint as a Microsoft-Workstation.&amp;nbsp; However i'm now getting the attached.&amp;nbsp; Digging into it.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 13:21:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5001030#M586558</guid>
      <dc:creator>ryanbess</dc:creator>
      <dc:date>2024-01-19T13:21:15Z</dc:date>
    </item>
    <item>
      <title>Re: NMAP Probe - Expected Behaviors?</title>
      <link>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5001054#M586559</link>
      <description>&lt;P&gt;Can you more elaborate what condition you use&amp;nbsp; in this profiling policy ?&lt;BR /&gt;MHM&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 13:43:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5001054#M586559</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-01-19T13:43:00Z</dc:date>
    </item>
    <item>
      <title>Re: NMAP Probe - Expected Behaviors?</title>
      <link>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5001058#M586560</link>
      <description>&lt;P&gt;ok think i got it.&amp;nbsp; When it now sees the dhcp-class-identifier&amp;nbsp; containing MSFT, it will trigger an OS scan on the endpoint.&amp;nbsp; I just did the pcap and i now see it.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 13:46:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5001058#M586560</guid>
      <dc:creator>ryanbess</dc:creator>
      <dc:date>2024-01-19T13:46:14Z</dc:date>
    </item>
    <item>
      <title>Re: NMAP Probe - Expected Behaviors?</title>
      <link>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5001061#M586561</link>
      <description>&lt;P&gt;You are welcome friend&amp;nbsp;&lt;BR /&gt;MHM&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 13:47:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5001061#M586561</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-01-19T13:47:31Z</dc:date>
    </item>
    <item>
      <title>Re: NMAP Probe - Expected Behaviors?</title>
      <link>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5001065#M586562</link>
      <description>&lt;P&gt;You or anyone know of a way to just have ISE do an NMAP scan on everything it finds vs having to go into each of these settings and enable it?&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 13:50:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/nmap-probe-expected-behaviors/m-p/5001065#M586562</guid>
      <dc:creator>ryanbess</dc:creator>
      <dc:date>2024-01-19T13:50:27Z</dc:date>
    </item>
  </channel>
</rss>

