<?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 lockdown user write access to indexes in Splunk Cloud Platform</title>
    <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/How-to-lockdown-user-write-access-to-indexes/m-p/601796#M1509</link>
    <description>&lt;P&gt;No problem, from my experience (with Splunk enterprise) the changes take place immediately.&lt;/P&gt;</description>
    <pubDate>Tue, 14 Jun 2022 21:33:32 GMT</pubDate>
    <dc:creator>jamie00171</dc:creator>
    <dc:date>2022-06-14T21:33:32Z</dc:date>
    <item>
      <title>How to lockdown user write access to indexes</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/How-to-lockdown-user-write-access-to-indexes/m-p/601741#M1505</link>
      <description>&lt;P&gt;Our users have discovered that they can add data to indexes.&amp;nbsp; This could lead to a user accidently polluting a production index.&amp;nbsp; I searched the Splunk documentation and the Internet but was unable to find a solution.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone know how we can restrict write-access to indexes to the sc_admin role and allow read access for everyone else?&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jun 2022 13:50:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/How-to-lockdown-user-write-access-to-indexes/m-p/601741#M1505</guid>
      <dc:creator>edgarrity</dc:creator>
      <dc:date>2022-06-14T13:50:55Z</dc:date>
    </item>
    <item>
      <title>Re: How to lockdown user write access to indexes</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/How-to-lockdown-user-write-access-to-indexes/m-p/601758#M1506</link>
      <description>&lt;P&gt;hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/216677"&gt;@edgarrity&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;Assuming the users are adding data via the collect command then you could remove the "run_collect" capability from user roles apart from sc_admin.&amp;nbsp;&lt;/P&gt;&lt;P&gt;If they are adding files through UI then you could remove the inputs_file capability from the roles.&amp;nbsp;&lt;/P&gt;&lt;P&gt;If they are adding inputs then you could remove the edit_monitor capability.&lt;/P&gt;&lt;P&gt;Thanks,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Jamie&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jun 2022 15:57:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/How-to-lockdown-user-write-access-to-indexes/m-p/601758#M1506</guid>
      <dc:creator>jamie00171</dc:creator>
      <dc:date>2022-06-14T15:57:33Z</dc:date>
    </item>
    <item>
      <title>Re: How to lockdown user write access to indexes</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/How-to-lockdown-user-write-access-to-indexes/m-p/601760#M1507</link>
      <description>&lt;P&gt;Please see here for list of capabilites:&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.2.6/Security/Rolesandcapabilities" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.2.6/Security/Rolesandcapabilities&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jun 2022 15:57:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/How-to-lockdown-user-write-access-to-indexes/m-p/601760#M1507</guid>
      <dc:creator>jamie00171</dc:creator>
      <dc:date>2022-06-14T15:57:51Z</dc:date>
    </item>
    <item>
      <title>Re: How to lockdown user write access to indexes</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/How-to-lockdown-user-write-access-to-indexes/m-p/601765#M1508</link>
      <description>&lt;P&gt;Thanks.&amp;nbsp; Do I need to restart Splunk Cloud after making changes to users capabilities or will the changes take effect immediately?&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jun 2022 16:15:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/How-to-lockdown-user-write-access-to-indexes/m-p/601765#M1508</guid>
      <dc:creator>edgarrity</dc:creator>
      <dc:date>2022-06-14T16:15:13Z</dc:date>
    </item>
    <item>
      <title>Re: How to lockdown user write access to indexes</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/How-to-lockdown-user-write-access-to-indexes/m-p/601796#M1509</link>
      <description>&lt;P&gt;No problem, from my experience (with Splunk enterprise) the changes take place immediately.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jun 2022 21:33:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/How-to-lockdown-user-write-access-to-indexes/m-p/601796#M1509</guid>
      <dc:creator>jamie00171</dc:creator>
      <dc:date>2022-06-14T21:33:32Z</dc:date>
    </item>
  </channel>
</rss>

