Courseiva
Incident Management →mediumMultiple Select

CISM Practice Question: Which TWO of the following are typical notification deadlines for regulatory reporting of…

Which TWO of the following are typical notification deadlines for regulatory reporting of a data breach? (Select two.)

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

✓

4 business days (SEC proposed)

Option A (4 business days, SEC proposed) is correct because the U.S. Securities and Exchange Commission's proposed rules for public companies would require disclosure of material cybersecurity incidents on Form 8-K within four business days of determining that the incident is material. Option C (72 hours, GDPR) is correct because Article 33 of the EU General Data Protection Regulation requires controllers to notify the competent supervisory authority of a personal data breach without undue delay and, where feasible, no later than 72 hours after becoming aware of it. The remaining options do not match these regulatory frameworks: 30 days (B) is not the standard GDPR or SEC notification deadline, 7 days (D) is not specified by either regime, and 24 hours (E) is a shorter window than either the SEC's four-business-day or GDPR's 72-hour requirement.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    4 business days (SEC proposed)

    Why this is correct

    The SEC's proposed rule requires registrants to report material cybersecurity incidents on Form 8-K within four business days of determining materiality, satisfying the stem's regulatory notification deadline. This fixed, short window reflects the US securities regime's emphasis on prompt investor disclosure, distinct from GDPR's 72-hour supervisory authority timescale.

  • ✗

    30 days

    Why it's wrong here

    Thirty days is a contractual or internal remediation window, not a typical regulatory breach notification deadline, which is usually expressed in hours or a few days. It tempts because GDPR-style timelines and many state laws use day-based limits, and 30 days fits payment-card or vendor remediation clauses rather than notification.

  • ✓

    72 hours (GDPR)

    Why this is correct

    GDPR Article 33 requires controllers to notify the supervisory authority within 72 hours of becoming aware of a personal data breach, unless the breach is unlikely to result in risk to rights and freedoms. This fixed deadline satisfies the stem's regulatory reporting constraint, making it a typical notification timeframe.

  • ✗

    7 days

    Why it's wrong here

    Seven days is not a typical regulatory breach notification deadline; statutes generally require notification within 72 hours or by a set number of days such as 30 or 60. It tempts because weekly reporting cycles exist in operational and vendor contexts, where seven days is the correct cadence for status updates rather than breach notification.

  • ✗

    24 hours

    Why it's wrong here

    Twenty-four hours is a plausible-sounding figure but is not the standard regulatory notification deadline; regimes typically specify 72 hours, 30 days, or 'without undue delay'. It tempts because incident response SLAs and some sector rules use 24-hour reporting, so it is correct for internal escalation, not statutory breach notification.

About these practice questions

One of 924 original CISM practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

You might also like

Similar CISM questions

Written by Johnson Ajibi, MSc IT Security

Security Systems Architect · founder of Courseiva

This CISM practice question is part of Courseiva's free ISACA 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 CISM exam.