Version: , v7.2x
Modules: Governance and Lifecycle
Product Area: Workflows
Time to apply: ~2 hours
Most organizations struggle to accurately manage and understand all their Application/Directory Accounts and which ones are actively being used. There is a huge risk associated to all accounts which are no longer in use but are still active and could be susceptible for attacks if compromised. Additionally, there could be unnecessary cost associated with licenses assigned to accounts that are no longer in use.
We see organizations introduce manual dormancy processes, but these can be inaccurate and require significant ongoing effort to be effective.
Typically, organizations want to introduce an automated and phased approach to managing dormant accounts. This process would first notify account owners and administration teams of any dormant accounts, enabling the user/team to take action if the account is still required. If no action is taken, the solution should then perform automated Account Disablement and possibly Account Deletion after a specified number of days of inactivity.
The following document, created by RSA Professional Services, provides steps on how to configure this solution within your environment.
NOTE: Always first add configuration to a non-production environment and test thoroughly against real life data before promoting to further environments.
Always take a backup of the environment/s before making any significant changes.
Related Articles
How to configure RSA Data Loss Prevention filtering on File Fingerprint Crawler using exclusions 19Number of Views ORA-01403 no data found error in Account Data Collectors (ADC) in Step 10/11 in RSA Governance & Lifecycle 50Number of Views RSA announces the upcoming release of RSA SecurID Access to accelerate and modernize MFA 15Number of Views Generic REST Collector fails with 'jsonpath.PathNotFoundException:Missing property in path $['members']' error collecting … 81Number of Views DSA-2019-165: RSA Identity Governance and Lifecycle Product Security Update for Multiple Apache Tomcat Vulnerabilities 9Number of Views
Trending Articles
RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows RSA Announces the Release of RSA MFA Agent 2.5 for Microsoft Windows RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to generate a PASSCODE for manual entry on a Ericsson R380 WAP phone