> For the complete documentation index, see [llms.txt](https://docs.alpha-security.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alpha-security.app/reference/supported-tools.md).

# Supported Tools

Alpha includes parsers for the following tools. Any tool not on this list still gets captured and stored as raw output with full-text search. You just won't get automatically extracted entities from it.

## Native Parsers

These parse complex output formats and extract rich entity data.

| Tool                       | Entities extracted                                           |
| -------------------------- | ------------------------------------------------------------ |
| nmap                       | Hosts, services, OS detection                                |
| httpx                      | Web endpoints (URL, status, title, tech)                     |
| nuclei                     | Findings (template ID, severity, matched URL)                |
| netexec (nxc/crackmapexec) | Hosts, services, credentials, shares, admin status           |
| gobuster                   | Web endpoints (directories, files)                           |
| ffuf                       | Web endpoints (fuzzed paths, status codes)                   |
| nikto                      | Findings (web vulnerabilities)                               |
| wpscan                     | Findings (WordPress vulnerabilities, users)                  |
| sqlmap                     | Findings (SQL injection points)                              |
| impacket                   | Credentials, identities, tickets (secretsdump, getTGT, etc.) |
| smbclient                  | Shares, files                                                |
| smbmap                     | Shares, permissions                                          |
| ldapsearch                 | Identities, group memberships                                |
| enum4linux-ng              | Hosts, shares, identities, groups                            |
| certipy                    | AD certificate templates, findings                           |
| bloodyad                   | AD objects, ACLs                                             |
| SharpHound / BloodHound.py | AD graph import (JSON collection files)                      |

## Declarative Packs

Line-by-line regex parsers for tools with simpler output.

| Tool        | Entities extracted                     |
| ----------- | -------------------------------------- |
| naabu       | Hosts, services (port scan)            |
| masscan     | Hosts, services (port scan)            |
| dnsx        | Hosts (DNS resolution)                 |
| subfinder   | Hosts (subdomain enumeration)          |
| gau         | Web endpoints (URL archive)            |
| whatweb     | Web endpoints (technology detection)   |
| feroxbuster | Web endpoints (directory brute-force)  |
| kerbrute    | Identities (Kerberos user enumeration) |
| rpcclient   | Identities, groups (RPC enumeration)   |
| hashcat     | Credentials (cracked hashes)           |
| john        | Credentials (cracked hashes)           |
| hydra       | Credentials (brute-forced logins)      |
| medusa      | Credentials (brute-forced logins)      |

## Unsupported tools

Tools without a parser are still fully captured. The raw output is stored, searchable, and linked to the engagement timeline. You can manually create entities from the output if needed.

If you want to add a parser for a tool you use frequently, see the [Parser Pipeline](/architecture/parsers.md) documentation.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.alpha-security.app/reference/supported-tools.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.