Repository navigation
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