Threat data · disclosure check

Has this company disclosed a cyber incident?

Enter a listed company's legal name.

In short
Listed companies tell the stock exchange about a cyber incident under Regulation 30 of the SEBI listing regulations, and on our reading the clock for one is twelve hours. The disclosure check reads a company's own NSE filings and returns what it disclosed, when it filed, and the gap from the incident time it states.

Covers NSE main-board filings from to . SME listings on NSE Emerge are not covered. Updated every Friday.

What the check reads

The company's own letters to the National Stock Exchange under Regulation 30 of the SEBI listing regulations: the first disclosure, every update, any clarification the exchange asked for and the reply. Each answer links the filing itself. The time of filing is NSE's dissemination time, to the second. The time of the incident is whatever the letter says, in its words, and nothing else — not a press report, not a later estimate.

Most letters don't say when the incident happened. They say the company “has become aware” or “has detected” it. In that case the answer says so, and the gap isn't measured.

What the filings show

Between 1 January 2023 and 13 November 2026, 67 companies on NSE's main board disclosed 71 cyber incidents between them. 27 of those letters give a date for the incident or for when the company learnt of it, and 5 give a time. Where a date is given, the median gap to the first filing is one day. In 5 cases the exchange itself asked the company for a clarification.

YearIncidents disclosed
202315
202414
202512
202630
Cyber incidents disclosed to NSE, by year of first filing
VerticalIncidents disclosed
Manufacturing20
Finance10
Technology10
Healthcare/Wellness8
Tourism/Hospitality6
Energy/Resources4
Retail3
Insurance2
Real Estate2
Transportation2
Business Services1
Education1
Engineering1
Food Production1
Cyber incidents disclosed to NSE, by scorecard vertical

No company is named in these counts, here or anywhere else in the scorecard. The check names only the company you ask about, from its own filing.

Twelve hours or twenty-four: which limb applies

Regulation 30(6) sets three limbs: twelve hours for an event emanating from within the listed entity (limb ii), twenty-four for one arising outside it (limb iii). SEBI has not said which a cyber incident falls in. Our reading is limb (ii), so the check measures each filing against twelve hours — and it reports the gap rather than calling any filing late.

  • The clock runs from occurrence. Where a letter states only when the company became aware, detected or confirmed the incident, the check says which, and measures from that.
  • Separately, Regulation 27(2)(ba) puts cyber incidents, breaches and loss of data into the quarterly corporate governance report with no materiality test, so an incident judged immaterial for Regulation 30 is still reported there.

Work out your own deadlines with the incident reporting clock, or read the LODR cyber disclosure obligations in full.

NSE main-board corporate announcements (not NSE Emerge) from 1 January 2023 to 13 November 2026, swept and read on , refreshed every Friday. Regulation 30(6) and 27(2)(ba) as read from the consolidated SEBI LODR Regulations.

This report counts other people. Find out what yours says.

Your organisation already has a security rating, calculated from signals anyone can see — including the suppliers in the verticals above. Request the complimentary Cyber Risk Rating Report and find out what it says — in as little as 45 minutes for publicly listed entities, up to 48 hours for all others. No agent, no system access, no questionnaire.

Get your free rating →Opens Bitsight’s request form; Bitsight handles what you submit there.See supplier monitoring