<?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 multiple indexes role-based access control in Security</title>
    <link>https://community.splunk.com/t5/Security/multiple-indexes-role-based-access-control/m-p/39635#M1312</link>
    <description>&lt;P&gt;I want to limit some users to view and search only certain data. I used multiple indexes access control.&lt;/P&gt;

&lt;P&gt;In the "authorize.conf" which located in "\Splunk\etc\system\local", it reads&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[role_c5viewer]
importRoles = user
rtSrchJobsQuota = 0
rtsearch = enabled
srchDiskQuota = 0
srchIndexesAllowed = c5only
srchIndexesDefault = c5only
srchJobsQuota = 0
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;If I logged as one user assigned role "c5viewer," I can only see data indexed by c5only in the search summary page. But If I put&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index="r2only"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;in the search bar, I  can still retrieve data indexed by r2only (a different index). The results come with all the data indexed by "r2only"&lt;/P&gt;

&lt;P&gt;Any thoughts how to enforce access control, i.e., prevent c5viewer to see data indexed by r2only? Did I put authorize.conf in the right directory?&lt;/P&gt;</description>
    <pubDate>Sat, 05 Feb 2011 07:03:42 GMT</pubDate>
    <dc:creator>myli12</dc:creator>
    <dc:date>2011-02-05T07:03:42Z</dc:date>
    <item>
      <title>multiple indexes role-based access control</title>
      <link>https://community.splunk.com/t5/Security/multiple-indexes-role-based-access-control/m-p/39635#M1312</link>
      <description>&lt;P&gt;I want to limit some users to view and search only certain data. I used multiple indexes access control.&lt;/P&gt;

&lt;P&gt;In the "authorize.conf" which located in "\Splunk\etc\system\local", it reads&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[role_c5viewer]
importRoles = user
rtSrchJobsQuota = 0
rtsearch = enabled
srchDiskQuota = 0
srchIndexesAllowed = c5only
srchIndexesDefault = c5only
srchJobsQuota = 0
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;If I logged as one user assigned role "c5viewer," I can only see data indexed by c5only in the search summary page. But If I put&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index="r2only"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;in the search bar, I  can still retrieve data indexed by r2only (a different index). The results come with all the data indexed by "r2only"&lt;/P&gt;

&lt;P&gt;Any thoughts how to enforce access control, i.e., prevent c5viewer to see data indexed by r2only? Did I put authorize.conf in the right directory?&lt;/P&gt;</description>
      <pubDate>Sat, 05 Feb 2011 07:03:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/multiple-indexes-role-based-access-control/m-p/39635#M1312</guid>
      <dc:creator>myli12</dc:creator>
      <dc:date>2011-02-05T07:03:42Z</dc:date>
    </item>
    <item>
      <title>Re: multiple indexes role-based access control</title>
      <link>https://community.splunk.com/t5/Security/multiple-indexes-role-based-access-control/m-p/39636#M1313</link>
      <description>&lt;P&gt;Judging by your "importRoles=user" statement, it looks like the &lt;STRONG&gt;c5viewer&lt;/STRONG&gt; role is inheriting indexes from the &lt;STRONG&gt;user&lt;/STRONG&gt; role.&lt;/P&gt;

&lt;P&gt;You should add the following to your $SPLUNK_HOME/etc/system/local/authorize.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[role_user]
srchIndexesAllowed = 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;By not having an entry for the &lt;STRONG&gt;user&lt;/STRONG&gt; role in your file, it grants default access to all non-internal indexes.  Adding this stanza is a safer method than simply removing your "importRoles=user" statement.&lt;/P&gt;

&lt;P&gt;For future reference, you can go to &lt;STRONG&gt;Manager--&amp;gt;Access Controls--&amp;gt;Roles&lt;/STRONG&gt; to manage these properties in the UI, rather than build the file by hand.&lt;/P&gt;</description>
      <pubDate>Sat, 05 Feb 2011 07:16:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/multiple-indexes-role-based-access-control/m-p/39636#M1313</guid>
      <dc:creator>Ron_Naken</dc:creator>
      <dc:date>2011-02-05T07:16:42Z</dc:date>
    </item>
  </channel>
</rss>

