Case 8BC7C2 · GRC · L3 Applied
The Six-Hour CERT-In Clock
Live alertSaturday 22:40: your SOC confirms an attacker logged into a production database server at your Bengaluru payments startup using a leaked admin key. The CISO is on a flight and Legal asks if anything must be filed tonight.
- 01 What happened?
- 02 What is the impact?
- 03 What do you do?
What a strong answer covers
Try it out loud first. Then check yourself:
- CERT-In directions of April 2022: report listed incident types within 6 hours of noticing; unauthorised system access is listed.
- File an initial report with what you know now; the clock does not wait for root cause. Send updates as facts firm up.
- Contain in parallel: revoke the key, isolate the host, preserve evidence. The directions require 180 days of logs kept in India.
- Check other clocks: sector regulators such as RBI, DPDP breach intimation, customer contracts. Run all from one timeline.
- Gaps to fix after: named CERT-In point of contact, pre-delegated authority to file out of hours, clocks synced to NIC or NPL NTP.
If the interviewer pushes back
- Six hours in, you still do not know whether data left the server. What does your report say about data impact?
- How do you pre-authorise filing so a 2am incident does not wait for the CISO to land?