Ch10 - Authentication Flashcards
Authentication Factors:
- Something you know
- Something you have
- Something you are (*)
- Somewhere you are
- Something you do
(*) biometrics offers the strongest form of authentication.
Authentication Factors - Something you know
This is the most common authentication factor,
where you know information to prove your identity. Examples of this authentication factor are knowing a password or a PIN.
Authentication Factors - Something you have
Also a common authentication factor, this is based on your having something in your possession to gain access to the environment. For example, you use a swipe card or physical token to enter a building. Another example is when a web site sends you a
text message with an authorization code when you log in. You need to have your phone with you to receive this SMS message, and then you type the authorization code as confirmation that you have the phone. This occurs after you have typed your username and password as well
Authentication Factors - Something you are
With this more advanced authentication factor,
you submit a physical characteristic of yourself, such as your retina, fingerprint, or voice, to prove your identity. Authenticating to a system using this method is known as biometrics and is considered the most secure method of authentication.
Authentication Factors - Somewhere you are
An authentication system can authenticate you based on your location. This could be GPS location or IP subnet information.
Authentication Factors - Something you do
This newer form of authentication factor is based on your habits. For example, a system may use your typing patterns in conjunction with another authentication factor to authenticate you.
Common examples of two-factor authentication schemes:
Physical token and password This is an example of
authenticating with something you have and something you know.
Smartcard and PIN Again, this is an example of authenticating with something you have and something you know.
Biometrics and password This example is using an
authentication scheme that uses something you are combined with something you know.
The exam will try to trick you by giving you examples that may look like multifactor authentication but are not because the exam-ples use the same authentication scheme. For example, using a retina scan and fingerprint for authentication is still only single-factor authentication because they are both examples of something you are. Another example of single-factor authentication would be a username and password because they are both examples of something you know.
Single Sign-on
An important concept regarding authentication is the concept of single sign-on, also known as SSO. Single sign-on is the principle that when you authenticate to the network, you then have the capability to access multiple
systems based on your authentication information. With SSO you are not required to authenticate with each different system you access—you authenticate once and then can gain access to multiple systems without
authenticating again.
Identity Federation
With SSO, the user logs on with one set of credentials and then accesses many different servers, even servers in other organizations. Authenticating against an identity store in your organization and being authorized to use network services from other organizations is known as identity federation.
Authentication methods used in the Microsoft world - Kerberos
Kerberos is a popular mutual authentication protocol and is used by default with Microsoft Active Directory environments.
Active Directory adheres to the Lightweight Directory Access Protocol (LDAP) standard, which is the Internet protocol for accessing and querying a directory.
Kerberos uses a key distribution center (KDC) server that is responsible for issuing tickets. These tickets are needed in order for a client to request a service from any other server on the network (known as a realm).
The Kerberos process starts when the client logs on to the network. The KDC has a component known as the Authentication Server (AS), which gives the client a ticket-granting ticket (TGT), which gives the client permission to request a service ticket.
The service ticket is required to request service from a server on the network. When the client wants to connect to a specific server on the network, it must request a ticket from the ticket-granting service (TGS), which is another component of the KDC.
The TGS grants the ticket to the client so the client can access the required server on the network.
Authentication Protocols:
- Password Authentication Protocol (PAP)
- Challenge Handshake Authentication Protocol (CHAP)
- Microsoft Challenge Handshake Authentication Protocol (MS-CHAP)
- MS-CHAPv2
- Extensible Authentication Protocol (EAP)
Password Authentication Protocol (PAP)
Password Authentication
Protocol sends the user’s credentials in plain text and is very insecure because of how easy it is for someone to analyze and interpret the logon traffic. This is the authentication protocol used by the basic authentication method mentioned previously.
Challenge Handshake Authentication Protocol (CHAP)
With the Challenge Handshake Authentication Protocol, the server sends a challenge to the client that is then used in the authentication process.
The following steps are performed by CHAP:
1. The server sends the client a challenge (a key).
- The client then combines the challenge with the password. Both the user’s password and the challenge are run through the MD5 hashing algorithm (a formula), which generates a hash value, or mathematical answer. The hash value is sent to the server for authentication.
- The server uses the same key to create a hash value with the password stored on the server and then compares the resulting value with the hash value sent by the client. If the two hash values are the same, the client has supplied the correct password.
The benefit is that the user’s credentials have not been passed across the network at all.
Microsoft Challenge Handshake Authentication Protocol (MSCHAP)
MS-CHAP is a variation of CHAP that uses MD4 as the
hashing algorithm, versus MD5 used by CHAP. MS-CHAP also uses the Microsoft Point-to-Point Encryption (MPPE) protocol along with MS-CHAP to encrypt all traffic from the client to the server.
MS-CHAPv2
With MS-CHAP version 2, the authentication method
has been extended to authenticate both the client and the server. MSCHAPv2 also uses stronger encryption keys than CHAP and MSCHAP.