1 1 00:00:00,450 --> 00:00:03,030 Business impact analysis. 2 2 00:00:03,030 --> 00:00:05,640 In this lesson, we are going to talk about the concept 3 3 00:00:05,640 --> 00:00:07,890 of a business impact analysis, 4 4 00:00:07,890 --> 00:00:09,270 and this is really focused on 5 5 00:00:09,270 --> 00:00:11,700 how do things affect our business. 6 6 00:00:11,700 --> 00:00:13,950 Now, when I talk about a business impact analysis, 7 7 00:00:13,950 --> 00:00:15,500 this is also abbreviate as BIA. 8 8 00:00:16,830 --> 00:00:18,450 This is a systemic activity 9 9 00:00:18,450 --> 00:00:20,430 that identifies organizational risks 10 10 00:00:20,430 --> 00:00:22,530 and determines their effect on ongoing, 11 11 00:00:22,530 --> 00:00:24,630 mission critical operations. 12 12 00:00:24,630 --> 00:00:25,770 Let me give you a great example 13 13 00:00:25,770 --> 00:00:28,860 of a business impact analysis from my own company. 14 14 00:00:28,860 --> 00:00:31,980 My company happens to reside in Puerto Rico. 15 15 00:00:31,980 --> 00:00:34,740 Puerto Rico is a small island in the Caribbean. 16 16 00:00:34,740 --> 00:00:36,810 Now you can see it here on the screen. 17 17 00:00:36,810 --> 00:00:38,550 Now, because our company is in Puerto Rico, 18 18 00:00:38,550 --> 00:00:40,560 we have to worry about natural disasters 19 19 00:00:40,560 --> 00:00:42,450 and their impact to our business. 20 20 00:00:42,450 --> 00:00:45,870 For example, after a massive hurricane in 2017, 21 21 00:00:45,870 --> 00:00:49,170 the island of Puerto Rico was without power for months. 22 22 00:00:49,170 --> 00:00:51,780 So when we decided to move our company to Puerto Rico, 23 23 00:00:51,780 --> 00:00:53,310 we had to consider the impacts 24 24 00:00:53,310 --> 00:00:55,290 to our employees and our business 25 25 00:00:55,290 --> 00:00:57,180 if another huge storm came through 26 26 00:00:57,180 --> 00:00:58,860 because we are in Hurricane Alley 27 27 00:00:58,860 --> 00:01:01,050 and we're likely to get more storms. 28 28 00:01:01,050 --> 00:01:02,820 Now, another thing we have in Puerto Rico 29 29 00:01:02,820 --> 00:01:04,920 that happened recently is earthquakes. 30 30 00:01:04,920 --> 00:01:07,110 So, right after I moved my company to Puerto Rico, 31 31 00:01:07,110 --> 00:01:08,310 the island started shaking 32 32 00:01:08,310 --> 00:01:10,200 and started having a series of earthquakes 33 33 00:01:10,200 --> 00:01:11,850 at the southern part of our island. 34 34 00:01:11,850 --> 00:01:14,670 Now this started creating damage to many businesses, houses 35 35 00:01:14,670 --> 00:01:16,770 and churches, as you can see here. 36 36 00:01:16,770 --> 00:01:19,050 Now, because of our choice to be based out of Puerto Rico, 37 37 00:01:19,050 --> 00:01:21,630 our company, our employees and my family 38 38 00:01:21,630 --> 00:01:24,000 all have to have primary and backup plans 39 39 00:01:24,000 --> 00:01:25,560 to continue our operations 40 40 00:01:25,560 --> 00:01:27,990 even when the local power grid goes offline 41 41 00:01:27,990 --> 00:01:31,050 due to storms or earthquakes or any other reason. 42 42 00:01:31,050 --> 00:01:32,790 That is one of the main things we have to think about 43 43 00:01:32,790 --> 00:01:35,280 as part of our business impact analysis. 44 44 00:01:35,280 --> 00:01:37,770 Now, when you're conducting your business impact analysis, 45 45 00:01:37,770 --> 00:01:39,540 this is going to be governed by metrics 46 46 00:01:39,540 --> 00:01:42,480 that express your system in terms of availability. 47 47 00:01:42,480 --> 00:01:44,820 For example, are you a hundred percent available 48 48 00:01:44,820 --> 00:01:46,650 or are you 90% available? 49 49 00:01:46,650 --> 00:01:49,980 In our company, we try to achieve 99% uptime, 50 50 00:01:49,980 --> 00:01:52,920 meaning we want to be available to you 99% of the time 51 51 00:01:52,920 --> 00:01:55,200 during normal business hours. 52 52 00:01:55,200 --> 00:01:57,090 Now, when we start talking about these metrics, 53 53 00:01:57,090 --> 00:01:59,310 there are lots of different ones we have to consider. 54 54 00:01:59,310 --> 00:02:02,880 We have things like our maximum tolerable downtime or MTD. 55 55 00:02:02,880 --> 00:02:06,000 We have recovery time objective, RTO; 56 56 00:02:06,000 --> 00:02:08,610 the work recovery time, WRT 57 57 00:02:08,610 --> 00:02:11,340 or recovery point objective, RPO. 58 58 00:02:11,340 --> 00:02:13,170 Let's talk about each of these. 59 59 00:02:13,170 --> 00:02:16,560 Now, when we talk about a maximum tolerable downtime or MTD, 60 60 00:02:16,560 --> 00:02:18,180 this is the longest period of time 61 61 00:02:18,180 --> 00:02:19,800 a business can be inoperable, 62 62 00:02:19,800 --> 00:02:22,740 without causing irrevocable business failure. 63 63 00:02:22,740 --> 00:02:24,810 Essentially, how long can you be down 64 64 00:02:24,810 --> 00:02:26,850 without going out of business? 65 65 00:02:26,850 --> 00:02:29,760 Now, the MTD is going to be different for each organization 66 66 00:02:29,760 --> 00:02:31,830 and even within each organization, 67 67 00:02:31,830 --> 00:02:35,250 each of your business processes can have its own MTD. 68 68 00:02:35,250 --> 00:02:37,680 For example, some may be just a couple of minutes 69 69 00:02:37,680 --> 00:02:40,020 or a couple hours for critical functions. 70 70 00:02:40,020 --> 00:02:42,540 You may have up to 24 hours for urgent functions 71 71 00:02:42,540 --> 00:02:45,420 and up to seven days or longer for normal functions. 72 72 00:02:45,420 --> 00:02:47,640 It really does depend on your organization 73 73 00:02:47,640 --> 00:02:50,100 and you have to figure that out for yourself. 74 74 00:02:50,100 --> 00:02:52,530 Now, the MTD is going to set your upper limit 75 75 00:02:52,530 --> 00:02:54,480 on the recovery time that the system 76 76 00:02:54,480 --> 00:02:59,010 and the asset owners have to have to resume your operations. 77 77 00:02:59,010 --> 00:03:00,630 So, keeping that in mind, 78 78 00:03:00,630 --> 00:03:02,730 let's take a look at my own business. 79 79 00:03:02,730 --> 00:03:03,570 I already mentioned that 80 80 00:03:03,570 --> 00:03:06,060 power was a really important thing for us. 81 81 00:03:06,060 --> 00:03:07,680 So, we know that power is critical 82 82 00:03:07,680 --> 00:03:08,730 to our business functions. 83 83 00:03:08,730 --> 00:03:10,740 Without it, we really can't do our job. 84 84 00:03:10,740 --> 00:03:13,350 I can't film courses and I can't answer student questions 85 85 00:03:13,350 --> 00:03:15,720 if I don't have power to turn on my computers 86 86 00:03:15,720 --> 00:03:17,610 and be able to run our internet. 87 87 00:03:17,610 --> 00:03:19,830 Now without this power, we can't do our job at all. 88 88 00:03:19,830 --> 00:03:21,990 So we have multiple backup systems 89 89 00:03:21,990 --> 00:03:24,060 to protect power to our building. 90 90 00:03:24,060 --> 00:03:26,700 First, we have power from our local electrical company 91 91 00:03:26,700 --> 00:03:29,100 coming through the wires on their grid. 92 92 00:03:29,100 --> 00:03:31,770 Then, we have solar power that provides us a backup 93 93 00:03:31,770 --> 00:03:33,750 during the day if the grid goes out 94 94 00:03:33,750 --> 00:03:36,060 and it actually reacts as our primary electrical source 95 95 00:03:36,060 --> 00:03:36,893 during the day 96 96 00:03:36,893 --> 00:03:39,180 because it's so bright and sunny in Puerto Rico. 97 97 00:03:39,180 --> 00:03:40,050 Now, after that, 98 98 00:03:40,050 --> 00:03:42,240 we have some Tesla power walls that we've installed. 99 99 00:03:42,240 --> 00:03:44,340 These are batteries and these collect power 100 100 00:03:44,340 --> 00:03:46,230 from our solar system during the day 101 101 00:03:46,230 --> 00:03:48,030 and that way, even if the grid goes out, 102 102 00:03:48,030 --> 00:03:49,710 we can end up having those batteries 103 103 00:03:49,710 --> 00:03:51,480 provide the power to us. 104 104 00:03:51,480 --> 00:03:53,520 And that can happen at night as well. 105 105 00:03:53,520 --> 00:03:55,650 When the sun goes down, we can actually survive 106 106 00:03:55,650 --> 00:03:58,500 off those batteries if the grid is gone. 107 107 00:03:58,500 --> 00:04:00,900 Now, if it becomes cloudy, then the solar won't work. 108 108 00:04:00,900 --> 00:04:02,190 Well, we still have the batteries 109 109 00:04:02,190 --> 00:04:05,040 and so we have primary of grid, secondary solar, 110 110 00:04:05,040 --> 00:04:06,810 tertiary of batteries. 111 111 00:04:06,810 --> 00:04:08,700 But for us, that's not enough. 112 112 00:04:08,700 --> 00:04:10,170 We actually, in addition to that, 113 113 00:04:10,170 --> 00:04:11,790 have a diesel generator as well, 114 114 00:04:11,790 --> 00:04:14,520 and that diesel generator has a hundred gallons of fuel. 115 115 00:04:14,520 --> 00:04:16,740 That's enough for us to run seven days straight 116 116 00:04:16,740 --> 00:04:18,450 without the need for more fuel. 117 117 00:04:18,450 --> 00:04:22,140 So, for us to be without power takes a lot these days 118 118 00:04:22,140 --> 00:04:25,200 because we have the grid, we have solar, we have battery, 119 119 00:04:25,200 --> 00:04:27,780 we have diesel, we have all of these systems in place 120 120 00:04:27,780 --> 00:04:28,620 because we realize 121 121 00:04:28,620 --> 00:04:31,020 that is an important mission essential thing for us 122 122 00:04:31,020 --> 00:04:34,410 is to have power for us to be able to do our jobs. 123 123 00:04:34,410 --> 00:04:37,290 Now, if the power grid goes out for more than 60 minutes, 124 124 00:04:37,290 --> 00:04:39,120 we found another issue though 125 125 00:04:39,120 --> 00:04:40,740 and that's that our primary internet connection 126 126 00:04:40,740 --> 00:04:42,870 from our cable provider dies. 127 127 00:04:42,870 --> 00:04:45,240 Now, that isn't a problem for me if I'm filming 128 128 00:04:45,240 --> 00:04:46,980 but if I'm trying to answer your questions 129 129 00:04:46,980 --> 00:04:49,650 and do student support, we can't do that without internet 130 130 00:04:49,650 --> 00:04:51,660 because we have to be able to reach to you, right? 131 131 00:04:51,660 --> 00:04:53,067 And so that's another issue for us 132 132 00:04:53,067 --> 00:04:55,860 and so we have a secondary service for that. 133 133 00:04:55,860 --> 00:04:58,500 We have a cellular modem that we use as a backup. 134 134 00:04:58,500 --> 00:05:00,570 Now we realized recently there was a big storm 135 135 00:05:00,570 --> 00:05:03,330 that came through and our area lost power for three days. 136 136 00:05:03,330 --> 00:05:04,320 Now we didn't lose power 137 137 00:05:04,320 --> 00:05:05,940 'cause we had all these systems in place, 138 138 00:05:05,940 --> 00:05:07,920 but our internet connection died. 139 139 00:05:07,920 --> 00:05:09,660 And so we tried to switch over to the cellular modem 140 140 00:05:09,660 --> 00:05:12,780 and we found out the speed was horrible. 141 141 00:05:12,780 --> 00:05:13,613 Why? 142 142 00:05:13,613 --> 00:05:15,000 Because everybody else was out as well 143 143 00:05:15,000 --> 00:05:16,950 and they all went onto their modems 144 144 00:05:16,950 --> 00:05:18,270 and because they wanted to a cellular modem, 145 145 00:05:18,270 --> 00:05:20,310 the cell towers were being flooded with users. 146 146 00:05:20,310 --> 00:05:24,180 And so we were getting speeds that were 10 or 20 or 30 147 147 00:05:24,180 --> 00:05:26,040 or 40 kilobits per second 148 148 00:05:26,040 --> 00:05:29,100 and we were hardly able to even open up our ticket system 149 149 00:05:29,100 --> 00:05:30,870 to be able to answer our students' questions. 150 150 00:05:30,870 --> 00:05:32,580 So now that we've learned from that, 151 151 00:05:32,580 --> 00:05:34,710 we have a third internet provider as well 152 152 00:05:34,710 --> 00:05:36,540 that provides a service over a microwave 153 153 00:05:36,540 --> 00:05:39,060 and they have a better backup plan for power outages. 154 154 00:05:39,060 --> 00:05:40,770 So they maintain services up 155 155 00:05:40,770 --> 00:05:42,780 even when the local cable company is down. 156 156 00:05:42,780 --> 00:05:44,850 So this helps eliminate that bottleneck. 157 157 00:05:44,850 --> 00:05:47,610 My point here is that you have to do this business impact 158 158 00:05:47,610 --> 00:05:49,560 for yourself in your organization 159 159 00:05:49,560 --> 00:05:52,230 and figure out what things are critical to your operations 160 160 00:05:52,230 --> 00:05:55,200 and put things in place to help protect those. 161 161 00:05:55,200 --> 00:05:57,180 So when I look at my support services, 162 162 00:05:57,180 --> 00:06:00,420 what is our MTD for our support services? 163 163 00:06:00,420 --> 00:06:03,090 Well, we calculated that our maximum tolerable downtime 164 164 00:06:03,090 --> 00:06:04,620 is 12 hours. 165 165 00:06:04,620 --> 00:06:06,570 Now how do I come up with 12 hours? 166 166 00:06:06,570 --> 00:06:09,510 Well, we started thinking about if I was a student, 167 167 00:06:09,510 --> 00:06:11,430 what was the longest period of time I would want to go 168 168 00:06:11,430 --> 00:06:13,230 without getting an answer to my questions? 169 169 00:06:13,230 --> 00:06:15,600 And we figured that 12 hours was a reasonable time 170 170 00:06:15,600 --> 00:06:17,490 in an emergency situation. 171 171 00:06:17,490 --> 00:06:18,480 Now to accommodate that, 172 172 00:06:18,480 --> 00:06:21,420 we actually have our staff split in two parts. 173 173 00:06:21,420 --> 00:06:23,730 Half of my team resides in Puerto Rico, 174 174 00:06:23,730 --> 00:06:26,010 the other half of my team is in the Philippines. 175 175 00:06:26,010 --> 00:06:28,230 They are 12 hours off sync from each other. 176 176 00:06:28,230 --> 00:06:30,000 So, when it's daytime in the Philippines, 177 177 00:06:30,000 --> 00:06:31,440 it's nighttime in Puerto Rico. 178 178 00:06:31,440 --> 00:06:32,790 And when it's daytime in Puerto Rico, 179 179 00:06:32,790 --> 00:06:34,350 it's nighttime in the Philippines. 180 180 00:06:34,350 --> 00:06:36,840 And so we actually can cover almost 24 hours a day 181 181 00:06:36,840 --> 00:06:38,250 using these two locations 182 182 00:06:38,250 --> 00:06:39,870 because each side works eight hours 183 183 00:06:39,870 --> 00:06:41,100 and there's a little bit of time 184 184 00:06:41,100 --> 00:06:43,080 that isn't covered by both teams. 185 185 00:06:43,080 --> 00:06:46,050 Now that again works within our 12 hours of time. 186 186 00:06:46,050 --> 00:06:47,400 Now the other good thing about this is 187 187 00:06:47,400 --> 00:06:49,560 because they're so geographically distanced, 188 188 00:06:49,560 --> 00:06:51,720 if there's a big storm that takes out Puerto Rico, 189 189 00:06:51,720 --> 00:06:53,850 hopefully it doesn't affect the Philippines. 190 190 00:06:53,850 --> 00:06:55,440 If there's a big storm that takes out the Philippines, 191 191 00:06:55,440 --> 00:06:57,510 hopefully it won't affect Puerto Rico. 192 192 00:06:57,510 --> 00:06:59,940 And so by having our geographic diversity here, 193 193 00:06:59,940 --> 00:07:02,190 it allows us to maintain that 12 hour response time 194 194 00:07:02,190 --> 00:07:04,440 because even if Puerto Rico was down, 195 195 00:07:04,440 --> 00:07:07,440 well in the 12 hours, the Philippines team would be awake 196 196 00:07:07,440 --> 00:07:09,090 and they'll be able to take on that load 197 197 00:07:09,090 --> 00:07:10,377 of being able to answer your questions. 198 198 00:07:10,377 --> 00:07:11,850 And so that's why we do that 199 199 00:07:11,850 --> 00:07:13,320 and that's why we break up our company. 200 200 00:07:13,320 --> 00:07:15,570 It was a risk management decision that we've made 201 201 00:07:15,570 --> 00:07:17,940 to provide better service to our students. 202 202 00:07:17,940 --> 00:07:20,580 Now again, you need to figure out what your MTD is 203 203 00:07:20,580 --> 00:07:22,710 for your company in the real world 204 204 00:07:22,710 --> 00:07:24,660 so you can design your risk management plan 205 205 00:07:24,660 --> 00:07:27,090 around supporting that MTD. 206 206 00:07:27,090 --> 00:07:28,470 What we've done for us 207 207 00:07:28,470 --> 00:07:30,180 was thinking about the biggest threats to us 208 208 00:07:30,180 --> 00:07:31,830 which are natural disasters. 209 209 00:07:31,830 --> 00:07:34,230 And so we have our MTD built around that 210 210 00:07:34,230 --> 00:07:35,550 for our student support services 211 211 00:07:35,550 --> 00:07:37,680 and we put power and internet connectivity 212 212 00:07:37,680 --> 00:07:40,110 at the top of that list of things that we need to have, 213 213 00:07:40,110 --> 00:07:42,180 two and three and four different mechanisms 214 214 00:07:42,180 --> 00:07:44,070 to be able to provide backups to our backups 215 215 00:07:44,070 --> 00:07:46,080 to make sure we can always support you. 216 216 00:07:46,080 --> 00:07:48,720 Now the next one we want to talk about is our RTO. 217 217 00:07:48,720 --> 00:07:50,940 This is our recovery time objective. 218 218 00:07:50,940 --> 00:07:53,190 Now this is the length of time it takes after an event 219 219 00:07:53,190 --> 00:07:56,280 to resume your normal business operations and activities. 220 220 00:07:56,280 --> 00:07:58,500 When you start thinking about recovery time objective, 221 221 00:07:58,500 --> 00:08:01,260 I want you to think about the fact of something went down, 222 222 00:08:01,260 --> 00:08:02,160 we lost power. 223 223 00:08:02,160 --> 00:08:04,140 How quickly do you need it back? 224 224 00:08:04,140 --> 00:08:07,800 In my case, we have a 60 second time for power. 225 225 00:08:07,800 --> 00:08:09,660 We want to make sure our power is back up and online 226 226 00:08:09,660 --> 00:08:11,070 within 60 seconds. 227 227 00:08:11,070 --> 00:08:12,210 Now, is that achievable? 228 228 00:08:12,210 --> 00:08:13,043 Yes. 229 229 00:08:13,043 --> 00:08:14,970 If you have a backup diesel generator, 230 230 00:08:14,970 --> 00:08:17,100 it will turn on in about 45 seconds 231 231 00:08:17,100 --> 00:08:19,260 and transfer power to the diesel generator. 232 232 00:08:19,260 --> 00:08:23,040 Now, my wife wasn't happy with 45 seconds or 60 seconds 233 233 00:08:23,040 --> 00:08:25,320 and she wanted a recovery time of zero. 234 234 00:08:25,320 --> 00:08:26,730 Now, can I achieve that? 235 235 00:08:26,730 --> 00:08:28,470 The answer is yes, and that's one of the reasons 236 236 00:08:28,470 --> 00:08:30,450 why we have those battery backup systems 237 237 00:08:30,450 --> 00:08:31,920 because if power goes away, 238 238 00:08:31,920 --> 00:08:33,780 those batteries come on instantly. 239 239 00:08:33,780 --> 00:08:35,610 There is zero lag time there. 240 240 00:08:35,610 --> 00:08:37,205 And so we're able to hit a recovery time objective for power 241 241 00:08:37,205 --> 00:08:39,390 of zero seconds. 242 242 00:08:39,390 --> 00:08:41,670 Now the overall power of getting it back to the grid, 243 243 00:08:41,670 --> 00:08:42,780 we can't control that. 244 244 00:08:42,780 --> 00:08:45,300 That's up to our local power company, but we can make sure 245 245 00:08:45,300 --> 00:08:47,160 that we can recover our business 246 246 00:08:47,160 --> 00:08:49,140 and make sure we're on battery, on solar 247 247 00:08:49,140 --> 00:08:51,450 or on generator within zero seconds 248 248 00:08:51,450 --> 00:08:53,670 and that's our recovery time objective. 249 249 00:08:53,670 --> 00:08:56,190 Now the next one we want to talk about is work recovery time 250 250 00:08:56,190 --> 00:08:57,810 or WRT. 251 251 00:08:57,810 --> 00:09:00,330 This is the length of time in addition to the RTO 252 252 00:09:00,330 --> 00:09:03,360 of individual systems to perform reintegration and testing 253 253 00:09:03,360 --> 00:09:06,540 of a restored or upgraded system following an event. 254 254 00:09:06,540 --> 00:09:07,980 So let me give you an example. 255 255 00:09:07,980 --> 00:09:11,010 Let's say in my organization, we had a power outage 256 256 00:09:11,010 --> 00:09:12,120 and we didn't have the batteries yet. 257 257 00:09:12,120 --> 00:09:13,920 We had to rely on those generators. 258 258 00:09:13,920 --> 00:09:16,140 So we had a 60 second recovery time. 259 259 00:09:16,140 --> 00:09:18,720 Well, in 45 seconds, power comes back up. 260 260 00:09:18,720 --> 00:09:22,080 But if those systems went down because of a power surge 261 261 00:09:22,080 --> 00:09:24,180 and I had to replace one of my servers, 262 262 00:09:24,180 --> 00:09:26,790 well that's going to take additional work recovery time. 263 263 00:09:26,790 --> 00:09:28,140 I fixed the main problem, 264 264 00:09:28,140 --> 00:09:30,360 the recovery time objective of getting the power up, 265 265 00:09:30,360 --> 00:09:32,700 but now I have to fix the second and third order effects 266 266 00:09:32,700 --> 00:09:34,560 to get work product going again 267 267 00:09:34,560 --> 00:09:36,120 which might be rebooting a computer, 268 268 00:09:36,120 --> 00:09:37,680 it might be rebuilding a computer, 269 269 00:09:37,680 --> 00:09:39,540 it might be replacing a hard drive. 270 270 00:09:39,540 --> 00:09:40,560 Whatever those things are, 271 271 00:09:40,560 --> 00:09:42,810 I have to perform that reintegration and testing 272 272 00:09:42,810 --> 00:09:44,430 to bring those systems back online 273 273 00:09:44,430 --> 00:09:46,290 in an upgrade or restored state 274 274 00:09:46,290 --> 00:09:48,780 to be able to get us back to regular work product. 275 275 00:09:48,780 --> 00:09:51,300 And our final one we want to talk about is RPO. 276 276 00:09:51,300 --> 00:09:53,460 This is our recovery point objective. 277 277 00:09:53,460 --> 00:09:55,200 This is the longest period of time 278 278 00:09:55,200 --> 00:09:59,280 an organization can tolerate lost data being unrecoverable. 279 279 00:09:59,280 --> 00:10:00,900 Now, the way I like to think about this one 280 280 00:10:00,900 --> 00:10:04,290 when I think about RPO is think about ransomware. 281 281 00:10:04,290 --> 00:10:05,940 If you have ransomware on a system, 282 282 00:10:05,940 --> 00:10:07,560 it's going to encrypt your files. 283 283 00:10:07,560 --> 00:10:09,330 Now you've got a couple of choices here. 284 284 00:10:09,330 --> 00:10:12,060 You can pay the ransom, which we never recommend. 285 285 00:10:12,060 --> 00:10:13,950 You could try to crack the ransomware key 286 286 00:10:13,950 --> 00:10:16,560 which could take you days, weeks or months or years 287 287 00:10:16,560 --> 00:10:18,060 depending on how strong it is 288 288 00:10:18,060 --> 00:10:20,370 or you can actually wipe that system 289 289 00:10:20,370 --> 00:10:22,380 and recover from a known good backup. 290 290 00:10:22,380 --> 00:10:23,370 Well, that's great. 291 291 00:10:23,370 --> 00:10:24,810 Let's go ahead and choose that option. 292 292 00:10:24,810 --> 00:10:27,450 Well, if we do that, what is the longest period of time 293 293 00:10:27,450 --> 00:10:29,580 that we can tolerate data loss? 294 294 00:10:29,580 --> 00:10:31,860 Well, there's going to be time that we're going to be lagging 295 295 00:10:31,860 --> 00:10:33,870 as we're recovering all that data back 296 296 00:10:33,870 --> 00:10:36,390 and that data may have several hours 297 297 00:10:36,390 --> 00:10:38,100 since it was last backed up. 298 298 00:10:38,100 --> 00:10:41,010 For instance, if you run your backup once a day at midnight, 299 299 00:10:41,010 --> 00:10:42,810 that's when your data was backed up. 300 300 00:10:42,810 --> 00:10:45,210 And if this ransomware hits you at six in the morning, 301 301 00:10:45,210 --> 00:10:46,980 you have six hours worth of lost data 302 302 00:10:46,980 --> 00:10:48,900 because you don't have a backup of that. 303 303 00:10:48,900 --> 00:10:49,733 This is what we're talking about 304 304 00:10:49,733 --> 00:10:51,810 when we're talking about recovery point objective. 305 305 00:10:51,810 --> 00:10:54,420 That six hours is going to be lost period of time. 306 306 00:10:54,420 --> 00:10:56,820 And so if your RPO was 12 hours, that's fine. 307 307 00:10:56,820 --> 00:10:59,700 If your RPO is four hours, you've just broken your RPO. 308 308 00:10:59,700 --> 00:11:00,930 So you need to keep that in mind. 309 309 00:11:00,930 --> 00:11:03,270 When you're thinking about your recovery point objective, 310 310 00:11:03,270 --> 00:11:07,110 you are focused on how long you can be without your data. 311 311 00:11:07,110 --> 00:11:08,850 That is the whole idea here. 312 312 00:11:08,850 --> 00:11:11,790 Now, when we start thinking about your MTD and your RPO, 313 313 00:11:11,790 --> 00:11:14,190 these are key terms that you need to know for the exam. 314 314 00:11:14,190 --> 00:11:15,300 They're going to help you determine 315 315 00:11:15,300 --> 00:11:17,190 which business functions are critical 316 316 00:11:17,190 --> 00:11:20,520 and they're going to specify appropriate risk countermeasures 317 317 00:11:20,520 --> 00:11:22,530 to help you make sure that you're going to be able 318 318 00:11:22,530 --> 00:11:24,000 to get those systems up and running 319 319 00:11:24,000 --> 00:11:26,730 and within those MTD and RPOs. 320 320 00:11:26,730 --> 00:11:29,550 For example - if your RPO is measured in days, 321 321 00:11:29,550 --> 00:11:31,710 then a simple tape backup will work fine 322 322 00:11:31,710 --> 00:11:33,510 or you can use a network attached storage array 323 323 00:11:33,510 --> 00:11:34,890 or something like that. 324 324 00:11:34,890 --> 00:11:38,580 But if your RPO is zero or measured in minutes or seconds, 325 325 00:11:38,580 --> 00:11:40,650 then a more expensive server cluster backup 326 326 00:11:40,650 --> 00:11:43,230 and redundancy solution is going to be needed. 327 327 00:11:43,230 --> 00:11:45,360 A good example of this is my own company. 328 328 00:11:45,360 --> 00:11:48,330 We have a server cluster backup and full redundancy solution 329 329 00:11:48,330 --> 00:11:50,010 for our web servers. 330 330 00:11:50,010 --> 00:11:52,800 This is because we can't afford to be down for long periods 331 331 00:11:52,800 --> 00:11:54,690 of time when over 200,000 students 332 332 00:11:54,690 --> 00:11:57,150 are relying on our servers to learn from our videos 333 333 00:11:57,150 --> 00:11:58,170 and our practice exams 334 334 00:11:58,170 --> 00:12:00,300 to prepare to pass their certifications. 335 335 00:12:00,300 --> 00:12:03,000 When I sold you a course, I sold you access to that course. 336 336 00:12:03,000 --> 00:12:05,610 We want to make sure you have access and we can't say, 337 337 00:12:05,610 --> 00:12:06,540 'Oh! I'm sorry. 338 338 00:12:06,540 --> 00:12:08,550 We lost all of your data for the last three weeks. 339 339 00:12:08,550 --> 00:12:10,020 We're going to have to have you start over.' 340 340 00:12:10,020 --> 00:12:12,000 So we want to make sure we have that set up right. 341 341 00:12:12,000 --> 00:12:14,370 And so we've taken the risk management mitigations 342 342 00:12:14,370 --> 00:12:17,640 to help make sure we maintain a good MTD and RPO 343 343 00:12:17,640 --> 00:12:18,960 based on that need. 344 344 00:12:18,960 --> 00:12:20,847 Keeping our MTD very low in time 345 345 00:12:20,847 --> 00:12:24,663 and our RPO very low in time so you get a better experience.