WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:0

00:06.280 --> 00:15.660
All right, the business continuity plan.

00:15.690 --> 00:17.440
Okay, business continuity plan is a

00:17.470 --> 00:21.160
comprehensive document formulated to
ensure resilience against potential

00:21.190 --> 00:25.220
threats operations to continue under
adverse or abnormal conditions.

00:25.240 --> 00:30.480
Again, the goals, analyzing potential
risks and losses, enabling risk management

00:30.510 --> 00:33.620
process to lessen the prospect of a
complete shutdown,

00:33.640 --> 00:38.580
always prioritizing safety, health and
welfare of the organization and staff.

00:38.610 --> 00:42.620
Human life safety always
our ultimate goal.

00:42.640 --> 00:46.560
Minimizing infrastructural damage in the
event of a disaster, restoring business

00:46.590 --> 00:51.160
conditions to pre disaster levels,
maintaining vital documents and telephone

00:51.160 --> 00:54.920
numbers, employee details, vendor details,
and so forth, providing staff training,

00:54.920 --> 00:57.660
building awareness, and
promoting disaster preparedness.

00:57.680 --> 01:00.060
Training, really important.

01:00.090 --> 01:04.800
In the training or testing phase of your

01:04.830 --> 01:10.620
BCPDRP, you'll go through a variety of
tabletops through full interruption test.

01:10.650 --> 01:14.980
You don't have a mature business
continuity disaster recovery plan until

01:15.010 --> 01:20.560
you've completed a live failover
within the recovery time objectives.

01:20.590 --> 01:24.720
You practice, practice, practice until you
got your recovery time objectives

01:24.750 --> 01:27.780
complete, then you go
into maintenance mode.

01:27.810 --> 01:31.840
I mentioned earlier, business
continuity plans are often outdated.

01:31.870 --> 01:33.760
They get stale really quickly.

01:33.790 --> 01:36.740
They should be linked
to change management.

01:36.770 --> 01:41.120
When changes occur in the environment, you
want to update the business continuity and

01:41.120 --> 01:44.260
disaster recovery plan accordingly
because your environment is changing.

01:44.290 --> 01:50.920
Also, any stakeholders, any participants
in BCP or DMP activities, you need to

01:50.950 --> 01:56.200
ensure that they've got a backup or depth
in those positions and that the

01:56.230 --> 02:01.060
responsibilities are transferred when the
job is turned over and needs to be

02:01.090 --> 02:05.640
included in job inscriptions to ensure
that the replacement is also trained on

02:05.670 --> 02:09.660
the disaster recovery planning
and procedures.

02:09.690 --> 02:12.000
So training, really important.

02:12.030 --> 02:14.800
What looks good on paper almost never

02:14.830 --> 02:20.170
works out in reality, needs to
be refined or tweaked somehow.

02:20.200 --> 02:22.120
The Disaster Recovery Plan.

02:22.150 --> 02:25.980
Okay, its goals, reduce overall
organizational risk,

02:26.010 --> 02:30.760
alleviate concerns of senior management,
ensure compliance with regulations,

02:30.790 --> 02:33.820
provide a rapid response
after a disruption.

02:33.850 --> 02:37.080
There are some physical security

02:37.110 --> 02:39.400
considerations that are
tied into all this.

02:39.430 --> 02:45.080
We talked about most of this in physical
security, but things like fault tolerance

02:45.110 --> 02:50.240
systems, uninterruptible power supplies,
line conditioners, things like that.

02:50.240 --> 02:52.000
Raid, we talked about that in backups.

02:52.030 --> 02:55.640
Backups are definitely a huge

02:55.640 --> 02:59.660
consideration with disaster recovery since
you need to resume at the alternate site.

02:59.690 --> 03:02.440
Also, the method at which you restore that

03:02.470 --> 03:06.860
data can be periodic or
interval based or real time.

03:06.890 --> 03:09.500
You have things like electronic vaulting,

03:09.530 --> 03:16.060
remote journaling, or
live database updates.

03:16.080 --> 03:18.600
Site to site backup, there
you go, onsite or hot site.

03:18.630 --> 03:20.800
I had to think about that for a second.

03:20.830 --> 03:26.800
Bunk transfers, periodically, bulk
transfers supplemented

03:27.720 --> 03:32.480
with transaction logs or shadowing. That
was the term I was looking for where an up

03:32.510 --> 03:37.100
to date copy is always being
maintained at the alternate site.

03:37.120 --> 03:38.940
Again, everything needs to be tested.

03:38.970 --> 03:42.000
Bcp and DRP are very closely intertwined.

03:42.030 --> 03:44.440
It's an incredibly important part of

03:44.470 --> 03:48.660
information security and it's also
quite often overlooked or outdated.

03:48.690 --> 03:51.020
Really important.

03:51.050 --> 03:54.380
That is going to wrap up Module 21,

03:54.400 --> 03:56.460
Deal with Business Conditioning
Disaster Recovery.

03:56.490 --> 04:00.360
We're going to continue the risk
analysis discussion in the next module.