Repository navigation
NTLMv1 evidence: who still uses it, from exported event logs - #20
Merged
Merged
Conversation
ADitor still never reads event logs itself. New:
- aditor ntlm-script prints a read-only PowerShell script (Get-WinEvent,
Event Log Readers is enough) that exports, per host:
- Security 4624 events with LmPackageName 'NTLM V1', skipping
ANONYMOUS LOGON;
- NTLM/Operational 4020-4023 and 4030-4033 whose message says
NTLMv1 (Windows 11 24H2 / Server 2025);
- probe rows: the log's oldest event, the newest logon, the newest
NTLM-log event and the export time.
- aditor ntlm-check reads one or more exports. It lists account,
client and server pairs with counts, and gives a verdict: blocked
(NTLMv1 seen), not yet (an unreadable host, no logon auditing, or under
14 days of log), or clear (only for the hosts exported). Exit codes
0 / 1 / 2.
- aditor scan --ntlm-evidence puts the result on the NTLMv2 card. Start
here warns "Still using NTLMv1" when it's blocked. Without evidence,
the card says how to collect it.
- CI runs the script on the Windows build machine with Windows
PowerShell 5.1 and has the built exe read its CSV.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is step 3 of the review follow-up: a "who would break" check for NTLMv1. Microsoft's
BlockNtlmv1SSOswitches to enforce this month.ADitor still never reads event logs itself. An admin runs a read-only script and ADitor reads its CSV.
Commands
aditor ntlm-scriptprints a PowerShell script built onGet-WinEvent. Event Log Readers membership is enough; it doesn't need Domain Admin. The admin lists the hosts to export. For each host it exports:LmPackageName=NTLM V1.TargetUserSidS-1-5-7 (ANONYMOUS LOGON) is skipped.NTLM Version: NTLMv1. These exist on Windows 11 24H2 and Server 2025. Microsoft documents them by display label, not XML field name, so the script reads the message text, which assumes English.aditor ntlm-check CSV…lists account, client and server pairs with counts and a last-seen time, a coverage line per host, and a verdict:aditor scan --ntlm-evidence CSV…puts the result on the NTLMv2 card, with a table and the hosts covered. Start here shows "Still using NTLMv1" when the verdict is blocked. Without evidence, the card explains how to collect it.Testing
aditor-cli.exeread it, and fails if the Security log wasn't read.Not in this PR