topic Assets -> Network configuration in Cortex XDR Discussions

Assets -> Network configuration

J.Risquez — Fri, 09 Jan 2026 11:37:57 GMT

Hi everyone,

Does anyone know if the ‘range names' created in the network configuration of the assets option can be seen in the assets information, or somewhere else, of the issues or cases?

Thanks in advance.

Regards,

J.Risquez

Re: Assets -> Network configuration

susekar — Mon, 12 Jan 2026 14:25:20 GMT

Hello @J.Risquez ,

Greetings for the day!

The Range Names (or descriptions) configured in the Assets → Network Configuration section are not visible as fields or columns within the Asset Inventory (Assets Information), nor are they displayed directly in Issues or Cases.

The primary purpose of defining these IP ranges in the Network Configuration is to distinguish between Internal and External traffic for analytics and detection purposes (e.g., determining if a connection is lateral or outbound), rather than for labeling assets in the user interface.

Workaround for Visualization:
To visualize or group assets by their network segment names in the console, you should use Endpoint Groups:
1. Navigate to Endpoints → Endpoint Groups.
2. Create a new group (e.g., name it "HQPrinters" or "ServerVLAN").
3. Set the filter criteria to include the specific IP addresses or ranges that correspond to your named network segment.
4. These Endpoint Groups can then be used for filtering, policy assignment, and visualization within the console.

Feature requests to add a field showing the "IP Range Name" in Endpoint Administration or to use these names to automatically create endpoint groups have been discussed internally but were marked as "will not implement".

If you feel this has answered your query, please let us know by clicking like and on "mark this as a Solution".

Happy New Year!!

Thanks & Regards,
S. Subashkar Sekar

Re: Assets -> Network configuration

J.Risquez — Tue, 13 Jan 2026 09:15:05 GMT

Hello @susekar,

thanks for your response.

I also considered the workaround you suggested, but I preferred to open this question to avoid having duplicated information about the VLANs and because the endpoint groups have to be manually created and one by one.

I don't know why the feature requests to show the "IP Range Name" in Endpoint Administration were marked as "will not implement", as I think this information is not confidential and would prevent having duplicated information in two different parts of the system.

Thanks for your help.

Regards,

José L.