+DER.2.1.A14 Escalation Strategy for Security Incidents [IT Operation Department] (S)

DER.2.1.A14 Escalation Strategy for Security Incidents [IT Operation Department] (S)

An escalation strategy SHOULD be formulated that goes beyond the communication and contact strategy at hand. This escalation strategy SHOULD be coordinated among the persons responsible for fault management and information security management.

It SHOULD contain clear instructions on who is to be involved in what way and when for each type of identifiable or suspected security incident. It SHOULD also specify the safeguards that are to follow an escalation and how those involved are to respond.

Suitable tools (e.g. ticket systems) SHOULD be selected for the defined escalation strategy. These SHOULD also be suitable for processing confidential information. It SHOULD be ensured that the tools will also be available during security incidents and emergencies.

The escalation strategy SHOULD be reviewed regularly and updated as required. The checklists (matching scenarios) for fault management SHOULD be complemented by security-relevant topics and updated regularly. The defined escalation paths SHOULD be tested by means of drills.

1. Übersicht

1.1 Referenzen

1.2 Identifizierte Anforderungen

1.3 Zugehörige Regulierungen

2. Identifizierte Anforderungen

Anforderungen

3. Zugehörige Regulierungen

Regulierungen

Verknüpfte Vorgänge

Verknüpfungen
blocks G 0.18 Poor Planning or Lack of Adaptation
blocks G 0.19 Disclosure of Sensitive Information
blocks G 0.20 Information or Products from an Unreliable Source
blocks G 0.22 Manipulation of Information
blocks G 0.29 Violations of Laws or Regulations
blocks G 0.46 Loss of Integrity of Sensitive Information