CyberKit

Event IDs

Security event 4776

The computer attempted to validate the credentials for an account

Channel: Security. Category: Account Logon (Audit Credential Validation).

What it records

Logged on whichever computer is authoritative for an account's credentials (a domain controller for domain accounts, or the local machine for local accounts) whenever NTLM credential validation occurs. Records the Logon Account, the Source Workstation the request originated from, and an Error Code for failures. It shows only the source workstation, not the destination computer being accessed, and does not fire when a domain account logs on locally to a domain controller.

Why it matters

The primary event for auditing NTLM authentication attempts against domain accounts on a domain controller (Microsoft recommends 4624 instead for local-account logons, since it carries more detail). The Error Code lets analysts distinguish bad-password, bad-username, lockout, and disabled-account scenarios, making it a key brute-force and password-spray detection source alongside 4625.

What triggers it

Any NTLM authentication attempt or a workstation-unlock event. Repeated 0xC000006A (bad password) or 0xC0000064 (bad username) events in sequence are classic brute-force or account-enumeration indicators.

Fields that carry the answer

Key fields
FieldWhat it tells you
Logon AccountThe account whose credentials were validated: the identity to pivot on for all NTLM authentication activity against this DC/host.
Source WorkstationThe computer the authentication attempt originated from: the only source-location field this event provides (it does not record the destination computer), useful for tracing where NTLM brute-force or spray traffic is coming from.
Error Code0xC000006A (bad password) or 0xC0000064 (bad username) repeated in sequence is the classic brute-force/enumeration signature; 0xC0000234 (account locked) helps confirm lockout causes.

In practice

A 4776 on a domain controller might show Logon Account jsmith, Source Workstation WKS-0142, and Error Code 0xC000006A (bad password): a burst of this exact pattern against many different Logon Account values from the same Source Workstation in a short window is the classic password-spray signature, while Error Code 0xC0000234 instead confirms the account is locked out.

Sample record

The computer attempted to validate the credentials for an account.

Authentication Package:	MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Logon Account:	jdoe
Source Workstation:	WKSTN01
Error Code:	0xC000006A

ATT&CK techniques

Sources

Paste a record into Event XML or open a log in EVTX Reader.