SHIELDPHISH · INCIDENT BRIEF

CERT-In 6-Hour Incident Reporting& DPDPA Breach Obligations

Most reportable incidents in Indian enterprises begin with someone clicking, scanning or answering. Two clocks start at once — CERT-In’s six hours from awareness, and the DPDPA’s notification duty — and neither waits for you to finish investigating.

6 hrs
to report to CERT-In, from awareness
180 days
of ICT logs, retained in India
62%
of breaches involved a person
₹250 cr
DPDPA ceiling, per instance

Get the Full Guide

Enter your details for instant access to the full guide and continue with the scope check below.

Please tell us your name.
Please give a valid work email.
Please give a number we can reach you on.

We respect your privacy. Your details will only be used to provide the guide and respond to your request.

✓

Here it is.

Your download should have started automatically. If it did not, use the button below.

The document link has not been set yet — see the comment at the top of this block.
Download the full briefThe First Six Hours — CERT-In and DPDPA incident obligations. PDF.Download the PDF
Take your scope check now20 yes / partly / no questions. Scored out of 20 the moment you finish. Takes 2 minutes.

Prefer to talk it through? Write to info@shieldbyteinfosec.com or call +91 8104995634 / 9820989640.

The evidence

Why Employee Reporting Matters in Cyber Incident Response

Nothing here says people are careless. It says the attack has moved to the one layer no gateway inspects — a well-written sentence, arriving at the moment it is most plausible.

62%
of breaches involved the human element

Verizon’s 2026 DBIR. Not 62% negligence — 62% of intrusions passed through a person doing their job.

16%
of all breaches were social engineering

The third most common breach pattern in the 2026 DBIR. Phishing accounts for 16%; pretexting for a further 6%.

29.44 lakh
incidents handled by CERT-In in 2025

Up roughly 85% on 2023. Phishing, spoofing and identity theft sit on the mandatorily-reportable list.

₹22,495 cr
lost to cyber fraud in India in 2025

Across 28.15 lakh cases reported to I4C, against 22.68 lakh the year before.

The click-rate trap. The 2026 DBIR puts the median click rate on simulated email phishing at about 1.4%, and it has barely moved in years. That number is regularly quoted as reassurance. It is not. In a five-thousand-person organisation, 1.4% is seventy people — and an attacker needs one. Meanwhile phone-centric lures now succeed at roughly 2%, a 40% increase, and large organisations see a median of forty-eight SMS phishing campaigns a year against their mobile devices.
What changed

Which Cyber Incidents Must Be Reported to CERT-In?

The lure is written by a machine

Generative models remove the two tells staff were trained on — broken grammar and generic framing. The message arrives in the reader’s own language, in their manager’s rhythm, referencing work that is genuinely underway.

It no longer arrives only by email

A QR code on a printed notice, an SMS about a delivery, a voice call from the service desk. An incident that arrives by phone starts exactly the same two clocks as one that arrives by inbox.

Shadow AI widened the surface

The 2026 DBIR finds 45% of employees are now regular users of AI on corporate devices, up from 15% the year before — and 67% of them are signed in with non-corporate accounts.

There is no technical control for a good sentence

A message with no attachment, no link and no spoofed domain passes every gateway ever built. The only control left in the path is the person reading it, and whether they say something.

The obligation

CERT-In vs DPDPA: Two Breach Notification Timelines

They start together, they run on different rules, and both are measured from the moment somebody in your organisation reasonably believes something has happened.

Clock one · CERT-In

WhenWhat is required
T + 0The clock starts at awareness, not confirmation. The moment a security team member reasonably believes an incident has occurred you are on it — a still-unproven phishing report already counts.
T + 6 hrsReport to CERT-In. Six hours from awareness, in the prescribed format. There is no extension for an incomplete investigation.
Ongoing180-day ICT log retention, held within India. Produced on request — including the mail-gateway and authentication logs that show what the user actually did.
AnnuallyEmpanelled audit. Since the Sep 2025 MSME baseline, smaller vendors in your chain commission one too.
If you miss itSection 70B consequences. Penalties, loss of empanelment, exclusion from tenders.

Clock two · DPDPA

WhenWhat is required
On breachNotify affected data principals in plain language. What happened, the impact on them, and the remedy. Legal phrasing that obscures the harm does not satisfy this.
On breachNotify the Data Protection Board. Personal-data breaches are notifiable irrespective of whether you judge the harm to be material. Detailed information should be provided to the Board within 72 hours, or such further time as permitted.
Within 90 daysAct on data-principal requests. Access, correction, erasure — including any that arrive because of the breach.
If you are an SDFAdditional duties. India-based DPO, independent audits and DPIAs above the Significant Data Fiduciary thresholds.
ExposureUp to ₹250 crore per instance. Once the Board’s full powers apply from May 2027. The Rules were notified 14 Nov 2025 and phase in until then.
Before hour one

Six Incident Response Controls to Establish Before a Breach

None of these can be built while the clock is running.

01

A reporting path your staff actually use

Six hours from awareness only helps if the person who clicked tells you in minutes rather than hiding it.

02

Report-rate data, not just click-rate

Click rate measures exposure; report rate measures whether the clock can start in time.

03

Coverage of every channel

Email phishing, quishing via QR, smishing over SMS and vishing by voice call.

04

Named owners and a rehearsed decision

Who declares awareness, who files, who drafts the plain-language notice — agreed before the day it is needed.

05

Logs you can produce

180 days, held in India, mapped to the users involved.

06

The same expectations of your vendors, in writing

Their breach starts your clock, and their notification timeline has to leave you time to meet it.

What closes the gap

How Phishing Simulations Strengthen Incident Readiness

Not a trap, and not a test of loyalty. A controlled rehearsal of the moment the organisation is most exposed, run often enough that the response becomes ordinary.

01

Baseline honestly

Segment the workforce and run one campaign before any training, so the number you improve against is real rather than flattering.

02

Simulate the way attacks actually arrive

By department, role, language and difficulty — and across every channel the attacker has, not just the inbox.

03

Train at the moment of the mistake

The teachable second is the one immediately after the click. Auto-enrolment at that moment outperforms an annual module by a distance.

04

Reinforce between campaigns

Awareness decays. Posters, wallpapers, leaderboards and praise for the people who reported keep it in daily sight.

05

Produce evidence, not opinion

Completion records, acknowledgements and certificates an auditor will accept without a follow-up conversation.

The two numbers

CERT-In Incident Reporting and DPDPA Breach Readiness

Click rate — measures exposure

How many people were fooled. Useful once, as a baseline. It falls quickly and then flattens, which makes it a comfortable number to report and a poor one to manage.

Report rate — measures whether the clock can start

How many people told you, and how fast. This is the only behavioural number the six-hour rule actually depends on, and the one that decides whether you file in time or explain later.

The uncomfortable arithmetic. If the average employee waits an hour to admit a click and triage takes two, you have three hours left to investigate, decide and file with CERT-In. That gap is closed by reporting behaviour, not by tooling.
ShieldPhish

How ShieldPhish Supports Incident Response Readiness

Simulation, training, intelligence and evidence in one console — so a click in a simulation triggers the right training, and every action lands in the audit trail.

Phishing Simulation

AI template engine, quishing, spoofing and Emotional Vulnerability Score.

Awareness Training

Courses, quizzes, gamification, certification and a live dashboard.

Threat Intel

Dark-web monitoring, credential leak detection and early alerts.

Document Hub

Policy repository, access control, acknowledgement and versioning.

Vision Board

Awareness posters and wallpapers that keep the message visible.

Data Privacy

DPDPA-aligned data-principal request handling, in the same console.

Self-assessment

Check Your CERT-In and DPDPA Incident Readiness

Twenty statements about how your organisation actually behaves on the day. Answer them with the people who run the mail gateway and the awareness programme in the room — where you cannot answer in one sentence, the honest answer is no.

🔒

Open the check

Fill the short form at the top of this page. It opens the check here and the full document at the same time — it takes about a minute.

Take me to the form

What is actually arriving

01
You know how many phishing attempts reach an inbox each month — a number, not an impression.
02
You know what proportion arrive by QR code, SMS or voice call rather than email.
03
Someone reviews which lures are working on your workforce, not just how many were blocked.
04
You have seen at least one attempt in the last year that used your executives’ names or writing style.

How people report

05
There is a report button in the mail client, and staff know it exists.
06
You measure report rate — how many people told you — alongside click rate.
07
You know the median time between a suspicious mail arriving and someone reporting it.
08
Someone who clicks and admits it is thanked, not disciplined, and staff believe that.

What you run today

09
You run simulations on a schedule, not once a year before an audit.
10
Lures are varied by department, role and difficulty rather than one template for everyone.
11
Simulations cover channels other than email — at least QR and SMS.
12
Vendors, contractors and temporary staff are inside the programme, not outside it.

Training and culture

13
Anyone who fails a simulation is enrolled in training immediately, not at the next cycle.
14
Training is role-based, and finance and HR get something different from engineering.
15
Completion is tracked and chased automatically, with supervisor escalation.
16
Awareness is visible between campaigns — not only in the week a module is due.

Evidence and the clock

17
You could produce completion and acknowledgement records for an auditor this week.
18
Your policy acknowledgements are tracked per person and per version.
19
A phishing report reaches a named owner who can declare awareness and start the six-hour clock.
20
You have rehearsed the six-hour filing at least once, with the people who would actually do it.
0 of 20 answered
0
of 20 yes
Your result

Where the gaps are

Download the full brief
Want the no’s turned into a dated plan? Write to info@shieldbyteinfosec.com.

Strengthen Your CERT-In and DPDPA Incident Readiness

CERT-In empanelled assessors work through this with the people who own the systems, and leave you with evidence rather than an opinion.

info@shieldbyteinfosec.com +91 8104995634 / 9820989640

Verizon 2026 Data Breach Investigations Report; CERT-In figures via PIB (2025); Ministry of Home Affairs / I4C (2025); CERT-In Directions under s.70B of the IT Act, 2000; Digital Personal Data Protection Rules, 2025. Platform capabilities as published in ShieldPhish collateral. This page is a summary prepared for orientation; it does not replace the underlying instrument or professional advice.

error: Content is protected !!