<?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: admin can execute custom command even if it haven't access permission in local.meta in Security</title>
    <link>https://community.splunk.com/t5/Security/admin-can-execute-custom-command-even-if-it-haven-t-access/m-p/313942#M8211</link>
    <description>&lt;P&gt;It works perfectly!! Thank you&lt;/P&gt;</description>
    <pubDate>Tue, 11 Apr 2017 07:43:44 GMT</pubDate>
    <dc:creator>clagese</dc:creator>
    <dc:date>2017-04-11T07:43:44Z</dc:date>
    <item>
      <title>admin can execute custom command even if it haven't access permission in local.meta</title>
      <link>https://community.splunk.com/t5/Security/admin-can-execute-custom-command-even-if-it-haven-t-access/m-p/313934#M8203</link>
      <description>&lt;P&gt;I create a custom command to decrypt some field. This command should be executable only from a specific role can_decrypt.&lt;BR /&gt;
I set local.meta in this way:&lt;/P&gt;

&lt;P&gt;[commands/decryptuserdata]&lt;BR /&gt;
 access = read : [ can_decrypt ], write : [ can_decrypt ]&lt;BR /&gt;
 export = system&lt;BR /&gt;
 owner = nobody&lt;BR /&gt;
 version = 6.2.2&lt;BR /&gt;
 modtime = 1491468711.224921000&lt;/P&gt;

&lt;P&gt;Why can all users with admin role execute decryptuserdata command?&lt;BR /&gt;
Do I forget some setting for the command? or  Should I remove some capability from the admin role? &lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 13:33:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/admin-can-execute-custom-command-even-if-it-haven-t-access/m-p/313934#M8203</guid>
      <dc:creator>clagese</dc:creator>
      <dc:date>2020-09-29T13:33:46Z</dc:date>
    </item>
    <item>
      <title>Re: admin can execute custom command even if it haven't access permission in local.meta</title>
      <link>https://community.splunk.com/t5/Security/admin-can-execute-custom-command-even-if-it-haven-t-access/m-p/313935#M8204</link>
      <description>&lt;P&gt;Have you restarted splunk since you made the changes?  (Or restarted authentication via  Manager &amp;gt; Authentication?)&lt;/P&gt;</description>
      <pubDate>Thu, 06 Apr 2017 15:03:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/admin-can-execute-custom-command-even-if-it-haven-t-access/m-p/313935#M8204</guid>
      <dc:creator>DalJeanis</dc:creator>
      <dc:date>2017-04-06T15:03:14Z</dc:date>
    </item>
    <item>
      <title>Re: admin can execute custom command even if it haven't access permission in local.meta</title>
      <link>https://community.splunk.com/t5/Security/admin-can-execute-custom-command-even-if-it-haven-t-access/m-p/313936#M8205</link>
      <description>&lt;P&gt;Well that is the whole purpose of having an admin account, isn't it? Admin roles can access and modify all objects in the system, and this is assigned by capability &lt;CODE&gt;admin_all_objects&lt;/CODE&gt;. If you remove this then basically there are no admins at all.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;admin_all_objects   Access and modify any object in the system (user objects, search jobs, etc.). (**Overrides any limits set in the objects.**)
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 06 Apr 2017 15:18:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/admin-can-execute-custom-command-even-if-it-haven-t-access/m-p/313936#M8205</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2017-04-06T15:18:27Z</dc:date>
    </item>
    <item>
      <title>Re: admin can execute custom command even if it haven't access permission in local.meta</title>
      <link>https://community.splunk.com/t5/Security/admin-can-execute-custom-command-even-if-it-haven-t-access/m-p/313937#M8206</link>
      <description>&lt;P&gt;Hmmmm.  This is a data security issue.  If an admin has no defined business need to see decrypted information from those fields, then there ought to be a way to turn it off.  &lt;/P&gt;

&lt;P&gt;On the other hand, an admin may have a defined business need to determine whether the encryption/decryption is working properly, and to debug it if not.   If your organization is giving admin access on your system to very many people, then perhaps a derived admin role could be created for the ones which do not have such a business need. &lt;/P&gt;</description>
      <pubDate>Thu, 06 Apr 2017 15:41:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/admin-can-execute-custom-command-even-if-it-haven-t-access/m-p/313937#M8206</guid>
      <dc:creator>DalJeanis</dc:creator>
      <dc:date>2017-04-06T15:41:57Z</dc:date>
    </item>
    <item>
      <title>Re: admin can execute custom command even if it haven't access permission in local.meta</title>
      <link>https://community.splunk.com/t5/Security/admin-can-execute-custom-command-even-if-it-haven-t-access/m-p/313938#M8207</link>
      <description>&lt;P&gt;I'm agree, this is a data security issue. A splunk admin should not view decrypted business data.&lt;BR /&gt;
If I create a new semi-admin role without  admin_all_objects capability, users with this role actually cannot administer splunk because in the setting menu  disappear users,system and clustering sections.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 13:34:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/admin-can-execute-custom-command-even-if-it-haven-t-access/m-p/313938#M8207</guid>
      <dc:creator>clagese</dc:creator>
      <dc:date>2020-09-29T13:34:01Z</dc:date>
    </item>
    <item>
      <title>Re: admin can execute custom command even if it haven't access permission in local.meta</title>
      <link>https://community.splunk.com/t5/Security/admin-can-execute-custom-command-even-if-it-haven-t-access/m-p/313939#M8208</link>
      <description>&lt;P&gt;Thanks for your reply&lt;BR /&gt;
As work-around for my problem I would check roles of the current user within custom command.&lt;BR /&gt;
I use splunk.Intersplunk package to get splunk results in custom commands. How can I get the user is executing the command?&lt;/P&gt;</description>
      <pubDate>Fri, 07 Apr 2017 13:56:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/admin-can-execute-custom-command-even-if-it-haven-t-access/m-p/313939#M8208</guid>
      <dc:creator>clagese</dc:creator>
      <dc:date>2017-04-07T13:56:25Z</dc:date>
    </item>
    <item>
      <title>Re: admin can execute custom command even if it haven't access permission in local.meta</title>
      <link>https://community.splunk.com/t5/Security/admin-can-execute-custom-command-even-if-it-haven-t-access/m-p/313940#M8209</link>
      <description>&lt;P&gt;In one of my search commands, I have used this to get the user executing the search command. (just the portion of the code show below)&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;dispatch="/var/opt/splunk/var/run/splunk/dispatch"

disjuncts = []

try:
     results, dummyresults, settings = isp.getOrganizedResults()
     sid = settings.get("sid", None)

     p = subprocess.Popen('cat {0}/*{1}*/args.txt'.format(dispatch ,sid) , shell=True, stdout=subprocess.PIPE, stderr=subprocess.STDOUT)
     for line in p.stdout.readlines():
          if re.match('.*user=.*',line):
              user = line.split('=')[1]
              user = user.rstrip()
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 07 Apr 2017 14:23:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/admin-can-execute-custom-command-even-if-it-haven-t-access/m-p/313940#M8209</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2017-04-07T14:23:55Z</dc:date>
    </item>
    <item>
      <title>Re: admin can execute custom command even if it haven't access permission in local.meta</title>
      <link>https://community.splunk.com/t5/Security/admin-can-execute-custom-command-even-if-it-haven-t-access/m-p/313941#M8210</link>
      <description>&lt;P&gt;As &lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/15147"&gt;@somesoni2&lt;/a&gt; stated, this is due to the nature of the admin_all_objects capability. The only workaround to accomplish what you are looking to do, would be to setup a separate search head with the custom command, and only give accounts to that search head to those that should be able to decrypt the data. &lt;/P&gt;

&lt;P&gt;You may want to consider making it a corporate policy that only authorized individuals can execute the command. Then, leverage Splunk's built-in logging to periodically audit who is using it (since all searches executed get logged). &lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 13:35:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/admin-can-execute-custom-command-even-if-it-haven-t-access/m-p/313941#M8210</guid>
      <dc:creator>masonmorales</dc:creator>
      <dc:date>2020-09-29T13:35:09Z</dc:date>
    </item>
    <item>
      <title>Re: admin can execute custom command even if it haven't access permission in local.meta</title>
      <link>https://community.splunk.com/t5/Security/admin-can-execute-custom-command-even-if-it-haven-t-access/m-p/313942#M8211</link>
      <description>&lt;P&gt;It works perfectly!! Thank you&lt;/P&gt;</description>
      <pubDate>Tue, 11 Apr 2017 07:43:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/admin-can-execute-custom-command-even-if-it-haven-t-access/m-p/313942#M8211</guid>
      <dc:creator>clagese</dc:creator>
      <dc:date>2017-04-11T07:43:44Z</dc:date>
    </item>
  </channel>
</rss>

