Agree authority before an incident.
Name the incident lead, technical responders, business decision makers and supplier contacts. Identify who can isolate a system, disable access, approve disruption and request specialist help. Include legal, privacy and communications responsibilities where they are relevant to the organisation.
Confirm the actual support hours and escalation commitments of each supplier. A routine support subscription should not be assumed to include emergency investigation or out-of-hours response. NIST incident-response guidance places preparation, detection, response and recovery within wider cybersecurity risk management.
Build runbooks for credible infrastructure events.
Consider compromised administrator access, suspected data exposure, ransomware, unusual traffic and loss of important services. For each scenario, record the first checks, evidence sources, permitted containment actions and stopping conditions. The right action depends on what is happening and which systems are affected.
Preserve evidence where appropriate while limiting continuing harm. Avoid assuming that restarting or rebuilding is always the first step. Use secure communications and record decisions, times and responsible people so that later investigation can distinguish observations from assumptions.
Prepare the route back to a trusted service.
Recovery may involve clean infrastructure, replacement credentials, validated backups and application checks. Confirm who assesses whether the original weakness has been addressed and who approves reopening the service. A restored system still needs investigation of the cause and any remaining access paths.
External notifications and reporting duties depend on the incident, contract and applicable law. Assign those decisions to the appropriate accountable people and advisers. A technical incident ticket does not automatically satisfy a customer, regulator or insurer notification requirement.
Test the plan and close the practical gaps.
A scenario exercise can reveal unavailable contacts, missing permissions, unusable backups or unclear supplier boundaries. Agree safe exercise methods and record corrective actions. Revisit the plan after major platform changes and actual incidents, using the findings to improve the service.
An agreed engagement can deliver an infrastructure response outline, contact and authority matrix, evidence checklist and exercise record. For planning, describe the critical services, supplier arrangements and current gaps. If an incident is already active, use your established customer-support or agreed emergency route and provide the service reference.
