<?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 Playbook construction in Cortex XSOAR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/playbook-construction/m-p/483733#M770</link>
    <description>&lt;P&gt;I would like to ask the community if perhaps someone has created a playbook that takes in Snort/Suricata alert data. I am looking a creating a automated block process that will compare an IDS alert with a Threat notification from the PAN. If the src_ip, src_port, dst_ip, dst_port and timestamp match and the firewall took no action on the threat. Then I will add the external src_ip to the Indicators database, make Verdict "suspicious", set Expiration Date to 30 days, add both the IDS and Threat log data to "Comments" to show reason for block, tag the new entry as "block_external_ips", "ids" and "pan threat". So that it gets added to the EDL that will be picked up by the Firewall. It would be helpful if someone had an IDS related playbook that they would be willing to share to start this process.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Fri, 29 Apr 2022 00:13:26 GMT</pubDate>
    <dc:creator>jpadro</dc:creator>
    <dc:date>2022-04-29T00:13:26Z</dc:date>
    <item>
      <title>Playbook construction</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/playbook-construction/m-p/483733#M770</link>
      <description>&lt;P&gt;I would like to ask the community if perhaps someone has created a playbook that takes in Snort/Suricata alert data. I am looking a creating a automated block process that will compare an IDS alert with a Threat notification from the PAN. If the src_ip, src_port, dst_ip, dst_port and timestamp match and the firewall took no action on the threat. Then I will add the external src_ip to the Indicators database, make Verdict "suspicious", set Expiration Date to 30 days, add both the IDS and Threat log data to "Comments" to show reason for block, tag the new entry as "block_external_ips", "ids" and "pan threat". So that it gets added to the EDL that will be picked up by the Firewall. It would be helpful if someone had an IDS related playbook that they would be willing to share to start this process.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 29 Apr 2022 00:13:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/playbook-construction/m-p/483733#M770</guid>
      <dc:creator>jpadro</dc:creator>
      <dc:date>2022-04-29T00:13:26Z</dc:date>
    </item>
    <item>
      <title>Re: Playbook construction</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/playbook-construction/m-p/495416#M926</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/3134"&gt;@jpadro&lt;/a&gt;, this seems like something that you could also raise as a feature request in our Aha portal, to have such a playbook (or more likely something a bit more generic).&lt;/P&gt;&lt;P&gt;Our R&amp;amp;D team is always happy to receive suggestions for playbooks and other content items.&lt;/P&gt;&lt;P&gt;The portal is&amp;nbsp;&lt;SPAN&gt;&lt;A href="https://xsoar.ideas.aha.io/," target="_blank"&gt;https://xsoar.ideas.aha.io/&lt;/A&gt;, make sure to be as detailed as you can, and to not share any personal information as this is a public community.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 31 May 2022 13:12:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/playbook-construction/m-p/495416#M926</guid>
      <dc:creator>nkazinets</dc:creator>
      <dc:date>2022-05-31T13:12:26Z</dc:date>
    </item>
  </channel>
</rss>

