> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/active-directory/kerberos/kerberos-observation-with-wireshark.md).
# Observing Kerberos with Wireshark
Active Directory security notes for Observing Kerberos with Wireshark, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.
### Observing an authentication
We open Wireshark, then connect with a user, for example:
```
user1
```
In Wireshark, you can filter Kerberos traffic with:
```
kerberos
```
We then observe the exchanges:
```bash
AS-REQ
AS-REP
TGS-REQ
TGS-REP
```
### Example with access to a share without permissions
From `user2`, we try to access an administrative share:
```
cd //WS01/C$
```
In Wireshark, we can observe:
```
TGS-REQ
TGS-REP
SMB Access Denied
```
This means that:
1. the user queries a service ticket;
2. the KDC issues the ticket;
3. the ticket is presented to the server;
4. the server refuses access because of SMB or NTFS permissions.
### Ticket and Authenticator
When accessing a service, the client generally sends:
* a service ticket;
* an authenticator.
The ticket proves that the KDC authorized access to the service.
The authenticator proves that the client is indeed the one using the ticket.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hacking-notes.jord4n.pro/active-directory/kerberos/kerberos-observation-with-wireshark.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
