+NET.3.2.A32 Firewall Contingency Planning (S)

NET.3.2.A32 Firewall Contingency Planning (S)

Diagnosis and troubleshooting SHOULD be planned and prepared in advance. Appropriate actions SHOULD be defined for typical failure scenarios and updated at regular intervals.

Contingency planning for firewalls SHOULD be coordinated with an organisation's overall incident and emergency preparedness. It SHOULD be based on the general contingency planning concept at hand (see DER.4 Business Continuity Management). It SHOULD be ensured that contingency planning documentation and the instructions it contains are available in paper form. The procedure described in the contingency planning concept SHOULD be tested regularly.

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.14 Interception of Information / Espionage
blocks G 0.18 Poor Planning or Lack of Adaptation
blocks G 0.23 Unauthorised Access to IT Systems
blocks G 0.27 Lack of Resources