> 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/es/active-directory/kerberos/kerberos-observation-with-wireshark.md).
# Observando Kerberos con Wireshark
Notas de seguridad de Active Directory para Observando Kerberos con Wireshark, que cubren enumeración, Kerberos, credenciales, abuso de ACL, movimiento lateral, flujo de explotación y pasos de validación.
### Observando una autenticación
Abrimos Wireshark y luego nos conectamos con un usuario, por ejemplo:
```
user1
```
En Wireshark, puedes filtrar el tráfico Kerberos con:
```
kerberos
```
A continuación observamos los intercambios:
```bash
AS-REQ
AS-REP
TGS-REQ
TGS-REP
```
### Ejemplo con acceso a un recurso compartido sin permisos
Desde `user2`, intentamos acceder a un recurso compartido administrativo:
```
cd //WS01/C$
```
En Wireshark, podemos observar:
```
TGS-REQ
TGS-REP
Acceso SMB denegado
```
Esto significa que:
1. el usuario solicita un ticket de servicio;
2. el KDC emite el ticket;
3. el ticket se presenta al servidor;
4. el servidor deniega el acceso debido a permisos SMB o NTFS.
### Ticket y autenticador
Al acceder a un servicio, el cliente generalmente envía:
* un ticket de servicio;
* un autenticador.
El ticket demuestra que el KDC autorizó el acceso al servicio.
El autenticador demuestra que el cliente es realmente quien usa el 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/es/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.
