> 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/ports-and-services/winrm-5986.md).

# WinRM - 5986

Notas de WinRM para acceso con Evil-WinRM, pruebas de fuerza bruta, Pass-the-Hash, autenticación con certificado y administración remota de PowerShell.

WinRM es una vía común de administración remota después de recuperar credenciales, hashes o certificados de cliente. Valida el acceso con Evil-WinRM y prioriza Pass-the-Hash o el inicio de sesión basado en certificados cuando esté disponible.

## Notas

<table data-view="cards" data-full-width="false" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Credenciales</strong></td><td>Conéctate con Evil-WinRM usando contraseñas o hashes NTLM.</td><td><a href="/es/ports-and-services/winrm-5986/evil-winrm-credentials.md">Evil-WinRM - Credenciales</a></td></tr><tr><td><strong>OpenSSL</strong></td><td>Extrae certificados y claves privadas de archivos PFX para iniciar sesión en WinRM.</td><td><a href="/es/ports-and-services/winrm-5986/evil-winrm-openssl.md">Evil-WinRM - OpenSSL</a></td></tr><tr><td><strong>Fuerza bruta</strong></td><td>Prueba la autenticación de WinRM con CrackMapExec y Metasploit.</td><td><a href="/es/ports-and-services/winrm-5986/evil-winrm-brute-force.md">Evil-WinRM - Fuerza bruta</a></td></tr></tbody></table>


---

# 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/ports-and-services/winrm-5986.md?ask=<question>&goal=<user_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.
