Know who to contact
Keep a short incident contact list outside the systems it depends on. Include business leadership, IT support, hosting providers, legal or privacy contacts and any insurer or specialist required by your agreements.
Define who can isolate a device, disable an account or contact customers. Staff should know how to report a concern without trying to investigate it themselves.
Contain the issue and preserve evidence
If a system appears compromised, follow the incident plan and contact the responsible technical lead. Isolate affected systems when this is safe and appropriate. Avoid deleting files, rebuilding devices or resetting every credential before evidence and dependencies are considered.
Record what was observed, when it was observed and who took each action. Preserve relevant logs and provider notices. Do not assume that a single alert proves what data was accessed.
Restore in a controlled way
Use a recovery source that the team has checked. Fix the access path or weakness before returning systems to normal use. Change affected credentials from a clean device and monitor for repeated activity.
Review customer, regulator and contract notification duties with the responsible adviser. After recovery, document what worked and update the plan. A security assessment can help reduce technical gaps before an incident occurs.
