How to close Open Violations for inactive Segregation of Duties (SoD) and User Access Rules in RSA Identity Governance & Lifecycle
Originally Published: 2020-04-14
Article Number
Applies To
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.x
Issue
- Open violations remain open after the rule has been inactivated.
- Exceptional access remains in effect and on the exceptional access expiration date, the violations become open violations and emails are sent to the remediators to take action.
Tasks
Resolution
- Delete the rule
- Change the rule:
- Edit the SoD or User Access rule.
- Set the status to Active
- Change the Selected users filter to something that is always false (for example, go to Advanced and enter 1=0 in the Where Clause).
- Save the rule changes.
- Run the rule once. This should close all violations.
- Edit the rule again
- Set the status to Inactive
- Remove the false filter.
- Save the rule changes.
Related Articles
Troubleshooting 'Administrative Access Denied' error message when scanning target machines using Datacenter Number of Views Close an Active User Session Number of Views sun/net/www/http/KeepAliveCleanerEntry class missing in upgradeJDK17_v004.tar in RSA Identity Governance & Lifecycle Number of Views Validate connection for Oracle Scanning - ORA - 12541 error Number of Views How to close ports used by the RSA Authentication Agent to block SSLv3 communication to RSA Authentication Manager 8.x Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager 8.9 Setup and Configuration Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings.
Don't see what you're looking for?
