Definition
Here are two well-known definitions for two factor and in general multi-factor authentication.
2-factor authentication becomes important --- an authentication process that involves 2 independent means of authenticating the principal. So, we might require that a principal not only possess a device but also know some secret password (often known as a PIN, or personal identification number). Without 2-factor authentication, stealing the device would allow an attacker to impersonate the owner of the device; with 2-factor authentication, the attacker would still have another authentication burden to overcome. (Cornell University)
Authentication can involve something the user knows (e.g., a password), something the user has (e.g., a smart card), or something the user “is” (e.g., a fingerprint or voice pattern). Single-factor authentication uses only one of the three forms of authentication, while two-factor authentication uses any two of the three forms. Three-factor authentication uses all three forms. (DHS – 4300 A directive)
What you know. What you have. What you are.
In general, two factor authentication is a form of strong authentication used in government, industry etc. The two factors can be any of the factors mentioned above but typically it uses user credentials/ Passcode and Token/ Smartcard as two factors.
The goal of the two factor authentication is not to allow an attacker impersonate the owner when the attacker holds the possession of a device (laptop/workstation) etc.
ISE and Two Factor Authentication Scenarios
ISE supports two factor authentication mechanisms using the following methods
- External 2FA Identity sources (e.g. RSA Secure ID, Smartcard) or any RADIUS RFC-2865 compliant token server for on or off campus support.
( Cisco Identity Services Engine Network Component Compatibility, Release 2.2 - Cisco)
- Cisco ASA/ Anyconnect with 2FA Identity sources such as RSA secure ID for remote access/off campus support
- Anyconnect NAM (unique chaining scheme) for on-campus.
Note that there are other multi-factor solutions that work with ISE, but are transparent to ISE. For example, a user that unlocks a smartcard with PIN, or enters AD credentials via a biometric reader at desktop, will end up sending credentials to ISE which are not known to have been provided using multi-factor methods.
Here are details of the 2 factor authentication implementation documented for ISE.
On-Campus
(Please click on the link on each item for step by step instruction)
a. User authentication: Using Passcode and token
b. Device Administration: Government issued PIV or CAC cards using PIN and certificates
Pragma Fortress CL SSH Client (RFC6187 compliant)
Training available in dcloud .
Using DUO with ISE 2.3 and ACS 5.X for 2FA Cisco Network Admin Access
c. User + Machine authentication chaining: EAP-chaining with Anyconnect and ISE
For two factor using web authentication ISE integrates with
a. Symantec Validation ID Protection
b. Azure AD with MFA with SAML 2.0 SSO (at ISE end-user-facing webauth portals if the primary auth is form-auth authentication).
c. Authentication chain( using CWA): Certificate/user credentials + Web portal(central web authentication)
Off-Campus
- ASA with ISE using user certificate and RSA secure ID for authentication
- ASA with ISE for two factor authentication using Safenet authentication service
- ASA for two factor authentication(ISE can be used for authorization here)
- Azure for 2FA, as a RADIUS token server for ISE(Thank you Richard Lucht) and with Anyconnect VPN
Finally with ASA, ISE can also just be used as authorization to provide access controls to ASA (with ASA configured to performing multi-factor authentication) as in the case of c above.
Conclusion
To summarize, ISE supports authentication mechanism that uses 3rd party two factor authentication service alone, or in conjunction with Cisco ASA server and Cisco Anyconnect client for on/off prem use cases.
ISE also provides authentication chaining and EAP chaining mechanism that chains two different authentication forms that can use two different factors for that. EAP-Chaining is a unique method where the user identity and machine identity are chained together within the same authentication session thereby ensuring that both the identities are tied to the machine that helps you to identify a corporate asset in a secure way.
I am using Cisco ISE 2.2 version where the Symantec VIP setting are not relevant. Could you please let me know how to achieve this in ISE 2.2
a. Symantec Validation ID Protection
