What are the pros and cons of using stand-alone authentication that is not Active Directory-based?

What are the pros and cons of using stand-alone authentication that is not Active Directory-based?

For an organization that does not use Active Directory-based authentication, what are the pros and cons of using stand-alone setups?

    Requires Free Membership to View

    SearchSecurity.com members gain immediate and unlimited access to breaking industry news, virus alerts, new hacker threats, highly focused security newsletters, and more -- all at no cost. Join me on SearchSecurity.com today!

    Michael S. Mimoso, Editorial Director

    By submitting your registration information to SearchSecurity.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSecurity.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

The nice thing about directory services, like Active Directory for Windows or LDAP for Unix, is that they centralize access control over all directory members. Usually everybody on a single network or domain is enrolled in the same directory, making it easier to enforce or change authentication policies across the board.

Tools such as Group Policy Objects (GPO) in Active Directory make it easy to enforce consistent authentication polices for all members of the Active Directory domain.

In addition, directory services have centralized reporting features for auditing user activity and for producing access management reports required for compliance with regulations like the Sarbanes-Oxley Act (SOX).

Another nice feature of directory services is they can mesh with two-factor authentication systems – one-time password (OTP) tokens, smart cards and biometrics. For stand-alone systems, such configuration would have to be done on each individual workstation.

Using stand-alone authentication systems makes it harder to centralize access management across an organization. It can lead to inconsistent access management policies on different workstations in a network, which would be chaotic in a large company with many users. It would also make tracking users and their access -- and removing stale accounts -- quite difficult.

The only advantage to standalone authentication systems would be if there were only a few desktops or workstations, as in a small company, or for specialized access that needs to be segregated from the rest of the network. A possible scenario would be a workstation dedicated to high-risk transactions or for unique access to an external network.

Unless the cost of Active Directory is prohibitive because of the size of your business, standalone setups aren't recommended.

More information:

This was first published in January 2008