Skip to main content
Breach Management

When a breach happens, know what is due and by when

Record the incident, see the time left on the 72-hour deadline, generate the reports for the Data Protection Board and notify the people affected. Every step lands in a timeline you can export.

The clock starts when you find out, not when you are ready

Section 8(6) of the Digital Personal Data Protection Act, 2023 requires you to tell the Data Protection Board and each affected person about a personal data breach. Under Rule 7 of the DPDP Rules, 2025 the people affected and the Board must be told without delay, and a detailed report must reach the Board within 72 hours of you becoming aware of the breach.

In those 72 hours the team is also containing the incident. Nobody has time to work out which report is due, what it must contain or who approved the wording sent to customers. Failing to notify can carry a penalty of up to ₹200 crore.

What the Breach Management module does

  • A structured breach record

    Capture the type of breach, when it happened and was discovered, the data categories involved, the number of people affected, severity, containment steps and the processing activities it touches.

  • 72-hour countdown

    The deadline is set from the time of discovery. The countdown turns from green to amber to red as it runs down, and the breach list counts overdue deadlines.

  • Reports for the Board

    The initial intimation, the 72-hour detailed report and any supplementary report are pre-filled from the breach record. Approve one and download it as a PDF.

  • Notices to affected people

    A plain-language notice is drafted for you, including the person's right to complain to the Board. After an admin approves it, send it by email and SMS to the recipients you provide.

  • A fixed workflow

    Draft, under review, notifying, filed with the Board, remediating, closed. Stages cannot be skipped, only an admin or the DPO can advance them, and a closed record is locked.

  • Remediation log and audit trail

    Track each remediation step as planned, in progress or completed. Export the full timeline of the breach as a PDF.

How it works

  1. Log the breach

    Record what is known now. The DPO is alerted by email, and the 72-hour countdown starts from the discovery time. Security tools can also create a breach through the API.

  2. Assess and contain

    Set severity, list the data categories and the people affected, and note the containment steps taken.

  3. Prepare the reports and notices

    Complete the pre-filled Board reports, approve them and download the PDFs. Approve and send the notice to affected people.

  4. Remediate and close

    Log the remediation work, then close the breach. The record and its timeline stay available for audit.

Questions teams ask

Does Consently file the report with the Data Protection Board for us?

No. Consently drafts the reports, tracks approval and produces the PDF. You file it with the Board yourself and then mark it as submitted, which keeps the record and the workflow up to date.

How are affected people notified?

By email and SMS, to the list of recipients your DPO provides, after an admin approves the wording. SMS to Indian numbers needs a DLT-registered template. Consently keeps the exact text sent and the number of recipients.

Who can see and change a breach record?

Only an account admin or the assigned DPO can move a breach through its workflow. Once a breach is closed the record is locked.

Can our security tooling open a breach automatically?

Yes. A breach-intake API lets a SIEM or other security tool create the record, so the countdown starts as soon as the incident is detected.

Be ready before the first incident

Book a demo and run a mock breach from discovery to the Board report.