hardMultiple ChoiceObjective-mapped
Brute Force Attack Detection: SIEM Alert Discrepancy
An organization has implemented a security information and event management (SIEM) system. The SOC analyst receives an alert indicating a high number of failed login attempts from a single IP address targeting a critical server. The analyst checks the server logs and finds that the server is configured to lock the account after 5 failed attempts. However, the alert shows thousands of attempts. Which of the following explains this discrepancy?
Quick Answer
The discrepancy is explained by the fact that the failed login attempts target different usernames rather than a single account. While the server’s account lockout policy blocks a specific user after five failed attempts, it does not limit the total number of attempts from a single IP address across multiple usernames. This means an attacker can cycle through thousands of distinct usernames, each failing up to five times, generating the high event count seen in the SIEM alert. On the Cisco CyberOps Associate 200-201 exam, this scenario tests your understanding of how SIEM aggregation differs from host-based security controls—a common trap is assuming lockout policies apply per source IP rather than per user. Remember the key distinction: lockout is user-specific, while SIEM alerts are source-IP-specific. A helpful memory tip is “Five per name, not per frame”—the lockout counts per username, not per network address.
⚠ Common exam trap
Cisco often tests the distinction between account lockout (per user) and failed login events (per source IP), trapping candidates who assume lockout limits total attempts from an IP rather than per-username attempts.
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
✓
The failed attempts are against different usernames, not the same account
The account lockout policy (5 failed attempts) applies per individual username, not per source IP address. If the attacker is attempting to authenticate with many different usernames from the same IP, each username can fail up to 5 times before being locked, allowing thousands of total failed attempts across different accounts. The SIEM aggregates all failed authentication events from that IP, while the server's lockout mechanism only triggers per user, explaining the discrepancy.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The failed attempts are against different usernames, not the same account
Why this is correct
This is a common technique to avoid lockout; each account may have only a few attempts, but total attempts across many accounts are high.
- ✗
The attacker is using a brute-force tool that bypasses account lockout
Why it's wrong here
Account lockout is a server-side setting; brute-force tools cannot bypass it if properly enforced.
- ✗
The server's logging is not capturing all authentication events
Why it's wrong here
Logging issues could cause inconsistencies, but the scenario describes a typical multi-username attack.
- ✗
The SIEM alert is a false positive due to a misconfiguration
Why it's wrong here
While possible, the described behavior is more consistent with a targeted attack using multiple usernames.
Go deeper
Related to this question
About these practice questions
This 200-201 question is part of Courseiva's 979-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 →
Same concept, more angles
1 more way this is tested on 200-201
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Refer to the exhibit. A Windows security log shows several events with Event ID 4625 (failed logon). What type of attack is indicated?
easy- ✓ A.Brute force attack
- B.Pass-the-hash attack
- C.Kerberos golden ticket attack
- D.Man-in-the-middle attack
Why A: Event ID 4625 indicates a failed logon attempt. A high volume of these events in a short period is characteristic of a brute force attack, where an attacker systematically tries multiple username/password combinations to gain unauthorized access. This is a direct indicator of repeated authentication failures, not a more sophisticated attack.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 200-201 practice question is part of Courseiva's free Cisco 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 200-201 exam.