ISC · Security and Confidentiality and Privacy · 10 practice questions
When to Activate Incident Response: Event vs. Incident
Activate incident response when credible indicators meet the plan’s threshold for suspected compromise, not only after proven data theft. Below: compare the same login activity with one fact changed each time.
Try one first
Hint
Focus on what level of evidence usually triggers incident response: suspicion based on credible indicators, or proof of final impact.
Answer C. Incident response should be triggered when there is credible evidence of a suspected security incident, not only after all facts are proven. Here, use of a terminated employee's account, access to sensitive customer tax documents, and unusual outbound traffic together provide a reasonable basis to escalate, contain, and investigate. Waiting for certainty could increase damage and delay required response actions.
Why not A: Legal counsel plays an important role in assessing obligations, but legal review does not replace the operational need to activate incident response once credible indicators appear. Notification and legal analyses proceed as part of the response.
Why not B: This is tempting because candidates may equate an incident with proven harm, but incident response begins when there is reasonable suspicion. Confirmation of exfiltration affects impact assessment and notifications, but is not required to start containment and investigation.
Why not D: While avoiding false positives is reasonable, the presence of multiple high-risk indicators tied to sensitive-data access warrants immediate escalation. Delaying to wait for repetition could allow further compromise or data loss.
Same scenario, one fact changes
Base case
Harbor Co.’s plan requires formal response for actual or reasonably likely unauthorized access to sensitive systems. Monitoring shows repeated failed administrator logins from an unfamiliar external IP after hours, followed by a successful login to the payroll server containing employee tax documents. The activity is unexplained. No data loss, outage, or other indicators are detected.
Answer: Classify this as a security incident and activate incident response now.
The failed attempts followed by unexplained successful administrator access indicate likely unauthorized access to a sensitive system. Harbor does not need confirmed data theft to meet its activation threshold.
Before you open each one, predict the answer.
Change 1The final login also fails, so all attempts are blocked.
Answer: Treat this as a routine security event for now; monitor and reassess.
All access attempts failed, with no other indicators of compromise or impact. Failed attempts alone do not meet Harbor’s stated threshold.
Change 2The activity is verified as an authorized administrator’s approved remote access after password mistakes.
Answer: Treat this as routine authorized activity, not a formal security incident.
Verification explains both the failures and successful access. An unfamiliar IP and after-hours timing do not override confirmed authorization.
Change 3The login activity occurs during business hours instead of after hours.
Answer: Classify this as a security incident and activate incident response now.
Timing does not change the result. Repeated failures followed by unexplained successful administrator access still indicate likely unauthorized access.
Key points
- Remember: likely unauthorized access can trigger incident response before data theft is proven.
- Failed attempts alone do not establish that access succeeded or that the plan’s impact threshold was met.
- A successful login is not automatically unauthorized; verified approval can change the classification.
- Business hours do not make an otherwise suspicious login safe.
How the exam traps you
- Waiting for confirmed theft of tax documents. Activate when likely unauthorized access meets the plan’s threshold.
- Treating every failed login attempt as a formal incident. Assess likely impact and whether access succeeded, rather than counting alerts alone.
- Dismissing suspicious access because it occurred during business hours. Apply the same authorization and impact criteria regardless of the clock.
Now the same facts as questions
Each question changes one fact from the one before. Watch which change flips the answer.
Question 1
Answer B. The unexplained successful login after repeated failures supports likely unauthorized access.
Why not A: Confirmed theft is not required under Harbor’s activation threshold.
Why not C: Use of a valid administrator account does not establish authorization.
Why not D: The threshold is already met; waiting for repetition delays response.
Question 2
Answer C. All attempts were blocked, and no other indicators support likely compromise or impact.
Why not A: Sensitive data increases concern but does not establish that access or likely compromise occurred.
Why not B: Repeated failures alone do not meet Harbor’s stated activation threshold.
Why not D: Failed attempts still warrant monitoring for changes that meet the threshold.
Question 3
Answer A. Verified authorization explains the failed attempts and successful login.
Why not B: An unfamiliar IP alone does not override verified authorization.
Why not C: After-hours timing alone does not turn approved access into an incident.
Why not D: The access is verified as authorized; absence of theft need not be separately proven.
Question 4
Answer D. The same indicators support likely unauthorized access regardless of timing.
Why not A: Business hours do not explain the suspicious successful access.
Why not B: Harbor’s plan does not require confirmed data theft.
Why not C: After-hours activity is not a required element of Harbor’s activation threshold.
Question 2
Hint
Ask what incident response is fundamentally trying to protect, rather than who reported the issue or how easy the fix might be.
Answer A. A formal incident response process is triggered by risk and potential impact, primarily possible harm to confidentiality, integrity, or availability of sensitive data or critical systems. In this scenario, repeated unauthorized login attempts against a database containing personal information pose a potential confidentiality/integrity risk and therefore warrant formal response even before a breach is confirmed. Source, report count, and ease of fix are operational considerations but do not replace an impact-based activation threshold.
Why not B: Candidates may assume incidents are mainly external attacks, but incident response also covers insider threats, accidental disclosures, and misuse. The decision to activate the formal process depends on impact, not solely on whether the actor is external.
Why not C: A higher number of reports can suggest broader impact but is only an indirect indicator. A single alert involving sensitive data can justify activation, while many help-desk complaints might reflect routine service issues.
Why not D: How quickly IT can apply a workaround affects handling and resourcing but does not determine whether the event meets the threshold for formal incident response. Potential exposure of sensitive information requires formal consideration regardless of expected repair speed.
Question 3
Hint
Focus on the limiting condition: which choice describes a security event that was contained with no indication of compromise, impact, or exposure?
Answer A. A blocked and contained suspicious email, with no sign of user interaction or system impact, is generally a routine security event rather than a confirmed or reasonably suspected incident. Formal incident response is usually triggered when there is evidence of compromise, data exposure, operational impact, or a credible threat requiring coordinated containment and investigation.
Why not B: Active ransomware encryption indicates a compromise and operational impact on systems; this is a clear security incident that requires immediate containment, investigation, and likely activation of the incident response plan.
Why not C: Loss of a device with unencrypted sensitive customer data creates a credible risk of data exposure and typically triggers incident response and breach assessment procedures, even before confirmation of actual unauthorized access.
Why not D: Unusual privileged access combined with large transfers of sensitive files strongly suggests possible account compromise and data exfiltration, which should prompt formal incident response to contain and investigate the activity.
Question 4
Hint
Focus on what actions are triggered by credible indicators of unauthorized access to sensitive personal data, even without final confirmation of exfiltration.
Answer C. Credible indicators of unauthorized access to sensitive PII (admin-account queries, large reads, and outbound transmission including SSNs) meet common escalation triggers for immediate IR activation. Early containment and forensic preservation mitigate further exfiltration and preserve evidence for investigation. Promptly involving legal/compliance and senior management enables assessment of regulatory duties and coordination of external communications.
Why not A: Tempting because additional logs can help confirm scope, and some rules reference 'confirmed' breaches. However, waiting for definitive proof risks ongoing exfiltration and loss of evidence; credible signs of unauthorized access to sensitive data warrant immediate containment and escalation rather than delay.
Why not B: Tempting because preparing notifications and lists speeds later communication and shows proactive thinking. But preparing notices alone does not address immediate containment or forensic preservation; external communications should be coordinated by legal after initial containment and investigation to avoid hindering the response or issuing inaccurate information.
Why not D: Tempting because credential resets are a common first step for account compromises. However, the evidence of large reads and outbound transfers of sensitive data (including SSNs) indicates a potential data breach that requires urgent IR activation, containment, and forensic work, not a routine, delayed remediation.
Question 5
Hint
Focus on whether protected personal information was sent to an unauthorized external destination and whether that matches the IR policy's definition of a breach; a valid service account does not automatically imply the activity was authorized.
Answer C. File-audit logs show a backup utility reading files containing customer PII and egress/firewall logs show a large (2.2 GB) outbound transfer to an external IP flagged for exfiltration, and IT confirms no authorized job or business justification for that destination. The organization's IR policy defines a data breach as confirmed unauthorized access or exfiltration of protected personal information; these facts meet that definition. Use of a legitimate service account does not imply authorization when the destination is unauthorized and associated with malicious activity.
Why not A: Appeals to extreme caution about 'definitive proof,' but the stem provides file-audit evidence that PII files were read and egress logs show a substantial transfer to an unauthorized, malicious-associated IP, which satisfies the policy's exfiltration threshold.
Why not B: This is tempting because a known service account performed the action, but it's wrong: the transfer went to an unauthorized external IP outside the scheduled backup window and involved PII, and IT reported no business justification, circumstances consistent with credential misuse or compromise that meet the incident/breach definition.
Why not D: Attractive to those favoring an operational root cause, but even if a scheduling or scripting error occurred, the result is an external transfer of protected PII to a malicious-associated IP with no authorization, making it a security incident and breach that requires IR handling.
Question 6
Hint
Focus on which event most clearly suggests an actual or likely compromise that would trigger formal investigation, not just routine IT support or normal remediation.
Answer C. This fact pattern indicates a likely compromise or attempted compromise of a privileged account and therefore fits the definition of a security incident. The combination of repeated failed attempts, an unfamiliar source, and a successful after-hours login creates a clear need for formal investigation and response; it goes beyond a routine operational event.
Why not A: This is tempting because account lockouts often appear in security logs and can look suspicious. However, the facts describe a routine access issue (forgotten password and automatic lockout) handled by normal controls, not evidence of compromise requiring incident response.
Why not B: This is tempting because unpatched systems are a security concern. But when a vulnerability is discovered by routine scanning and the system is within the approved remediation window with no sign of exploitation, it is a remediation/risk-management issue rather than an active security incident.
Why not D: Performance problems can sometimes stem from malware, which makes this plausibly tempting. Here, though, the cause is identified as low disk space from user files, which makes it an operational support issue rather than a security incident under the stated definition.
Common questions
Does incident response require confirmed data exfiltration?
No. Harbor’s unexplained successful administrator login supports likely unauthorized access, even without confirmed loss of tax documents.
Are failed login attempts a security event or an incident?
Apply the plan’s threshold. If all attempts fail and no other indicators suggest likely compromise or significant impact, routine monitoring is appropriate.
Does a successful administrator login always trigger incident response?
No. Verified, authorized administrator activity can remain routine. An unexplained successful login following repeated failures can support likely unauthorized access.
Practice ISC like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Incident response
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.