<?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 does role composition work? in Security</title>
    <link>https://community.splunk.com/t5/Security/How-does-role-composition-work/m-p/153424#M4641</link>
    <description>&lt;P&gt;Yikes - I would not suggest 500 indexes! This would surely make searches much longer and negate any performance benefits I mentioned. And it would of course make things at least as complicated to manage.&lt;/P&gt;

&lt;P&gt;I think you have a great counter example to my suggestions!&lt;/P&gt;</description>
    <pubDate>Tue, 26 Nov 2013 15:28:30 GMT</pubDate>
    <dc:creator>lguinn2</dc:creator>
    <dc:date>2013-11-26T15:28:30Z</dc:date>
    <item>
      <title>How does role composition work?</title>
      <link>https://community.splunk.com/t5/Security/How-does-role-composition-work/m-p/153420#M4637</link>
      <description>&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0/Security/Aboutusersandroles#How_users_inherit_search_filter_restrictions" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/6.0/Security/Aboutusersandroles#How_users_inherit_search_filter_restrictions&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;I read the blurb above, but still find myself with questions.&lt;/P&gt;

&lt;P&gt;Not using inheritance, but rather composition.&lt;/P&gt;

&lt;P&gt;What would I expect to happen if:&lt;/P&gt;

&lt;P&gt;Role A :  gives search on index XYZ, with search filter "source=XYZ_App1"&lt;BR /&gt;
Role B :  gives search on index XYZ, with search filter "source=XYZ_App2"&lt;BR /&gt;
Role C :  gives search on index XYZ, with no search filter &lt;BR /&gt;
Role D :  gives search on index 123, with search filter "source=123_test"&lt;BR /&gt;
Role E :  gives search on index XYZ, with search filter source=XYZ_App1 ERROR&lt;BR /&gt;
Role F :  gives search on index 123, with search filter source=123_test INFO&lt;/P&gt;

&lt;P&gt;User1 is assigned Role A and Role B&lt;BR /&gt;
User2 is assigned Role A and Role C&lt;BR /&gt;
User3 is assigned Role A and Role D&lt;BR /&gt;
User4 is assigned Role E and Role F&lt;/P&gt;

&lt;P&gt;What will the effective search filter be for these users?&lt;/P&gt;

&lt;P&gt;Any advice in the way of gotchas around composing roles?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 15:21:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-does-role-composition-work/m-p/153420#M4637</guid>
      <dc:creator>juniormint</dc:creator>
      <dc:date>2020-09-28T15:21:09Z</dc:date>
    </item>
    <item>
      <title>Re: How does role composition work?</title>
      <link>https://community.splunk.com/t5/Security/How-does-role-composition-work/m-p/153421#M4638</link>
      <description>&lt;PRE&gt;&lt;CODE&gt;User1 filter (source=XYZ_App1 OR source=XYZ_App2)
User2 filter (source=* OR source=XYZ_App1)
User3 filter (source=XYZ_App1 OR source=123_test)
User4 filter ((source=XYZ_App1 AND ERROR) OR (source=123_test AND INFO))

Applied to whatever combined set of indexed the roles can search.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 26 Nov 2013 03:17:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-does-role-composition-work/m-p/153421#M4638</guid>
      <dc:creator>juniormint</dc:creator>
      <dc:date>2013-11-26T03:17:36Z</dc:date>
    </item>
    <item>
      <title>Re: How does role composition work?</title>
      <link>https://community.splunk.com/t5/Security/How-does-role-composition-work/m-p/153422#M4639</link>
      <description>&lt;P&gt;My suggestion: try not to use search filters for composing roles. &lt;/P&gt;

&lt;P&gt;Use indexes to segregate data by visibility as much as possible. For example, &lt;/P&gt;

&lt;P&gt;The networking team should see only firewall data&lt;BR /&gt;&lt;BR /&gt;
The ops team should see only server data&lt;BR /&gt;&lt;BR /&gt;
The security team can see all data&lt;/P&gt;

&lt;P&gt;Then create 2 indexes: network and server. Give the networking role access to its index, and ditto for the ops role. Give the security role access to both indexes.&lt;/P&gt;

&lt;P&gt;Why is this better?  I can think of a few reasons off-hand&lt;BR /&gt;&lt;BR /&gt;
1 - It is a lot easier to understand and manage than a bunch of filters OR'ed together&lt;BR /&gt;&lt;BR /&gt;
2 - Searches will run faster because they are not applying extra criteria or examining unnecessary data&lt;BR /&gt;&lt;BR /&gt;
3 - Different levels of data security (such as encryption) can be applied to indexes  &lt;/P&gt;

&lt;P&gt;Is this always the best answer? No. Having 30 little indexes doesn't work either. But I try to avoid search filters as much as practical.&lt;/P&gt;

&lt;P&gt;Important: Roles inherit BOTH capabilities and index visibility. Example: Given the roles above, I want to create a new role for the web team. They will have the same capabilities as the security role, so I create the web role as inheriting from the security role -&amp;gt; I just gave the web role access to the network and server indexes! So be aware of this, no matter how you chose to set up your roles.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Nov 2013 03:35:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-does-role-composition-work/m-p/153422#M4639</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2013-11-26T03:35:45Z</dc:date>
    </item>
    <item>
      <title>Re: How does role composition work?</title>
      <link>https://community.splunk.com/t5/Security/How-does-role-composition-work/m-p/153423#M4640</link>
      <description>&lt;P&gt;@lguinn: It's a balance though.  My use case is that I will have many sources (&amp;gt;500), each with potentially different and overlapping sets of users with search access. &lt;/P&gt;

&lt;P&gt;The daily data rate for each source is between 0 and about 10000 events. &lt;/P&gt;

&lt;P&gt;Generally, events are only relevant for a day or two...so historical searches are the exception.&lt;/P&gt;

&lt;P&gt;Should I really set up 500 indexes? Or would one index with all of the sources be better?&lt;/P&gt;</description>
      <pubDate>Tue, 26 Nov 2013 13:13:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-does-role-composition-work/m-p/153423#M4640</guid>
      <dc:creator>juniormint</dc:creator>
      <dc:date>2013-11-26T13:13:30Z</dc:date>
    </item>
    <item>
      <title>Re: How does role composition work?</title>
      <link>https://community.splunk.com/t5/Security/How-does-role-composition-work/m-p/153424#M4641</link>
      <description>&lt;P&gt;Yikes - I would not suggest 500 indexes! This would surely make searches much longer and negate any performance benefits I mentioned. And it would of course make things at least as complicated to manage.&lt;/P&gt;

&lt;P&gt;I think you have a great counter example to my suggestions!&lt;/P&gt;</description>
      <pubDate>Tue, 26 Nov 2013 15:28:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-does-role-composition-work/m-p/153424#M4641</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2013-11-26T15:28:30Z</dc:date>
    </item>
    <item>
      <title>Re: How does role composition work?</title>
      <link>https://community.splunk.com/t5/Security/How-does-role-composition-work/m-p/153425#M4642</link>
      <description>&lt;P&gt;@lguinn: Am I missing functionality or approaches that handle large numbers of sources with different access groups better?&lt;/P&gt;</description>
      <pubDate>Tue, 26 Nov 2013 16:05:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-does-role-composition-work/m-p/153425#M4642</guid>
      <dc:creator>juniormint</dc:creator>
      <dc:date>2013-11-26T16:05:20Z</dc:date>
    </item>
    <item>
      <title>Re: How does role composition work?</title>
      <link>https://community.splunk.com/t5/Security/How-does-role-composition-work/m-p/153426#M4643</link>
      <description>&lt;P&gt;Upvoting because @lguinn's comments seem very relevant...and probably accurate&lt;/P&gt;</description>
      <pubDate>Tue, 26 Nov 2013 16:06:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-does-role-composition-work/m-p/153426#M4643</guid>
      <dc:creator>juniormint</dc:creator>
      <dc:date>2013-11-26T16:06:23Z</dc:date>
    </item>
    <item>
      <title>Re: How does role composition work?</title>
      <link>https://community.splunk.com/t5/Security/How-does-role-composition-work/m-p/153427#M4644</link>
      <description>&lt;P&gt;I think this is literally the answer to my primary question.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Nov 2013 16:06:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-does-role-composition-work/m-p/153427#M4644</guid>
      <dc:creator>juniormint</dc:creator>
      <dc:date>2013-11-26T16:06:52Z</dc:date>
    </item>
  </channel>
</rss>

