Design of a Disaster Recovery Plan based on the NIST 800-34 standard and the PMBOK framework for an ecuadorian insurance company
Abstract
This document summarizes the design of a disaster recovery plan in the technology area for an insurance company in Ecuador. The first section sets out the legal, technical and project management frameworks; which are: the Codification of Insurance of Ecuador, the standard of the National Institute of Standards and Technology 800-34 and the management framework of the Project Management Institute, respectively. In the second section, the critical infrastructure and its recovery strategies are determined based on the processes of high criticality in impact analysis. As a result of the project management, the work breakdown structure, the risk matrix and the cost analysis are delivered; which will be important for the company to approve the execution of the project.
Downloads
References
NIST, Contingency Planning Guide for Information Technology Systems, Washintong: U.S. Goverment Printing Office, 2002.
A. Cárdenas Pallo, Desarrollo del plan de Continuidad del negocio para la Empresa Equivida SA para el período 2012-2015, Sangolqui: Universidad de las Fuerzas Armadas ESPE, 2013.
Seguros del Pichincha.Marzo,2019. [En línea]. Disponible en: https://www.segurosdelpichincha.com/conoce-seguros-del-pichincha-aseguradora-lider-en-ecuador.html.
F. d. V. y. S. Codificación de Resoluciones Monetarias, Junta Financiera Monetaria, Quito.Registro Oficial de la Asamblea Nacional, 2017, pp. 227-239.
Project Management Institute. La guía de los fundamentos para la dirección de proyectos (Guía del PMBOK).Sexta ed., Newtown Square, Pennsylvania 19073-3299 EE.UU.Project Management Institute, Inc., 2017, pp. 23-25.
Microsoft.Windows IP Pro Center -Use DNS policy for app load balancing. Microsoft.Mayo,2019. [En línea]. Disponible en: https://docs.microsoft.com/en-us/windows-server/networking/dns/deploy/app-lb. [Último acceso: 10 Junio2019].
S. Branham.ExchangeITup.Stacey Branham, 6 Enero 2015. [En línea]. Disponible en: http://www.exchangeitup.net/2015/01/exchange-2013-planning-diagrams-part-1.html. [Último acceso: 10 Junio 2019].
Avaya Inc. .AVAYA. Product Documentation. Redundancy and high availability.Avaya, 20 6 2018. [En línea]. Disponible en: https://bit.ly/3tBbSh3 [Último acceso: 10 Junio2019].
Instituto Tecnológico de Matehuala. 2.1 Arquitectura de las aplicaciones Web. Junio,2015. [En línea]. Disponible en: https://programacionwebisc.wordpress.com/2-1-arquitectura-de-las-aplicaciones-web/.
Universitat Oberta de Catalunya.Glosario.[En línea]. Disponible en: http://cv.uoc.edu/UOC/a/moduls/90/90_519/web/nwin/glossari/. [Último acceso: 2019].
Superintendencia de Bancos.Superintendencia de Bancos. Libro I. Normas generales para instituciones del sistema financiero. Administración de Riesgos.10 enero 2010. [En línea]. Disponible en: https://www.superbancos.gob.ec/bancos/wp-content/uploads/downloads/2017/06/L1_X_cap_I.pdf. [Último acceso: junio 2019].
A. Guardiola Lozano, Manual de Introducción al Seguro, Madrid.Editorial MAPFRE, 1990.
Indiana University.Knowledge Base.2019. [En línea]. Disponible en: https://kb.iu.edu/d/aiuv. [Último acceso: Junio 2019].
Microsoft.Microsoft Docs: Exchange Server -High availability -Database availability groups.Agosto, 2018. [En línea]. Disponible en: https://docs.microsoft.com/en-us/exchange/high-availability/database-availability-groups/database-availability-groups?view=exchserver-2019. [Último acceso: Junio 2019].
Microsoft.Documentación principal de BizTalk Server.Microsoft. Junio,2017. [En línea]. Disponible en: https://docs.microsoft.com/es-es/biztalk/core/rules. [Último acceso: Agosto 2019].
This article is published by LAJC under a Creative Commons Attribution-Non-Commercial-Share-Alike 4.0 International License. This means that non-exclusive copyright is transferred to the National Polytechnic School. The Author (s) give their consent to the Editorial Committee to publish the article in the issue that best suits the interests of this Journal. Find out more in our Copyright Notice.
Disclaimer
LAJC in no event shall be liable for any direct, indirect, incidental, punitive, or consequential copyright infringement claims related to articles that have been submitted for evaluation, or published in any issue of this journal. Find out more in our Disclaimer Notice.
