Emergency Response

When incidents happen, sequence matters.

First understand what is affected. Then contain the issue, preserve evidence and restore services in a controlled way. Here are the questions and responsibilities to settle beforehand.

Open escalation Phone contact

Service illustration

P1 / CRITICAL

Emergency Incident Intake

An outage, suspected ransomware, compromised access or critical site disruption first requires a clear assessment of affected systems and impact.

First focus01

01Contain

Stop propagation and isolate accounts and systems in a controlled way.

02Preserve

Preserve logs, timelines and relevant artifacts.

03Recover

Prioritize recovery and use clean recovery points.

04Communicate

Provide management, IT and affected stakeholders with a clear situation report.

Report incident by phone E-Mail Incident form

This website does not establish a guaranteed response time. Your agreed support or incident contract governs coverage, including any contracted 24/7 service. New enquiries are first assessed for urgency.

Crisis Readiness

The best incident is the one you are prepared for.

Keep contact and escalation matrix current
Test restore processes regularly
Document admin access and break-glass accounts
Plan communication channels outside compromised systems

When incidents happen, sequence matters.

Emergency Incident Intake

The best incident is the one you are prepared for.

Which controls can be tested beforehand.