<?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 audit the admin activities on Splunk ? in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/How-to-audit-the-admin-activities-on-Splunk/m-p/400008#M3410</link>
    <description>&lt;P&gt;Yes, auditing Splunk is a challenge.  However, if you think the audit log is noisy, you're not going to like this answer.  The data you want is not in _audit, but in _internal.  For example, this query will help you find out who deleted a dashboard.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=_internal sourcetype=splunkd_ui_access method=DELETE views 
| rex field=uri_path "\/[-\w]+\/\w+\/[_\w]+\/\w+\/(?&amp;lt;User&amp;gt;[^\/]+)\/(?&amp;lt;App&amp;gt;[^\/]+)\/data\/ui\/views\/(?&amp;lt;Dashboard&amp;gt;[^\?]+)" 
| table _time App Dashboard User
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Thu, 18 Jul 2019 13:01:47 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2019-07-18T13:01:47Z</dc:date>
    <item>
      <title>How to audit the admin activities on Splunk ?</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/How-to-audit-the-admin-activities-on-Splunk/m-p/400007#M3409</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I have read the document, but the audit log of splunk seems very noisy....&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.3.0/Security/AuditSplunkactivity" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/7.3.0/Security/AuditSplunkactivity&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;My manager want me to show the admin activities of splunk .&lt;BR /&gt;
For example:&lt;BR /&gt;
Who and when they add data inputs , add user , Modify scheduled search , modified dashboard ....&lt;/P&gt;

&lt;P&gt;I tried to search on the _audit index to find the answer , but the data is too noisy to do so... It recorded a lot of activities that we don't understand and we have not done. &lt;BR /&gt;
For example :&lt;BR /&gt;
There is a lot of edit_user action for "admin"&lt;/P&gt;

&lt;P&gt;&lt;EM&gt;Audit:[timestamp=07-18-2019 18:39:34.616, user=admin, action=edit_user, info=granted object="admin" operation=edit][n/a]&lt;/EM&gt;&lt;/P&gt;

&lt;P&gt;But we haven't  edited the admin account during these time !?&lt;/P&gt;

&lt;P&gt;It is weird that we use Splunk to audit other system, but  it is hard to audit the activities on Splunk itself....&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 01:24:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/How-to-audit-the-admin-activities-on-Splunk/m-p/400007#M3409</guid>
      <dc:creator>leo_systex</dc:creator>
      <dc:date>2020-09-30T01:24:35Z</dc:date>
    </item>
    <item>
      <title>Re: How to audit the admin activities on Splunk ?</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/How-to-audit-the-admin-activities-on-Splunk/m-p/400008#M3410</link>
      <description>&lt;P&gt;Yes, auditing Splunk is a challenge.  However, if you think the audit log is noisy, you're not going to like this answer.  The data you want is not in _audit, but in _internal.  For example, this query will help you find out who deleted a dashboard.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=_internal sourcetype=splunkd_ui_access method=DELETE views 
| rex field=uri_path "\/[-\w]+\/\w+\/[_\w]+\/\w+\/(?&amp;lt;User&amp;gt;[^\/]+)\/(?&amp;lt;App&amp;gt;[^\/]+)\/data\/ui\/views\/(?&amp;lt;Dashboard&amp;gt;[^\?]+)" 
| table _time App Dashboard User
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 18 Jul 2019 13:01:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/How-to-audit-the-admin-activities-on-Splunk/m-p/400008#M3410</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2019-07-18T13:01:47Z</dc:date>
    </item>
  </channel>
</rss>

