07 - Implementing Authentication Controls
07 - Implementing Authentication Controls
1
Outlines
Labs
Lab 8: Auditing Passwords with a Password Cracking Utility
Lab 9: Managing Centralized Authentication
1. The client sends the authentication service (AS) a request for a Ticket Granting
Ticket (TGT), This is composed by encrypting the date and time on the local
computer with the user's password hash as the key.
2. The AS checks that the user account is present, that it can decode the request
by matching the user's password hash with the one in the Active Directory
database, and that the request has not expired, If the request is valid, the AS
responds with the following data:
✓ Ticket Granting Ticket (TGT)—this contains information about the client (name and IP
address) plus a timestamp and validity period, This is encrypted using the KDC's secret key.
✓ TGS session key for use in communications between the client and the Ticket Granting
Service (TGS), This is encrypted using a hash of the user's password.
3. MS-CHAPv2
✓ Microsoft's implementation of CHAP.
✓ Because of the way it uses vulnerable NTLM hashes, MS-CHAP should not be deployed
without the protection of a secure connection tunnel so that the credentials being passed are
encrypted.