Forum Discussion
Defender for Identity の TLS Syslog での SIEM (IBM QRadar) への連携（English follows）
Thank you Eli, it seems like an IP address will be put in the column, right?
Where can we find the IPs to be put in the column for each Sensors?
2-21-2018 16:19:35 Auth.Warning 192.168.0.220 1 2018-02-21T14:19:27.540731+00:00 CENTER CEF 6076 AccountEnumerationSecurityAlert 0|Microsoft|Azure ATP|2.22.4228.22540|AccountEnumerationSecurityAlert|Reconnaissance using account enumeration|5|start=2018-02-21T14:19:02.6045416Z app=Kerberos shost=CLIENT1 suser=LMaldonado msg=Suspicious account enumeration activity using the Kerberos protocol, originating from CLIENT1, was observed and successfully guessed Lamon Maldonado (Software Engineer). externalId=2003 cs1Label=url cs1=https://contoso-corp.atp.azure.com/securityAlert/eb6a35da-ff7f-4ab5-a1b5-a07529a89e6d cs2Label=trigger cs2=new cs3Label=shostfqdn cs3=client1.contoso.com
Microsoft- Thank you Eli,
okay, so I'd like to specify the IP of the sensors.
We can see the names of the sensors in the dashboard of the Defender for Identity console.
Where can we locate the IP of the sensors then?- EliOfekThe portal will only show names.
If you go to the machine profile it should allow you to see the last IP we saw it using.
But it's not displayed on the sensors list easily.- Thank you Eli,
I understand that we can locate the IPs of the sensors at "the machine profile".
But I supposed that these IPs are not static right?
For receiving Syslogs in QRadar, we need to configure a parameter called "Log Source ID" in QRadar.
The parameter of "Log Source ID" should be the strings which is at the head of the payload and is usually hostname/IP address and should be static.
QRadar identify the consumed logs as the specific LogSourceName registered in QRadar by verifying that the registered "Log Source ID", which is mapped to the LogSourceName, and the head of the payload is the same.