Active Directory Hardening Series - Part 1 – Disabling NTLMv1
Hello everyone, Jerry Devore back again after to along break from blogging to talk about Active Directory hardening. In my role at...
For outbound NTLM enabling Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers - Audit all will log a 8001 event like this one which shows what the client was authenticating to using NTLM and which process was used to make the connection
If the resource server has Network security: Restrict NTLM: Audit Incoming NTLM Traffic - Enable auditing for domain accounts the server will log a 8003 event that will capture the process being connected to by the client.
If the domain controller performing the "credential verification" for that connection has Network security: Restrict NTLM: Audit NTLM authentication in this domain - Enable all (Domain Controllers Only) it will log a event 8004 which captures the user name, workstation name and server name (Secure Channel Name).
The 8001, 8002, 8004 events will be logged a log dedicated to NTLM (Applications and Services Logs\Microsoft\Windows\NTLM\Operational)
Additionall logging will soon be added to Windows 11 24H2 and Server 2025 which will enabling central logging of NTLMv1 via the domain controller logs.
Thanks I 100% agree and I somehow knew that this can be a way how to analyze this. However, in my case I don't have access to logs of domain controllers. I'm just an admin on a server joined to a domain.