<?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: Search Proofpoint Logs in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Search-Proofpoint-Logs/m-p/27069#M177706</link>
    <description>&lt;P&gt;Thanks Kristian, I'll look into your recommendations.   To answer your questions:&lt;/P&gt;

&lt;P&gt;yes, it is the same set of events, all emails,  s=ssssss    is a session identifier,  m=mm   is a particulater email/message.  There can be (and are) multiple emails associated with a session.   There are a lot more log entries per each email, but I condensed it to the fields I want to pull.&lt;BR /&gt;
Thanks again.&lt;/P&gt;</description>
    <pubDate>Wed, 08 May 2013 19:05:41 GMT</pubDate>
    <dc:creator>RB5</dc:creator>
    <dc:date>2013-05-08T19:05:41Z</dc:date>
    <item>
      <title>Search Proofpoint Logs</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-Proofpoint-Logs/m-p/27067#M177704</link>
      <description>&lt;P&gt;Hi, I was hoping to get help for a search.  I haven't had much time to spend on it so I apoligize for not trying harder 1st.&lt;/P&gt;

&lt;P&gt;I've started out with below, but both searches only return 2 results, even though there are over 1K log entries of the same format.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=xyz | transaction startswith="cmd=connect" endswith="cmd=disconnect" 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;OR: &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=xyz * | transaction s,m maxspan=301s startswith="mod=session cmd=connect" endswith="mod=session cmd=disconnect"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I want to pull items such as value=&lt;A href="mailto:abc@xyz.com" target="_blank"&gt;abc@xyz.com&lt;/A&gt;   where have  cmd=env_rcpt,   value=&lt;A href="mailto:uvh@gmail.com" target="_blank"&gt;uvh@gmail.com&lt;/A&gt; where have cmd=env_from and pull 'subject' and various scores, &lt;BR /&gt;
like '3'  from:   suspectscore=3&lt;/P&gt;

&lt;P&gt;The log entries are of the format below.&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[2011-10-23 16:05:59.502387 +0000] rprt s=10kch03n9t mod=session cmd=connect ip=209.85.210.182  perlwait=0.085
[2011-10-23 16:06:26.251606 +0000] rprt s=10kch03n9t m=3 x=p9NG5xMt010615 mod=mail cmd=env_from value=uvh@gmail.com qid=p9NG5xMt010615  ip=209.85.210.182
[2011-10-23 16:06:26.405437 +0000] rprt s=10kch03n9t m=3 x=p9NG5xMt010615 mod=mail cmd=env_rcpt r=1 value=abc@xyz.com verified= routes=
[2011-10-23 16:06:26.875486 +0000] rprt s=10kch03n9t m=3 x=p9NG5xMt010615 mod=spam cmd=run score=0 spamscore=0 ipscore=0 suspectscore=3 phishscore=0 bulkscore=0 adultscore=0 duration=0.091
[2011-10-23 16:06:26.879828 +0000] rprt s=10kch03n9t m=3 x=p9NG5xMt010615 mod=mail cmd=msg module=spf rule=pass action=continue attachments=0 rcpts=1 subject="Hi" spamscore=0
[2011-10-23 16:06:56.927722 +0000] rprt s=10kch03n9t mod=session cmd=disconnect module= rule= action= helo=mail-iy0-f182.google.com msgs=3 rcpts=3 routes= duration=1.119 elapsed=57.43

[2011-10-23 17:05:59.502387 +0000] rprt s=10kch03n9t mod=session cmd=connect ip=209.85.210.182  perlwait=0.085
[2011-10-23 17:06:26.251606 +0000] rprt s=10kch03n9t m=3 x=p9NG5xMt010615 mod=mail cmd=env_from value=xyz@hotmail.com qid=p9NG5xMt010615  ip=209.85.210.182
[2011-10-23 17:06:26.405437 +0000] rprt s=10kch03n9t m=3 x=p9NG5xMt010615 mod=mail cmd=env_rcpt r=1 value=123@xyz.com verified= routes=
[2011-10-23 17:06:26.875486 +0000] rprt s=10kch03n9t m=3 x=p9NG5xMt010615 mod=spam cmd=run score=0 spamscore=0 ipscore=0 suspectscore=3 phishscore=0 bulkscore=0 adultscore=0 duration=0.091
[2011-10-23 17:06:26.879828 +0000] rprt s=10kch03n9t m=3 x=p9NG5xMt010615 mod=mail cmd=msg module=spf rule=pass action=continue attachments=0 rcpts=1 subject="Hi" spamscore=0
[2011-10-23 17:06:56.927722 +0000] rprt s=10kch03n9t mod=session cmd=disconnect module= rule= action= helo=mail-iy0-f182.google.com msgs=3 rcpts=3 routes= duration=1.119 elapsed=57.43

[2011-10-23 18:05:59.502387 +0000] rprt s=10kch03n9t mod=session cmd=connect ip=209.85.210.182  perlwait=0.085
[2011-10-23 18:06:26.251606 +0000] rprt s=10kch03n9t m=3 x=p9NG5xMt010615 mod=mail cmd=env_from value=123@gmail.com qid=p9NG5xMt010615  ip=209.85.210.182
[2011-10-23 18:06:26.405437 +0000] rprt s=10kch03n9t m=3 x=p9NG5xMt010615 mod=mail cmd=env_rcpt r=1 value=xxtt@xyz.com verified= routes=
[2011-10-23 18:06:26.875486 +0000] rprt s=10kch03n9t m=3 x=p9NG5xMt010615 mod=spam cmd=run score=0 spamscore=0 ipscore=0 suspectscore=3 phishscore=0 bulkscore=0 adultscore=0 duration=0.091
[2011-10-23 18:06:26.879828 +0000] rprt s=10kch03n9t m=3 x=p9NG5xMt010615 mod=mail cmd=msg module=spf rule=pass action=continue attachments=0 rcpts=1 subject="Hi" spamscore=0
[2011-10-23 18:06:56.927722 +0000] rprt s=10kch03n9t mod=session cmd=disconnect module= rule= action= helo=mail-iy0-f182.google.com msgs=3 rcpts=3 routes= duration=1.119 elapsed=57.43
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 28 Sep 2020 13:51:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-Proofpoint-Logs/m-p/27067#M177704</guid>
      <dc:creator>RB5</dc:creator>
      <dc:date>2020-09-28T13:51:23Z</dc:date>
    </item>
    <item>
      <title>Re: Search Proofpoint Logs</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-Proofpoint-Logs/m-p/27068#M177705</link>
      <description>&lt;P&gt;You are aware of what the &lt;CODE&gt;transaction&lt;/CODE&gt; command is supposed to be doing, right? It will bundle all events matching the conditions into transactions. The result will be a new multi-line event for each transaction. &lt;/P&gt;

&lt;P&gt;In your first query, you'd probably get the wrong transaction-events, as the only condition is connect/disconnect - regardless of any other data in the events. It &lt;EM&gt;may&lt;/EM&gt; be ok for something very sequential in nature, where sessions do not intermingle. But for some kind of webserver log, it would be meaningless.&lt;/P&gt;

&lt;P&gt;So, what are the events you have listed? It looks like it the same set of events repeated 3 times. &lt;/P&gt;

&lt;P&gt;Is &lt;CODE&gt;s&lt;/CODE&gt; some kind of session identifier? (in respect to the sessions of the spamfilter(?))&lt;BR /&gt;
What is &lt;CODE&gt;m&lt;/CODE&gt;? Why is that important?&lt;BR /&gt;
It seems like &lt;CODE&gt;x&lt;/CODE&gt; is present on all lines that you're interested in. &lt;/P&gt;

&lt;P&gt;There is a bit of a problem when the logging application write logs in the style of &lt;CODE&gt;key=&amp;lt;key&amp;gt; value=&amp;lt;value&amp;gt;&lt;/CODE&gt;, instead of &lt;CODE&gt;&amp;lt;key&amp;gt;=&amp;lt;value&amp;gt;&lt;/CODE&gt;, since the field &lt;CODE&gt;value&lt;/CODE&gt; will be ambiguous. For this exercise, we'll use &lt;CODE&gt;rex&lt;/CODE&gt; to do the extraction as part of the search.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=xyz 
| rex "env_from\s+value=(?&amp;lt;sender&amp;gt;\S+)" 
| rex "env_rcpt\s+r=\d+value=(?&amp;lt;receiver&amp;gt;\S+)"
| transaction s maxspan=5m
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This should build the transaction that you're looking for. However, there might be a simpler way by using &lt;CODE&gt;stats&lt;/CODE&gt;. &lt;CODE&gt;stats&lt;/CODE&gt; is cheaper than &lt;CODE&gt;transaction&lt;/CODE&gt; in terms of execution costs. Modify the query below to fit your own needs.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=xyz 
| rex "env_from\s+value=(?&amp;lt;sender&amp;gt;\S+)" 
| rex "env_rcpt\s+r=\d+value=(?&amp;lt;receiver&amp;gt;\S+)"
| stats list(sender) as Sender values(receiver) as Receivers first(subject) as Subject max(suspectscore) as SuspectScore by s
| where SuspectScore&amp;gt;2
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Hope this helps,&lt;/P&gt;

&lt;P&gt;Kristian&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2013 08:24:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-Proofpoint-Logs/m-p/27068#M177705</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-05-08T08:24:36Z</dc:date>
    </item>
    <item>
      <title>Re: Search Proofpoint Logs</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-Proofpoint-Logs/m-p/27069#M177706</link>
      <description>&lt;P&gt;Thanks Kristian, I'll look into your recommendations.   To answer your questions:&lt;/P&gt;

&lt;P&gt;yes, it is the same set of events, all emails,  s=ssssss    is a session identifier,  m=mm   is a particulater email/message.  There can be (and are) multiple emails associated with a session.   There are a lot more log entries per each email, but I condensed it to the fields I want to pull.&lt;BR /&gt;
Thanks again.&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2013 19:05:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-Proofpoint-Logs/m-p/27069#M177706</guid>
      <dc:creator>RB5</dc:creator>
      <dc:date>2013-05-08T19:05:41Z</dc:date>
    </item>
    <item>
      <title>Re: Search Proofpoint Logs</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-Proofpoint-Logs/m-p/27070#M177707</link>
      <description>&lt;P&gt;Proofpoint now has a beta app that will allow you report on and visualze your Proofpoint Protection Server and TAP data! Check out the new app here:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://splunkbase.splunk.com/app/3727/#/details"&gt;https://splunkbase.splunk.com/app/3727/#/details&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Be sure to follow the instructions listed in the details to get all the needed TA's etc that the app needs to work correctly.&lt;/P&gt;

&lt;P&gt;There are pre-built dashboards to aid in searching for message events.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Oct 2017 02:34:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-Proofpoint-Logs/m-p/27070#M177707</guid>
      <dc:creator>eckolp2003</dc:creator>
      <dc:date>2017-10-12T02:34:26Z</dc:date>
    </item>
  </channel>
</rss>

