[an error occurred while processing this directive]

Single Sign-on eSecurity Web Seminar
Intelligent Authentication FAQ
Novell Modular Authentication Service (NMAS)

Q1.

Why did Novell create NMAS?

A1.

NMAS represents another step in Novell's strategy to deliver security solutions. Today many businesses have a mixture of authentication methods and no way to manage them or to use a combination of those methods.

In addition, many NDS-installed organizations have determined that password authentication is insufficient for their security needs. Such organizations have decided to expand their network authentication from requiring the network user to authenticate via "something you know" (for example, a password) to "something you have" (for example, a smart card), or "something that you are" (for example, a fingerprint).

Novell recognizes the value that these different forms of network authentication provide and has developed an extensible framework to support and manage different and multiple authentication methods in NDS.

Q2.

Who needs this kind of solution?

A2.

NMAS is a dual product offering answering the needs of many customers.

NMAS Starter Pack is a free Web download at www.novell.com/products/nmas that allows for any provided single form of user login method. This means that NDS users can now authenticate using either a smart card, physical token, biometric, X.509 certificate, or a simple or NDS password.

NMAS Starter Pack is targeted towards organizations looking to implement different single-method NDS authentication policies. Undoubtedly, many of these initial customers will be existing customers whose authentication methods Novell is making available on the Web download.

NMAS Enterprise Edition is a for-charge product (available in April, 2000) that allows for multi-factor authentication as well as "Graded Authentication." Multi-factor authentication is the ability to chain authentication methods in a login sequence. Graded Authentication is the ability to grant network access based on authentication methods used.

NMAS Enterprise Edition is built for organizations with security needs that require multi-factor and Graded Authentication. While this can be virtually any large enterprise, the greatest need will come from health services, financial services, government agencies, pharmaceuticals, and utilities.

Q3.

How will NMAS help the CIO?

A3.

First, NMAS simplifies management of the authentication process, lowering costs of administration on the CIO's IT staff. Second, NMAS offers the management framework to increase security throughout the organization by offering IT the ability to write access policies that offer greater access protection to various volumes and partitions within the NDS. No dollar amount can be placed on undesired access to highly sensitive information.

Q4.

How will NMAS help the network administrator?

A4.

NMAS is flexible in allowing administrators to set the access policies for accessing NDS partitions and volumes, and then establishing who can access those areas through authentication.

With Graded Authentication, network administrators will feel confident in knowing that secure information in an NDS partition or volume requiring a certain login sequence, cannot be accidentally or purposefully moved or copied to any area that is not as equally secure.

Q5.

How will NMAS help the user?

A5.

More than anything, network users want to easily authenticate to NDS and get to their work. The Novell and third party authentication methods included in NMAS provide easy to follow user prompts that let the user authenticate to NDS quickly and securely.

Q6.

Why is network authentication management so important in an enterprise security program?

A6.

Authentication is the demonstration of credentials that indicate the user is who he or she claims to be. As the practical repository for enterprise data, network services must be able to adequately maintain the security of network data by limiting access to authorized users. These users validate their identities through authentication prompts and, provided the authentication credential is provided, are granted access.

NMAS supports a variety of strong authentication methods (smart card, physical token, biometric, X.509 certificate authentication) from many of today's leading network authentication developers.

Q7.

What are the primary security problems associated with passwords alone?

A7.

In many cases, it's unwise user tendencies that make password authentication vulnerable. For example, many users set up passwords that are easy to guess. Some users have their passwords noted in plain view of others on a sticky note on their monitor. For these reasons, and others, many organizations have decided to adopt strong authentication methods such as smart cards, physical tokens, biometrics, and PKI systems using X.509 certificates.

Q8.

What are tokens?

A8.

A token is a hand-held hardware device that generates a one-time password to authenticate its owner. Token authentication systems are based on various schemes.

NMAS includes a challenge-response token authentication from VASCO, and a time-synchronous token authentication method from RSA Security.

Q9.

What are biometrics?

A9.

Biometric authentication involves providing a unique physical characteristic that distinguishes one user from another. These characteristics might be a fingerprint, voice, handwriting, facial features, eye or retina scan, etc. Biometric characteristics are measured using sensors that produce data values that can then be processed by a computer using specialized algorithms for analysis and comparison against a known data value sample.

NMAS includes fingerprint authentication methods from Identicator and SAFLINK. SAFLINK also provides biometric authentication methods using voice and facial recognition technologies.

Q10.

Are strong authentication technologies expensive to implement and maintain?

A10.

As more and more organizations have begun adopting strong authentication methods, the deployment costs have dropped significantly. With smart card, physical token, and biometric authentication options now at affordable prices, many organizations are considering these methods as strong authentication alternatives.

NMAS supports a variety of industry-leading authentication methods for smart cards, physical tokens, and biometrics.

Q11.

Why would I be interested in chaining methods together?

A11.

NMAS Enterprise Edition allows for administrators to create login sequences that prompt for single, or a series of multiple (multi-factor) authentication prompts. By creating multi-factor login sequences that, for example, require the user to provide something he knows (such as a password), with something he has (such as a smart card), along with something he is (for example a fingerprint), the administrator has greater confidence that the user is who he or she claims to be.

As a security measure, certain industries are beginning to require multi-factor authentication policies for network users. These industries include health care, financial services, pharmaceuticals, as well as government departments.

The NMAS Enterprise Edition framework allows for Novell- and partner-developed authentication methods to work together easily and securely.

Q12.

Which authentication technology is best?

A12.

This is debatable among the different authentication developers and Novell makes no claims as to the superiority of one authentication method over another. Novell and it NMAS partners all agree that multi-factor authentication is normally more secure than single-factor authentication.

The NMAS Enterprise Edition framework allows network administrators to easily build multi-factor login sequences using a variety of Novell- and partner-developed authentication methods.

Q13.

Is Novell pursuing partnerships with any other authentication developers?

A13.

The value of NMAS comes from strong partnerships with some of the world's leading authentication developers. Novell continues to pursue partnerships and is currently working with nearly 30 partners in developing NMAS authentication methods.

Q14.

Does NMAS work with SSO? With BorderManager?

A14.

NMAS and Single Sign-on (SSO) provide different network security solutions to different security problems. NMAS provides security at the network authentication level, while SSO provides security at the application level.

Nevertheless, NMAS and SSO are designed to work together. For example, If a user has the connector for the Novell Client for Windows NT (http://www.novell.com/products/sso/applications.html), he can authenticate to NDS through NMAS, then, with the NT Client password stored in SecretStore, have the client launched automatically.

While BorderManager and NMAS work together well in the same network environment, there is no formal integration work between the two products with this release.

Q15.

Does NMAS replace BorderManager Authentication Service (BMAS)?

A15.

The NMAS roadmap includes plans to integrate the RADIUS authentication offering in BMAS in a future NMAS release.

Q16.

How much does it cost? When will it be available?

A16.

NMAS Starter Pack is a free Web download available January 18, 2000. NMAS Enterprise Edition will be available in April, 2000 and will be priced at $49 per user.

Novell Single Sign-On

Q1.

What is Novell Single Sign-on?

A1.

Novell Single Sign-on is a new directory-based software solution that simplifies the end-user computing experience by eliminating the need for users to remember and input multiple passwords. With a single, existing NDS password, users can log in to the computer network only once and access a variety of applications across multiple platforms.

This breakthrough solution is made possible because users take advantage of Novell Directory Servicesâ (NDSÔ), which reduces the costly and time-consuming task that most companies incur for password management and password-related calls to their helpdesks.

Q2.

Doesn’t NDS already provide single sign-on capability? What is different/new with Novell Single Sign-on?

A2.

It’s important to differentiate what NDS already does with what Novell Single Sign-on does. NDS enables single sign-on to the network, regardless of the platform. Users authenticate to NDS once and get authenticated to the network operating system resources they need to access, whether the resources are on NetWare, NT, Solaris, or OS/390. Novell Single Sign-on, on the other hand, gives users the added convenience of logging in one time using their existing NDS password and getting automatic access to the network applications within their intranet. Now, users can get single sign-on to the network and all of their applications by logging in once and entering one password. It’s a beautiful thing.

Q3.

How does NDS provide security for Novell Single Sign-on?

A3.

Each user’s security profile, which includes log-in credentials and access rights information, is centrally located in NDS. While the network administrator usually controls users’ access privileges to network resources, Novell Single Sign-on lets companies use an optional enhanced protection setting that prevents anyone but the user (not even the network administrator) from accessing users’ login credentials.

Novell Single Sign-on also uses Novell International Cryptographic Infrastructure (NICI), the encryption capability built into NDS, to securely transmit passwords to the users’ applications. For more information on NICI, check out /corp/security/

Q4.

Does Novell Single Sign-on support authentication methods besides passwords?

A4.

Yes. Novell Single Sign-on supports any authentication method that is integrated with NDS, including smart cards, X.509 certificates, tokens, or biometric devices.

Q5.

If it only requires one password to access many applications, doesn’t it make it easier for an intruder to get into all password protected applications at once?

A5.

If a user’s NDS password is compromised, the intruder would get access to all the user’ applications. That is the very nature of single sign-on. However, Novell Single Sign-on is much more secure than competing solutions, since almost all of them use password synchronization to enable single sign-on. Since these solutions use password synchronization, users' passwords generally are stored in a single location, which is a huge security risk. If an intruder hacks the security system of these offerings, the password store (and the entire user base) is compromised. On the other hand, Novell Single Sign-on does not synchronize passwords and store them in one location. Instead, the user’s application passwords are encrypted and stored in the SecretStore of his or her User object in NDS. An intruder would have to hack into each user’s SecretStore in order to get access to every user’s password.

Q6.

Which applications are currently enabled for Novell Single Sign-on?

A6.

Novell has worked with several companies to enable single sign-on for widely used applications that run in mixed network environments. This first release of Novell Single Sign-on includes support for Lotus Notes, Entrust applications and PeopleSoft applications.

Novell will continue to work with numerous companies to provide single sign-on access to a variety of applications, including data and applications stored in mainframe computers.

Q7.

Will there be more applications that utilize Novell Single Sign-on? When will they be available?

A7.

Novell will continue to add single sign-on support for many applications. Novell will be providing frequent Web-based releases that will detail this information and offer application updates for download at /products/sso

Q8.

There are only very limited applications on the market with Novell Single Sign-on capability. What is the benefit of implementing this now, rather than waiting until more applications are integrated with Single Sign-on?

A8.

The majority of customers are looking to provide single sign-on access for enterprise applications, such as Lotus Notes. In addition, many corporate applications are customized applications that are developed in-house. Network professionals have made us aware that much of their time is being consumed by password administration and they need single sign-on for their custom applications as well. To make it easy to enable their applications for single sign-on, we offer a set of free Application Programming Interface (APIs) for all third-party developers. These easy-to-use APIs make it especially convenient for companies to enable their in-house custom applications for single sign-on with NDS, and deploy the solution to each user’s desktop. Developers don’t even have to modify their existing enterprise applications, since the only change required is to add a single file to existing desktop clients in the network (Win95, Win98, or WinNT). Novell Single Sign-on is so non-intrusive, users don’t have to do a thing except show up and log in.

Q9.

What other NDS-based applications will Novell build in the near future?

A9.

Novell has a number of solutions in the pipeline that we think will drive directory use in e-business. We have made several strategic moves to become an Internet company, and that should be reflected even more in our product releases this year.

Q10.

Who will benefit most from Novell Single Sign-on?

A10.

Users and network administrators will benefit most from Novell Single Sign-on. The end-user experience is completely transparent. Users log into NDS and launch any Single Sign-on enabled application and they will be quickly granted access to that application without having to enter any other password. Network administrators who have cited password administration as the number one complaint of time drain will also see significant time savings. Novell Single Sign-on will eliminate password-related help desk calls and redundant password administration tasks. The bottom line is Novell Single Sign-on will signal significant cost savings and boost productivity for companies.

Q11.

What differentiates Novell Single Sign-on from its competitors?

A11.

There are four main differentiates: Novell Single Sign-on is NDS-enabled, easy to deploy, non-intrusive, and aggressively priced. Because Novell Single Sign-on is based on NDS, users benefit from the integrated security and access controls built into NDS. Administrators benefit from centralized administration and control.

Third party developers and companies will find Novell Single Sign-on easy to roll out because the APIs are simple to use. Developers don’t even have to modify their existing enterprise applications, since the only change required is to add a single file to existing desktop clients in the network (Win95, Win98, or WinNT). They can also use Novell’s desktop management software, ZENworks, to easily roll out the solution to every desktop. Novell Single Sign-on is so non-intrusive, users don’t have to do a thing except show up and log in. And finally, Novell Single Sign-on is priced to make it very difficult for our competitors to offer similar price/performance advantages.

Q12.

How much does Novell Single Sign-on cost? How can I purchase it?

A12.

Novell Single Sign-on is available to NetWareÒ 5 customers for US $49 per user. Novell Single Sign-on can be purchased from an authorized Novell reseller or by calling (888) 321-4272. In addition, customers may download Novell Single Sign-on for all PeopleSoft applications from Novell’s Web site at /products/sso.

Developers can download the Novell Single Sign-on Software Development Kit (SDK) for free from the Novell Web site at http://developer.novell.com/ndk/sdk/index.htm. Additional information about Novell Single Sign-on is available on Novell’s Web site at /products/sso.

Q13.

Lotus issued an announcement stating their support of Novell Single Sign-on today. Are you working with Lotus on future products?

A13.

Lotus and Novell recognize that Single Sign-on has enormous benefit to their mutual customers. Novell will continue to work on future versions of Single Sign-on, and we anticipate working closely with Lotus in the future to meet our mutual customers’ needs.

Q14.

How does the new Novell Single Sign-on enabled connector for Novell Client for NT work? How does the new connector for the SQL Integrator ODBC driver work with Novell Single Sign-on?

A14.

Before the SSO-enabled NT Client, the NDS/NT single sign-on experience was accomplished by synchronizing the NDS password to NT. The client update removes the need to synchronize passwords; the NT password is stored and retrieved from the user's SecretStore. The client update also provides for multiple NT machine/username secrets to support logging into more than one NT account or machine, again, without password synchronization. Additional functionality has been provided in the enabled NT Client that allows a user to unlock enhanced protection secrets after an administrative password change. Before the client, the user could do this only from ConsoleOne.

The SQL Integrator enabled ODBC driver provides single sign-on when the application connecting to the database does not provide the username/password in the connect string passed to the driver. The driver has the ability to prompt for and store this information in the SecretStore for use in subsequent database connections.