<?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: permission on knowledge object in Security</title>
    <link>https://community.splunk.com/t5/Security/permission-on-knowledge-object/m-p/523855#M11871</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/227359"&gt;@KaS&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;you can give the grants adding to a knowledge object the roles of your users.&lt;/P&gt;&lt;P&gt;The only problem is that if a role/user cannot see a field, all the searches containing that field have no results for thet role!&lt;/P&gt;&lt;P&gt;In other words, if a role connot see a field it isn't used in all searches.&lt;/P&gt;&lt;P&gt;The only way to mask some fields for some users is to create different dashboards for the different roles containing a different list of fields; remember to disable the feature "open in search" for the limited users.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
    <pubDate>Fri, 09 Oct 2020 06:43:05 GMT</pubDate>
    <dc:creator>gcusello</dc:creator>
    <dc:date>2020-10-09T06:43:05Z</dc:date>
    <item>
      <title>permission on knowledge object</title>
      <link>https://community.splunk.com/t5/Security/permission-on-knowledge-object/m-p/523832#M11870</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Normal users should see a subset of a field extraction, small set of higher privilled users should be able to see more fields extracted from a log event in the search app.&lt;/P&gt;&lt;P&gt;reason: deeper analysis capabilities for special analysts, limit field analysis and search time saving for normal users.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you please tell me, how this have to be implemented? Is there an easier approach than mine?&lt;/P&gt;&lt;P&gt;What do I have to configure and where?&lt;/P&gt;&lt;P&gt;Can I handle it in on Addon?&lt;/P&gt;&lt;P&gt;Do I really save search time, if field extraction limited for the majority of the users? How can I measure the differences?&lt;/P&gt;&lt;P&gt;My approach and actual (no) results:&lt;/P&gt;&lt;P&gt;I created an add on's with report field extraction for specific sourcetypes (log events)&lt;/P&gt;&lt;P&gt;- create an Addon &lt;STRONG&gt;..._baseline&lt;/STRONG&gt; with the field &lt;STRONG&gt;subset&lt;/STRONG&gt; - &lt;STRONG&gt;all users are granted&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;- create an Addon &lt;STRONG&gt;..._all&lt;/STRONG&gt; but with&lt;STRONG&gt; all fields&lt;/STRONG&gt; extracted but &lt;STRONG&gt;limit access&lt;/STRONG&gt; to a &lt;STRONG&gt;role&lt;/STRONG&gt; "deep_data"&lt;/P&gt;&lt;P&gt;- assigned the role to the user, who should see all the data&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But there is no difference, if a user had the role or not.&amp;nbsp;&lt;BR /&gt;By playing with some permission assignments I can enforce, that users can see the subset or the whole set.&lt;BR /&gt;But it's not depends on the role assignment. It's just for all users.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thx and Regards&lt;BR /&gt;KaS&lt;/P&gt;</description>
      <pubDate>Fri, 09 Oct 2020 02:56:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/permission-on-knowledge-object/m-p/523832#M11870</guid>
      <dc:creator>KaS</dc:creator>
      <dc:date>2020-10-09T02:56:48Z</dc:date>
    </item>
    <item>
      <title>Re: permission on knowledge object</title>
      <link>https://community.splunk.com/t5/Security/permission-on-knowledge-object/m-p/523855#M11871</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/227359"&gt;@KaS&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;you can give the grants adding to a knowledge object the roles of your users.&lt;/P&gt;&lt;P&gt;The only problem is that if a role/user cannot see a field, all the searches containing that field have no results for thet role!&lt;/P&gt;&lt;P&gt;In other words, if a role connot see a field it isn't used in all searches.&lt;/P&gt;&lt;P&gt;The only way to mask some fields for some users is to create different dashboards for the different roles containing a different list of fields; remember to disable the feature "open in search" for the limited users.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Fri, 09 Oct 2020 06:43:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/permission-on-knowledge-object/m-p/523855#M11871</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2020-10-09T06:43:05Z</dc:date>
    </item>
    <item>
      <title>Re: permission on knowledge object</title>
      <link>https://community.splunk.com/t5/Security/permission-on-knowledge-object/m-p/523863#M11873</link>
      <description>&lt;P&gt;Hi Giuseppe,&lt;/P&gt;&lt;P&gt;thx for reply. Yes I know, that the user can not see these fields in searches (except with regexing).&lt;BR /&gt;But this is exact, what I wanne to achieve. You wrote I should grants adding to knowledge objects.&lt;/P&gt;&lt;P&gt;I did that, but unfortunately with no success.&lt;BR /&gt;How exactly do I have to do?&lt;BR /&gt;&lt;BR /&gt;My recent steps are:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;create a role "deep_data"&lt;/LI&gt;&lt;LI&gt;got Apps-&amp;gt;Manage apps&lt;/LI&gt;&lt;LI&gt;select the app "addon_all"&lt;/LI&gt;&lt;LI&gt;edit "permissions"&lt;/LI&gt;&lt;LI&gt;deselect "everyone"&lt;/LI&gt;&lt;LI&gt;select the role&amp;nbsp; "deep_data"&lt;/LI&gt;&lt;LI&gt;keep "All apps(system") --&amp;gt; I tried it with app only, but this could not work, due to it's an addon to search&lt;/LI&gt;&lt;LI&gt;assign the role to the user "xxxx_all"&lt;/LI&gt;&lt;LI&gt;restart&lt;/LI&gt;&lt;LI&gt;logon with user "xxxx_all"&lt;/LI&gt;&lt;LI&gt;logon with user "xxxx_restricted"&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Results:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;whatever I switched, the users "xxx_all" and "xxx_restricted" has the same view&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;What's did I wrong?&lt;/P&gt;&lt;P&gt;Reg&amp;nbsp;&lt;/P&gt;&lt;P&gt;KaS&lt;/P&gt;</description>
      <pubDate>Fri, 09 Oct 2020 07:37:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/permission-on-knowledge-object/m-p/523863#M11873</guid>
      <dc:creator>KaS</dc:creator>
      <dc:date>2020-10-09T07:37:47Z</dc:date>
    </item>
    <item>
      <title>Re: permission on knowledge object</title>
      <link>https://community.splunk.com/t5/Security/permission-on-knowledge-object/m-p/523948#M11875</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/227359"&gt;@KaS&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;why do you want to intervene on the app "&lt;SPAN&gt;addon_all", is this the app containing the Knowledge objects?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Anyway, try in this way:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;click on Manage Apps,&lt;/LI&gt;&lt;LI&gt;choose the App &lt;SPAN&gt;containing the Knowledge objects,&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;click on "View Objects",&lt;/LI&gt;&lt;LI&gt;click, one by one, on all the fields you have to assign roles,&lt;/LI&gt;&lt;LI&gt;assign to each field the roles:&lt;UL&gt;&lt;LI&gt;both to the fields open to all the users,&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;xxx_restricted to the fields with restricted access.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;You can assign grants to only app (usually) or all apps (if you think that a field is common to more apps.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Fri, 09 Oct 2020 14:52:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/permission-on-knowledge-object/m-p/523948#M11875</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2020-10-09T14:52:45Z</dc:date>
    </item>
  </channel>
</rss>

