Parsing rules

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

Parsing rules

L2 Linker



I am sending Cisco Asa logs to Cortex XDR and XDR automatically creates parsing rule of "Ingest". When I am searching for "cisco_asa_rules" in query, I got a field named "raw" which contains detailed format of log: 


That is a detailed format of raw field:


<116>Feb 16 2024 05:54:25 firepower : %FTD-4-430003: EventPriority: Low, DeviceUUID: baafab88-ed6c-11ec-baf4-ca1c8650edd2, InstanceID: 9, FirstPacketSecond: 2024-02-16T05:54:25Z, ConnectionID: 11587, AccessControlRuleAction: Allow, SrcIP: x, DstIP: x, SrcPort: 54659, DstPort: 80, Protocol: tcp, IngressInterface: Inside, EgressInterface: outside, IngressZone: Inside, EgressZone: outside-zone, SourceSecurityGroup: 26, SourceSecurityGroupTag: 26, SourceSecurityGroupType: Session Directory, IngressVRF: Global, EgressVRF: Global, ACPolicy: BRD-FTD4112-AccessPolicy, AccessControlRuleName: DNA GUEST to OUTSIDE, Prefilter Policy: BRD-FTD-4112-PrefilterPolicy, UserAgent: HT Parental Controls 8.6.1, Client: Web browser, ApplicationProtocol: HTTP, WebApplication: Web Browsing, ConnectionDuration: 0, InitiatorPackets: 5, ResponderPackets: 17, InitiatorBytes: 696, ResponderBytes: 17532, NAPPolicy: Balanced Security and Connectivity, HTTPResponse: 403, ReferencedHost:, URL:, NAT_InitiatorPort: 54659, NAT_ResponderPort: 80, NAT_InitiatorIP: x, NAT_ResponderIP: x, ClientAppDetector: AppID


I want Cortex XDR to show me necessary fields seperately. For example, when I query to cisco_asa dataset, I want to see Source IP, Destination IP, Ports and action that was done. 

Can you help me. How can I seperate these data from "raw" field and show them seperately inside "cisco_asa" dataset. 


Thanks in advance...


L4 Transporter

Hi @JahidAliyev, thanks for reaching us using the Live Community.


I'll recommend you to start with this recent webinar about Parsing Rules:


You will learn there the basics to start creating parsing rules, and I'm sure this will help you to think how to create this one. In this case you should us regular expressions to parse the logs.

  • 1 replies
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!