[MUSIC PLAYING] Hi, I'm Bill Evans, a member of the identity and access management team at Dell Software. This is part one of a five-part series on the questions you need to ask before purchasing a two-factor authentication solution. The first thing we're going to talk about is architecture as it is the foundation of any solution. And if you don't have a good foundation, well, things can come crashing down pretty quickly.
Ensuring that the architecture of your two-factor solution will blend well with your existing infrastructure is also key. So how do you go about doing this? You need to start by asking where all the identity and token information will be stored. This data is critical in making the solution work and making sure that it is as accurate and secure should be a top priority. Will this information be stored in one of your existing identity databases? Or is it going to be housed in a new identity database that will need to be supported and kept in sync with another identity store, and yet another place that the user will need to be provisioned or deprovisioned from?
Another architectural consideration deals with authentication protocols. Ask your vendor if they use proprietary protocols or industry standards, like RADIUS, LDAP, OATH and PAM. Using industry standards enables fast and easy integration with more applications and devices, and offers the ability to integrate quickly with other standards-based solutions.
Now that we've outlined what questions you should ask about architecture, let me tell you quickly how Dell software's Defender is architected. First of all, Defender bases all administration and identity management on your organization's existing investment an Active Directory, eliminating the cost and time involved in setting up and maintaining proprietary databases to support two-factor authentication. In addition, since Defender integrates directly with Active Directory, it scales as you grow Active Directory within your environment, making load balancing and redundancy a breeze.
And remember those standards we talked about earlier? Yeah, Defender uses all of them. Supporting this standards enables Defender to integrate with more applications and devices, as well as to quickly integrate with any other standards-based two-factor solution needed in case of a merger or acquisition.
Well, that wraps it up for our question on architecture. Remember that devil is in the details, and not all two factor authentication solutions are the same. So check out the Videos tap on software.dell.com/defender to see the next part of our video series on the questions you need to ask before purchasing a two-factor solution.