<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Parsing rules in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/parsing-rules/m-p/577472#M6075</link>
    <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That is a detailed format of raw field:&lt;/P&gt;
&lt;P&gt;---&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class="ui-provider a b c d e f g h i j k l m n o p q r s t u v w x y z ab ac ae af ag ah ai aj ak"&gt;&amp;lt;116&amp;gt;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: hidetools.com, URL: &lt;A class="fui-Link ___1rxvrpe f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1hu3pq6 f11qmguv f19f4twv f1tyq0we f1g0x7ka fhxju0i f1qch9an f1cnd47f fqv5qza f1vmzxwi f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="http://hidetools.com/" href="http://hidetools.com" target="_blank" rel="noreferrer noopener" aria-label="Link http://hidetools.com"&gt;http://hidetools.com&lt;/A&gt;, NAT_InitiatorPort: 54659, NAT_ResponderPort: 80, NAT_InitiatorIP: x, NAT_ResponderIP: x, ClientAppDetector: AppID&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;---&lt;BR /&gt;&lt;BR /&gt;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.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Can you help me. How can I seperate these data from "raw" field and show them seperately inside "cisco_asa" dataset.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in advance...&lt;/P&gt;</description>
    <pubDate>Fri, 16 Feb 2024 08:14:26 GMT</pubDate>
    <dc:creator>JahidAliyev</dc:creator>
    <dc:date>2024-02-16T08:14:26Z</dc:date>
    <item>
      <title>Parsing rules</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/parsing-rules/m-p/577472#M6075</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That is a detailed format of raw field:&lt;/P&gt;
&lt;P&gt;---&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class="ui-provider a b c d e f g h i j k l m n o p q r s t u v w x y z ab ac ae af ag ah ai aj ak"&gt;&amp;lt;116&amp;gt;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: hidetools.com, URL: &lt;A class="fui-Link ___1rxvrpe f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1hu3pq6 f11qmguv f19f4twv f1tyq0we f1g0x7ka fhxju0i f1qch9an f1cnd47f fqv5qza f1vmzxwi f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="http://hidetools.com/" href="http://hidetools.com" target="_blank" rel="noreferrer noopener" aria-label="Link http://hidetools.com"&gt;http://hidetools.com&lt;/A&gt;, NAT_InitiatorPort: 54659, NAT_ResponderPort: 80, NAT_InitiatorIP: x, NAT_ResponderIP: x, ClientAppDetector: AppID&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;---&lt;BR /&gt;&lt;BR /&gt;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.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Can you help me. How can I seperate these data from "raw" field and show them seperately inside "cisco_asa" dataset.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in advance...&lt;/P&gt;</description>
      <pubDate>Fri, 16 Feb 2024 08:14:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/parsing-rules/m-p/577472#M6075</guid>
      <dc:creator>JahidAliyev</dc:creator>
      <dc:date>2024-02-16T08:14:26Z</dc:date>
    </item>
    <item>
      <title>Re: Parsing rules</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/parsing-rules/m-p/577507#M6082</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/274228"&gt;@JahidAliyev&lt;/a&gt;, thanks for reaching us using the Live Community.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'll recommend you to start with this recent webinar about Parsing Rules:&amp;nbsp;&lt;A href="https://live.paloaltonetworks.com/t5/cortex-xdr-webinars/cortex-customer-success-webinar-series-part-1-getting-started/ta-p/575388" target="_blank"&gt;https://live.paloaltonetworks.com/t5/cortex-xdr-webinars/cortex-customer-success-webinar-series-part-1-getting-started/ta-p/575388&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Feb 2024 12:52:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/parsing-rules/m-p/577507#M6082</guid>
      <dc:creator>jmazzeo</dc:creator>
      <dc:date>2024-02-16T12:52:43Z</dc:date>
    </item>
  </channel>
</rss>

