Repository navigation
Releases
ADitor v0.1.5
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.
Changed: partly applied settings say what's done and what isn't
When a GPO reaches only some of the machines a check is about, the card now leads with the progress, then the gap:
✓ Done on 40 of 50 computers: OU=Workstations (40).
✗ Not yet on 10: OU=Servers (8), OU=Domain Controllers (2). What that leaves open: (why the setting matters). Link the GPO there too, or to a container above them.
Next: apply the same setting to the 10 computers it doesn't reach yet.
Fixed: computer accounts that never apply Group Policy no longer count
v0.1.3 counted every enabled computer account. Some never process Group Policy, so a GPO "missing" them isn't a gap: appliances, cluster and listener names, and AZUREADSSOACC. ADitor now counts only accounts with a Windows operating system, and "About this scan" says how many it left out.
If you upgraded from 0.1.2 and saw checks for all computers go from pass to fail: most of those are real. Usually the GPO is linked to the workstations OU but not to servers or domain controllers. The cards now name where.
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 ntlm-script and ntlm-check. For scheduled tasks, RMM agents and Server Core. |
SHA256SUMS.txt |
Checksums. Check them with sha256sum -c, or compare against (Get-FileHash .\ADitor.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. Treat the report as sensitive.
Code signing policy: https://github.com/alexlinos/ADitor#code-signing-policy · Security reports: SECURITY.md
Full changelog: v0.1.4...v0.1.5
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
ADitor v0.1.3
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.
This release changes results. Your verdicts may change compared with 0.1.2, and comparing scans in History will say "Different ADitor versions". That comes from these fixes, not from your domain.
New: ADitor works out which computers a GPO reaches
ADitor now reads every enabled computer once and works out which GPOs reach it. It walks the computer's OU up to the domain root; Block Inheritance stops a link unless the link is enforced.
- Each card says how far a setting reaches, for example "Applies to: 12 of 1,450 computers".
- The machines it doesn't reach count as having no value, so they get the check's Windows default, unknown, or not started. A setting linked only to a test OU no longer passes as if it applied domain-wide.
- Domain controllers are found by account type, so a DC moved out of the Domain Controllers OU still counts.
- Block Inheritance is read even on OUs with no GPO links.
- Site links are read from the forest root. A site link to another domain's GPO is no longer credited to your domain.
- If computers can't be read, ADitor falls back to judging GPOs by their links, and "About this scan" says so.
A report that's easier to act on
- Start here is ordered safest first, with a risk badge on each item: Safe: logging only, Low risk, Pilot first, Can lock people out.
- A "Lockout risk right now" warning when domain controllers refuse NTLMv1 (NTLMv2 level 5) while other machines are still set to send it.
- Each card leads with one line on why it matters, plus Microsoft's deadline where there is one. NTLMv1 blocking becomes the default this month on Windows 11 24H2 and Server 2025.
- The full fix folds under "How to fix it, step by step". The next step and safety warnings stay open.
- A rollout progress line sits under the results: enforced / at step 1 / not started.
- The result tiles add up to the number of checks.
Fixed
- One caveat said the opposite of what it meant: "No value here means NTLM is blocked". It now says no value of this setting blocks NTLM.
- The Print Spooler check is "unknown" when unset. It used to assume RPC over TCP, which the scan can't see.
- No "Done" ticks on checks the scan couldn't confirm.
- History no longer flags reworded explanations as "the expected value changed".
- Channel-binding events 3074 and 3075 are listed, with the updates that added them.
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, for scheduled tasks, RMM agents and Server Core. |
SHA256SUMS.txt |
Checksums. Check them with sha256sum -c, or compare against (Get-FileHash .\ADitor.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. Treat the report as sensitive.
Code signing policy: https://github.com/alexlinos/ADitor#code-signing-policy · Security reports: SECURITY.md
Full changelog: v0.1.2...v0.1.3
ADitor v0.1.2
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.
This release fixes results. Your verdicts may change compared with 0.1.1, and comparing a new scan with an older one in History will say "Different ADitor versions". That's expected: the differences come from these fixes, not from your domain.
Fixed
- A GPO only counts where it applies. Before, a setting counted even if its GPO was unlinked, its link was disabled, or it was linked only to an OU without the machines the check is about. So a domain-controller setting sitting in an unused GPO could show as a pass. Now:
- A setting only counts through an enabled link.
- For domain-controller checks, that link must be on the domain root, the Domain Controllers OU, or a site.
- A GPO with its computer settings disabled counts nowhere.
- A setting that doesn't count is still shown, with a note naming the GPO and why.
- Site links are read, so a GPO linked to an AD site isn't treated as unlinked.
- A pass next to an unreadable GPO is now "unknown". If a GPO that applies couldn't be read, it could be setting a weaker value, so ADitor no longer calls the check a pass.
- Step 1 of a rollout says what it really does. It used to be called "audit mode" that blocks nothing, for every check. That was wrong for NTLMv2 (level 3 already stops old devices that only accept NTLMv1) and for LDAP channel binding. Each check now describes its own first step.
- Kerberos: any AES-only value passes. The domain-controller encryption-types check used to accept only 0x38, so 0x18 (also AES only) failed. Settings that include RC4 or DES still fail.
- Conflicts between different parts of the domain. When GPOs are linked to different places, for example 1 on the domain root and 5 enforced on the Domain Controllers OU, the report now says machines outside the enforced link really get the other value. It used to say they were "likely overridden".
- A plain GPO name in the sample report, in place of the test name it used to show.
Also
- Both executables now carry product name and version details (right-click → Properties → Details).
- The README has a Code signing policy. Releases will be signed through the SignPath Foundation once the project is approved; this release is still unsigned.
Which file do I want?
| File | Use it for |
|---|---|
ADitor.exe |
The desktop app: connect, scan, and compare scans over time. Needs WebView2, which Windows 10 and 11 already have. |
aditor-cli.exe |
The command line, for scheduled tasks, RMM agents and Server Core. |
SHA256SUMS.txt |
Checksums for both. |
Neither needs Python installed. To check a download in PowerShell, run this and compare the result with the line in SHA256SUMS.txt:
(Get-FileHash .\ADitor.exe -Algorithm SHA256).Hash.ToLower()Before you run it
- The executables aren't code-signed yet. Windows SmartScreen will warn you the first time. Choose More info → Run anyway, or build from source.
- Use
ldaps://(port 636). With plainldap://the bind password crosses the network unencrypted. - An ordinary domain user account is enough.
- Treat the report as sensitive. It contains your GPO names, registry values and distinguished names.
Code signing policy: https://github.com/alexlinos/ADitor#code-signing-policy · Security reports: SECURITY.md
Full changelog: v0.1.1...v0.1.2
ADitor v0.1.1
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.
This release has the same scanner and checks as 0.1.0. What's new is how it's built and tested.
What changed
- Tested on a machine without Python. Before a release is published,
aditor-cli.exeis now run on a clean Windows Server Core machine with no Python, uv or pip installed. That confirms the download really is a single file you can run. - Releases wait for every check. A release is only published after the build, the tests and the clean-machine run all pass.
- New project page at https://alexlinos.github.io/ADitor/, with a sample report you can open in your browser.
Which file do I want?
| File | Use it for |
|---|---|
ADitor.exe |
The desktop app: connect, scan, and compare scans over time. Needs WebView2, which Windows 10 and 11 already have. |
aditor-cli.exe |
The command line, for scheduled tasks, RMM agents and Server Core. |
SHA256SUMS.txt |
Checksums for both. |
Neither needs Python installed.
To check a download, run this in PowerShell and compare the result with the line in SHA256SUMS.txt:
(Get-FileHash .\ADitor.exe -Algorithm SHA256).Hash.ToLower()Before you run it
- The executables aren't code-signed yet. Windows SmartScreen will warn you the first time. Choose More info → Run anyway, or build from source.
- Use
ldaps://(port 636). With plainldap://the bind password crosses the network unencrypted. ADitor allows it, but warns every time. - An ordinary domain user account is enough. It doesn't need Domain Admin.
- Treat the report as sensitive. It contains your GPO names, registry values and distinguished names.
Found a security problem? Please report it privately, as described in SECURITY.md.
Full changelog: v0.1.0...v0.1.1
ADitor v0.1.0
Full Changelog: https://github.com/alexlinos/ADitor/commits/v0.1.0