Hi, yes, we use QRADAR and just went through this. It is working. We did use SHA256 and it did work. SHA 256 did not work for our Symantec Managed Services Appliance (LCP3.0) and we had to switch to SHA1 but QRADAR worked fine. Below is how we configured the LEA settings for QRADAR. Good Luck:
Log Source Name (Our CP Log Server Name)
Log Source Desc Checkpoint Log Server
Log Source Type Checkpoint
Protocol OPSEC/LEA
Log Source IDentifier (the ip address of our log server)
Server IP (also the ip of our log server)
Server Port 18184
Use Server IP for Log Source Checked
Statistics Report Interval 600
Authentication Type sslca
OpSEC App Obj SIC Attr The DN path of your OPSEC application Object
Log Source SIC Attribute The DN path of your logging server
Specify Certificate Checked
Certificate Authority IP IP of your management server
Pull Certificate Password the shared / trusted SIC secret you specified in OBSEC object
OPSEC Application Just the name of the application ( I used the short non-DN name of the OPSEC Object)
Enabled Checked
Target Collector which QRADAR appliance do you want to reach out to the Log Server
Coalescing Events Checked
Store Event Payload Checked
Log Source Extension I left this blank
Select QRadar Groups Check the group you want.
This site was helpful:
IBM Knowledge Center