<?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 Re: SPLUNK SOAR Data Collection over Email in Splunk SOAR</title>
    <link>https://community.splunk.com/t5/Splunk-SOAR/SPLUNK-SOAR-Data-Collection-over-Email/m-p/684475#M1481</link>
    <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/265957"&gt;@harishlnu&lt;/a&gt;&amp;nbsp;one way I have done this in the past is to use 2 lots of automation.&amp;nbsp;&lt;/P&gt;&lt;P&gt;1st automation sends the email with a key nested in the HTML such as "SOARKEY=" and then add useful information to the other side, usually b64 encoded, at a minimum having the original container id in it. This sends the email and then stops automation.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then you ingest the replies (you may need to setup mail rules to push replies to SOAR emails into a dedicated inbox) using SOAR and look for the SOARKEY in the HTML Body, get the encoded string, decode and then &amp;lt;do something&amp;gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-- Hope this helps! Happy SOARing! --&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 17 Apr 2024 08:58:16 GMT</pubDate>
    <dc:creator>phanTom</dc:creator>
    <dc:date>2024-04-17T08:58:16Z</dc:date>
    <item>
      <title>SPLUNK SOAR Data Collection over Email</title>
      <link>https://community.splunk.com/t5/Splunk-SOAR/SPLUNK-SOAR-Data-Collection-over-Email/m-p/684473#M1480</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;I am having requirement where i need to send an email for approval, if they reply to that email i need to read that email and continue with next steps.&lt;/P&gt;&lt;P&gt;Could you please help me with your suggestions.&lt;BR /&gt;&lt;BR /&gt;Thanks in Advance&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Apr 2024 08:52:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-SOAR/SPLUNK-SOAR-Data-Collection-over-Email/m-p/684473#M1480</guid>
      <dc:creator>harishlnu</dc:creator>
      <dc:date>2024-04-17T08:52:10Z</dc:date>
    </item>
    <item>
      <title>Re: SPLUNK SOAR Data Collection over Email</title>
      <link>https://community.splunk.com/t5/Splunk-SOAR/SPLUNK-SOAR-Data-Collection-over-Email/m-p/684475#M1481</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/265957"&gt;@harishlnu&lt;/a&gt;&amp;nbsp;one way I have done this in the past is to use 2 lots of automation.&amp;nbsp;&lt;/P&gt;&lt;P&gt;1st automation sends the email with a key nested in the HTML such as "SOARKEY=" and then add useful information to the other side, usually b64 encoded, at a minimum having the original container id in it. This sends the email and then stops automation.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then you ingest the replies (you may need to setup mail rules to push replies to SOAR emails into a dedicated inbox) using SOAR and look for the SOARKEY in the HTML Body, get the encoded string, decode and then &amp;lt;do something&amp;gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-- Hope this helps! Happy SOARing! --&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Apr 2024 08:58:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-SOAR/SPLUNK-SOAR-Data-Collection-over-Email/m-p/684475#M1481</guid>
      <dc:creator>phanTom</dc:creator>
      <dc:date>2024-04-17T08:58:16Z</dc:date>
    </item>
  </channel>
</rss>

