Better Separation of Duties Handling and Permission Tracking

Idea ID 2784646

Better Separation of Duties Handling and Permission Tracking

0 Votes
"When there is a SoD condition and the resolution calls for the revoking of a Permssion X from Application Y which a user is entitled to as part of a Business Role, Permission X will automatically be added back to the the user by Identity Governance after an Application Y collection in 3.5 or as part of the detect inconsistencies process in 3.5.2. Permissin X should not be granted back to the user if the reason it was taken away was intentional as in the SoD case.

There should be some rules in effect as well as tracking Permission X was removed from the user due to a SoD condition and was intentional. When the SoD no longer exists, Permission X should be granted again to the user as a result of the user being authorized for Permission X via membership in the Business Role. In addition, the reason a Permission authorized by a Business Role is missing on a user should be made transparent. It should show on the user Permission X is revoked for x time period for a particular reason like SoD policy x remediation."
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.