Get Started

Select a download option on the left:

  • Release - the latest compiled version of the software (recommended).
  • .zip - a compressed folder containing the latest source for the application.
  • .tar.gz - the same source, as a .tar.gz archive.

If you want to view or contribute to the source, fork the repository on GitHub. Builds and tests run in GitHub Actions; there is no local development environment to set up.

No Licenses, Forks Welcome

Vulnerator 2.0 is free and open source under the MIT License, including the Dashboards add-on. It needs no license key, and future versions will not add one. Anyone may fork it and carry on their own work. Integrations with outside services (Elastic, LLMs and other APIs) are not planned for Vulnerator; forks are welcome to add them.

Using the Release

  1. Download Vulnerator-<version>.zip and check its SHA-256 against the release page:
    Get-FileHash .\Vulnerator-<version>.zip
  2. If Windows marks the zip as downloaded from the internet, right-click it, choose Properties, tick Unblock, then extract it. It is important that you extract all of the files.
  3. Run Vulnerator.exe from inside the extracted folder. To make a desktop shortcut, right-click Vulnerator.exe and choose Send to > Desktop (create shortcut).
  4. Choose Portable (a database next to the program) or Persistent (a database file you pick), then complete the one-time setup under Settings: your details, the eMASS export values and marking, the DISA STIG library and your eMASS IG/AP export.

Requirements: 64-bit Windows with .NET Framework 4.8. No installation and no administrator rights. Works on hardened DoD workstations: the database engine is winsqlite3.dll, part of Windows, and the program runs with .NET strong-name bypass disabled. It works offline; nothing contacts the internet unless you turn on Settings > Online Checks, and STIG Manager pulls contact only the server you enter. The release zip also holds LICENSE.txt, THIRD-PARTY-NOTICES.txt, a per-file hash list for application allow-listing and Test-RealData.ps1, which checks a folder of your own files against a throwaway database.

What Vulnerator 2.0 Does

Imports

  • STIG checklists: .ckl, STIG Viewer 3 .cklb and Evaluate-STIG output (older results in Previous folders are skipped)
  • ACAS / Nessus: .nessus and CSV, from files, zips or folders of zips
  • SCAP / SCC XCCDF results and the DISA STIG library
  • Checklists pulled from your STIG Manager server (optional, off by default)

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, kept on your machine

Reports

  • eMASS POA&M and Hardware / Software import workbooks
  • STIG Details, PDF Summary, Risk Assessment Report, SCAP & STIG Discrepancies
  • Ports, Protocols & Services (PPSM starting point) and per-host STIG checklists

Handling

  • Classification / handling marking on every export
  • Labeled input files imported only after you confirm the label
  • Hardware, software, groups and ports managed in Configuration Management
  • One record per device: permanent VUL- registry numbers, matching by name, FQDN or NetBIOS, and Merge with remembered aliases

Dashboards (included)

  • Open findings by severity, top hosts and compliance by NIST control family
  • POA&M aging, open/closed trend, assets with no scan or checklist
  • Outdated STIG checklists and active IAVMs with finding titles - offline, with the classification marking
  • Device matching across ACAS and STIG names; open source (MIT)

Security Scan

Every build is scanned automatically: 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). The results below are from the latest scan of master; each release carries its own -security-scan.zip with the full evidence package.

Scan results appear here after the first scan of master finishes.

Scan method and control mapping: Compliance overview · References. Automated scanning does not replace manual review or your ISSO/ISSM's risk decisions.

Latest Release

See the releases page

Further Information

Thank you for your continued support for the project!