CRISC · Question #615
Which of the following controls will BEST mitigate risk associated with excessive access privileges?
The correct answer is D. Entitlement reviews. Entitlement reviews are the best control to mitigate risks associated with excessive access privileges by regularly verifying that user permissions align with current job functions.
Question
Which of the following controls will BEST mitigate risk associated with excessive access privileges?
Options
- AReview of user access logs
- BFrequent password expiration
- CSeparation of duties
- DEntitlement reviews
How the community answered
(17 responses)- A6% (1)
- C12% (2)
- D82% (14)
Why each option
Entitlement reviews are the best control to mitigate risks associated with excessive access privileges by regularly verifying that user permissions align with current job functions.
Review of user access logs helps detect *misuse* of privileges but does not prevent the existence of excessive privileges in the first place.
Frequent password expiration is a control for authentication strength, not directly for mitigating the risk of users having too many privileges once authenticated.
Separation of duties prevents a single individual from completing a critical task end-to-end, reducing the risk of fraud or error, but it doesn't directly address the granularity of individual user privileges.
Entitlement reviews, also known as access reviews or user access certifications, involve systematically examining and verifying that each user's assigned access privileges are appropriate and necessary for their current job function. This process directly identifies and rectifies instances of excessive access, dormant accounts, or outdated permissions, ensuring the principle of least privilege is maintained and thereby mitigating the risk of unauthorized access due to over-privileging.
Concept tested: Mitigating excessive access privileges
Source: https://learn.microsoft.com/en-us/azure/active-directory/governance/access-reviews-overview
Topics
Community Discussion
No community discussion yet for this question.