Create an IT emergency concept with itpilot®

IT service based IT emergency concept

In the event of a security incident, after a cyber attack or any other security incident, an IT service-based emergency concept represents a comprehensive guide to control the process and communication chain and to take efficient action against the threats.

IT services-based IT emergency concept, for disaster recovery

In the event of a crisis, a structured approach is key to whether or not a company survives a cyber attack. If a structured representation of the IT services and the existing dependencies is not available, companies are not usually in a position to create an effective disaster recovery concept.

Only with a structured IT security concept are guidelines in place for the rational shutdown of IT systems and for disaster recovery, i.e. for smooth restarting and regular restart of the individual IT landscapes after a crisis.

The effort is worth it: a disaster recovery concept can be the decisive factor in whether your company survives a cyber attack or not.

IT structuring including dependencies as the basis for your IT emergency concept

The basic requirement for an IT emergency concept and effective disaster recovery is a structured representation of your IT services including the resources used. An overview of the interdependencies of the IT services is particularly important:

IT Services: Dependencies

With the IT structuring of all hardware, software, cloud and infrastructure components in the company using the standardized itpilot® IT service list , this transparency can be achieved. As an IT service provider, we have long missed a standard for IT structuring and our itpilot® methodology for IT analysis was developed as a result.

IT documentation with itpilot® for recovery plan, communication plan and emergency checklist

With itpilot® you document your IT services and estimate which ones will be affected in the event of a security incident. You identify the neuralgic points of your IT and on this basis can make binding agreements for each individual IT service and determine the right measures.

With the IT key figures from itpilot®, not only do you have an overview of the responsibilities of each IT service within your own IT department, but also when working with an IT service provider – as well as the estimated downtime costs per IT service.

8 steps to an IT emergency concept for your disaster recovery

1. Request free itpilot® test access

2. Enter your company’s master data in itpilot®

3. First entry of your IT services in itpilot® (time required: approx. 2 hours)

4. IT service list: Evaluation of the individual IT services in itpilot® (effort: 1-2 hours)

5. If necessary: request itpilot® support

6. Recovery plan based on simulated dependencies and planned resources (effort: 8 – 16 hours)

7. Communication plan for your disaster recovery (effort: approx. 5 hours)

8. Emergency checklist for your disaster recovery from recovery plan and communication plan (effort: 1 – 2 hours)