<?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 Help: Syslog and Matching Security Event Log in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Search-Help-Syslog-and-Matching-Security-Event-Log/m-p/21064#M3387</link>
    <description>&lt;P&gt;Try this. I didn't know much about what you were looking for, so you will need to insert your original search for syslog data where I have indicated &lt;CODE&gt;&amp;lt;search for syslog data&amp;gt;&lt;/CODE&gt;. Ditto for the login search. Don't include the &amp;lt;&amp;gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;search for login data&amp;gt; [search &amp;lt;search for syslogdata&amp;gt; | stats latest(_time) as latestTime 
| eval earliest=relative_time(latestTime, "-5m") |  eval latest=relative_time(latestTIme, "+5m") | fields + earliest latest]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This technique uses a subsearch to look for the syslog data. If found, it extracts the most recent time from the results and calculates a time range that begins 5 minutes before that time and ends 5 minutes after that time. The time range is then returned to the outer search. This leverages the fact that &lt;STRONG&gt;earliest&lt;/STRONG&gt; and &lt;STRONG&gt;latest&lt;/STRONG&gt; are actually parameters that set the search time range.&lt;/P&gt;

&lt;P&gt;Look at the docs about &lt;A href="http://docs.splunk.com/Documentation/Splunk/4.3/User/HowSubsearchesWork"&gt;Subsearches&lt;/A&gt; for more info.&lt;/P&gt;</description>
    <pubDate>Fri, 02 Mar 2012 04:34:42 GMT</pubDate>
    <dc:creator>lguinn2</dc:creator>
    <dc:date>2012-03-02T04:34:42Z</dc:date>
    <item>
      <title>Search Help: Syslog and Matching Security Event Log</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-Help-Syslog-and-Matching-Security-Event-Log/m-p/21063#M3386</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I am hoping to be able to right a search that does the following:&lt;/P&gt;

&lt;P&gt;searches syslog data from a router. If criteria are met, look for login data on a specific server in a time window around the time of the syslog traffic.&lt;/P&gt;

&lt;P&gt;We have some remote routers that are watched for SSL traffic. If criteria are met, I would like to get logins on a specific server (the only server with a route to these routers) for say, 10 minutes prior to the SSL Traffic. Not only am I not sure how to structure such a search, but the SSL traffic generates numerous syslog packets when hitting the router and I don't want to do the Securtiy Event Log lookup for each packet.&lt;/P&gt;

&lt;P&gt;Thanks for any guidance.&lt;/P&gt;

&lt;P&gt;Kevin&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jul 2010 21:51:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-Help-Syslog-and-Matching-Security-Event-Log/m-p/21063#M3386</guid>
      <dc:creator>kholleran</dc:creator>
      <dc:date>2010-07-27T21:51:39Z</dc:date>
    </item>
    <item>
      <title>Re: Search Help: Syslog and Matching Security Event Log</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-Help-Syslog-and-Matching-Security-Event-Log/m-p/21064#M3387</link>
      <description>&lt;P&gt;Try this. I didn't know much about what you were looking for, so you will need to insert your original search for syslog data where I have indicated &lt;CODE&gt;&amp;lt;search for syslog data&amp;gt;&lt;/CODE&gt;. Ditto for the login search. Don't include the &amp;lt;&amp;gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;search for login data&amp;gt; [search &amp;lt;search for syslogdata&amp;gt; | stats latest(_time) as latestTime 
| eval earliest=relative_time(latestTime, "-5m") |  eval latest=relative_time(latestTIme, "+5m") | fields + earliest latest]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This technique uses a subsearch to look for the syslog data. If found, it extracts the most recent time from the results and calculates a time range that begins 5 minutes before that time and ends 5 minutes after that time. The time range is then returned to the outer search. This leverages the fact that &lt;STRONG&gt;earliest&lt;/STRONG&gt; and &lt;STRONG&gt;latest&lt;/STRONG&gt; are actually parameters that set the search time range.&lt;/P&gt;

&lt;P&gt;Look at the docs about &lt;A href="http://docs.splunk.com/Documentation/Splunk/4.3/User/HowSubsearchesWork"&gt;Subsearches&lt;/A&gt; for more info.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Mar 2012 04:34:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-Help-Syslog-and-Matching-Security-Event-Log/m-p/21064#M3387</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2012-03-02T04:34:42Z</dc:date>
    </item>
  </channel>
</rss>

