> For the complete documentation index, see [llms.txt](https://docs.wehost.co.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wehost.co.in/cybersecurity/kerberos.md).

# Kerberos

* Kerberos uses symmetric encryption and provides mutual authentication of both clients and servers.
* build by MIT
* Kerberos has the following components:
* Principal: Client (user) or service
* Realm: A logical Kerberos network
* Ticket: Data that authenticates a principal’s identity Access Control technologies
* Credentials: a ticket and a service key
* KDC: Key Distribution Center, which authenticates principals
* TGS: Ticket Granting Service
* TGT: Ticket Granting Ticket
* C/S: Client/Server

#### Kerberos Operational Steps

*

```
<figure><img src="/files/UDrA2eOSbPDmiMB1md72" alt=""><figcaption></figcaption></figure>
```

* Alice, wishes to access a printer

  * Kerberos Principal Alice contacts the KDC (Key Distribution Center, which acts as an \[\[Identity and Authentication ,Authorization, ,Accountability and Auditing(AAAA) and Non-repudiation|authentication]] server), requesting \[\[Identity and Authentication ,Authorization, ,Accountability and Auditing(AAAA) and Non-repudiation|authentication]]
  * The KDC sends Alice a session key, encrypted with Alice’s secret key.
    * The KDC also sends a TGT (Ticket Granting Ticket), encrypted with the TGS’s secret key
  * Alice decrypts the session key and uses it to request permission to print from the TGS (Ticket Granting Service)
    * Alice cannot decrypt the TGT
      * only the TGS can
  * Seeing Alice has a valid session key (and therefore has proven her identity claim), the TGS sends Alice a C/S session key (second session key) to use to print.
    * The TGS also sends a service ticket, encrypted with the printer’s key
  * Alice connects to the printer.
    * The printer, seeing a valid C/S session key, knows Alice has permission to print, and also knows that Alice is authentic
  *

  ```
  <figure><img src="/files/nTppyDWKKizM72R90147" alt=""><figcaption></figcaption></figure>
  ```

<figure><img src="/files/IAYLp9kmUmk1gWplnAPA" alt=""><figcaption></figcaption></figure>

* <https://youtu.be/5N242XcKAsM>

<figure><img src="/files/9CByqiJagC7UIZnFwaxY" alt=""><figcaption></figcaption></figure>

#### Kerberos Weaknesses

* primary weakness of Kerberos is that the KDC stores the keys of all principals


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.wehost.co.in/cybersecurity/kerberos.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.