ISC · Security and Confidentiality and Privacy · 6 practice questions
SEC Cybersecurity Disclosure: The Four-Business-Day Clock
The SEC filing clock starts when the company determines a cybersecurity incident is material, not when it first detects it. Follow one incident from Monday's alert through Thursday's determination to the following Wednesday's Form 8-K deadline.
Try one first
Hint
Focus on when Item 1.05 says the Form 8-K clock begins: the company's decision about materiality, not the initial discovery or final cost numbers.
Answer A. Under SEC Item 1.05 the four-business-day Form 8-K filing clock begins when the registrant determines a cybersecurity incident is material to investors. Management's June 10 materiality determination therefore triggers the filing deadline; the company need not wait to quantify total remediation costs or to complete the forensic investigation (absent an Attorney General delay).
Why not B: Confirmed exfiltration is a significant factual development and may influence materiality, which makes this choice plausible. It is wrong because confirmation alone does not start the four-business-day filing period, the clock starts when management determines the incident is material.
Why not C: This option tempts because initial detection starts the internal response and investigation. It is incorrect because Item 1.05 ties the Form 8-K clock to the registrant's materiality determination, not mere discovery of an incident.
Why not D: This distractor appeals to the idea that filings should wait for complete facts and cost estimates. It is incorrect because Item 1.05 does not require waiting for final remediation quantification or a completed investigation before the four-business-day period begins once the incident is determined to be material (unless a valid Attorney General delay applies).
The timeline
- MondayA public company detects a ransomware incident.
Assume Item 1.05 applies, no Attorney General delay applies, and no federal holiday intervenes. Detection alone does not start the filing clock.
- WednesdayThe response team confirms customer data access and operational disruption.
These facts inform the materiality assessment. Confirmation alone does not start the clock.
- ThursdayManagement determines the incident is material to investors.
This determination triggers the filing deadline. The company must make the determination without unreasonable delay.
- FridayBusiness day 1 after the determination.
Count from the day after Thursday's determination. The weekend does not count.
- Following MondayBusiness day 2; management briefs the board.
The board briefing does not restart the clock. Thursday remains the trigger.
- Following TuesdayBusiness day 3; forensic work continues.
The company cannot wait for final forensic results or a complete remediation cost estimate before meeting its filing deadline.
- Following WednesdayBusiness day 4; Form 8-K Item 1.05 is due.
File within four business days after Thursday's materiality determination, even though the investigation remains open.
Key points
- Remember: Start the four-business-day clock at the materiality determination, not the initial alert.
- Count business days after the determination date; skip the weekend.
- Ongoing forensic work does not extend the filing deadline.
- A later board briefing does not restart the clock.
How the exam traps you
- Starting the clock at Monday's initial alert. Start at Thursday's materiality determination.
- Waiting for final forensic results before filing. Meet the deadline even though the investigation continues.
- Starting the clock when the board receives its briefing. Use the earlier materiality determination, not the later briefing.
Question 2
Hint
Focus on what event makes an incident a HIPAA breach, not on the separate rules for how or to whom notice must later be given.
Answer D. Under HIPAA's Breach Notification Rule, an impermissible use or disclosure of unsecured PHI is presumed to be a breach unless the covered entity can demonstrate, via a documented risk assessment, a low probability that the PHI was compromised. If the entity cannot make that showing and no exception applies, breach notification procedures must be followed. The 500-individual threshold affects certain reporting logistics (such as timing and HHS/media notice requirements), not whether a breach has occurred.
Why not A: This is tempting because HIPAA has special reporting rules for breaches involving 500 or more individuals, but that threshold governs notice logistics (when to notify HHS and media), not whether breach notification duties arise. Smaller incidents can still trigger required notification.
Why not B: Notification does not depend on proving actual financial harm to individuals. The key question is whether unsecured PHI was impermissibly disclosed and whether the entity can demonstrate a low probability that the PHI was compromised.
Why not C: Some may think you must wait for regulator confirmation, but covered entities are responsible for evaluating incidents themselves under the Breach Notification Rule and initiating notification when required, no prior regulator finding is necessary.
Question 3
Hint
Decide which timeline event actually creates 'awareness' of a personal data breach for the purposes of the 72‑hour rule, not the first sign of an incident or the final investigative milestone.
Answer C. GDPR Article 33 requires notification to the supervisory authority without undue delay and, where feasible, not later than 72 hours after becoming aware of a personal data breach. Nova became aware that personal data were exfiltrated at 5:00 p.m. Saturday when logs confirmed the customer table was taken; therefore the 72-hour deadline is 5:00 p.m. Tuesday. Confirming malware earlier or completing identification later does not delay the start of that 72‑hour period; the controller can provide additional details in follow-up communications.
Why not A: This is tempting because it uses the earliest observable sign of an incident as the start point. However, unusual outbound traffic alone does not establish that the controller was aware a personal data breach had occurred; the GDPR clock runs from awareness of an actual personal data breach, not from initial anomalous activity.
Why not B: This distractor is plausible because confirming malware can give reasonable grounds to suspect a breach. But malware presence does not necessarily mean personal data were exfiltrated; in the scenario the controller only became aware of the personal data breach when logs confirmed exfiltration at 5:00 p.m. Saturday, so the 72‑hour window starts then.
Why not D: This reflects a common but incorrect belief that notification can wait until the investigation is fully complete. GDPR requires notification without undue delay and normally within 72 hours of awareness of the breach; controllers should notify promptly and submit any missing details (such as the final list of affected individuals) later.
Question 4
Hint
Focus on the notice thresholds for HIPAA breaches affecting fewer than 500 individuals and separate individual notice from media notice.
Answer C. Under the HIPAA Breach Notification Rule, a covered entity must notify affected individuals without unreasonable delay and no later than 60 days after discovery for a breach of unsecured PHI. For breaches affecting fewer than 500 individuals in a state or jurisdiction, the covered entity submits the breach information to HHS on the annual timetable (no later than 60 days after the end of the calendar year); media notice applies only when more than 500 residents are affected.
Why not A: This confuses the timelines. The annual timing applies to the HHS report for breaches affecting fewer than 500 individuals; individual notice must still be provided without unreasonable delay and no later than 60 days after discovery.
Why not B: This overgeneralizes the notice requirements. Media notice is required only when a breach affects more than 500 residents of a state or jurisdiction. HHS immediate reporting also applies to breaches affecting 500 or more; smaller breaches use the annual HHS submission.
Why not D: Notice obligations are triggered by a reportable breach of unsecured PHI itself, not by later proof of misuse or identity theft, so affected individuals must be notified on the breach timetable.
Question 5
Hint
Focus on when the controller 'becomes aware' of a reportable personal data breach versus earlier detection, later risk conclusions, or final forensic results.
Answer A. Under Article 33, the controller must notify the supervisory authority without undue delay and, where feasible, not later than 72 hours after becoming aware of a personal data breach. The clock runs from the controller's awareness that a reportable breach occurred; the controller does not need to wait for a final forensic report or a complete record count and may provide supplementary information as it becomes available.
Why not B: Tempting because incident response starts at detection, but mere detection or initial suspicion that data may be involved is not automatically the point of 'awareness' for GDPR timing. The 72‑hour period begins when the controller becomes aware that a reportable personal data breach has occurred, not at the first sign of anomalous activity.
Why not C: Tempting because risk assessment affects other obligations (for example, whether data subjects must be notified), but determining risk is a separate step. Notification to the supervisory authority is triggered earlier, by awareness of the breach, whereas the assessment of whether the breach is likely to result in a risk informs additional actions.
Why not D: Tempting because full forensic clarity seems like the logical moment to report complete details, but GDPR requires notification without undue delay and within 72 hours of awareness. Controllers should not wait for the final investigative conclusion and can submit further details later as they become available.
Question 6
Hint
Distinguish initial discovery and technical confirmation from the registrant's formal determination that it has experienced a material cybersecurity incident (and remember the 'without unreasonable delay' limitation).
Answer A. Under SEC Item 1.05, the four-business-day Form 8-K filing period is triggered when the registrant determines that it has experienced a material cybersecurity incident. That trigger applies when the determination is made (assuming it was made without unreasonable delay) and does not require completion of all forensic work or finalization of every fact. Therefore the clock starts on Friday, the date of the materiality determination.
Why not B: Confirmation and containment are important facts that may inform materiality, which makes this tempting; however, the four-business-day clock starts only when the registrant actually determines the incident is material, which here occurred later on Friday.
Why not C: Detection initiates investigation and escalation and is a plausible milestone, but Item 1.05 ties the filing clock to the registrant's materiality determination, not mere detection (unless detection itself led the registrant to determine materiality).
Why not D: Board review and counsel drafting are governance and drafting steps that commonly follow a materiality determination, but Item 1.05 does not allow delaying the Form 8-K until board sign-off or finalized disclosure language once the registrant has determined the incident is material (absent an authorized delay).
Common questions
Does detecting a cyber incident start the SEC four-business-day clock?
Not by itself. Item 1.05 starts the clock when the company determines the incident is material, which happens Thursday in this timeline.
When is Form 8-K due if materiality is determined on Thursday?
With no intervening federal holiday or permitted delay, the deadline is the following Wednesday. Friday, Monday, Tuesday, and Wednesday are the four business days.
Can a company wait for its cyber investigation to finish before filing?
No. Ongoing forensic work does not postpone the deadline, and the company must make its materiality determination without unreasonable delay.
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 Regulations and standards and frameworks
- PCI DSS vs. NIST CSF vs. ISO 27001 vs. COBIT
- Do NIST CSF and ISO 27001 Satisfy HIPAA or PCI DSS?
- SOC 2 vs ISO 27001 vs PCI DSS vs NIST CSF
- PCI DSS Scope: Card Data, Hosted Checkout, and Admin Systems
- ISO 27001 vs NIST CSF vs SOC 2: Which Should You Choose?
- When Is the NIST Cybersecurity Framework the Right Choice?
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.