Free tool · Incident response

What a stock broker must report after a client data leak

Work out every regulatory notification an Indian entity owes after a cyber incident, as wall-clock IST deadlines — CERT-In, the seven RBI Directions and the RBI’s payment-operator Directions, SEBI CSCRF and LODR, IRDAI, PFRDA, IFSCA and NCIIPC, each with the clause it comes from.

In short
An Indian entity that notices a cyber incident owes CERT-In a report within six hours. RBI regulated entities file on DAKSH within six hours of detection; SEBI entities file to SEBI and CERT-In within six hours, the portal within twenty-four, then reports to seventy-five days. IRDAI is six hours, with no second step. A listed entity owes the exchanges twelve hours. DPDP does not commence until 13 May 2027.

What this case turns on

CSCRF is three filings for most regulated entities and four for a stock broker: six hours to SEBI and CERT-In, six hours to the exchanges and depositories, and the necessary details to the SEBI Incident Reporting Portal at twenty-four. None of them discharges any of the others, and the twenty-four-hour filing is not the end: Annexure-O then wants an interim report at three days, an RCA at thirty, incident VAPT at forty-five and, for a High or Critical incident, a forensic report within seventy-five. Data leak is its own category in CERT-In Annexure I, and it is triggered well below the threshold most firms think of as a breach.

InstrumentWhat you fileWindowStarts from
CERT-In Directions, 2022Report the incident to CERT-In6 hours from noticing, or being brought to noticeNoticing, or being brought to notice
SEBI CSCRFInitial notification of the incident6 hours from noticing, or being brought to noticeNoticing, or being brought to notice
SEBI CSCRFAdditional notification for stock brokers and depository participants6 hours from noticing, or being brought to noticeNoticing, or being brought to notice
SEBI CSCRFNecessary details of the incident24 hours from noticing, or being brought to noticeNoticing, or being brought to notice
SEBI CSCRFSubmit the interim report3 days from reporting the incidentReporting the incident
SEBI CSCRFSubmit the mitigation measures taken7 days from reporting the incidentReporting the incident
SEBI CSCRFSubmit the root cause analysis report, reviewed by the IT Committee30 days from reporting the incidentReporting the incident
SEBI CSCRFSubmit VAPT for the incident, and its closure report45 days from reporting the incidentReporting the incident
SEBI CSCRFSubmit the forensic audit report and its closure report — mandatory for a High or Critical incident75 days from reporting the incidentReporting the incident
SEBI CSCRFReport the quarter’s cyber-attacks, threats, incidents and breaches, and the measures takenWithin 15 days of each quarter ending June, September, December and March—
DPDP Act, 2023 and DPDP Rules, 2025Intimation to affected Data Principals, and a two-stage report to the Data Protection BoardNot in force—
Every filing owed on this scenario, with the window each one runs for.

Adjust it to your own facts

The tool below opens on this scenario. Change anything that does not match your entity, and add the moment you noticed to turn the windows into wall-clock IST deadlines.

Your entity
When you noticed
10filings owed — windows from each trigger
InstrumentWhat you fileWindowGoes to
CERT-In Directions, 2022No. 20(3)/2022-CERT-InReport the incident to CERT-Inwithin 6 hours of noticing such incidents or being brought to notice about such incidents6 hours from noticing, or being brought to noticefrom: noticing, or being brought to noticeCERT-Inincident@cert-in.org.in · 1800-11-4949
SEBI CSCRFSEBI/HO/ITD-1/ITD_CSC_EXT/P/CIR/2024/113Initial notification of the incidentshall be notified to SEBI and CERT-In within 6 hours of noticing/ detecting such incidents or being brought to notice about such incidentsCSCRF’s six hours and CERT-In’s six hours are two filings, not one. Neither discharges the other.6 hours from noticing, or being brought to noticefrom: noticing, or being brought to noticeSEBI and CERT-Inmkt_incidents@sebi.gov.in
SEBI CSCRFSEBI/HO/ITD-1/ITD_CSC_EXT/P/CIR/2024/113Additional notification for stock brokers and depository participants6 hours from noticing, or being brought to noticefrom: noticing, or being brought to noticeStock Exchanges and Depositories
SEBI CSCRFSEBI/HO/ITD-1/ITD_CSC_EXT/P/CIR/2024/113Necessary details of the incidentA third step, not a substitute for either six-hour filing. Since August 2026 the portal takes the report in stages — this filing opens it, and intermediate updates and a final closure are owed as the incident develops.24 hours from noticing, or being brought to noticefrom: noticing, or being brought to noticeSEBI Incident Reporting Portalsiportal.sebi.gov.in
SEBI CSCRFSEBI/HO/ITD-1/ITD_CSC_EXT/P/CIR/2024/113 · Annexure-O, Table 36Submit the interim reportMust carry the time of occurrence, the affected processes, systems, network and services, the severity, and the steps taken to start response and recovery. Counted from the date of reporting, so the deadline shown from noticing can only be early.3 days from reporting the incidentfrom: reporting the incidentSEBI
SEBI CSCRFSEBI/HO/ITD-1/ITD_CSC_EXT/P/CIR/2024/113 · Annexure-O, Table 36Submit the mitigation measures taken7 days from reporting the incidentfrom: reporting the incidentSEBI
SEBI CSCRFSEBI/HO/ITD-1/ITD_CSC_EXT/P/CIR/2024/113 · Annexure-O, Table 36Submit the root cause analysis report, reviewed by the IT CommitteeThe IT Committee reviews the RCA before it goes to SEBI, and a report of that review goes with it — schedule the meeting now. More time is given only on request, case by case, as an exception rather than the rule. A deficient RCA can draw regulatory action, with up to fifteen days to correct it.30 days from reporting the incidentfrom: reporting the incidentSEBI, with the IT Committee’s review report
SEBI CSCRFSEBI/HO/ITD-1/ITD_CSC_EXT/P/CIR/2024/113 · Annexure-O, Table 36Submit VAPT for the incident, and its closure report45 days from reporting the incidentfrom: reporting the incidentSEBI, after IT Committee review
SEBI CSCRFSEBI/HO/ITD-1/ITD_CSC_EXT/P/CIR/2024/113 · Annexure-O, clauses 4.1–4.3Submit the forensic audit report and its closure report — mandatory for a High or Critical incidentthe maximum period for the submission of forensic audit report shall be 75 days from date of reporting of incidentSeventy-five days is the ceiling; the actual date is agreed with SEBI. Any incident that disrupts normal service delivery must be classified High or Critical, so a ransomware event or an outage owes this. For Low or Medium it is owed only if the RCA is inconclusive or SEBI or the HPSC-CS directs it.75 days from reporting the incidentfrom: reporting the incidentSEBI, after IT Committee review
SEBI CSCRFSEBI/HO/ITD-1/ITD_CSC_EXT/P/CIR/2024/113 · RS.CO.S1, guideline 4Report the quarter’s cyber-attacks, threats, incidents and breaches, and the measures takenA standing cadence, not an incident clock, and owed by every regulated entity. It falls due after the incident has closed, so put it on the post-incident checklist.Within 15 days of each quarter ending June, September, December and MarchSEBI
DPDP Act, 2023 and DPDP Rules, 2025G.S.R. 846(E) · Rule 7 · G.S.R. 843(E), section 8Intimation to affected Data Principals, and a two-stage report to the Data Protection BoardNot in force. Rule 7 falls in the eighteen-month tranche under Rule 1(4), and section 8 commences on the same date — 13 May 2027. There is no DPDP breach clock running on an incident today. Plan and rehearse against it; do not file against it.Not in forceData Principals and the Data Protection Board of India

Indicative, and not legal advice. Whether an instrument applies to a particular entity, and whether an event is a reportable incident, are determinations for your compliance and legal team. Verify every citation against the published text before a notification is filed.

Take this away as an escalation pack

Everything above is yours already. This is the version you can put in front of your team — the same result with your details on it, the owner columns your incident file needs, and the checklist attached. It opens here and lands in your inbox, so it is to hand when you actually need it rather than in a tab you closed.

For the full picture — every clock, how they overlap, and the standing obligations that decide how the first six hours go — see the complete incident reporting clock.

This page is indicative and is not legal advice. Whether an instrument applies to your entity, and whether an event is a reportable incident, are determinations for your compliance and legal team. Every instrument cited here was verified against the issuing regulator's own notification on .

Other worked examples

The same calculator, run for a specific entity — with the thresholds and clocks that apply to it, and the instrument each one comes from.

Questions this page answers

How long do you have to report a cyber incident in India?
Six hours to CERT-In, from noticing the incident or being brought to notice of it. Most sectoral clocks are also six hours: RBI regulated entities report on DAKSH within six hours of detection, SEBI regulated entities notify SEBI and CERT-In within six hours, and insurers report to CERT-In within six hours copied to IRDAI. A listed entity separately owes its stock exchanges a disclosure within twelve hours where the incident is material.
Does the six-hour clock start when an incident is confirmed?
No. The CERT-In Directions run from noticing the incident or being brought to notice of it, which means a vendor, a researcher or a regulator telling you starts the clock exactly as your own alerting does. The RBI Directions run from detection. In neither case does an incomplete investigation pause the clock — draft on what is known, mark the unknowns as under investigation, and file the update.
How quickly must a payment system operator report an incident to the RBI?
Within six hours of detection, in the Incident Reporting Format at Annex 1 of the RBI’s Master Directions for non-bank payment system operators, RBI/DPSS/2026-27/475. The duty is wider than a cyber incident — outages of critical systems, internal fraud and settlement delays are reportable too — and a cyber incident goes to CERT-In separately. Large and medium operators are bound now; small PPI issuers and Instant Money Transfer Operators from 1 April 2028.
Is the SEBI LODR deadline for a cyber incident 12 hours or 24 hours?
Plan on twelve hours. Regulation 30(6) sets twelve hours for an event emanating from within the listed entity and twenty-four for an event arising outside it, and SEBI has not said which a cyber incident is. Our reading is that a ransomware event, data breach or IT outage originates within the entity, so it falls in the twelve-hour limb. The twenty-four hour figure is the one most commonly repeated, and planning on it risks a late disclosure if the shorter limb applies.
What does SEBI CSCRF require after the 24-hour portal filing?
Five more reports under Annexure-O, Table 36, each counted from the date the incident was reported: an interim report at three days, mitigation measures at seven, a root cause analysis at thirty, VAPT for the incident with its closure report at forty-five, and a forensic audit report within at most seventy-five days, mandatory for High and Critical incidents. The IT Committee reviews each before it goes to SEBI.
Does the DPDP Act require breach notification within 72 hours today?
No. Rule 7 of the DPDP Rules, 2025 and section 8 of the Act both commence eighteen months after the Rules were notified on 13 November 2025, which is 13 May 2027. There is no DPDP breach-intimation clock running on an incident today. The regime is worth planning and rehearsing against, but a notification filed against it now is filed against an obligation that has not commenced.
How long does a GIFT City entity have to report a cyber incident?
Six hours from detection, to the Authority at cyber-incidents@ifsca.gov.in with a copy to the CISO, IFSCA, under the IFSCA Guidelines on Cyber Security and Cyber Resilience of 10 March 2025. The obligation then continues: an interim report at three days, mitigation measures at seven, and a detailed root cause analysis at thirty. An IFSC licence displaces the mainland regulator, so a GIFT City banking unit does not file under the RBI Directions — but CERT-In still binds it.
Which RBI Direction applies to an NBFC after a cyber incident?
RBI/DoS/2026-27/461, the Non-Banking Financial Companies instrument — not the Commercial Banks Directions at 410. Its chapters are graded: a Base Layer NBFC below ₹500 crore sits under Chapter III, which carries no six-hour DAKSH clause at all, while Chapter IV covers Base Layer at ₹500 crore and above and Chapter V covers the Middle, Upper and Top Layers. CERT-In’s six hours binds every one of them.

Knowing the rule is the easy half.

This page tells you what you owe. It cannot tell you what an attacker already sees. Your organisation has a security rating calculated from signals visible from outside — request the complimentary Cyber Risk Rating Report and find out what it says. No agent, no system access, no questionnaire.

Get your free rating →Opens Bitsight’s request form; Bitsight handles what you submit there.All free tools