Technology for innovators.
IndiaGlobal website

Prepare incident evidence before an incident

Prepare incident evidence before an incident

Response becomes more effective when ownership and records are already in place.

Operators monitoring a control room

Know which records exist

Map important systems, logs, timestamps and retention behavior. Confirm who can access the evidence and how it can be exported without losing context. A written incident plan cannot recover records that were never captured.

Assign the reporting decision

Identify the people who classify the incident, coordinate containment and evaluate applicable reporting duties. India’s CERT-In Directions and FAQs should inform the scoped process. Legal and security owners must interpret obligations for the actual organisation and incident.

Practise a realistic handoff

Exercise an incomplete alert, an unavailable specialist and a dependency outside the organisation. Test evidence gathering and communication alongside technical recovery. Record what prevented the team from making the next decision.

Use the exercise to improve the system

Turn findings into assigned changes and retest the affected process. Recovery objectives and response expectations need evidence from exercises, not a generic promise. Keep the current runbook accessible to the people who will use it.

Further reading

CERT-In Directions and FAQs

Common questions

What is the practical starting point?

Map important systems, logs, timestamps and retention behavior. Confirm who can access the evidence and how it can be exported without losing context. A written incident plan cannot recover records that were never captured.

Start a conversation

What would you
like to move forward?

Find your next step.

Browse all pages
Website analytics