Use of the collect command, or enabling summary indexing for a report, this feature allows a user/role to write to any index that can be searched.
Are there any options to restrict a role's access to index such that it is read-only, or alternatively is it possible to remove the collect command and summary indexing features from a role's capabilities?
It appears that there is no way for a user to have read-only access to an index while also allowing said search head to write to the same index. You could potentially work around this if you had one search head for users to perform searches (with read-only for that index enabled) and another search head to perform summary indexing (with read/write allowed to the index).
Reference: https://answers.splunk.com/answers/390225/how-to-prevent-users-from-writing-to-indexes.html
It appears that there is no way for a user to have read-only access to an index while also allowing said search head to write to the same index. You could potentially work around this if you had one search head for users to perform searches (with read-only for that index enabled) and another search head to perform summary indexing (with read/write allowed to the index).
Reference: https://answers.splunk.com/answers/390225/how-to-prevent-users-from-writing-to-indexes.html