mediumMultiple SelectObjective-mapped
Windows Event Log Indicators of Successful Compromise
Which THREE indicators in Windows Event Log are most commonly associated with a successful compromise?
Quick Answer
The answer is Event ID 4624, 4720, and 7045. These three Windows Event Log indicators of compromise are most commonly associated with a successful compromise because they map directly to the attacker’s post-exploitation lifecycle: 4720 signals persistence via a new backdoor account, 7045 reveals a new service installed to execute malicious code with system privileges, and 4624 records anomalous successful logons, such as from unexpected IPs or off-hours, using compromised credentials. On the Cisco CyberOps Associate 200-201 exam, this question tests your ability to correlate specific Event IDs with attacker behavior, often appearing in scenario-based items where you must distinguish normal admin activity from malicious actions. A common trap is confusing 4624 with failed logon events (4625) or overlooking that 4720 and 7045 are post-compromise actions, not initial access. Remember the mnemonic “LNS” for Logon (4624), New user (4720), Service (7045) to recall the triad of successful compromise indicators.
⚠ Common exam trap
Cisco often tests the distinction between events that indicate a successful compromise (e.g., account creation, service installation, successful logon) versus events that indicate failed attempts or normal operations, leading candidates to mistakenly select lockout or firewall allow events as compromise indicators.
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 4720: A user account was created
Event ID 4720 indicates a new user account was created, which is a common post-compromise action where an attacker establishes persistence by adding a backdoor account. Event ID 7045 logs when a new service is installed, often used by malware or attackers to maintain persistence or execute code with system privileges. Event ID 4624 records successful logon events, which after a compromise may show anomalous logons (e.g., from unexpected IPs, off-hours, or using compromised credentials).
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 4740: A user account was locked out
Why it's wrong here
Lockouts are associated with brute force, not necessarily compromise.
- ✓
Event ID 4720: A user account was created
Why this is correct
Creation of new accounts by attacker for persistence.
- ✓
Event ID 7045: A service was installed in the system
Why this is correct
Malware often installs as a service.
- ✓
Event ID 4624: An account was successfully logged on
Why this is correct
Successful logon from unknown account or unusual time indicates compromise.
- ✗
Event ID 5156: The Windows Filtering Platform allowed a connection
Why it's wrong here
This is common and not specific to compromise.
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
2 more ways 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. Which two Sysmon Event IDs are most commonly associated with code injection techniques?
easy- A.Event ID 3 (Network connect)
- ✓ B.Event ID 8 (CreateRemoteThread)
- C.Event ID 1 (Process creation)
- D.Event ID 7 (Image loaded)
- ✓ E.Event ID 10 (ProcessAccess)
Why B: Sysmon Event ID 8 (CreateRemoteThread) is directly associated with code injection because it logs when a thread is created in a remote process, a common technique used by malware to inject malicious code into a legitimate process. Event ID 10 (ProcessAccess) is also critical as it records when a process opens a handle to another process, often a precursor to injecting code via APIs like OpenProcess and WriteProcessMemory.
Variation 2. Match each Windows event log type to its description.
medium- ✓ A.Application: Records events generated by software programs.
- B.Application: Logs events related to system hardware failures.
- C.Security: Logs application installation events.
- ✓ D.Security: Logs security-related events such as logon attempts.
- ✓ E.System: Records events related to system components like drivers.
- ✓ F.Forwarded Events: Contains events collected from remote computers.
Why A: In Windows Event Viewer, the main logs are Application (software events), Security (audit events), Setup (installation events), System (system component events), and Forwarded Events (remote logs). Common confusions include mixing Application and System logs, or Security with Setup.
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.