[Security Solution]Security Privilege access conflicting between Read and None

[ghost]

Describe the bug Security Privilege access conflicting between Read and None

Build Details

Version: 8.1.0-BC3
Commit:0335dd6a26ef29ae9021d0fae9347dc88f3b7d6e
Build:50346

Pre-Condition

• Create a 8.1.0 BC3 Released Build
• Create Custom User (user1) and Assign custom Role (role1) to it

  Role 1
  - Security : Read
  - Case : All

• Create another Custom User (user2) and another custom Role (role2) to it

Role 2
 - Security : None
 - Case : All

Steps

• Login with user1 and verify the user have there correct Privilege as we have provided under role
• log out
• Login with user2 and verify the user have there correct Privilege as we have provided under role
• Now we have observed that on setting security to none whole security app access changed to no access which is correct ✔️ if we go with the name of feature that is Security and on other end by setting security to Read whole security access not changed to Read and only Detect group pages is being set to read so it is conflicting if we match the observation for Read and None to Security Feature.

we came up with below suggestion for this issue:-

• Either updating the security text showing under feature to be specific Area of Security applike ( Alerts ,Rules & Exception ) or add a note Setting Security to Read will not impact Host,Network ,Timeline & Cases Pages

• Or we need to add tool tip information under preview of role section updating which particular area of security app will be changed to Read

Observations:

Please find below actual observation for different page of security app on setting security feature to Read and None under kibana privilege

Security Privilege	Overview	Alerts	Rules	Exception	Host	Network	Timeline	Cases	Mange Group
Security : Read , Case : All	All Access ❌	Read Access ✔️	Read Access ✔️	Read Access ✔️	All Access ❌	All Access ❌	All Access ❌	All Access ✔️	Out of Scope as this page requires only super user to access them
Security : None, Case : All	No Access ✔️	No Access ✔️	No Access ✔️	No Access ✔️	No Access ✔️	No Access ✔️	No Access ✔️	Access ✔️	Out of Scope as this page requires only super user to access them

Screen-Cast

• Read Privilege to Security feature

https://user-images.githubusercontent.com/59917825/155517129-731a478b-e331-46a2-983b-9dba3bbe958a.mp4

• None Privilege to Security feature

https://user-images.githubusercontent.com/59917825/155517114-330e9a0a-e859-41ff-a08f-73242d64a0a0.mp4

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[manishgupta-qasource]

Reviewed & assigned to @MadameSheema

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[yctercero]

@XavierM Hey Xavier! I might be remembering wrong, but I thought I saw you had a PR or issue around this?