Contain carefully
Disconnect clearly affected systems if needed, but preserve logs, snapshots, email evidence and access records where possible.
If you are dealing with ransomware, business email compromise, cloud exposure, identity compromise, malware or suspected data loss, call now and preserve evidence before making major changes.
Incident response is a balance between containment and evidence preservation. Do not wipe devices, delete logs or make large uncontrolled changes before the response path is understood.
Disconnect clearly affected systems if needed, but preserve logs, snapshots, email evidence and access records where possible.
Record what happened, when it was noticed, affected systems, suspected accounts, screenshots, alerts and known business impact.
Identify who can approve containment, communications, legal coordination, insurer notification and executive decisions.
Confirm incident type, affected systems, current business impact and immediate containment risk.
Preserve evidence, stop obvious spread, secure accounts and define communications and decision authority.
Review logs, endpoint evidence, identity events, email artefacts, cloud activity and known indicators.
Apply containment, remove persistence, restore operations and validate that affected pathways are controlled.
Document lessons learned, root causes, evidence gaps, control improvements and executive reporting requirements.
Containment, evidence capture, affected system scoping, recovery coordination and post-incident uplift.
Mailbox investigation, forwarding rules, OAuth app review, access reset and communications support.
IAM review, access key rotation, logging review, public exposure investigation and remediation priorities.
Technical scoping, evidence collection, affected data analysis support and governance reporting.
Call the incident response line or submit the urgent incident form. The contact form requires the key details needed to respond.