<?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: How to extract a heavily nested JSON data? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-to-extract-a-heavily-nested-JSON-data/m-p/422743#M121391</link>
    <description>&lt;P&gt;Have you used the &lt;CODE&gt;| spath&lt;/CODE&gt; command to autoextract some of these values? This should do the majority of the work for you, but you may have to use &lt;CODE&gt;mvexpand&lt;/CODE&gt; as well. Check out &lt;CODE&gt;spath&lt;/CODE&gt; first though to see if it works for you.&lt;/P&gt;</description>
    <pubDate>Tue, 29 May 2018 19:40:13 GMT</pubDate>
    <dc:creator>Justinboucher0</dc:creator>
    <dc:date>2018-05-29T19:40:13Z</dc:date>
    <item>
      <title>How to extract a heavily nested JSON data?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-extract-a-heavily-nested-JSON-data/m-p/422742#M121390</link>
      <description>&lt;P&gt;Hey everyone,&lt;BR /&gt;
I am very new to Splunk and many of the examples I see use relatively simple data.  I am trying to extract certain fields for use in a mapping scheme. &lt;BR /&gt;
Here is the JSON format below:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; "cve" : {
      "data_type" : "CVE",
      "data_format" : "MITRE",
      "data_version" : "4.0",
      "CVE_data_meta" : {
        "ID" : "CVE-1999-0986",
        "ASSIGNER" : "cve@mitre.org"
      },
      "affects" : {
        "vendor" : {
          "vendor_data" : [ {
            "vendor_name" : "debian",
            "product" : {
              "product_data" : [ {
                "product_name" : "debian_linux",
                "version" : {
                  "version_data" : [ {
                    "version_value" : "2.1"
                  } ]
                }
              } ]
            }
          }, {
            "vendor_name" : "linux",
            "product" : {
              "product_data" : [ {
                "product_name" : "linux_kernel",
                "version" : {
                  "version_data" : [ {
                    "version_value" : "2.0"
                  }, {
                    "version_value" : "2.0.34"
                  }, {
                    "version_value" : "2.0.35"
                  }, {
                    "version_value" : "2.0.36"
                  }, {
                    "version_value" : "2.0.37"
                  }, {
                    "version_value" : "2.0.38"
                  } ]
                }
              } ]
            }
          }, {
            "vendor_name" : "redhat",
            "product" : {
              "product_data" : [ {
                "product_name" : "linux",
                "version" : {
                  "version_data" : [ {
                    "version_value" : "5.2"
                  } ]
                }
              } ]
            }
          } ]
        }
      },
      "problemtype" : {
        "problemtype_data" : [ {
          "description" : [ {
            "lang" : "en",
            "value" : "NVD-CWE-Other"
          } ]
        } ]
      },
      "references" : {
        "reference_data" : [ {
          "url" : "http://www.securityfocus.com/bid/870",
          "name" : "870",
          "refsource" : "BID"
        } ]
      },
      "description" : {
        "description_data" : [ {
          "lang" : "en",
          "value" : "The ping command in Linux 2.0.3x allows local users to cause a denial of service by sending large packets with the -R (record route) option."
        } ]
      }
    },
    "configurations" : {
      "CVE_data_version" : "4.0",
      "nodes" : [ {
        "operator" : "OR",
        "cpe" : [ {
          "vulnerable" : true,
          "cpe22Uri" : "cpe:/o:debian:debian_linux:2.1",
          "cpe23Uri" : "cpe:2.3:o:debian:debian_linux:2.1:*:*:*:*:*:*:*"
        }, {
          "vulnerable" : true,
          "cpe22Uri" : "cpe:/o:linux:linux_kernel:2.0",
          "cpe23Uri" : "cpe:2.3:o:linux:linux_kernel:2.0:*:*:*:*:*:*:*"
        }, {
          "vulnerable" : true,
          "cpe22Uri" : "cpe:/o:linux:linux_kernel:2.0.34",
          "cpe23Uri" : "cpe:2.3:o:linux:linux_kernel:2.0.34:*:*:*:*:*:*:*"
        }, {
          "vulnerable" : true,
          "cpe22Uri" : "cpe:/o:linux:linux_kernel:2.0.35",
          "cpe23Uri" : "cpe:2.3:o:linux:linux_kernel:2.0.35:*:*:*:*:*:*:*"
        }, {
          "vulnerable" : true,
          "cpe22Uri" : "cpe:/o:linux:linux_kernel:2.0.36",
          "cpe23Uri" : "cpe:2.3:o:linux:linux_kernel:2.0.36:*:*:*:*:*:*:*"
        }, {
          "vulnerable" : true,
          "cpe22Uri" : "cpe:/o:linux:linux_kernel:2.0.37",
          "cpe23Uri" : "cpe:2.3:o:linux:linux_kernel:2.0.37:*:*:*:*:*:*:*"
        }, {
          "vulnerable" : true,
          "cpe22Uri" : "cpe:/o:linux:linux_kernel:2.0.38",
          "cpe23Uri" : "cpe:2.3:o:linux:linux_kernel:2.0.38:*:*:*:*:*:*:*"
        }, {
          "vulnerable" : true,
          "cpe22Uri" : "cpe:/o:redhat:linux:5.2::i386",
          "cpe23Uri" : "cpe:2.3:o:redhat:linux:5.2:*:i386:*:*:*:*:*"
        } ]
      } ]
    },
    "impact" : {
      "baseMetricV2" : {
        "cvssV2" : {
          "version" : "2.0",
          "vectorString" : "(AV:N/AC:L/Au:N/C:N/I:N/A:P)",
          "accessVector" : "NETWORK",
          "accessComplexity" : "LOW",
          "authentication" : "NONE",
          "confidentialityImpact" : "NONE",
          "integrityImpact" : "NONE",
          "availabilityImpact" : "PARTIAL",
          "baseScore" : 5.0
        },
        "severity" : "MEDIUM",
        "exploitabilityScore" : 10.0,
        "impactScore" : 2.9,
        "obtainAllPrivilege" : false,
        "obtainUserPrivilege" : false,
        "obtainOtherPrivilege" : false,
        "userInteractionRequired" : false
      }
    },
    "publishedDate" : "1999-12-08T05:00Z",
    "lastModifiedDate" : "2008-09-09T12:36Z"
  }
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Essentially the data I am trying to group together would ideally look like this for example:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;vendor: debian        product_name: debian_linux       version_value:2.1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;And to have this repeat in the case that there are additional versions, I've tried using mvexpand but this ends up with duplicates as well getting version_value for other products. Any insight would be much appreciated &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 29 May 2018 18:47:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-extract-a-heavily-nested-JSON-data/m-p/422742#M121390</guid>
      <dc:creator>LunarLlama</dc:creator>
      <dc:date>2018-05-29T18:47:39Z</dc:date>
    </item>
    <item>
      <title>Re: How to extract a heavily nested JSON data?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-extract-a-heavily-nested-JSON-data/m-p/422743#M121391</link>
      <description>&lt;P&gt;Have you used the &lt;CODE&gt;| spath&lt;/CODE&gt; command to autoextract some of these values? This should do the majority of the work for you, but you may have to use &lt;CODE&gt;mvexpand&lt;/CODE&gt; as well. Check out &lt;CODE&gt;spath&lt;/CODE&gt; first though to see if it works for you.&lt;/P&gt;</description>
      <pubDate>Tue, 29 May 2018 19:40:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-extract-a-heavily-nested-JSON-data/m-p/422743#M121391</guid>
      <dc:creator>Justinboucher0</dc:creator>
      <dc:date>2018-05-29T19:40:13Z</dc:date>
    </item>
  </channel>
</rss>

