ICT DISASTER RECOVERY PLAN

Transcription

1 EMAKHAZENI LOCAL MUNICIPALITY ICT DISASTER RECOVERY PLAN

2 Approval DOCUMENT: Copy Number: ICT INCIDENT RESPONSE PLAN MASTER COPY Compiled by: Niall Carroll Deputy Manager ICT Reviewed by: Compilation Date: August 2013 Review Date: Version: Draft V 1.00 Revision: Distribution: All Classification: Document Release Approval Document Acceptance Releasing Authority: Manager: Corporate Services ICT Department Acceptance Authority: Council Date Released: Date Accepted: Signature: Signature: 2

3 Document Control Revision Record Revision Date Change Record Changed By Issue Control This policy is issued by the DEPARTMENT OF CORPORATE SERVICES on behalf of the Emakhazeni Local Municipality, to whom any change requests or queries should be directed. The review life for this document is 12 months. Distribution Copy No. Name TICTle Organisation Master The MASTER for this document is held electronically and only signed copies are valid. An unsigned, printed document is not copy controlled and is to be used for information purposes ONLY, as ICT will not be automatically updated. ICT is therefore the responsibilicty of the reader to ensure that ICT is a currently valid copy. 3

4 TABLE OF CONTENTS Document Control... 3 Revision Record... 3 Issue Control... 3 Distribution Organisation About & Overview Departments Contact Lists for Personnel & Suppliers ICT Contact Lists Senior ICT Management & ICT Disaster Recovery Leader Key Contact List (KCL) ICT Personnel ICT Disaster Recovery Team ICT Recovery Testing Team Relevant ICT Suppliers (Contract / SLA) Invocation Plan & Response Communications Plan Invocation Communications Plan Emergency Communications Plan Post Emergency Communications Plan Recovery Points Primary Assembly Point Secondary Assembly Point Primary Recovery Facility

5 5.4 Secondary Recovery Facility Business Impact Analysis Risk Paradigm (Classification Index) Risk Impact Table Risk Likelihood Table Inherent Risk Exposure Table ICT Environment Overview Key Equipment List Recovery Start-up Sequence Diagram: Overall ICT Environment Applications in the Environment ICT Department Controlled Applications Essential ICT Services Network - Overview Network Architecture & Design Network Functional Components Network Backups Network Full Recovery Procedure Network Component Recovery Procedure Network - Risk & Impact Analysis Threat Management Gateway - Overview Threat Management Gateway - Architecture & Design Threat Management Gateway Functional Components Threat Management Gateway - Backups Threat Management Gateway Full Recovery Procedure

6 9.3.5 Threat Management Gateway Component Recovery Procedure Domain Controller (Active Directory / AD) - Overview Domain Controller (Active Directory / AD) Functional Components Domain Controller (Active Directory / AD) - Backups Domain Controller (Active Directory / AD) Full Recovery Procedure Domain Controller (Active Directory / AD) Component Recovery Procedure Domain Controller (Active Directory / AD) - Risk & Impact Analysis Backup Service - Overview Backup Service - Architecture & Design Backup Service - Functional Components Backup Service - Backups Backup Service Full Recovery Procedure Backup Service Component Recovery Procedure Backup Service - Risk & Impact Analysis Antivirus Overview Antivirus - Architecture & Design Antivirus - Functional Components Antivirus - Backups Antivirus - Risk and Impact Analysis System Specific ICT Services Mail Service - Overview Mail Service - Architecture & Design Mail Service - Functional Components Authoritative Domains Domain Hosting Mail Records Mail Server

7 Client Access Inbound Observations Outbound Observations Mail Service - Backups Mail Service Recovery Procedures Mail Service Component Recovery Procedure Mail Service - Risk & Impact Analysis Munsoft Service - Overview Munsoft Service - Architecture & Design Munsoft Service - Functional Components Munsoft Service - Backups Munsoft Service Full Recovery Procedure Munsoft Service Component Recovery Procedure Munsoft Service - Risk and Impact Analysis VIP Payroll Overview VIP Payroll Service - Architecture & Design VIP Payroll Service - Functional Components VIP Payroll Service - Backups VIP Payroll Service Full Recovery Procedure VIP Payroll Service Component Recovery Procedure VIP Payroll Service - Risk and Impact Analysis VIP ESS Service Overview VIP ESS Service - Architecture & Design VIP ESS Service - Functional Components VIP ESS Service - Backups VIP ESS Service Full Recovery Procedure VIP ESS Service Component Recovery Procedure

8 VIP ESS Service - Risk and Impact Analysis CaseWare Service - Overview CaseWare Service - Architecture & Design CaseWare Service - Functional Components CaseWare Service Full Recovery Procedure CaseWare Service Component Recovery Procedure CaseWare Service - Risk and Impact Analysis Non-Core Services GIS Service (TGIS) IP Cameras Service Access Control Service Corporate Printing Service Telephony Services Annexure Software List

9 1. Organisation 1.1 About & Overview The Emakhazeni Local Municipality has set a vision for the organisation to Improved qualicty of life through balanced, sustainable development and service excellence. The Mission of Council is to achieve this through the Emakhazeni Local Municipality being commictted to the improvement of the physical, socio-economic and instictutional environment in order to address poverty and promote development. The Emakhazeni Local Municipality ICT Department will contribute to this mission by putting the necessary and required procedures in place to ensure the institution can deliver on ICTs Vision and Mission from an ICT perspective. This ICT DRP/BCP document serves as part of the broader ICT strategy and operations. 1.2 Departments DEPARTMENTS Office Of The Municipal Manager Department of Corporate Services Department of Technical Services Department of Finance Department of Community Services DEPARTMENTS AND DIVISIONS Financial Services Corporate Services Technical Services Municipal Manager Technical Services Executive Mayor Community Services Speakers Office Information and Communication Technology Development and Planning Local Economic Development Internal Audit 9

10 2. Contact Lists for Personnel & Suppliers This is a complete list with contact details for personnel and suppliers. 2.1 ICT Contact Lists This section pertains to the various types of contacts used as part of the process Senior ICT Management & ICT Disaster Recovery Leader NAME DESIGNATION TELEPHONE CELL Niall Carroll Deputy Manager ICT (H) niall@emakhazenilm.co.za ICT Disaster Recovery Team Leader (W) Key Contact List (KCL) The Key Contact List is the identified Key ICT contacts within the ICT Department. Their contact information should be shared and disseminated within the organisation. The ICT Disaster Recovery Team Leader remains the first point of contact. NAME DESIGNATION TELEPHONE CELL Niall Carroll Deputy Manager ICT (H) niall@emakhazenilm.co.za Eunice Mnguni ICT Technician eunicem@emakhazenilm.co.za Vusi Ntshwane ICT Technician vusi@emakhazenilm.co.za ICT Personnel NAME DESIGNATION TELEPHONE CELL Niall Carroll Deputy Manager ICT (H) niall@emakhazenilm.co.za Eunice Mnguni ICT Technician eunicem@emakhazenilm.co.za Vusi Ntshwane ICT Technician vusi@emakhazenilm.co.za 10

11 2.1.4 ICT Disaster Recovery Team The ICT Disaster Recovery Team is sorted in the order of succession for the ICT Disaster Recovery Team Leader role. NAME DESIGNATION TELEPHONE CELL Niall Carroll Deputy Manager ICT (H) Eunice Mnguni ICT Technician Vusi Ntshwane ICT Technician ICT Recovery Testing Team The ICT Recovery Testing Team is the team responsible for the periodic restore or DR testing in the environment. NAME DESIGNATION TELEPHONE CELL Niall Carroll Deputy Manager ICT (H) Eunice Mnguni ICT Technician N/A Vusi Ntshwane ICT Technician N/A Relevant ICT Suppliers (Contract / SLA) The following Suppliers/Vendors have direct impact on the DRP. 1. Telkom (internet, VPN & VOIP access) Duma Shange Regional Accounts Manager Glenn Van Dalen Regional Service Manager 2. Obsidian (Software infrastructure) Support Support Centre 3. ITNA (Munsoft) ITNA Disaster Recovery Service desk Ian Graham-Parker Service Delivery Manager Marius Richter Account Manager 11

12 3. Invocation Plan & Response Incident Occures Emakhazeni Local Municipality is notified of possible DR incident. Initial assessment and classification of disaster is done by Nkangala District Municipality DR Team. IT Disaster Recovery Team Leader invokes and communicates the incident to the IT Disaster Recovery. Assemble Emakhazeni Local Municipality DR Team informs different departments of incident. IT Disaster Recovery Team assembles at predefined assembly points. In event of Nkangala District Municipality building being damaged and not accessible at predefined secondary assembly point. Assess IT Disaster Recovery Team does IT damage assessment to ascertain the impact of the event on the IT Department and the services reliant on it. Determine recovery location based on damage assessment. Respond IT Disaster Recovery Team starts recovery process full or partial on various affected systems. Test systems post recovery. Provide access to systems. Communicate IT Disaster Recovery Team reports back to Emakhazeni Local Municipality on status and completion of DRP via IT Disaster Recovery Team Leader. 12

13 4. Communications Plan This section covers the communication between Emakhazeni Local Municipality and the ICT department along witch the internal departmental communication in the event of an incident. All communications during the event should be treated as confidential and only the ICT Disaster Recovery Leader should communicate with the organisation with regards to the status and progress of the ICT Department and ICTs People, Technology, Premises, Information (Systems) and Suppliers (Equipment, Services, Systems). The only exception to this should be if the ICT Disaster Recovery Leader is not able to handle these communications for whatever reason the responsibility will fall on the ICT Recovery Team member next inline. 4.1 Invocation Communications Plan In the event of a disaster or incident that has been invoked by Emakhazeni Local Municipality the initial communication between the ICT Disaster Recovery team members will be either face to face or via phone calls (one to one or conference call). Once damage assessment has been completed, and the impact warrants a Disaster, the Organisation DR Leader declares a disaster The Organisation DR Leader informs all relevant DR team leaders including the IT DR Team Leader The IT DR Team Leader informs all IT DR Team members who then activate the steps in the IT DRP 4.2 Emergency Communications Plan During and post the invocation of the incident ICT is critical that the ICT Disaster Recovery Team communicate with each other in a frequently, clear, reliable and concise manner. All ICT related communication should be relayed through the ICT Disaster Recovery Team Leader. The ICT Disaster Recovery Team Leader will be the interface for all communication between the ICT Disaster Recovery Team and the Organisation. Communications between the ICT Disaster Recovery Team and the organisation should be frequent initially ICT is recommend to between minutes as the initial recovery period continues communications could be 2 4 hours apart. This will however be dependent and dictated by the request for information from the Organisation DR Leader. 13

14 Team Member 2 Team Member 3 Team Member 4 Team Member 1 IT Disaster Recovery Team Leader Team Member Post Emergency Communications Plan ICT Disaster Recovery Team Leader will communicate to the Organisation DR Leader and later on the organisation the post incident information. This should include any changes (permanent or temporarily) to the People, Technology, Premises, Information (Systems) and Suppliers (Equipment, Services, Systems) relating to ICT environment. 14

15 5. Recovery Points This section covers the ICT Departments emergency assembly points and the recovery points. 5.1 Primary Assembly Point In the event of an incident the ICT Disaster Recovery Team should assemble at the location market on the map below. In the event of the primary location not being accessible proceed to the secondary location. The team should gather at this location within the first hour. Primary Assembly Point for Emakhazeni LM ICT Disaster Recovery Team Secondary Assembly Point for Emakhazeni LM ICT Disaster Recovery Team 5.2 Secondary Assembly Point In the event of not being able to use the primary assembly point proceed to the secondary assembly point, located a across the road in Steepers Street. The team should gather at this location within the first hour. 15

16 5.3 Primary Recovery Facility Recovery Procedures are to start at the primary location. Primary Recovery Facility for Emakhazeni ICT Disaster Recovery Team in Existing Municipal Building 16

17 5.4 Secondary Recovery Facility Secondary site for recovery at Entokozweni Municipal Office. 6. Business Impact Analysis The Business Impact Analysis (BIA) section of this document serves the purpose of depicting the architecture & design as well as to highlight the risks & impacts for the various technologies deployed. Vendors and Service Provider details can be found in the Supplier list section of this document. 6.1 Risk Paradigm (Classification Index) The tables below are used to calculate the risk impact and likelihoods of your organisation and then to quantify the possible exposure of these risks. In order to get final risk exposure rating you need to quantify impact and likelihood. This is done by multiplying the ratings of impact and likelihood. 17

18 6.2 Risk Impact Table RATING ASSESSMENT DEFINICTION 1 INSIGNIFICANT Negative outcomes or missed opportunities that are likely to have a negligible impact on the ability to meet objectives. 2 MINOR Negative outcomes or missed opportunities that are likely to have a relatively low impact on the ability to meet objectives. 3 MODERATE Negative outcomes or missed opportunities that are likely to have a relatively moderate impact on the ability to meet objectives. 4 MAJOR Negative outcomes or missed opportunities that are likely to have a relatively substantial impact on the ability to meet objectives. 5 CRICTICAL Negative outcomes or missed opportunities that are of critical importance to the achievement of the objectives. 6.3 Risk Likelihood Table RATING ASSESSMENT DEFINICTION 1 RARE The risk is conceivable but is only likely to occur in extreme circumstances. 2 UNLIKELY The risk occurs infrequently and is unlikely to occur within the next three (3) years. 3 MODERATE There is an above average chance that the risk will occur at least once in the next three (3) years. 4 LIKELY The risk could easily occur, and is likely to occur at least once within the next 12 months. 5 COMMON The risk is already occurring, or is likely to occur more than once within the next 12 months. 6.4 Inherent Risk Exposure Table RISK INHERENT RISK RESPONSE RATING MAGNICTUDE HIGH Unacceptable level of risk High level of control intervention required to achieve an acceptable level of residual risk 8-14 MEDIUM Unacceptable level of risk, except under unique circumstances or conditions Moderate level of control intervention required to achieve an acceptable level of residual risk 1-7 LOW Mostly acceptable Low level of control intervention required, if any. 18

19 7. ICT Environment Overview The municipality consists of various departments each with their own requirements from ICT. However the ICT environment of Emakhazeni Local Municipality is a well structured environment. The environment consists of a number of systems required to support the services needed by Emakhazeni Local Municipality. These services used by Emakhazeni Local Municipality include Financial, Payroll, Communication, Document Management and the base infrastructure. The Municipality relies on a 2 MB internet breakout for ICTs connectivity as well as dedicated system specific connectivity for ICTs financial system. 7.1 Key Equipment List DEVICE / SERVER NAME IP ADDRESSS TYPE Main ICT Servers Untangle Server CentOS Virtual Drive Zimbra Server CentOS Virtual Drive ClearOS Server Finance Munsoft Server VIP Server Budget Plan Server TELKOM OPTICON PRI Telephony 7.2 Recovery Start-up Sequence The recovery sequence is the proposed sequence to be used for a full recover. Certain services are dependent on others and thus the recovery sequence becomes important to ensure when recovering a service ICT already has ICTs dependencies in place. # SERVICE NAME DESCRIPTION 1 Network & Connectivity Setup WAN & LAN networks. 2 Domain Controller Recover Domain Controller and ensure (DNS, AD, DHCP, WINS) is functioning. 3 Firewall (TMG) Recover firewall and load original configuration from backup. 4 Antivirus Recover Antivirus service for environment. 5 Backup Recover Storage Platform and relevant data. 6 Printing Recover printing service. Multifunction & Scanning Device and Tally Line printers required. 7 Mail Recover all Mail related services and establish access for users. 8 Munsoft Recover Munsoft s Municipal Financial & Billing software and data and establish access for users. 9 VIP Premier Recover VIP Payroll service and establish access for users. 10 VIP ESS Recover VIP Premier (Application and Database) service and establish access for end users. 11 File Server Recover File Server and data and establish access for users to Home folder 15 Non-core Recover where possible non-core services 19

20 7.3 Diagram: Overall ICT Environment This diagram presents an overview of the organisation ICT structure. Backup Site Machadodorp 90 Users Belfast HQ 1984 kbs Internet 1984kbs 1984kbs 1024kbs 10 Users Fritzegerald 512kbs Waterval Boven 10 Users 512kbs Emakhazeni Local Municipality MPLS VPN 512kbs 512kbs Siyathuthu 6 Users Emthonjeni 4 Users Dullstroom 4 Users 20

21 8. Applications in the Environment Various applications have been identified in the organisation. These are listed below and will be broken down in to two sections. The two sections are those that fall under the control and support of the ICT department and those that live elsewhere in the organisation. 8.1 ICT Department Controlled Applications APPLICATIONS MANUFACTURER USAGE USERS SYSTEM FUNCTION Munsoft Financial Munsoft Software Pty Ltd Daily Finance Is used to managed the finances of the Management System Department Emakhazeni Local Municipality VIP Payroll System Softline Pty Ltd Daily Finance & HR Departments This application is used to administrate the salaries and HR functions such as leave at Emakhazeni Local Municipality CaseWare CaseWare International Weekly Finance (1 User) Application used to financial reporting ESS (VIP) Softline Pty Ltd Daily All Departments Module for users to be able to manage their own HR including leave applications etc. File Data Electronic Mail Service (Zimbra) Untangle. Management Gateway (TMG) Intel Server / CentOS sharing Open Source, Telkom, Lantic, Cisco etc. Daily All Departments All users have home folders on the server with redirection taking place back to the individual workstations Daily All Departments The mail service forms part of an important communication tool in the Emakhazeni Local Municipality. ICT is also used to store contacts and schedule meetings by ICTs users. Open Source Daily All Departments Protects the users from and allows access to the Internet from the Emakhazeni Local Municipality LAN. Other Applications in Organisation APPLICATIONS MANUFACTURER USAGE USERS SYSTEM FUNCTION GIS TGIS N/A Technical GIS system is in PoC / Review phase Services TELKOM OptiCon PRI Telkom N/A All Telephone management system Departments IP Cameras (ICT) N/A Daily ICT Used to monitor Server Room Call Centre Telkom Daily Disaster Management To answer any emergency 21

22 9. Essential ICT Services Functional components of the environment include: Network (LAN & WAN) The LAN and WAN provides the access layer between end users and the services they require. Firewall Provides the security gateway that manages the internal and external networks. Domain Controller - Active Directory (AD) provides the underlying centralised authorisation and authentication which is used by servers and end users to access various systems and services on the ICT network. Backup Service Service that is used to backup and recovery of data across the environment. IMPORTANT NOTE: ALL SERVERS SHOULD RETAIN THEIR ORGINAL NAMES WHEN DOING THE RECOVERY 9.1 Recovering Essential ICT Services In order to start recovering services, the basic ICT infrastructure needs to be configured and ready for use in order to deploy the recovered systems. These systems will be classified as essential ICT services and are made up of the Network (LAN & WAN), Firewall and Active Directory (AD). As opposed to the essential services mentioned above, there are a few other essential services which are required at the Recovery location as listed below: Secure Environment (New) Power (New) Network (physical) Domain Controller (Networking infrastructure, e.g. DNS, AD, DHCP, WINS) Firewall Network Printing Line Matrix Printer (New) Multi-Function Printers (Must Include Scanner and be Network capable) (New) 22

23 9.2 Network - Overview The physical network configuration of the network is a flat Layer 2 network. No VLAN s are in use Network Architecture & Design The network architecture of Emakhazeni Local Municipality is a Virtual Private Network. All systems are located on eight IP address structure Network Functional Components Functional components of the network include: Physical Line (2MB Telkom) This is the primary connection to internet. Router Cisco 1900 This is the router used by the primary connection. Core Switching This handles the uplinks to LAN (Floor Switches) and the server room. Floor Switching The floor Switches allow end users and devices to connect to each other and the core network. Cabling Cabling is in place to link the different Switches and users. Cabinet All equipment is placed in the cabinets. 23

24 9.2.3 Network Backups Telkom manages the Cisco 1800 and 1900 series router and maintains the backup of the configuration. As there are no VLAN's or other Layer2 or Layer3 actions, the backups of the production Switches are not required Network Full Recovery Procedure Procure 4 x 48 port Switches Setup 1 x core Switch Connect 4 x floor Switches to the core Switch in star configuration Start connecting core infrastructure to the network Test access to infrastructure Start connecting users to network to access systems Test user access to systems Network Component Recovery Procedure PHYSICAL LINE (PRIMARY 2MB CONNECTION) Component Physical Line (circuit number ) Responsible Company / Telkom Department Contact Details: Service Desk Actions Emakhazeni LM ICT will log the incident of the line down with the WAN (Telkom) provider to restore the service. When logging the incident an ETA and incident number should be requested. Potential time of service interruption Estimated recovery time: With WAN connectivity and outages due to incidents such as natural disasters, breakages and cable theft, an outage can be anything from a couple of hours to several weeks. Emakhazeni LM does have an SLA on the line, but if the SLA is breached, the conditions only force the WAN provider not to charge for the service during the outage. 3 Days (Best Estimate) ROUTER CISCO 1900 Component CISCO Router 1900 circuit number Responsible Company / Telkom Department Contact Details: Service Desk Actions Emakhazeni LM ICT will log the incident of the Cisco Router with the WAN (Telkom) provider to investigate & repair. When logging the incident an ETA and incident number should be requested. Potential time of service interruption Estimated recovery time: Dependent on how quick Telkom can swap out the Router and restore the configuration or setup the router. 3 Days (Best Estimate) 24

25 CORE SWITCH Component Responsible Company / Department Contact Details: Service Desk 3COM Emakhazeni Local Municipality ICT Department N/A Actions Emakhazeni Local Municipality ICT Department to procure new Core Switch. Configure IP address for remote management Send existing failed Switch in for warranty repair, repair or scrap equipment Potential time of service interruption Estimated recovery time This is a service that is managed by Emakhazeni Local Municipality ICT and as such there exists no uptime guarantee. The time to restore is governed by the time to procure Hardware as well as the reinstallation of software 3 Days (Best Estimate) FLOOR SWITCH Component Responsible Company / Department Contact Details: Service Desk Generic Manufacturer Emakhazeni Local Municipality ICT Department N/A Actions Emakhazeni Local Municipality ICT Department to procure new Floor Switch. Install Floor Switch reconnect Switching stack Configure IP address for remote management Send existing failed Switch in for warranty repair, repair or scrap equipment Potential time of service interruption Estimated recovery time This is a service that is managed by Emakhazeni Local Municipality ICT and as such there exists no uptime guarantee. The time to restore is governed by the time to procure Hardware as well as the reinstallation of software 3 Days (Best Estimate) Network - Risk & Impact Analysis The network is setup with a rudimentary design with low levels of fault tolerance. ESTIMATED SERVICE RESTORATION TIME 3 DAYS OVERAL RISK RATING 10 (MEDIUM) SERVICES COMPONENT IMPACT DESCRIPTION IMPACT LIKELIHOOD RISK RATING ESTIMATED RECOVERY TIME Connectivity Telkom Line No external connectivity (Internet & ) (MEDIUM) 3 DAYS Connectivity Telkom Router No external connectivity (Internet & ) Connectivity DHCP If DHCP is not functional, no computer can get on the network. This is a SPOF since there is only one Switch providing this service (MEDIUM) 3 DAYS (MEDIUM) 4 HOURS Connectivity Switch Main Building Users directly (LOW) 3 DAYS 25

26 connected to Switch will lose connectivity to the LAN Connectivity Switch Corporate and Community Services Users directly connected to Switch will lose connectivity to the LAN (LOW) 3 DAYS 9.3 Threat Management Gateway - Overview Threat Management Gateway is not actively used by all users as an application but ICT is an underlying service that protects the network from external and internal threats. ICT further allows for the user management of internet access Threat Management Gateway - Architecture & Design The Threat Management Gateway (TMG) is used as the firewall in the organisation. This firewall is what governs and manages the access policies in and out of the environment. The firewall is in line between the external Telkom link and the internal LAN. Internal LAN TMG Internet Threat Management Gateway Functional Components PHYSICAL DEVICE PHYSICAL LOCATION IP ADDRESS NOTES Untangle Firewall (TMG) Server Room CISCO Telkom Router Server Room N/A 26

27 9.3.3 Threat Management Gateway - Backups NDMSVMBGFAPP01 DEVICE IP SERVER ROLE BACKUP GROUP A copy of the latest configuration is backed up on the ELM01 server. This will need to be restored from the C:\TMG Backup files folder in the event of a recovery. BACKUP AGENT VERSION BACKUP SCHEDULE LAST SUCCESSFUL BACKUP DATA RETENTION PERIOD OFFSICTE DATA RETENTION PERIOD DATA RECOVERY POINT ESTIMATED RESTORE TIME DATA PROTECTED DATA COMPRESSED Application Server EMAKHAZENI LM-SRV\SERVERS Daily backups for this backup set occurs at 19h00 11 June 2013, 19:00 2 months Offsite backups to B-site yet RPO (Recovery Point Objective) 24 hours, we run backups daily 1 Hour Depending on size of data transfer 8.67 GB 7.63 GB SELECTION EXPORT DATE 7 June Threat Management Gateway Full Recovery Procedure FIREWALL UNTANGLE Component Responsible Company / Department Contact Details: Service Desk Actions Intel Server Emakhazeni Local Municipality ICT Department N/A Backing up the Firewall configuration Resource - System requirements for Untangle Resource - Secure / procure a server that meets the minimum requirements. (64-bICT, 6GB RAM, Dedicated 6 X 1TB HDD formatted with NTFS file system, 2 x NIC) Ensure the base / core network is operational in order to connect the Untangle server. Install OS and Untangle and ensure ICT s on the same patch / service pack level as the Untangle server being recovered. Restore the Untangle configuration file. This is the XML export that contains the firewall s properties. Import the XML file this restore will reconstruct most configuration details. When importing always select the option to Overwrite the existing configuration. Use the password created when the export of the configuration was done to decrypt the configuration file for Untangle. Ensure the certificates settings are correct, failure to do so will result in the TMG service not starting. Potential time of service interruption Estimated recovery time This is a service that is managed by Emakhazeni Local Municipality ICT Department and as such there exists no external uptime guarantee or SLA. The time to recover is governed by the time to procure the required hardware and the reinstallation of software and the configuration thereof. 3 Days (If the configuration is backed up and the equipment is available) 27

28 9.3.5 Threat Management Gateway Component Recovery Procedure In the event of component failure replacement parts should be ordered and if need be the above full recovery procedure followed. Threat Management Gateway - Risk & Impact Analysis ESTIMATED SERVICE RESTORATION TIME 3 DAYS OVERAL RISK RATING 5 (LOW) SERVICES COMPONENT IMPACT DESCRIPTION Firewall Service No external connectivity (Internet & ) Access policies and restrictions not applied IMPACT LIKELIHOOD RISK ESTIMATED RATING RECOVERY TIME (LOW) 3 DAYS 9.4 Domain Controller (Active Directory / AD) - Overview Active Directory is used by all users and is a crucial underlying component of all systems since ICT provides an authentication and authorisation functionality. Without Active Directory no users will be able to login, and therefore access their applications Domain Controller (Active Directory / AD) Functional Components PHYSICAL DEVICE PHYSICAL LOCATION IP ADDRESS NOTES Domain Controller Intel Server Server Room Server Domain Controller (Active Directory / AD) - Backups An Attix5 agent is loaded on the Active Directory server and backs up the System State of the machine on a daily basis. ELM SERVER DEVICE IP SERVER ROLE BACKUP GROUP BACKUP AGENT VERSION BACKUP SCHEDULE DATA RETENTION PERIOD OFFSITE DATA RETENTION PERIOD DATA RECOVERY POINT ESTIMATED RESTORE TIME Active Directory EMAKHAZENI LM\SERVERS ClearOS Daily backups for this backup set occurs at 19h00 2 months 2 Months RPO (Recovery Point Objective) 24 hours, we run backups daily 1 Hour (depending on size of data) 28

29 9.4.3 Domain Controller (Active Directory / AD) Full Recovery Procedure ACTIVE DIRECTORY (AD / DOMAIN CONTROLLER) Component Domain Controller Server INTEL SERVER Responsible Company / Department Contact Details: Service Desk Emakhazeni Local Municipality ICT Department N/A Actions Secure / procure a server that meets the minimum requirements. (64-bICT, 6GB RAM, Dedicated 6 X 1TB HDD, 2 x NIC) Install OS, Service Packs and fixes from media Install Attix5 agent and connect account to Storage Platform Restore last backup to original location Then perform System State Restore Ensure server is rebooted as required by Microsoft Potential time of service interruption Estimated recovery time This is a service that is managed by Emakhazeni Local Municipality ICT Department and as such there exists no external uptime guarantee or SLA. The time to recover is governed by the time to procure the required hardware and the reinstallation of software and the configuration thereof. 3 Days (If the configuration is backed up and the equipment is available) Domain Controller (Active Directory / AD) Component Recovery Procedure ACTIVE DIRECTORY (AD / DOMAIN CONTROLLER) Component Domain Controller Server INTEL SERVER Responsible Company / Department Contact Details: Service Desk Emakhazeni Local Municipality ICT Department N/A Actions Hardware - Log a call with HP to replace the damaged components. Get the incident number from the service operator. Hardware After hardware has been repaired rebuild domain controller from backup if necessary. Follow the Full Recovery Procedure. Software If problem cannot be rectified, rebuild from last available backup using the Full Recovery Procedure. Potential time of service interruption Estimated recovery time This is a service that is managed by Emakhazeni Local Municipality ICT Department and as such there exists no external uptime guarantee or SLA. The time to recover is governed by the time to procure the required hardware and the reinstallation of software and the configuration thereof. 3 Days (If the configuration is backed up and the equipment is available) Domain Controller (Active Directory / AD) - Risk & Impact Analysis ESTIMATED SERVICE RESTORATION TIME 3 DAYS OVERAL RISK RATING 15 (HIGH) SERVICES COMPONENT IMPACT DESCRIPTION IMPACT LIKELIHOOD RISK RATING ESTIMATED RECOVERY TIME Active Directory Service No authentication (HIGH) 1 DAY DNS Service Slow or no authentication (HIGH) 1 DAY Domain Controller Server No authentication (HIGH) 3 DAYS 29

30 9.5 Backup Service - Overview The Backup Service provides backups for all the servers at Emakhazeni Local Municipality for backup and disaster recovery purposes. The service provides LAN-based backups with the additional redundancy of a mirror copy of the Data Server data stored offsite at a DR site. This provides access to easy DR procedure testing without disrupting the operational environment and negates the need for tape. 9.6 Backup Service - Architecture & Design The Backup Service is a service that stores backups for all the servers in the organisation. The backup service is a disaster recovery tool that allows the organisation to have daily backups of the servers to assist in the event of data loss. The service also provides offsite backups in the event of disaster on the server that the application resides on. 9.7 Backup Service - Functional Components PHYSICAL DEVICE PHYSICAL LOCATION IP ADDRESS NOTES Database & File Server (Intel Server) Server Room Backup Service - Backups The Attix5 agent is loaded on the Emakhazeni LM backup server to back up the Storage Platform. This backup includes the Account and Report Server. UNTANGLE (INTERNET SERVER) DEVICE IP SERVER ROLE BACKUP GROUP BACKUP AGENT VERSION BACKUP SCHEDULE DATA RETENTION PERIOD OFFSITE DATA RETENTION PERIOD DATA RECOVERY POINT ESTIMATED RESTORE TIME File / Data Management System EMAKHAZENI LM-SRV\SERVERS Daily backups for this backup set occurs at 19h00 2 months 2 Months RPO (Recovery Point Objective) 24 hours, we run backups daily 1 Hour (Depending on data size) 30

31 9.7.2 Backup Service Full Recovery Procedure BACKUP SERVICE Component Responsible Company / Department Contact Details: Service Desk Actions INTEL SERVER Emakhazeni Local Municipality ICT Department N/A Components to be restored: Storage Platform database Storage Platform Reports database Stage 1: Task file Backup Server from Mirror Server at Entokozweni Office Requirements: Mirror Server The account GUID The account encryption key Full access to the Storage Server where the backup data resides Write access to the target location where the data must be written Potential time of service interruption Estimated recovery time This is a service that is managed by Emakhazeni Local Municipality ICT Department and as such there exists no external uptime guarantee or SLA. The time to recover is governed by the time to procure the required hardware and the reinstallation of software and the configuration thereof. 3 Days (If the configuration is backed and the equipment is available. Further the complete data restoration time could influence the recovery time due to the amount of data being retrieved and restored) Backup Service Component Recovery Procedure BACKUP SERVICE Component Responsible Company / Department Contact Details: Service Desk INTEL SERVER Emakhazeni Local Municipality ICT Department N/A Actions Hardware - Log a call to suppliers to replace the damaged components. Hardware After hardware has been repaired and should the Backup Service still not work a rebuild of Server from backup may be necessary. Follow the Full Recovery Procedure in order to restore the Backup Service. Software If problem cannot be rectified, rebuild from last available backup using the Full Recovery Procedure to restore the Backup Service. Emakhazeni Local Municipality ICT Department to make staff available for testing of the Backup Service once ICT has been restored. Potential time of service interruption This is a service that is managed by Emakhazeni Local Municipality ICT Department and as such there exists no external uptime guarantee or SLA. The time to recover is governed by the time to procure the required hardware and the reinstallation of software and the configuration thereof. Estimated recovery time 3 Days (If the configuration is backed and the equipment is available. Further the complete data restoration time could influence the recovery time due to the amount of data being retrieved and restored) 31

32 9.7.4 Backup Service - Risk & Impact Analysis ESTIMATED SERVICE RESTORATION TIME 3 DAYS OVERAL RISK RATING 15 (HIGH) SERVICES COMPONENT IMPACT DESCRIPTION IMPACT LIKELIHOOD RISK RATING Backup Service No new backups for organisation at Emakhazeni Local Municipality No access to existing backups No access to backup reports No account access to backup platform No data restoration (MEDIUM) ESTIMATED RECOVERY TIME 1 DAY Backup Server No new backups for organisation at Emakhazeni Local Municipality No access to existing backups No access to backup reports No account access to backup platform No data restoration Potential backup data loss (HIGH) 3 DAYS 9.8 Antivirus Overview McAfee Enterprise Anti-virus is deployed to ensure a virus free environment Antivirus - Architecture & Design The antivirus is setup in a centralised design with a master console Antivirus - Functional Components PHYSICAL DEVICE PHYSICAL LOCATION IP ADDRESS NOTES Internet Router (Cisco 1900) Server Room N/A Firewall - Untangle Server Room

33 9.8.3 Antivirus - Backups An agent is loaded on the App server which houses the AV application and backs up the AV Databases on the machine. INTERNET SERVER - UNTANGLE DEVICE IP SERVER ROLE BACKUP GROUP BACKUP AGENT VERSION BACKUP SCHEDULE Application Server EMAKHAZENI LM-SRV\SERVERS LAST SUCCESSFUL BACKUP 11 June 2013, 19:00 DATA RETENTION PERIOD OFFSICTE DATA RETENTION PERIOD DATA RECOVERY POINT ESTIMATED RESTORE TIME Daily backups for this backup set occurs at 19h00 2 months Offsite backups to B-site yet RPO (Recovery Point Objective) 24 hours, we run backups daily 1 Hour ( Depending size of data) Antivirus - Risk and Impact Analysis ESTIMATED SERVICE RESTORATION TIME 3 DAYS OVERAL RISK RATING 6 (LOW) SERVICES COMPONENT IMPACT DESCRIPTION AV Service Service Computers will not be updated with latest AV patterns, potentially leading to virus infections AV Database Service Computers will not be updated with latest AV patterns, potentially leading to virus infections NDMSVMBGFAPP01 Server Computers will not be updated with latest AV patterns, potentially leading to virus infections IMPACT LIKELIHOOD RISK RATING ESTIMATED RECOVERY TIME (LOW) 2 DAYS (LOW) 2 DAYS (LOW) 3 DAYS 10. System Specific ICT Services 10.1 Mail Service - Overview The mail services is actively used throughout the day between the hours of 7:00 to 18:00. Some users access their on mobile devices like Smart Phones and Tablets. This usage is generally remote and at all hours of the day or week. 33

34 Mail Service - Architecture & Design The mail system of Emakhazeni Local Municipality is a locally hosted Microsoft Exchange system. ICT is a single server which does have RAID redundancy on the hard drives. The server is backed up daily via the Attix5 platform. Mail is not spooled and cleaned via any third parties and is delivered to and from Emakhazeni Local Municipality via the mail server directly. The firewall at Emakhazeni Local Municipality is configured to allow for direct access to the mail server via TCP ports 443 and Internet Mail Service - Functional Components DIAGRAM # PHYSICAL DEVICE PHYSICAL LOCATION IP ADDRESS 1 DNS Provider SAIX / Telkom Cloud N/A 2 Internet Router (Cisco 1900) Server Room N/A 3 Firewall - Untangle Server Room Untangle Domain Controller Server Room CentOS Zimbra Mail Server Room NOTES Authoritative Domains The following domain is associated with the organisation: Emakhazeni lm.co.za Domain Hosting On the dnsadmin.gov.za portal ICT only states the domain is registered and no further WHOIS information is available Mail Records The system on the Internet require Zimbra Mail record that is accessible on the public DNS in order to be able to find the Post Office (Mail Server) that is responsible for the delivery of mail destined to a specific addressee (domain) in this instance : mail.emakhazenilm.co.za / zimbra Record for domain: emakhazenilm.local Mail Server Only one mail server is implemented and is located in the server room at Emakhazeni Local Municipality. The name of the server is Virtual Drive - Zimbra 34

35 Client Access Access to is via Microsoft Outlook, Outlook Web Access (OWA) as well as Outlook Mobile Access Inbound Observations No unified management service is currently used. (Spooling, archiving, etc.) Outbound Observations No unified management service is currently used. (Spooling, archiving, SMTP relay, etc.) Mail Service - Backups Loaded on the Mail server and backs up the DR Server daily. CentOS - Zimbra DEVICE IP SERVER ROLE BACKUP GROUP BACKUP SCHEDULE Zimbra Server EMAKHAZENI LM\SERVERS LAST SUCCESSFUL BACKUP 11 June 2013, 19:00 DATA RETENTION PERIOD OFFSICTE DATA RETENTION PERIOD DATA RECOVERY POINT ESTIMATED RESTORE TIME Daily backups for this backup set occurs at 19h00 2 months Offsite backups to B-site RPO (Recovery Point Objective) 24 hours, we run backups daily 1 Hour (depending on data size) Mail Service Recovery Procedures There are two facets to the recovery of the Mail Service. As a disaster can be invoked due to total mail system outage or component outage which affects only a subset of the mail service but can cause the mail service not to function Mail Service Component Recovery Procedure Component failures are the more general types of service failures to be experienced in an organisation. These failures could be hardware, software, network or connectivity related. EXCHANGE MAIL SERVER Component Responsible Company / Department Contact Details: Service Desk Zimbra Mail Server INTEL SERVER Emakhazeni Local Municipality ICT Department N/A Actions Hardware - Log a call with supplier to replace the damaged components. Hardware After hardware has been repaired and should the Exchange service still not work rebuild Exchange Server from backup if necessary. Follow the Full Recovery Procedure. Software If problem cannot be rectified, rebuild from last available backup using the Full Recovery Procedure. Potential time of service interruption Estimated recovery time This is a service that is managed by Emakhazeni Local Municipality ICT Department and as such there exists no external uptime guarantee or SLA. The time to recover is governed by the time to procure the required hardware and the reinstallation of software and the configuration thereof. 3 Days (If the configuration is backed up and the equipment is available) 35

36 Mail Service - Risk & Impact Analysis The Mail Service is an important part of the organisation. Mail Services though simple in function are often complex by design and require various other services to function. These include all of the Essential ICT Services in the organisation including the Network, Firewall, and Domain Controller as well as external service providers for the DNS (MX Record) components. ESTIMATED SERVICE RESTORATION TIME 3 DAYS OVERAL RISK RATING 10 (MEDIUM) SERVICES COMPONENT IMPACT DESCRIPTION IMPACT LIKELIHOOD RISK RATING DNS Provider Service MX record affects mail delivery No mail flow out of the organisation ESTIMATED RECOVERY TIME (LOW) 2 DAYS Exchange Service Service No mail flow internally or externally in the organisation (LOW) 1 DAY Exchange Server Hardware No mail flow internally or externally in the organisation (MEDIUM) 3 DAYS 10.2 Munsoft Service - Overview Munsoft is Municipal Financial & Billing software generally used by the Finance Department. As part of the Munsoft service a recovery strategy is in place to assist a Municipality in the event of a disaster. The service includes both backups and DR infrastructure. This process involves making the Application available on the recovery platform at ICTNA or onsite Munsoft Service - Architecture & Design Munsoft is one of the financial systems of Emakhazeni Local Municipality and as such is a very important system. 36

37 Munsoft Service - Functional Components PHYSICAL DEVICE PHYSICAL LOCATION IP ADDRESS NOTES 256k Telkom Line (Circuit ) Server Room N/A CISCO - Router Server Room N/A Provisioned by Telkom as part of the Munsoft MPLS network. IBM - Munsoft Server Room Munsoft Service - Backups Loaded on the App server which houses the VIP application and backs up the Mail Databases of the machine. MUNSOFTDR\EMAKHAZENI LM DEVICE IP USER BACKUP GROUP BACKUP AGENT VERSION BACKUP SCHEDULE Financial System MUNSOFTDR LAST SUCCESSFUL BACKUP 13 June 2013, 19:00 DATA RETENTION PERIOD OFFSICTE DATA RETENTION PERIOD DATA RECOVERY POINT ESTIMATED RESTORE TIME Daily backups for this backup set occurs at 22h00 2 roll-ups 2 roll-ups RPO (Recovery Point Objective) 24 hours, we run backups daily 12 minutes Munsoft Service Full Recovery Procedure MUNSOFT SERVICE Component As part of the Munsoft range service Emakhazeni Local Municipality has subscribed to the Munsoft DR Service. This service is provided by Munsoft / ICTNA and covers any DR failure on the financial system. Responsible Company / Department Contact Details: Service Desk IBM Server Emakhazeni Local Municipality ICT Department N/A Actions Emakhazeni Local Municipality ICT Department to call ITNA on Request to invoke Munsoft Disaster with ICTNA o You will be asked a security question o The operator will issue an incident reference number The service provider will provide you with updates as to the DR recovery progress o Database recovery progress o Restoration of Munsoft Service Emakhazeni Local Municipality to make staff available for testing on the financial system. This should ideally be person from both the Finance and ICT Department Emakhazeni Local Municipality to obtain at minimum 1 x 80 Column Line Matrix Printers, 1 x 136 Column Line Matrix Printer and 1 x High Volume Multi-Function Printer Emakhazeni Local Municipality to make staff available for testing on the financial system. This should ideally be person from both the Finance and ICT Department Post Recovery A new server will be need to be procured Munsoft / ICTNA will re-install and restore the system Further printers to be procured for optimal work distribution by Emakhazeni LM Potential time of service interruption Estimated recovery time There is a service contract in place that would limit potential downtime to a minimum. Downtime can be up to 16 work hours. Next Business Day 37