<?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: Parse JSON file from Emerging Threats rules. in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Parse-JSON-file-from-Emerging-Threats-rules/m-p/492737#M84238</link>
    <description>&lt;P&gt;Thanks.  &lt;/P&gt;

&lt;P&gt;Using it to provide details on the the ET rules sets I use on sensors.  Trying to tie in rules/usage/and details of the rules together.   Hoping that it gives a better view of the total rule sets instead of just loading the newest ones.  I want to see what they are, which are disabled, which are enabled, and what they do.  &lt;/P&gt;

&lt;P&gt;I have something like it being used for Snort Rules, just could not figure out how to use it for the ET Description.  Will give this a try soon.&lt;/P&gt;</description>
    <pubDate>Sun, 10 May 2020 05:16:24 GMT</pubDate>
    <dc:creator>xfaith</dc:creator>
    <dc:date>2020-05-10T05:16:24Z</dc:date>
    <item>
      <title>Parse JSON file from Emerging Threats rules.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Parse-JSON-file-from-Emerging-Threats-rules/m-p/492735#M84236</link>
      <description>&lt;P&gt;So I am trying to parse the description of the ET Rules which is downloaded as  &lt;CODE&gt;json.gz&lt;/CODE&gt; So it should be a JSON file but it's not taking the default JSON sourcetype, it's showing it as one file.  &lt;/P&gt;

&lt;P&gt;The beginning of the file starts with a {&lt;BR /&gt;
Its rule starts like this  "2012742":{&lt;/P&gt;

&lt;P&gt;And each rule ends like this: :"2012742"},&lt;/P&gt;

&lt;P&gt;I have tried to do line breaks, indexed  &lt;CODE&gt;extractions=json&lt;/CODE&gt;, &lt;BR /&gt;
I thought BREAK_AFTER= }, &lt;/P&gt;

&lt;P&gt;But I am not good with regex and so it's not working.&lt;/P&gt;

&lt;P&gt;Thanks for any assistance.&lt;/P&gt;</description>
      <pubDate>Fri, 08 May 2020 21:15:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Parse-JSON-file-from-Emerging-Threats-rules/m-p/492735#M84236</guid>
      <dc:creator>xfaith</dc:creator>
      <dc:date>2020-05-08T21:15:05Z</dc:date>
    </item>
    <item>
      <title>Re: Parse JSON file from Emerging Threats rules.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Parse-JSON-file-from-Emerging-Threats-rules/m-p/492736#M84237</link>
      <description>&lt;PRE&gt;&lt;CODE&gt;[ ET_json ]
CHARSET=UTF-8
INDEXED_EXTRACTIONS=none
KV_MODE=json
SHOULD_LINEMERGE=false
category=Structured
description=json
disabled=false
pulldown_type=true
LINE_BREAKER=(({|,)\"\d+\":){
SEDCMD-trim = s/}}/}/g
TRUNCATE=0
DATETIME_CONFIG=CURRENT
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;What do you use this data for? Please tell me.&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;creation date&lt;/CODE&gt; is better for &lt;CODE&gt;_time&lt;/CODE&gt; ,I think.&lt;BR /&gt;
but  you should modify &lt;EM&gt;indexes.conf&lt;/EM&gt;&lt;/P&gt;

&lt;P&gt;I don't know much about it, so I decided to stay in the present for now&lt;/P&gt;

&lt;P&gt;&lt;A href="https://conf.splunk.com/files/2017/slides/splunk-data-life-cycle-determining-when-and-where-to-roll-data.pdf"&gt;https://conf.splunk.com/files/2017/slides/splunk-data-life-cycle-determining-when-and-where-to-roll-data.pdf&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 08 May 2020 23:19:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Parse-JSON-file-from-Emerging-Threats-rules/m-p/492736#M84237</guid>
      <dc:creator>to4kawa</dc:creator>
      <dc:date>2020-05-08T23:19:43Z</dc:date>
    </item>
    <item>
      <title>Re: Parse JSON file from Emerging Threats rules.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Parse-JSON-file-from-Emerging-Threats-rules/m-p/492737#M84238</link>
      <description>&lt;P&gt;Thanks.  &lt;/P&gt;

&lt;P&gt;Using it to provide details on the the ET rules sets I use on sensors.  Trying to tie in rules/usage/and details of the rules together.   Hoping that it gives a better view of the total rule sets instead of just loading the newest ones.  I want to see what they are, which are disabled, which are enabled, and what they do.  &lt;/P&gt;

&lt;P&gt;I have something like it being used for Snort Rules, just could not figure out how to use it for the ET Description.  Will give this a try soon.&lt;/P&gt;</description>
      <pubDate>Sun, 10 May 2020 05:16:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Parse-JSON-file-from-Emerging-Threats-rules/m-p/492737#M84238</guid>
      <dc:creator>xfaith</dc:creator>
      <dc:date>2020-05-10T05:16:24Z</dc:date>
    </item>
  </channel>
</rss>

