- A
Enable signature-based detection on the IDS
Why wrong: Signature-based IDS detects known attack patterns, but failed logins may not be a signature-based detection scenario unless combined with other indicators.
- B
Implement a host-based IDS on the server
Why wrong: A HIDS monitors system calls and file integrity; it is not the most efficient direct solution for alerting on failed logins across the network.
- C
Create a SIEM correlation rule to alert on multiple failed logins from the same source
A SIEM correlation rule can aggregate failed login events and trigger an alert when a threshold is met, which directly addresses the scenario.
- D
Increase log retention to 1 year
Why wrong: Log retention helps with forensics but does not proactively alert on failed login attempts.
SSCP Risk Identification, Monitoring, and Analysis Practice Question
This SSCP practice question tests your understanding of risk identification, monitoring, and analysis. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A security analyst is reviewing logs and notices multiple failed login attempts from a single IP address against an administrative account. The SIEM has not generated an alert. Which configuration change would best detect this scenario?
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
Create a SIEM correlation rule to alert on multiple failed logins from the same source
Option C is correct because a SIEM correlation rule can specifically detect multiple failed login attempts from the same source IP address by aggregating and analyzing log events in real time. Unlike signature-based or host-based IDS solutions, a SIEM correlation rule can be tuned to match this exact behavioral pattern, triggering an alert when the configured threshold (e.g., 5 failures within 10 minutes) is exceeded. This directly addresses the gap where the SIEM failed to generate an alert due to the absence of such a rule.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Enable signature-based detection on the IDS
Why it's wrong here
Signature-based IDS detects known attack patterns, but failed logins may not be a signature-based detection scenario unless combined with other indicators.
- ✗
Implement a host-based IDS on the server
Why it's wrong here
A HIDS monitors system calls and file integrity; it is not the most efficient direct solution for alerting on failed logins across the network.
- ✓
Create a SIEM correlation rule to alert on multiple failed logins from the same source
Why this is correct
A SIEM correlation rule can aggregate failed login events and trigger an alert when a threshold is met, which directly addresses the scenario.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Increase log retention to 1 year
Why it's wrong here
Log retention helps with forensics but does not proactively alert on failed login attempts.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse the roles of IDS/IPS and SIEM, mistakenly thinking signature-based or host-based IDS can natively correlate login failures from a single source, when in fact SIEM correlation rules are specifically designed for this multi-event behavioral detection.
Trap categories for this question
Scenario analysis trap
Signature-based IDS detects known attack patterns, but failed logins may not be a signature-based detection scenario unless combined with other indicators.
Detailed technical explanation
How to think about this question
SIEM correlation rules use event aggregation and sliding time windows (e.g., 5 events in 300 seconds) to detect brute-force attacks, leveraging fields like Source IP, EventID (e.g., Windows Event ID 4625 for failed logon), and Account Name. Under the hood, the SIEM engine performs stateful analysis by maintaining counters per source IP and resetting them after the window expires, which is far more efficient than signature-based IDS for this scenario. In real-world deployments, tuning the threshold is critical to avoid false positives from legitimate users with forgotten passwords.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A security analyst at a medium-sized enterprise encounters this scenario during an investigation or architecture review. The correct answer reflects best practice for the specific threat or control described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Security exam questions test whether you can match controls to threats in context — not just recall definitions.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Risk Identification, Monitoring, and Analysis — study guide chapter
Learn the concepts, then practise the questions
- →
Risk Identification, Monitoring, and Analysis practice questions
Targeted practice on this topic area only
- →
All SSCP questions
1,000 questions across all exam domains
- →
Systems Security Certified Practitioner SSCP study guide
Full concept coverage aligned to exam objectives
- →
SSCP practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SSCP practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Access Controls practice questions
Practise SSCP questions linked to Access Controls.
Risk Identification, Monitoring, and Analysis practice questions
Practise SSCP questions linked to Risk Identification, Monitoring, and Analysis.
Incident Response and Recovery practice questions
Practise SSCP questions linked to Incident Response and Recovery.
Security Operations and Administration practice questions
Practise SSCP questions linked to Security Operations and Administration.
Cryptography practice questions
Practise SSCP questions linked to Cryptography.
Network and Communications Security practice questions
Practise SSCP questions linked to Network and Communications Security.
Systems and Application Security practice questions
Practise SSCP questions linked to Systems and Application Security.
Risk Identification, Monitoring and Analysis practice questions
Practise SSCP questions linked to Risk Identification, Monitoring and Analysis.
SSCP fundamentals practice questions
Practise SSCP questions linked to SSCP fundamentals.
SSCP scenario practice questions
Practise SSCP questions linked to SSCP scenario.
SSCP troubleshooting practice questions
Practise SSCP questions linked to SSCP troubleshooting.
Practice this exam
Start a free SSCP practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SSCP question test?
Risk Identification, Monitoring, and Analysis — This question tests Risk Identification, Monitoring, and Analysis — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Create a SIEM correlation rule to alert on multiple failed logins from the same source — Option C is correct because a SIEM correlation rule can specifically detect multiple failed login attempts from the same source IP address by aggregating and analyzing log events in real time. Unlike signature-based or host-based IDS solutions, a SIEM correlation rule can be tuned to match this exact behavioral pattern, triggering an alert when the configured threshold (e.g., 5 failures within 10 minutes) is exceeded. This directly addresses the gap where the SIEM failed to generate an alert due to the absence of such a rule.
What should I do if I get this SSCP question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jul 4, 2026
This SSCP practice question is part of Courseiva's free ISC2 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 SSCP exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.