<?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 XSIAM Assets / Network Mapper - How to identify unknown assets in Cortex XSIAM Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/xsiam-assets-network-mapper-how-to-identify-unknown-assets/m-p/995608#M121</link>
    <description>&lt;P&gt;We configured network mapper in the BrokerVM settings and using multiple ports for network identification. Of course, on the firewalls we allow all traffic from them to make a full visibility internally. However, the scan doesn't resolve the hostname or open ports on the machine that can support with OS identification, like 22/ssh - potential Linux etc. Sometimes with manual scan using nmap we can see much more open ports and zero return from mapper.&lt;BR /&gt;&lt;BR /&gt;Using network mapper, possible to resolve FQDN of the machine like with nmap ARP scan? How possible to identify or which process is the best to identify unknown assets in the network?&lt;/P&gt;</description>
    <pubDate>Thu, 28 Nov 2024 09:31:14 GMT</pubDate>
    <dc:creator>MDovirak</dc:creator>
    <dc:date>2024-11-28T09:31:14Z</dc:date>
    <item>
      <title>XSIAM Assets / Network Mapper - How to identify unknown assets</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/xsiam-assets-network-mapper-how-to-identify-unknown-assets/m-p/995608#M121</link>
      <description>&lt;P&gt;We configured network mapper in the BrokerVM settings and using multiple ports for network identification. Of course, on the firewalls we allow all traffic from them to make a full visibility internally. However, the scan doesn't resolve the hostname or open ports on the machine that can support with OS identification, like 22/ssh - potential Linux etc. Sometimes with manual scan using nmap we can see much more open ports and zero return from mapper.&lt;BR /&gt;&lt;BR /&gt;Using network mapper, possible to resolve FQDN of the machine like with nmap ARP scan? How possible to identify or which process is the best to identify unknown assets in the network?&lt;/P&gt;</description>
      <pubDate>Thu, 28 Nov 2024 09:31:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/xsiam-assets-network-mapper-how-to-identify-unknown-assets/m-p/995608#M121</guid>
      <dc:creator>MDovirak</dc:creator>
      <dc:date>2024-11-28T09:31:14Z</dc:date>
    </item>
    <item>
      <title>Re: XSIAM Assets / Network Mapper - How to identify unknown assets</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/xsiam-assets-network-mapper-how-to-identify-unknown-assets/m-p/999750#M129</link>
      <description>&lt;P&gt;Hi MDovirak,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The Broker VM Network Mapper is only using a ping scan to identify interfaces on the network.&amp;nbsp; It is not doing nmap or any other method that would allow more detailed discovery.&amp;nbsp; You can ingest DHCP logs from &lt;A href="https://docs-cortex.paloaltonetworks.com/r/Cortex-XSIAM/Cortex-XSIAM-Documentation/Ingest-logs-from-Windows-DHCP-using-Elasticsearch-Filebeat?tocId=GLiluNJ6nH13UESGRFEDpA" target="_self"&gt;Microsoft DHCP&lt;/A&gt; to provide additional enrichment of hostname for discovered IP addresses.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Dec 2024 15:53:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/xsiam-assets-network-mapper-how-to-identify-unknown-assets/m-p/999750#M129</guid>
      <dc:creator>afurze</dc:creator>
      <dc:date>2024-12-27T15:53:41Z</dc:date>
    </item>
  </channel>
</rss>

