Integrating multiple Cortex XDR with QRadar

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

Integrating multiple Cortex XDR with QRadar

L0 Member

Hi,

 

Thought I would give livecommunity a shot on this. We have been looking into integrating several Cortex XDR instances into a single QRadar instance but have come across an issue where it does not seem to let us change the syslog identifier name on any of them. This leads to a problem distinguishing the different XDR tenants from each other as they are all showing up with cortexxdr as the identifier.

 

All the XDR forwarding will be done over Syslog TLS. 

 

Normally, when configuring syslog for other services we are able to change this, but that does not seem to be the case for XDR. But then again, we have not worked that much with XDR so hoping someone might have found a way of solving this. 

 

Anyone had any luck implementing multiple XDR instances into their SIEM tool through syslog?

 

Edit: Think we may have found a way of doing this, without involving a new server with rsyslog or similar. Will feedback if it works. 

1 REPLY 1

L4 Transporter

Hi @Edmund66-

 

Please let me know if your approach does not work at which time I'd like to gather a little more info to take to Product Management.


David Falcon 
Senior Solutions Architect, Cortex
Palo Alto Networks® 
  • 2341 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!