Describe the bug
Parsing issue with Cisco ISE data source
Using the parser from the Cisco Identity Service Engine data connector page in Sentinel provide and still got wrong information in the logs.
I found out that the parser will apply for these logs:
Syslog
| where ProcessName has_any ("CSCO", "CISE")
There are many logs with different structures of SyslogMessage which causes the parser to not be able to function properly.
When applied this line in parser for the above results, there will be an eventid with a date (Ex 1: 2024-01-05) and an eventid with a string (Ex 2: NetworkDeviceGroups...).
| parse SyslogMessage with * " " * " " * " " EventId " " EventSeverity " " EventCategory " " RestOfMessage
To Reproduce
Steps to reproduce the behavior:
- Go to Sentinel portal > Data Connectors > Cisco Identity Service Engine
- Click on "Follow these steps"
- Copy the function code then paste into Logs then Save as function.
- See wrong information in CiscoISEEvent table.
Expected behavior
Correct data from Syslog parse into the correct field in CiscoISEEvent table.
Screenshots
Describe the bug
Parsing issue with Cisco ISE data source
Using the parser from the Cisco Identity Service Engine data connector page in Sentinel provide and still got wrong information in the logs.
I found out that the parser will apply for these logs:
Syslog
| where ProcessName has_any ("CSCO", "CISE")
There are many logs with different structures of SyslogMessage which causes the parser to not be able to function properly.
When applied this line in parser for the above results, there will be an eventid with a date (Ex 1: 2024-01-05) and an eventid with a string (Ex 2: NetworkDeviceGroups...).
| parse SyslogMessage with * " " * " " * " " EventId " " EventSeverity " " EventCategory " " RestOfMessage
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Correct data from Syslog parse into the correct field in CiscoISEEvent table.
Screenshots