Documentation
Modules Guide
Which scan modules to pick for your goal, in what order, and what to check before trusting results.
What modules are for#
A module is one specific capability a scan can run — checking for known CVEs, mapping a network, testing a web app, and so on. You don't need to understand how any individual module works internally; you choose which ones to include when building a scan or a scan profile, based on what you're trying to find out about a target.
Which category to pick, by goal#
Trying to find out what's reachable on a target? Use Reconnaissance. Checking a target against known vulnerabilities (including the same CVE data behind Threat Intel)? Use Vulnerability scanning. Confirming whether a found vulnerability is actually exploitable, in an authorized test? Use Exploitation — only against targets you have explicit permission to test. Gathering public information about a target (web crawling, OSINT) supports the other categories by giving you more context before you scan.
A typical order for a new target#
Start with Reconnaissance to see what's actually there, then run Vulnerability scanning against what you found, and only reach for Exploitation modules if you specifically need to confirm exploitability — most day-to-day analyst work stops after vulnerability scanning. Save this combination as a scan profile (see the Scan Profiles help topic) once you find a set that works well for a given target type, so you don't have to reselect it every time.
Reading a module's status before you scan#
Before running a scan, check the Modules page for anything you're relying on showing Failed or Disabled — a Failed module won't run and won't warn you mid-scan, it'll just be silently missing from your results. If something you need is Failed, flag it to your admin (or reload the registry yourself if you're a Tenant Admin) before trusting a scan's results as complete.
When results seem incomplete#
If a scan came back with less than you expected, check whether any relevant module was Failed or Disabled at the time it ran — that's the most common reason for a gap. A Tenant Admin can reload the module registry (Modules page → Reload, or Settings → General → "Reload modules") to recover a module that failed to load, then you can re-run the scan.
Exploitation modules — a note on authorization#
Modules like payload_generator actively probe whether a vulnerability can be exploited, which is a meaningfully more intrusive action than scanning or observing. Only run these against systems you or your organization are explicitly authorized to test — running them against a target without authorization may violate the law, regardless of intent. These modules are available on the Enterprise plan only.