GSEC Windows Security Infrastructure Practice Question
When analyzing Windows event logs to detect brute-force activity, which Event ID indicates a failed logon attempt?
⚠ Common exam trap
Test-takers frequently confuse Event ID 4625 (failed logons) with Event ID 4624 (successful logons) when writing detection queries for brute-force attacks.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Event ID 4625
Event ID 4625 is the standard Windows Security log identifier for a failed logon. Monitoring this ID is essential for identifying brute-force or credential-stuffing attacks. By correlating these logs across multiple systems, security teams can detect patterns of malicious behavior, allowing for automated account lockouts or IP blocking, which are critical components of an effective incident response strategy for Windows infrastructure.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Event ID 4624
Why it's wrong here
Event ID 4624 signifies a successful logon. In a security operations context, this event provides critical information about user access patterns, but it does not alert on failed attempts, making it ineffective for detecting brute-force activity or unauthorized login attempts occurring within the enterprise network.
- ✓
Event ID 4625
Why this is correct
Event ID 4625 is the definitive log entry for a failed logon attempt in the Windows Security event log. It contains valuable metadata such as the username, source IP address, and logon type, which are necessary for identifying the origin and target of a brute-force attack.
- ✗
Event ID 4740
Why it's wrong here
Event ID 4740 indicates that a user account has been locked out. While this is a byproduct of a brute-force attack, the initial failure is captured by 4625. Event 4740 is a lagging indicator of a completed security event rather than the precursor event itself.
- ✗
Event ID 4768
Why it's wrong here
Event ID 4768 represents a Kerberos TGT (Ticket Granting Ticket) request. While useful for auditing Kerberos authentication traffic, it is not the standard event generated for generic failed logon attempts, especially those occurring via NTLM or interactive local login methods which are common in brute-force scenarios.
About these practice questions
This GSEC question is part of Courseiva's 351-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official GIAC exam blueprint
This GSEC practice question is part of Courseiva's free GIAC certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GSEC exam.