Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
Kerberos is an identity-checking mechanism used on in-house networks. The IETF's RFC 4120 describes it as a means of verifying the identity of users and servers on an open network that is not protected. It uses a trusted third party and encryption with shared secret keys.
How does Kerberos work?
Picture the entry gate of an amusement park. After you finish the identity check at the entrance you get a wristband. At each attraction you do not repeat the check, you just show the wristband. A Kerberos ticket is that wristband.
In RFC 4120, a ticket is a record that helps a user prove themselves to a server. The ticket is sealed with that server's secret key. The user shows it together with a new proof made on the spot (an authenticator). What hands out tickets and keys is the key distribution center (KDC), which has a service that does authentication and a service that issues tickets.
A user's secret key can be made from the password. For that reason, replies from the service arrive encrypted with that key. Think of the whole flow together with the entrance defenses in unauthorized access countermeasures. If you have worries about your authentication settings, contact us.
Why does Kerberos matter?
It runs behind everyday logins, so it goes unnoticed and its settings tend to stay old. The points for a review lie in the cautions RFC 4120 itself gives.
The first is weak passwords. The RFC says that attacks that guess passwords are not solved by Kerberos. If a weak password is chosen, you may suffer an attack in which dictionary candidates are tried at hand.
The second is clocks. Each machine's clock needs to be loosely synchronized. The permitted range can be set, and about 5 minutes is given as an example.
If a clock drifts widely, the server returns an error and refuses the login. When you use a mechanism to set the time, the RFC says to protect that traffic from attackers too. When you review, check these points.
- Decide the length and strength of passwords as a policy.
- Set the time of every machine from the same time source.
- Limit the administrators of the servers that handle secret keys.
- Do not leave detailed settings with one person. Decide when to review them and keep records.
Related terms
- Active Directory: a mechanism that manages a company's staff and computers together
- Two-factor authentication: layers one more check on top of the password
- Password manager: a tool that stores many passwords safely
- Identity provider: a mechanism that takes on the identity check at login for everyone
Frequently asked questions
If I use Kerberos, is a weak password all right?
No. RFC 4120 says Kerberos does not solve attacks that guess passwords. If a weak password is chosen, you may suffer an attack in which candidates are tried at hand. The strength of passwords must be decided separately.
What happens if a computer's clock drifts?
The server returns an error when it finds drift beyond the permitted range. RFC 4120 assumes each machine's clock is loosely synchronized, and gives 5 minutes as an example. Use a mechanism that sets the time on every machine.
Next step
Unauthorized access countermeasures sets out the wider order for protecting logins. If you are unsure about your in-house authentication settings, contact us. The free URL check shows only what is visible from outside.
Frequently asked questions
If I use Kerberos, is a weak password all right?
No. RFC 4120 says Kerberos does not solve attacks that guess passwords. If a weak password is chosen, you may suffer an attack in which candidates are tried at hand. The strength of passwords must be decided separately.
What happens if a computer's clock drifts?
The server returns an error when it finds drift beyond the permitted range. RFC 4120 assumes each machine's clock is loosely synchronized, and gives 5 minutes as an example. Use a mechanism that sets the time on every machine.