<?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 Detecting the Nmap Scanning Engine User Agent in Automation/API Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/detecting-the-nmap-scanning-engine-user-agent/m-p/16531#M437</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Nmap is an open source utility used to scan map networks, and scan for open ports on workstations and servers. During the scripting stage of the network scan, Nmap will attempt to connect using HTTP, and has it's own user agent.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __default_attr="plain" __jive_macro_name="code" class="jive_text_macro jive_macro_code"&gt;User-Agent: Mozilla/5.0 (compatible; Nmap Scripting Engine; &lt;A href="http://nmap.org/book/nse.html"&gt;http://nmap.org/book/nse.html&lt;/A&gt;)&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nmap does contain the ability to change the user agent to any user agent, the vulnerability will defend off most script kidies and novices. This vulnerability is set to alert so you can monitor your network to make sure there are no false positives.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please let me know if you have any problems, and I'll try to refine the RegEx.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 25 Aug 2010 18:50:51 GMT</pubDate>
    <dc:creator>mharding</dc:creator>
    <dc:date>2010-08-25T18:50:51Z</dc:date>
    <item>
      <title>Detecting the Nmap Scanning Engine User Agent</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/detecting-the-nmap-scanning-engine-user-agent/m-p/16531#M437</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Nmap is an open source utility used to scan map networks, and scan for open ports on workstations and servers. During the scripting stage of the network scan, Nmap will attempt to connect using HTTP, and has it's own user agent.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __default_attr="plain" __jive_macro_name="code" class="jive_text_macro jive_macro_code"&gt;User-Agent: Mozilla/5.0 (compatible; Nmap Scripting Engine; &lt;A href="http://nmap.org/book/nse.html"&gt;http://nmap.org/book/nse.html&lt;/A&gt;)&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nmap does contain the ability to change the user agent to any user agent, the vulnerability will defend off most script kidies and novices. This vulnerability is set to alert so you can monitor your network to make sure there are no false positives.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please let me know if you have any problems, and I'll try to refine the RegEx.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Aug 2010 18:50:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/detecting-the-nmap-scanning-engine-user-agent/m-p/16531#M437</guid>
      <dc:creator>mharding</dc:creator>
      <dc:date>2010-08-25T18:50:51Z</dc:date>
    </item>
    <item>
      <title>Re: Detecting the Nmap Scanning Engine User Agent</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/detecting-the-nmap-scanning-engine-user-agent/m-p/16532#M438</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;FYI you are leaking admin (mharding) information in the xml file.&amp;nbsp; Plus unless that is taken out you can not use the import.&amp;nbsp; Anyhow it was a good reference as I used it to create mine.&amp;nbsp; Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Mar 2012 20:09:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/detecting-the-nmap-scanning-engine-user-agent/m-p/16532#M438</guid>
      <dc:creator>odonnek</dc:creator>
      <dc:date>2012-03-22T20:09:19Z</dc:date>
    </item>
  </channel>
</rss>

