lobilearn.blogg.se - Inetwork system disaster and incident recovery plan

#INETWORK SYSTEM DISASTER AND INCIDENT RECOVERY PLAN DRIVERS#

The collection of resources and tasks to restore IT services (including components such as infrastructure, telecommunications, systems, applications and data) at an alternate site following a disruption of IT services.

DRI International (Disaster recovery, not disaster recovery plan): The technical aspect of business continuity.

NIST SP 800-82: A written plan for processing critical applications in the event of a major hardware or software failure or destruction of facilities.

NIST SP 800-34: A written plan for restoring one or more information systems at an alternate facility in response to a major hardware or software failure or destruction of facilities.

Therefore, let’s start with some classic definitions of DR plans (bold my emphasis): This is a very good time to discuss disaster recovery (DR), as it goes through a change of sorts. Cyber Resilience for Disaster Recovery: How Is it Changing?

#INETWORK SYSTEM DISASTER AND INCIDENT RECOVERY PLAN DRIVERS#

Therefore, you must understand your business drivers if you want to make an effective plan. Small aside, the difference between a business continuity plan and a continuity of operations plan is that the latter focuses on restoring essential functions in the short term (think 30 days or less).īefore we jump in, think about it like this: if BC is about backup strategies for people, DR is about backup strategies for all the stuff people rely on.

If you recall from the previous piece, NIST SP 800-34 calls out a separate disaster recovery plan, as it supports business continuity and continuity of operation plans. Moving along our organizational resilience journey, we focus on disaster recovery (DR), the perfect follow-up to business continuity (BC) The two go hand-in-hand, often referenced as BCDR, and both are key to your cyber resilience planning.