> 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-user-enumeration.md). # Enumeración de usuarios con Kerberos Notas de seguridad de Active Directory para Enumeración de usuarios con Kerberos, que cubren enumeración, Kerberos, credenciales, abuso de ACL, movimiento lateral, flujo de explotación y pasos de validación. ### Objetivo Kerberos se puede usar para comprobar si los usuarios existen en el dominio. Esta técnica es útil porque el KDC puede responder de manera diferente dependiendo de si el usuario existe o no. {% embed url="" %} ### Creación de una lista de usuarios Creamos un archivo: {% code overflow="wrap" %} ```bash user1 user2 test1 Administrator Administrador jordan carlos ``` {% endcode %} ### Enumeración con Kerbrute Usamos `kerbrute` para comprobar usuarios válidos: {% code overflow="wrap" %} ```bash kerbrute userenum -d whoami.local --dc dc01.whoami.local usernames.txt ``` {% endcode %} Resultado en el laboratorio: ``` user1 user2 Administrador ``` Esto significa que estas cuentas existen en el dominio.

--- # 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-user-enumeration.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.