S 6 Safeguard catalogues Contingency planning

S 6.1 Development of a survey of availability requirements

S 6.2 Definition of emergency, person-in-charge in an emergency - not to apply

S 6.3 Development of an Emergency Procedure Manual - not to apply

S 6.4 Documentation on the capacity requirements of IT applications - not to apply

S 6.5 Definition of restricted IT operation - not to apply

S 6.6 Study of internally and externally available alternatives - not to apply

S 6.7 Responsibilities in an emergency - not to apply

S 6.8 Alert plan - not to apply

S 6.9 Contingency plans for selected incidents - not to apply

S 6.10 Contingency plans for breakdown of data transmission - not to apply

S 6.11 Development of a post-incident recovery plan - not to apply

S 6.12 Performing penetration tests - not to apply

S 6.13 Development of a data backup plan - not to apply

S 6.14 Replacement procurement plan - not to apply

S 6.15 Agreements with suppliers - not to apply

S 6.16 Taking out insurance

S 6.17 Alert plan and fire drills

S 6.18 Provision of redundant lines

S 6.19 Data backup on PCs - not to apply

S 6.20 Appropriate storage of backup data media

S 6.21 Backup copy of the software used

S 6.22 Sporadic checks of the restorability of backups

S 6.23 Procedures in the event of malware

S 6.24 Creating an emergency boot medium

S 6.25 Regular backup of the server hard disk - not to apply

S 6.26 Regular backup of PBX configuration data

S 6.27 Secure update of BIOS

S 6.28 Agreement on the delivery deadlines for vital PBX units - not to apply

S 6.29 PBX base line for emergency calls

S 6.30 Emergency circuit - not to apply

S 6.31 Procedural patterns following a loss of system integrity

S 6.32 Regular data backup

S 6.33 Development of a data backup policy

S 6.34 Determining the factors influencing data backup

S 6.35 Stipulating data backup procedures

S 6.36 Stipulating a minimal data backup policy

S 6.37 Documentation of the data backup

S 6.38 Backup copies of transferred data

S 6.39 Listing dealerships for re-procurement of fax products

S 6.40 Regular battery checks/replacements - not to apply

S 6.41 Training data reconstruction

S 6.42 Creating start-up disks for Windows NT - not to apply

S 6.43 Use of redundant Windows servers

S 6.44 Data backup under Windows NT - not to apply

S 6.45 Data backup under Windows 95 - not to apply

S 6.46 Creating start-up disks for Windows 95 - not to apply

S 6.47 Storage of backup copies as part of telecommuting

S 6.48 Procedures in case of a loss of database integrity

S 6.49 Data backup in a database

S 6.50 Archiving a database

S 6.51 Restoring a database

S 6.52 Regular backup of configuration data of active network components

S 6.53 Redundant arrangement of network components

S 6.54 Procedures in case of a loss of network integrity

S 6.55 Reduction of restart times for Novell Netware servers - not to apply

S 6.56 Data backup when using cryptographic methods

S 6.57 Creation of an emergency plan for the failure of the management system

S 6.58 Establishment of a procedure for handling security incidents

S 6.59 Specification of responsibilities for dealing with security incidents

S 6.60 Specification of reporting paths for security incidents

S 6.61 Escalation strategy for security incidents

S 6.62 Specifying priorities for handling security incidents

S 6.63 Investigation and assessment of a security incident - not to apply

S 6.64 Remedial action in connection with security incidents

S 6.65 Notification of parties affected by security incidents

S 6.66 Evaluation of security incidents

S 6.67 Use of detection measures for security incidents

S 6.68 Testing the effectiveness of the management system for the handling of security incidents

S 6.69 Contingency planning and operational reliability of fax servers

S 6.70 Creation of a contingency plan for failure of the RAS system - not to apply

S 6.71 Data backup for a mobile IT system

S 6.72 Precautions relating to mobile phone failures

S 6.73 Contingency planning and emergency drills for the Lotus Notes/Domino environment

S 6.74 Emergency archive

S 6.75 Redundant communication links

S 6.76 Creation of a contingency plan for failure of a Windows network

S 6.77 Creating start-up disks for Windows 2000 - not to apply

S 6.78 Data backup under Windows clients

S 6.79 Protection of Data on Internet PCs

S 6.80 Creation of a contingency plan for failure of a Novell eDirectory directory service - not to apply

S 6.81 Creation of data backups for Novell eDirectory

S 6.82 Creation of a contingency plan for the failure of Exchange systems - not to apply

S 6.83 Contingency planning for outsourcing

S 6.84 Regular data backup of the system and archived data

S 6.85 Creation of a contingency plan covering failure of IIS - not to apply

S 6.86 Protection against harmful code on the IIS - not to apply

S 6.87 Data backup on the IIS - not to apply

S 6.88 Creation of a business continuity plan for the web server

S 6.89 Contingency planning for an Apache web server - not to apply

S 6.90 Data backup and archiving of groupware and e-mails

S 6.91 Data backup and recovery on routers and switches

S 6.92 Contingency planning for routers and switches

S 6.93 Contingency planning for z/OS systems

S 6.94 Contingency planning for security gateways

S 6.95 Data backups and other precautions relating to PDAs

S 6.96 Contingency planning for a server

S 6.97 Contingency planning for SAP systems

S 6.98 Contingency planning for storage systems

S 6.99 Regular backup of important system components for Windows Server

S 6.100 Drawing up a business continuity plan for VoIP failure

S 6.101 Data backup when using VoIP

S 6.102 Procedures in the event of WLAN security incidents

S 6.103 Redundancies for the primary cabling

S 6.104 Redundancies for the secondary and tertiary cabling

S 6.105 Contingency planning for printers, copiers, and all-in-one devices

S 6.106 Creation of a business continuity plan for the failure of a directory service

S 6.107 Creation of data backups for directory services

S 6.108 Data backup for domain controllers

S 6.109 Business continuity plan for the failure of a VPN

S 6.110 Specification of the scope and the business continuity management strategy

S 6.111 Policy for business continuity management and acceptance of overall responsibility by management

S 6.112 Establishment of a suitable organisational structure for business continuity management

S 6.113 Providing adequate resources for business continuity management

S 6.114 Creating a business continuity concept

S 6.115 Integration of the employees in the business continuity management process

S 6.116 Integrating business continuity management into organisation-wide procedures and processes

S 6.117 Tests and emergency drills

S 6.118 Checking and maintaining the emergency measures

S 6.119 Documentation in the business continuity management process

S 6.120 Checking and controlling the business continuity management process

S 6.121 Drawing up a policy for handling security incidents

S 6.122 Definition of a security incident

S 6.123 Assembling a team of experts for handling security incidents

S 6.124 Specification of where security incident handling overlaps with incident management

S 6.125 Establishment of a central contact point for reporting security incidents

S 6.126 Introduction to computer forensics

S 6.127 Establishment of measures for collecting and securing the evidence of security incidents

S 6.128 Training on the use of evidence collection tools

S 6.129 Training service desk employees how to handle security incidents

S 6.130 Detection and documentation of security incidents

S 6.131 Classifying and assessing security incidents

S 6.132 Limiting the effects of security incidents

S 6.133 Recovering the operating environment after security incidents

S 6.134 Documentation of security incidents

S 6.135 Regular backup of important system components of a Samba server

S 6.136 Creation of a contingency plan for the failure of a Samba server

S 6.137 Trusted storage (escrow)

S 6.138 Drawing up a business continuity plan for virtualisation component failure

S 6.139 Creation of a business continuity plan for DNS servers

S 6.140 Drawing up a business continuity plan for the failure of groupware systems

S 6.141 Defining alternate procedures when using the Internet

S 6.142 Use of redundant terminal servers

S 6.143 Provision of terminal server clients from depot maintenance

S 6.144 Configuration of terminal server clients for dual use as normal client PCs

S 6.145 Contingency planning for PBX systems

S 6.146 Data backup and restoration of Mac OS X clients

S 6.147 Restoring system parameters when using Mac OS X

S 6.148 Disposal of a Mac OS X system

S 6.149 Data backup under Exchange

S 6.150 Data backup when using OpenLDAP

S 6.151 Alarm concept for the logging function