<?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 ClamAV 'Last Scanned' and 'Definition Date' not populating in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/ClamAV-Last-Scanned-and-Definition-Date-not-populating/m-p/761983#M120641</link>
    <description>&lt;P&gt;Good morning everyone, first time poster and very much a novice Splunk user.&lt;/P&gt;&lt;P&gt;My colleague is currently having an issue with our cyber team's dashboards not populating with&amp;nbsp;ClamAV's Last Scanned and definition date properties. Currently, we're implementing&amp;nbsp; a temporary solution for having the definition dates populate properly, by manually setting the permissions to '644' on main.cvd, daily.cvd, and bytecode.cvd, and I think also for the database, via Ansible ad-hoc command.&amp;nbsp;Is this something I can fix my modifying the inputs.conf file? If so, what properties would I need to add?&amp;nbsp;&lt;/P&gt;&lt;P&gt;For the 'Last Scanned' problem, Splunk simply shows up with 'Not Found'. I'm unsure of how to address this one, so any starters would be great.&lt;/P&gt;&lt;P&gt;I should add, this Splunk Enterprise instance is on an air-gapped environment.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you all in advance&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 29 Jun 2026 14:10:16 GMT</pubDate>
    <dc:creator>jcanoy24</dc:creator>
    <dc:date>2026-06-29T14:10:16Z</dc:date>
    <item>
      <title>ClamAV 'Last Scanned' and 'Definition Date' not populating</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/ClamAV-Last-Scanned-and-Definition-Date-not-populating/m-p/761983#M120641</link>
      <description>&lt;P&gt;Good morning everyone, first time poster and very much a novice Splunk user.&lt;/P&gt;&lt;P&gt;My colleague is currently having an issue with our cyber team's dashboards not populating with&amp;nbsp;ClamAV's Last Scanned and definition date properties. Currently, we're implementing&amp;nbsp; a temporary solution for having the definition dates populate properly, by manually setting the permissions to '644' on main.cvd, daily.cvd, and bytecode.cvd, and I think also for the database, via Ansible ad-hoc command.&amp;nbsp;Is this something I can fix my modifying the inputs.conf file? If so, what properties would I need to add?&amp;nbsp;&lt;/P&gt;&lt;P&gt;For the 'Last Scanned' problem, Splunk simply shows up with 'Not Found'. I'm unsure of how to address this one, so any starters would be great.&lt;/P&gt;&lt;P&gt;I should add, this Splunk Enterprise instance is on an air-gapped environment.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you all in advance&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jun 2026 14:10:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/ClamAV-Last-Scanned-and-Definition-Date-not-populating/m-p/761983#M120641</guid>
      <dc:creator>jcanoy24</dc:creator>
      <dc:date>2026-06-29T14:10:16Z</dc:date>
    </item>
  </channel>
</rss>

