WEBVTT 1 00:00:00.000 --> 00:00:01.290 In this lesson, 2 00:00:01.290 --> 00:00:04.740 we will learn about fail-safe mechanisms. 3 00:00:04.740 --> 00:00:07.920 Fail-safe mechanisms are systems designed 4 00:00:07.920 --> 00:00:12.920 to default to a secure state or a safe operational mode 5 00:00:12.960 --> 00:00:16.740 in the event of a failure or security breach. 6 00:00:16.740 --> 00:00:19.590 Fail-safe mechanism concepts include 7 00:00:19.590 --> 00:00:22.620 fail-secure and fail-safe. 8 00:00:22.620 --> 00:00:26.940 Fail-secure mechanisms prioritize maintaining security 9 00:00:26.940 --> 00:00:31.140 by locking down access or shutting down critical functions 10 00:00:31.140 --> 00:00:33.210 when a failure occurs. 11 00:00:33.210 --> 00:00:37.740 Fail-secure mechanisms prevent unauthorized access 12 00:00:37.740 --> 00:00:41.910 even if it causes a temporary denial of service. 13 00:00:41.910 --> 00:00:46.020 Let's learn more about fail-secure and fail-safe. 14 00:00:46.020 --> 00:00:48.930 First, we have fail-secure. 15 00:00:48.930 --> 00:00:51.390 Fail-secure mechanisms are critical 16 00:00:51.390 --> 00:00:55.860 in systems where security must remain the highest priority, 17 00:00:55.860 --> 00:00:59.190 even in the face of unexpected issues. 18 00:00:59.190 --> 00:01:03.150 In a fail-secure system, when a failure occurs, 19 00:01:03.150 --> 00:01:06.180 the system shuts down or locks access 20 00:01:06.180 --> 00:01:11.100 to protect against unauthorized entry or data breaches. 21 00:01:11.100 --> 00:01:13.620 The main goal of fail-secure 22 00:01:13.620 --> 00:01:17.190 is to maintain a strict security posture, 23 00:01:17.190 --> 00:01:21.450 even if that means temporarily disrupting availability. 24 00:01:21.450 --> 00:01:23.670 For example, if a server 25 00:01:23.670 --> 00:01:26.250 handling sensitive customer information 26 00:01:26.250 --> 00:01:28.800 experiences a critical error, 27 00:01:28.800 --> 00:01:33.180 a fail-secure approach would immediately cut off all access 28 00:01:33.180 --> 00:01:34.530 to the server, 29 00:01:34.530 --> 00:01:39.120 preventing anyone from reaching potentially vulnerable data 30 00:01:39.120 --> 00:01:41.760 until the issue is resolved. 31 00:01:41.760 --> 00:01:43.320 This measure ensures 32 00:01:43.320 --> 00:01:46.470 that sensitive information stays protected, 33 00:01:46.470 --> 00:01:51.470 but it may limit authorized users access temporarily. 34 00:01:51.480 --> 00:01:53.190 On an enterprise scale, 35 00:01:53.190 --> 00:01:57.060 a fail-secure mechanism could look like a database 36 00:01:57.060 --> 00:01:59.760 that automatically locks down access 37 00:01:59.760 --> 00:02:02.190 during unexpected incidents. 38 00:02:02.190 --> 00:02:06.180 For example, suppose a bank's core database 39 00:02:06.180 --> 00:02:09.000 containing confidential financial data 40 00:02:09.000 --> 00:02:13.410 detects an anomaly, like an unusual data request pattern, 41 00:02:13.410 --> 00:02:17.460 which could signal a breach attempt or internal error. 42 00:02:17.460 --> 00:02:21.300 A failure secure setup would immediately block access 43 00:02:21.300 --> 00:02:22.710 to the database, 44 00:02:22.710 --> 00:02:25.170 safeguarding sensitive financial records 45 00:02:25.170 --> 00:02:27.030 from possible compromise, 46 00:02:27.030 --> 00:02:31.890 though it may also temporarily prevent legitimate users 47 00:02:31.890 --> 00:02:34.020 from accessing the system. 48 00:02:34.020 --> 00:02:36.750 In this case, with fail-safe, 49 00:02:36.750 --> 00:02:40.260 the highest priority is keeping the data secure 50 00:02:40.260 --> 00:02:43.980 and ensuring no unauthorized access occurs 51 00:02:43.980 --> 00:02:46.290 during the vulnerability period, 52 00:02:46.290 --> 00:02:50.520 even prioritizing that over customer convenience. 53 00:02:50.520 --> 00:02:53.340 Second, we have fail-safe. 54 00:02:53.340 --> 00:02:55.860 In contrast to fail-secure, 55 00:02:55.860 --> 00:02:59.310 fail-safe mechanisms emphasize safety, 56 00:02:59.310 --> 00:03:03.840 focusing on ensuring an IT system continues to function 57 00:03:03.840 --> 00:03:08.220 in a manner that prevents harm or damage during a failure. 58 00:03:08.220 --> 00:03:12.210 Think of the difference between fail-secure and fail-safe 59 00:03:12.210 --> 00:03:16.710 like the response of two different doors in a power outage. 60 00:03:16.710 --> 00:03:20.190 Imagine one is the main entry to a vault 61 00:03:20.190 --> 00:03:22.440 representing fail-secure, 62 00:03:22.440 --> 00:03:25.770 and the other is an emergency exit door 63 00:03:25.770 --> 00:03:28.020 representing fail-safe. 64 00:03:28.020 --> 00:03:31.740 The fail-secure door guarding valuable assets 65 00:03:31.740 --> 00:03:34.620 will lock up tight when the power goes out. 66 00:03:34.620 --> 00:03:37.650 This approach prioritizes security. 67 00:03:37.650 --> 00:03:40.530 Even if someone can't get in temporarily, 68 00:03:40.530 --> 00:03:42.930 the valuables remain protected. 69 00:03:42.930 --> 00:03:47.490 In this approach, security is maintained above all else. 70 00:03:47.490 --> 00:03:51.090 Conversely, the fail-safe door is a safe exit 71 00:03:51.090 --> 00:03:52.860 in case of emergency. 72 00:03:52.860 --> 00:03:56.760 So, in the power outage, this door unlocks, 73 00:03:56.760 --> 00:03:59.160 ensuring people can get out quickly 74 00:03:59.160 --> 00:04:01.980 if there's a fire or another risk. 75 00:04:01.980 --> 00:04:04.470 Here, safety is the priority, 76 00:04:04.470 --> 00:04:08.340 ensuring no one is harmed by being trapped inside, 77 00:04:08.340 --> 00:04:11.310 even if it slightly reduces security 78 00:04:11.310 --> 00:04:14.550 by allowing potential outside access. 79 00:04:14.550 --> 00:04:16.260 In IT systems, 80 00:04:16.260 --> 00:04:20.580 fail-secure mechanisms lock down the data or systems 81 00:04:20.580 --> 00:04:24.720 to prevent unauthorized access when something goes wrong, 82 00:04:24.720 --> 00:04:26.820 while fail-safe mechanisms 83 00:04:26.820 --> 00:04:30.300 prioritize safe continuous operation, 84 00:04:30.300 --> 00:04:34.110 even if that means sacrificing a bit of security 85 00:04:34.110 --> 00:04:37.050 to ensure ongoing functionality. 86 00:04:37.050 --> 00:04:39.030 In an enterprise environment, 87 00:04:39.030 --> 00:04:41.400 network switches or routers 88 00:04:41.400 --> 00:04:44.460 can be configured to detect a failure 89 00:04:44.460 --> 00:04:47.730 in the primary external internet connection 90 00:04:47.730 --> 00:04:50.400 and automatically reroute traffic 91 00:04:50.400 --> 00:04:52.590 through an alternative link, 92 00:04:52.590 --> 00:04:56.520 even if the secondary link has lower security controls 93 00:04:56.520 --> 00:04:58.710 or bandwidth capacity. 94 00:04:58.710 --> 00:05:00.780 For example, if a company's 95 00:05:00.780 --> 00:05:03.540 primary internet connection fails, 96 00:05:03.540 --> 00:05:07.200 a fail-safe configuration could redirect traffic 97 00:05:07.200 --> 00:05:10.110 to a secondary internet service provider 98 00:05:10.110 --> 00:05:12.060 or virtual private network 99 00:05:12.060 --> 00:05:15.150 to maintain operational continuity. 100 00:05:15.150 --> 00:05:16.890 While this backup path 101 00:05:16.890 --> 00:05:19.830 may lack the same level of firewall protection 102 00:05:19.830 --> 00:05:23.340 or traffic inspection as the primary route, 103 00:05:23.340 --> 00:05:26.940 it ensures that employees retain internet access 104 00:05:26.940 --> 00:05:30.270 and can continue working without interruption, 105 00:05:30.270 --> 00:05:33.720 thereby prioritizing business continuity 106 00:05:33.720 --> 00:05:35.550 over strict security 107 00:05:35.550 --> 00:05:37.800 during the failover period. 108 00:05:37.800 --> 00:05:42.600 So, remember, fail-safe mechanisms are designed 109 00:05:42.600 --> 00:05:45.480 to keep systems secure or safe 110 00:05:45.480 --> 00:05:49.500 during unexpected failures or security breaches. 111 00:05:49.500 --> 00:05:54.500 There are two primary types, fail-secure and fail-safe. 112 00:05:54.720 --> 00:05:58.320 Fail-secure mechanisms prioritize security 113 00:05:58.320 --> 00:06:02.490 by locking down access or shutting down critical functions 114 00:06:02.490 --> 00:06:04.200 when issues arise, 115 00:06:04.200 --> 00:06:07.950 even if it temporarily disrupts availability. 116 00:06:07.950 --> 00:06:10.980 In contrast, fail-safe mechanisms 117 00:06:10.980 --> 00:06:15.180 focus on maintaining safe and continuous operations, 118 00:06:15.180 --> 00:06:19.920 allowing systems to continue functioning during a failure, 119 00:06:19.920 --> 00:06:23.730 even if some security measures are relaxed. 120 00:06:23.730 --> 00:06:27.090 Together, these approaches help organizations 121 00:06:27.090 --> 00:06:29.340 manage risks effectively, 122 00:06:29.340 --> 00:06:33.180 balancing security and operational continuity 123 00:06:33.180 --> 00:06:36.753 based on the specific needs of the situation.