- Signal
- Unauthorised export · storage policy change
- Awareness recorded
- 03:02:44 IST · decision and reason on record
- CERT-In due
- 6 h · by 09:02:44
- Board due
- 72 h · 3 days from awareness
- Submission
- Built and on record
Wheelhouse (Data protection) · Breach Clocks
CERT-In and DPDP breach clocks, from the moment you became aware.
Two clocks, started from awareness, not from the alert. A breach in India starts two deadlines under two different laws. Wheelhouse records the moment you became aware as a decision, starts both clocks from it, and builds both filings on the same screen.
Runs in your cloud, on your premises, or air-gapped. No managed SaaS.
Last reviewed
Illustrative. No customer data.
The difference
Their way, and ours.
The CERT-In 6-hour clock and the DPDP 72-hour Board clock run as separate instruments from one recorded awareness decision.
Source: Incident service and awareness schema
The record
The breach, on the record.
Awareness is a decision. From that decision, two clocks run and both filings are built and on record.
The call path
Where the clock runs.
- ObserveBreach signal arrives
- DetermineAwareness recorded as a decision
- ActBoth intimations built in place
- SignReceipts for both filings
- ProveChain entry, write-once
Also covered
- Signal triage
- Awareness record
- Two clocks
- Intimation composer
- Board submission
Common questions