Vulnerator 2.0 is a maintained rewrite of Vulnerator. It brings the tool to NIST SP 800-53 Rev 5, current DISA checklist and scan formats, and eMASS POA&M and hardware / software exports, and it runs offline on hardened DoD workstations without administrator rights.
- Download
Vulnerator-<version>.zipfrom Releases and check its SHA-256 against the release page:Get-FileHash .\Vulnerator-<version>.zip. - If Windows marks the zip as downloaded from the internet, right-click it > Properties > Unblock, then extract it. Extract all of the files.
- Run
Vulnerator.exefrom inside the folder (desktop shortcut: right-click > Send to > Desktop (create shortcut)). - Choose Portable (database next to the program) or Persistent (a database file you pick), then complete the one-time setup under Settings: your details, eMASS export values and marking, the DISA STIG library and your eMASS IG/AP export.
Requirements: 64-bit Windows, .NET Framework 4.8. No installation, no administrator rights. The database engine is
winsqlite3.dll (part of Windows), and the program runs with .NET strong-name bypass disabled. Nothing contacts the
internet unless you turn on Settings > Online Checks; STIG Manager pulls (Settings > STIG Manager, off by
default) contact only the server you enter. The program's Help page covers setup, importing, findings,
reports and the log.
| Imports | STIG checklists (.ckl, STIG Viewer 3 .cklb, Evaluate-STIG output - older results in Previous folders skipped); ACAS / Nessus (.nessus, CSV) from files, zips or folders of zips; SCAP / SCC XCCDF results; the DISA STIG library; checklists pulled from a STIG Manager server (opt-in) |
| NIST SP 800-53 Rev 5 | Findings mapped to CCIs and Rev 5 controls (DISA CCI list, CNSSI 1253 baselines); eMASS assessment procedures from your own IG/AP export |
| Reports | eMASS POA&M and Hardware / Software workbooks, STIG Details, PDF Summary, Risk Assessment Report, SCAP & STIG Discrepancies, Ports, Protocols & Services, per-host STIG checklists |
| Handling | Classification / handling marking on every export; labeled input files imported only after you confirm the label |
| Configuration Management | Hardware, software, groups and ports, protocols and services; one record per device (permanent VUL- registry numbers, matching by name / FQDN / NetBIOS, merge with aliases) |
| Dashboards (included add-on) | Offline charts: open findings by severity, top hosts, compliance by control family, POA&M aging, trend, coverage gaps, outdated STIG checklists, active IAVMs |
Vulnerator.exe and its libraries, LICENSE.txt, THIRD-PARTY-NOTICES.txt, the Dashboards add-on in
Add-ons\Dashboards, and Test-RealData.ps1, which imports a
folder of your own files into a throwaway database and prints one line per file (nothing leaves your machine). Each
release also carries the zip's SHA-256 and a per-file hash list for application allow-listing.
Every build is scanned by the security-scan job in the Build workflow: an SBOM of the shipped program (Syft, SPDX 2.3 and CycloneDX), dependency vulnerabilities with CVSS, EPSS and CISA KEV (Grype), and static analysis of the source (Semgrep). It writes Developer, Analyst and Leadership reports.
- Latest results: the project page and
docs/security/, updated on every push tomaster. - Per release:
Vulnerator-<version>-security-scan.zip(with.sha256) is attached to each release and holds the reports, SBOMs and raw scanner output. - Code findings: the repository's Security tab (code scanning).
- Method and control mapping:
scanner-payload/COMPLIANCE-OVERVIEW.mdandREFERENCES.md.
There is no local development environment: builds and tests run in GitHub Actions on Windows
(.github/workflows/build.yml) - reference-data and SQL checks, the Release build, a
launch test with strong-name bypass disabled, end-to-end import / export / edit tests on synthetic files, and eMASS
template checks. Pushing a release/v* branch (or a v* tag) publishes that release. Reference data is regenerated
with the scripts in tools/rev5. The project page is docs/index.html (GitHub Pages).
Vulnerator 2.0 application rewrite: Hector L. Bones. Based on Vulnerator by Alex Kuchta, Jeff Vanerwegen, Rick
Murphy, Jeff Purcell and contributors. MIT License (see LICENSE), including the Dashboards add-on (AddOns); bundled
components are listed in THIRD-PARTY-NOTICES.txt in each release.
Vulnerator 2.0 is free and open source. It needs no license key, and future versions will not add one. Anyone may fork it and carry on their own work under the MIT License. Integrations with outside services (Elastic, LLMs and other APIs) are not planned for Vulnerator; forks are welcome to add them.
