From an identity management perspective, if Active Directory is being used for access and as the repository-of-record for user data for applications, the inconsistencies mentioned above can greatly affect how applications function. Incomplete, unacceptable and just plain wrong information may cause an application using that data to malfunction, or worse, grant invalid access rights (whether denying authorized users or allowing unauthorized...
The best practices are simple: Treat Active Directory as an enterprise repository. That means architect and plan what fields will be managed by end users, and put in place the controls needed for consistent/valid data (whether the control is an Active Directory control, a process or even training for the end users).
Having users maintain their own information can be great for administrative cost savings, but if left uncontrolled, can cause more expenditures than what it saves.
Dig deeper on Active Directory and LDAP Security
Related Q&A from Randall Gamby, Contributor
Is your remote desktop access software really secure? Randall Gamby offers advice for conducting a remote access audit to validate security.continue reading
Expert Randall Gamby discusses risk-based authentication, and whether that type of user identification system is right for the enterprise.continue reading
Expert Randall Gamby discusses various types of single sign-on, specifically the approaches of Ping Identity's SSO and Symplified SSO.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.