One Kerberos Ticket on several hosts?

Anahaym 496 Reputation points
2022-05-05T09:45:22.303+00:00

Hello,

we have implemented ATP and now we are getting warnings, that one Kerberos Ticket of one employee was used on two machines. It is ok?

Alert Description: An actor took employee's Kerberos ticket from TS-Server and used it on 2 computers to access 1 resource.
{"$id":"23","IsValid":false,"Type":"DomainResourceIdentifier","ResourceName":"ldap/dc.domain.local"},{"$id":"24","IsValid":false,"Type":"ResourceAccessInfo","IpAddress":"192.168.100.174","Time":"04/27/2022 08:57:38"}
{"$id":"25","IsValid":false,"Type":"DomainResourceIdentifier","ResourceName":"ldap/dc.domain.local"},{"$id":"26","IsValid":false,"Type":"ResourceAccessInfo","IpAddress":"192.168.100.171","Time":"04/28/2022 07:59:06"},

important notice: TS-Server has several IP-Adresses (bindet to a user), so 100.174 and 100.171 is the same TS-Server. We also have another TS-Server with serveral IPs too, that's why I'm asking whether Kerberos Ticket is the same on all machines?

Thank you in advance!

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
Windows for business | Windows Server | User experience | Other
Windows for business | Windows Server | Devices and deployment | Configure application groups
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Limitless Technology 40,046 Reputation points
    2022-05-06T03:34:51.52+00:00

    Hello @Anahaym

    In fact the ticket will be different based on the network. For example, during the request for TGT the client sends a plaintext message to the authentication server. This message contains:

    -username;
    -the name of the requested service (in this case this is the Ticket Granting Server – TGS);
    -the network address;
    -the requested lifetime of the TGT.

    After verifying different information, the server generates a random key called the session key that is to be used between the client and the TGS.

    The authentication server then sends back two messages to the client:

    • Message A is encrypted with the client secret key. The client secret key is not transferred but is retrieved from the password (more to speak the hash) found in the user database. This happens all on the server side. The message contains:
      TGS name;
      timestamp;
      lifetime;
      the TGS session key (the key generated in the beginning of this step).
    • Message B is the Ticket Granting Ticket, encrypted with the TGS secret key, that contains
      your name;
      the TGS name;
      timestamp;
      your network address;
      lifetime;
      the TGS session key (same as in message A).

    Hope this helps with your query,

    -----------------

    --If the reply is helpful, please Upvote and Accept as answer--


  2. Anahaym 496 Reputation points
    2022-05-06T07:41:27.09+00:00

    Hello LimitlessTechnology-2700,

    If the ticket is always different, why then we are getting message, that the same ticket is used from different IP adresses?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.