Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Best Practices for Privilege Elevation #43

Open
sarahcec opened this issue May 13, 2021 · 1 comment
Open

Best Practices for Privilege Elevation #43

sarahcec opened this issue May 13, 2021 · 1 comment
Labels
refresh target for article refresh Verified Issue has been verified by the IDPro BoK Committee
Milestone

Comments

@sarahcec
Copy link

This needs to be incorporated into the BoK, probably in one of the Intro to Identity articles:

Privilege elevation is a best practice that is used by operators and developers of identity systems to help achieve the principle of least privilege. People should only access high sensitivity resources like live customer data when there is a valid business reason like debugging an issue with the logs of live customer data. It is not appropriate to use elevated permissions when they are not necessary, when the person is merely curious, or to help a friend or family member.

@hlflanagan
Copy link
Contributor

We will reach out to the authors about adding this to Intro to Identity - Part 1 in the section on Privileged Account Management. Make sure to include that "Privilege escalation" is a synonym. Note that some further information will also be added to Intro to Access Management.

@hlflanagan hlflanagan added refresh target for article refresh Verified Issue has been verified by the IDPro BoK Committee labels Aug 5, 2021
@hlflanagan hlflanagan added this to the BoK Issue 13 milestone Oct 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refresh target for article refresh Verified Issue has been verified by the IDPro BoK Committee
Projects
None yet
Development

No branches or pull requests

2 participants