Kerberos Authentication in Network Security
Kerberos Authentication
Kerberos is a network authentication protocol used to
verify the identity of users and systems before access to network resources is
provided.
It uses secret-key cryptography and a trusted
third party, called the Key Distribution Center (KDC), to perform
authentication. The important feature is that the user's password is not
sent directly across the network.
Kerberos was developed at MIT (Massachusetts Institute of
Technology) and provides secure login along with Single Sign-On (SSO).
(Kerberos in Greek mythology: Kerberos is a
multi-headed dog that guards the gates of the underworld. The name is used for
the authentication system because it acts as a guard for network resources.)
In a traditional client-server login:
Username + Password
The client sends the username and password directly to
the server.
Problems
- The
password travels through the network.
- An
attacker may capture the login message.
- The
captured information may be reused for unauthorized access.
- There
is no Single Sign-On (SSO).
- The
user may need to log in separately for different services.
Kerberos addresses these problems by using authentication
tickets instead of repeatedly sending the password across the network.
- Ticket
Granting Ticket (TGT) encrypted with the TGS key.
- TGS
Session Key encrypted using a key derived from the user's password.
- The client uses the user's password to obtain the TGS session key.
- The client can use the TGS session key without decrypting the TGT.
- The TGT remains protected because it is encrypted with the TGS's secret key.
- Client
ID / username
- Client
address
- Current
timestamp
The authenticator is encrypted using the TGS session key.
- The client sends the service ticket and required authentication information to the application server.
- The application server verifies the ticket.
- Strong
authentication security
- Password
is not transmitted over the network
- Supports
Single Sign-On (SSO)
- Provides
secure communication between authenticated entities
- Uses
a trusted authentication server
- Uses
tickets for accessing network services
- Depends
on a central KDC server.
- Implementation
can be complex.
- Proper
configuration and management are required.
- Availability of the authentication infrastructure is important.

Comments
Post a Comment