Repository navigation
ADitor v0.1.4
ADitor checks your domain's Group Policy and a few directory settings against a catalog of hardening controls, then writes a report you can hand to someone. It only reads; it never changes anything in the directory or SYSVOL.
New: who still uses NTLMv1?
Microsoft switches BlockNtlmv1SSO to enforce by default this month on Windows 11 24H2 and Server 2025. Raising domain controllers to "Refuse LM & NTLM" while something still uses NTLMv1 locks accounts out. ADitor can now tell you who that is.
It still never reads event logs itself. Instead:
- Get the script.
aditor-cli ntlm-script > export.ps1prints a read-only PowerShell script. - List your hosts (domain controllers and member servers) in
$Hostsand run it. Membership of Event Log Readers is enough; it doesn't need Domain Admin. It writesntlmv1-evidence.csv, which holds account and machine names. - Check it.
aditor-cli ntlm-check ntlmv1-evidence.csvlists who still uses NTLMv1, and from where, with counts. - Put it in the report.
aditor-cli scan --ntlm-evidence ntlmv1-evidence.csvshows the same list on the NTLMv2 card.
The script reads two sources:
- Security event 4624 with
NTLM V1, on every Windows version. Anonymous logons are skipped. - The new NTLM log events 4020–4023 and 4030–4033 on Windows 11 24H2 and Server 2025.
An empty list never reads as safe on its own. For each host the check reports how many days of log it read and whether logon auditing was on. The verdict is one of:
- blocked: NTLMv1 was seen.
- not yet: a host couldn't be read, logon auditing was off, or a log covers less than 14 days.
- clear: only for the hosts you exported. NTLMv1 is logged on the server being signed in to, so include every server.
Known limits:
- English only. The script reads the NTLM log's message text, because Microsoft documents those fields by their display names.
- Command line only. The desktop app doesn't have this yet.
- NTLMv1 detection is untested. The build machine runs the script on every build. Reading the logs and the coverage check have been tested there, but the build machine has no NTLMv1 traffic, so picking out real NTLMv1 events hasn't been. Reports from real domains are welcome.
Also in this release (from 0.1.3)
- "Applies to: N of M computers" on each card. ADitor works out which computers each GPO actually reaches, including Block Inheritance and enforced links.
- Start here is ordered safest first, with risk badges, and warns "Lockout risk right now" when needed.
Downloads
| File | Use it for |
|---|---|
ADitor.exe |
The desktop app. Needs WebView2, which Windows 10 and 11 already have. |
aditor-cli.exe |
The command line, including the NTLMv1 commands. For scheduled tasks, RMM agents and Server Core. |
SHA256SUMS.txt |
Checksums. Check them with sha256sum -c, or compare against (Get-FileHash .\aditor-cli.exe -Algorithm SHA256).Hash.ToLower() in PowerShell. |
Neither needs Python installed. This release is still unsigned, so Windows SmartScreen will warn the first time; choose More info → Run anyway. Use ldaps:// (port 636). An ordinary domain user account is enough for the scan. Treat the report and the evidence CSV as sensitive.
Code signing policy: https://github.com/alexlinos/ADitor#code-signing-policy · Security reports: SECURITY.md
Full changelog: v0.1.3...v0.1.4