<?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: Why aren't the severity numbers from Tenable in Splunk not matching the numbers in Security Center? in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-aren-t-the-severity-numbers-from-Tenable-in-Splunk-not/m-p/696670#M80977</link>
    <description>&lt;P&gt;Any solution for this issue?&lt;/P&gt;</description>
    <pubDate>Mon, 19 Aug 2024 07:35:06 GMT</pubDate>
    <dc:creator>itsGhisla1n</dc:creator>
    <dc:date>2024-08-19T07:35:06Z</dc:date>
    <item>
      <title>Why aren't the severity numbers from Tenable in Splunk not matching the numbers in Security Center?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-aren-t-the-severity-numbers-from-Tenable-in-Splunk-not/m-p/371637#M44889</link>
      <description>&lt;P&gt;We are using the add-on to ingest data from Nessus SecurityCenter into Splunk. However, the numbers do not match up. Week-long searches in SecurityCenter show numbers different from week-long searches in Splunk when we do a timechart. For example, on the day of the last scan, the numbers for critical and high are off by ~200, but the mediums are off by ~2500+. Is there something we can dedup by, or a way to get the numbers closer? We have little confidence in the accuracy of what's in Splunk since the numbers are so far off of what is in SecurityCenter&lt;/P&gt;</description>
      <pubDate>Mon, 30 Apr 2018 17:14:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-aren-t-the-severity-numbers-from-Tenable-in-Splunk-not/m-p/371637#M44889</guid>
      <dc:creator>bcyates</dc:creator>
      <dc:date>2018-04-30T17:14:26Z</dc:date>
    </item>
    <item>
      <title>Re: Why aren't the severity numbers from Tenable in Splunk not matching the numbers in Security Center?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-aren-t-the-severity-numbers-from-Tenable-in-Splunk-not/m-p/371638#M44890</link>
      <description>&lt;P&gt;Are your numbers in Splunk too high or too low? &lt;/P&gt;</description>
      <pubDate>Mon, 30 Apr 2018 18:31:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-aren-t-the-severity-numbers-from-Tenable-in-Splunk-not/m-p/371638#M44890</guid>
      <dc:creator>xpac</dc:creator>
      <dc:date>2018-04-30T18:31:33Z</dc:date>
    </item>
    <item>
      <title>Re: Why aren't the severity numbers from Tenable in Splunk not matching the numbers in Security Center?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-aren-t-the-severity-numbers-from-Tenable-in-Splunk-not/m-p/371639#M44891</link>
      <description>&lt;P&gt;It depends on the severity. Criticals and highs area little too low, but mediums are way too high&lt;/P&gt;</description>
      <pubDate>Mon, 30 Apr 2018 18:35:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-aren-t-the-severity-numbers-from-Tenable-in-Splunk-not/m-p/371639#M44891</guid>
      <dc:creator>bcyates</dc:creator>
      <dc:date>2018-04-30T18:35:33Z</dc:date>
    </item>
    <item>
      <title>Re: Why aren't the severity numbers from Tenable in Splunk not matching the numbers in Security Center?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-aren-t-the-severity-numbers-from-Tenable-in-Splunk-not/m-p/696670#M80977</link>
      <description>&lt;P&gt;Any solution for this issue?&lt;/P&gt;</description>
      <pubDate>Mon, 19 Aug 2024 07:35:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-aren-t-the-severity-numbers-from-Tenable-in-Splunk-not/m-p/696670#M80977</guid>
      <dc:creator>itsGhisla1n</dc:creator>
      <dc:date>2024-08-19T07:35:06Z</dc:date>
    </item>
  </channel>
</rss>

