Account lifecycle management

1. A system for managing user access privileges within a computer network, wherein the system comprises at least one processor in communication with a memory, the at least one processor configured to implement:

a discovery engine configured to discover and identify an existing user account from a source list, the source list comprising a list of at least one account repository that is curated based on a predetermined preference;

a policy engine configured to identify privileged access data granted to the existing user account, the privileged access data including at least one access privilege level that corresponds to a system control level, an update data level, an appropriate access level, an unvetted access level, and a sensitive read level;

a data modeling engine configured to:

determine recommended organizational data to associate with the privileged access data based on a likelihood that the existing user account is associated with a business unit with a corresponding business unit access privilege; and

associate the privileged access data with the recommended organizational data, the recommended organizational data comprising associated application data, support team data, and business unit data; and

a remediation engine configured to modify access privileges of the existing user account.

2. The system of claim 1 , wherein the at least one processor is further configured to implement a mitigation engine configured to apply an exception to the modified access privileges of the existing user account.

3. The system of claim 2 , wherein the mitigation engine is configured to split the existing user account into multiple new user accounts.

4. The system of claim 1 , wherein the discovery engine is configured to identify the existing user account as a single user account or a functional account.

5. The system of claim 4 , wherein the existing user account is a single user account associated with a Security Identifier (SID).

6. The system of claim 5 , wherein the existing user account is a functional account, wherein the functional account includes a shared interactive account, an application-to-application account, a hybrid account, a platform default account, and an active directory primary account.

7. The system of claim 5 , wherein remediation engine is configured to modify access privileges of the existing user account based on the type of functional account identified by the discovery engine.

8. The system of claim 7 , wherein the remediation engine is configured to modify access privileges of the existing user account identified as a shared interactive account by: disabling the existing user account, removing the existing user account, reducing privileges of the existing user account, or onboard the existing user account to an Enterprise Password Vault (EPV).

9. The system of claim 7 , wherein the remediation engine is configured to modify access privileges of the existing user account identified as a hybrid account by splitting the existing user account into a shared interactive account and an application-to-application account.

10. A computer implemented method for account lifecycle management, the method comprising:

identifying an existing account that is associated with a user from a source list, the source list comprising a list of at least one account repository that is curated based on a predetermined preference;

identifying privileged access data granted to the existing user account, the privileged access data including at least one access privilege level that corresponds to a system control level, an update data level, an appropriate access level, an unvetted access level, and a sensitive read level;

determining recommended organizational information to associate with the privileged access data based on a likelihood that the existing user account is associated with a business unit with a corresponding business unit access privilege;

associating the privileged access data with the recommended organizational information, the recommended organizational information comprising associated application information, support team information, and business unit information; and

modifying access privileges of the existing user account.

11. The method of claim 10 , further comprising:

applying an exception to the modified access privileges of the existing user account.

12. The method of claim 11 , further comprising:

splitting the existing user account into multiple new user accounts.

13. The method of claim 10 , further comprising:

identifying the existing user account as a single user account or a functional account.

14. The method of claim 13 , further comprising:

identifying the existing user account as a single user account associated with a Security Identifier (SID).

15. The method of claim 14 , further comprising:

identifying the existing user account as a functional account, wherein the functional account includes a shared interactive account, an application-to-application account, a hybrid account, a platform default account, and an active directory primary account.

16. The method of claim 15 , further comprising:

modifying access privileges of the existing user account based on the type of functional account identified by the discovery engine.

17. The method of claim 16 , further comprising:

modifying access privileges of the existing user account identified as a shared interactive account by: disabling the existing user account, removing the existing user account, reducing privileges of the existing user account, or onboard the existing user account to an Enterprise Password Vault (EPV).

18. The method of claim 16 , further comprising:

modifying the access privileges of the existing user account identified as a hybrid account by splitting the existing user account into a shared interactive account and an application-to-application account.

19. The method of claim 10 , further comprising:

modifying access privileges of the existing user account based on at least one input received from a dashboard user interface.

20. A non-transitory computer readable medium having instructions stored thereon for executing a method of account lifecycle management, that, when executed by a processor, cause the processor to perform operations comprising:

identifying an existing account that is associated with a user from a source list, the source list comprising a list of at least one account repository that is curated based on a predetermined preference;

identifying privileged access data granted to the existing user account, the privileged access data including at least one access privilege level that corresponds to a system control level, an update data level, an appropriate access level, an unvetted access level, and a sensitive read level;

determining recommended organizational information to associate with the privileged access data based on a likelihood that the existing user account is associated with a business unit with a corresponding business unit access privilege;

associating the privileged access data with the recommended organizational information, the recommended organizational information comprising associated application information, support team information, and business unit information; and

modifying access privileges of the existing user account.