MyMIS Test the Disaster Recovery/Contingency Plan at least once a year In order to ensure smooth transition, the disaster recovery/contingency plan should be tested yearly if not more. The testing of the plan has the added advantage of keeping the personnel trained and skills fine-tuned as well as identifying likely operational problems. The plan should also be evaluated periodically to ascertain that it is still appropriate and meeting the purpose it was intended for. In ensuring against business interruption, recommended actions under the disaster recovery/contingency plan are: (a) include telephone and voice mail service continuation to ensure the continued availability of voice mail and telephone services; (b) include image systems and facsimile capability to ensure against business interruption due to loss of image systems; (c) include e-mail service continuation to ensure business continuation in case of loss of e-mail services; (d) continued availability of information stored on microfilm, microfiche, or other mass storage media should be ensured through the following procedures: i. include mass storage media, as part of the contingency and disaster recovery plan; ii. provide for back-up of all important files, critical business data, important programmes and documentation to enable business resumption of core processes; iii. the frequency of back-up should be in-line with the importance of the information and the business resumption plan; iv. back-up should be securely stored, and the recovery procedure checked and tested regularly for reliability; and v. access to back-up should be strictly controlled. (e) include paper documents and media storage to ensure that vital business records are not lost through destruction or loss of paper documents; (f) protect government operations from disastrous effects of fire and/ or water: i. a business continuity or resumption plan should be in place and fully tested; and ii. back-ups of all important information, services and resources should be available. (g) protect buildings containing key equipment and the key equipment against the effects of lightning; and (h) protect against natural disasters by avoiding disaster prone areas. 3.8 A security incident affects confidentiality, integrity, availability and accountability Public Sector ICT Security Incident Handling A security incident is an incident that affects either directly or indirectly, the confidentiality, integrity and availability of the ICT system. Incident handling is similar to first-aid. Once an organisation suffers a disruption and is given an ‘incident handling’, where its ICT infrastructure needs to undergo a proper overall security diagnosis. Copyright MAMPU Chapter 3 - 18

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents