WEBVTT

1
00:00:00.000 --> 00:00:02.400
In this section of the course, we are going

2
00:00:02.400 --> 00:00:05.160
to discuss vulnerabilities and attacks.

3
00:00:05.160 --> 00:00:06.507
The vulnerabilities and attacks section

4
00:00:06.507 --> 00:00:11.130
of the course focuses on domain three, security engineering,

5
00:00:11.130 --> 00:00:14.220
as well as domain four, security operations,

6
00:00:14.220 --> 00:00:19.110
specifically objectives 3.4 and 4.2.

7
00:00:19.110 --> 00:00:23.430
Objective 3.4 states that given a scenario, you must be able

8
00:00:23.430 --> 00:00:27.510
to implement hardware security technologies and techniques.

9
00:00:27.510 --> 00:00:30.990
Objective 4.2 states that given a scenario,

10
00:00:30.990 --> 00:00:34.560
you must be able to analyze vulnerabilities and attacks

11
00:00:34.560 --> 00:00:38.160
and recommend solutions to reduce the attack surface.

12
00:00:38.160 --> 00:00:40.794
Understanding vulnerabilities and attacks is crucial

13
00:00:40.794 --> 00:00:43.975
in safeguarding enterprise networks and systems.

14
00:00:43.975 --> 00:00:46.950
Enterprise vulnerabilities and weaknesses arise

15
00:00:46.950 --> 00:00:48.930
from how software is built,

16
00:00:48.930 --> 00:00:53.310
how systems are configured, and even how access is managed.

17
00:00:53.310 --> 00:00:56.400
Attackers often work to exploit these vulnerabilities

18
00:00:56.400 --> 00:01:00.150
by injecting harmful code, manipulating system memory,

19
00:01:00.150 --> 00:01:02.940
or even targeting physical hardware.

20
00:01:02.940 --> 00:01:06.480
Staying ahead of threat actors requires a proactive approach

21
00:01:06.480 --> 00:01:09.480
to identifying and addressing vulnerabilities

22
00:01:09.480 --> 00:01:11.760
before they can be exploited.

23
00:01:11.760 --> 00:01:13.530
As we go through this section,

24
00:01:13.530 --> 00:01:16.590
we will cover many topics related to vulnerabilities

25
00:01:16.590 --> 00:01:20.130
and attacks, including injection vulnerabilities,

26
00:01:20.130 --> 00:01:22.050
memory-related vulnerabilities,

27
00:01:22.050 --> 00:01:24.180
configuration vulnerabilities,

28
00:01:24.180 --> 00:01:27.840
authorization vulnerabilities, malicious code attacks,

29
00:01:27.840 --> 00:01:31.650
hardware and firmware attacks, memory-based attacks,

30
00:01:31.650 --> 00:01:34.530
and electromagnetic attacks.

31
00:01:34.530 --> 00:01:38.040
First, we will look at injection vulnerabilities.

32
00:01:38.040 --> 00:01:41.610
Injection vulnerabilities occur when an attacker is able

33
00:01:41.610 --> 00:01:44.970
to inject malicious code into a system

34
00:01:44.970 --> 00:01:47.760
through an input field or other interface.

35
00:01:47.760 --> 00:01:50.640
Malicious code injection can lead to unintended

36
00:01:50.640 --> 00:01:53.070
or harmful execution of commands.

37
00:01:53.070 --> 00:01:55.110
Specific injection vulnerabilities

38
00:01:55.110 --> 00:01:58.710
include command injection, code injection,

39
00:01:58.710 --> 00:02:01.927
cross-site scripting, cross-site request forgery,

40
00:02:01.927 --> 00:02:06.060
server-side request forgery, and deserialization.

41
00:02:06.060 --> 00:02:07.740
Command injection occurs

42
00:02:07.740 --> 00:02:11.130
when an attacker exploits vulnerabilities in a system

43
00:02:11.130 --> 00:02:13.380
to execute arbitrary commands

44
00:02:13.380 --> 00:02:15.570
on the host operating system.

45
00:02:15.570 --> 00:02:17.160
Command injection may result

46
00:02:17.160 --> 00:02:20.370
in attackers getting unauthorized network access,

47
00:02:20.370 --> 00:02:22.440
manipulating system files,

48
00:02:22.440 --> 00:02:25.530
or taking control of the entire system.

49
00:02:25.530 --> 00:02:28.620
Code injection involves inserting malicious code

50
00:02:28.620 --> 00:02:30.630
into a vulnerable application,

51
00:02:30.630 --> 00:02:34.050
which is then executed by that application.

52
00:02:34.050 --> 00:02:36.870
Code injection can then lead to data breaches,

53
00:02:36.870 --> 00:02:39.600
unauthorized access, and the execution

54
00:02:39.600 --> 00:02:42.900
of unintended actions within the application,

55
00:02:42.900 --> 00:02:46.500
potentially compromising the entire system's integrity.

56
00:02:46.500 --> 00:02:49.560
Injection attacks can also take various forms,

57
00:02:49.560 --> 00:02:53.940
including structured query language or SQL injection.

58
00:02:53.940 --> 00:02:56.130
In an SQL injection attack,

59
00:02:56.130 --> 00:02:59.490
an attacker inserts malicious SQL commands

60
00:02:59.490 --> 00:03:01.170
into a database query

61
00:03:01.170 --> 00:03:03.660
for the purpose of manipulating the database

62
00:03:03.660 --> 00:03:05.970
to execute unauthorized actions,

63
00:03:05.970 --> 00:03:07.800
altering or deleting records,

64
00:03:07.800 --> 00:03:11.730
or even gaining administrative control over the database.

65
00:03:11.730 --> 00:03:14.340
Cross-site scripting is another type of attack

66
00:03:14.340 --> 00:03:17.820
that can occur as a result of injection vulnerabilities.

67
00:03:17.820 --> 00:03:19.740
In a cross-site scripting attack,

68
00:03:19.740 --> 00:03:23.100
an attacker injects malicious scripts into webpages.

69
00:03:23.100 --> 00:03:25.830
These scripts can steal sensitive information,

70
00:03:25.830 --> 00:03:29.790
hijack accounts, redirect users to malicious websites,

71
00:03:29.790 --> 00:03:32.460
or manipulate the webpage content.

72
00:03:32.460 --> 00:03:35.488
Cross-site request forgery attacks involve manipulating

73
00:03:35.488 --> 00:03:39.330
a user into performing actions they did not intend.

74
00:03:39.330 --> 00:03:42.510
Cross-site request forgery attacks abuse the trust

75
00:03:42.510 --> 00:03:44.790
between a client and a server.

76
00:03:44.790 --> 00:03:47.670
A server-side request forgery allows an attacker

77
00:03:47.670 --> 00:03:51.210
to force a server to make unauthorized requests

78
00:03:51.210 --> 00:03:54.660
to internal systems or external resources.

79
00:03:54.660 --> 00:03:57.690
A server-side request forgery abuses the trust

80
00:03:57.690 --> 00:04:00.450
between a front-end server and a back-end

81
00:04:00.450 --> 00:04:02.310
or internal resource.

82
00:04:02.310 --> 00:04:04.440
Deserialization attacks occur

83
00:04:04.440 --> 00:04:06.930
when an attacker injects malicious data

84
00:04:06.930 --> 00:04:10.110
into an application that processes the data

85
00:04:10.110 --> 00:04:12.990
by converting it from a serialized format

86
00:04:12.990 --> 00:04:16.080
back into its original object form.

87
00:04:16.080 --> 00:04:18.540
This is called deserialization.

88
00:04:18.540 --> 00:04:20.004
During deserialization,

89
00:04:20.004 --> 00:04:24.360
the application may inadvertently execute harmful code

90
00:04:24.360 --> 00:04:28.050
embedded in the data leading to remote code execution,

91
00:04:28.050 --> 00:04:31.050
privilege escalation, or data corruption.

92
00:04:31.050 --> 00:04:35.130
Next, we'll explore memory-related vulnerabilities.

93
00:04:35.130 --> 00:04:37.980
Memory-related vulnerabilities refer to flaws

94
00:04:37.980 --> 00:04:40.470
in how an application handles memory,

95
00:04:40.470 --> 00:04:42.150
potentially allowing attackers

96
00:04:42.150 --> 00:04:45.420
to execute malicious code, cause crashes,

97
00:04:45.420 --> 00:04:47.700
or leak sensitive information.

98
00:04:47.700 --> 00:04:52.080
Memory-related vulnerabilities include deprecated functions,

99
00:04:52.080 --> 00:04:56.610
unsafe memory utilization, overflows, race conditions,

100
00:04:56.610 --> 00:05:00.600
and time of check to time of use vulnerabilities.

101
00:05:00.600 --> 00:05:04.410
Deprecated functions are older, insecure functions

102
00:05:04.410 --> 00:05:06.360
that are still in use.

103
00:05:06.360 --> 00:05:08.850
The use of deprecated functions can lead

104
00:05:08.850 --> 00:05:11.640
to unsafe memory utilization

105
00:05:11.640 --> 00:05:13.500
and exposure of a system

106
00:05:13.500 --> 00:05:16.560
to vulnerabilities like buffer overflows.

107
00:05:16.560 --> 00:05:18.390
In a buffer overflow attack,

108
00:05:18.390 --> 00:05:21.120
an attacker overflows a memory buffer

109
00:05:21.120 --> 00:05:23.400
to overwrite adjacent memory.

110
00:05:23.400 --> 00:05:26.160
An overflow attack can lead to the execution

111
00:05:26.160 --> 00:05:29.550
of arbitrary code, allowing the attacker to take control

112
00:05:29.550 --> 00:05:31.680
of the system, corrupt data,

113
00:05:31.680 --> 00:05:34.110
or crash the application entirely.

114
00:05:34.110 --> 00:05:38.070
Overflows and unsafe memory usage often create opportunities

115
00:05:38.070 --> 00:05:39.390
for race conditions.

116
00:05:39.390 --> 00:05:41.760
A race condition occurs when the timing

117
00:05:41.760 --> 00:05:45.480
of operations is manipulated to exploit the system.

118
00:05:45.480 --> 00:05:48.420
Specifically, a race condition can occur

119
00:05:48.420 --> 00:05:50.400
when two processes attempt

120
00:05:50.400 --> 00:05:53.580
to modify the same data concurrently leading

121
00:05:53.580 --> 00:05:55.440
to unpredictable results,

122
00:05:55.440 --> 00:05:59.910
such as a financial transaction being processed twice.

123
00:05:59.910 --> 00:06:03.960
A specific type of race condition is a time of check

124
00:06:03.960 --> 00:06:05.970
to time of use condition.

125
00:06:05.970 --> 00:06:09.720
To exploit a time of check to time of use vulnerability,

126
00:06:09.720 --> 00:06:12.360
an attacker may change the system's state

127
00:06:12.360 --> 00:06:15.480
between the time the system checks a condition

128
00:06:15.480 --> 00:06:17.471
and the time it uses the result,

129
00:06:17.471 --> 00:06:20.550
leading to unexpected behavior.

130
00:06:20.550 --> 00:06:24.660
After that, we will look at configuration vulnerabilities.

131
00:06:24.660 --> 00:06:28.110
Configuration vulnerabilities occur when systems,

132
00:06:28.110 --> 00:06:32.250
applications, or networks are improperly configured.

133
00:06:32.250 --> 00:06:33.930
Configuration vulnerabilities

134
00:06:33.930 --> 00:06:37.440
include directory service misconfiguration,

135
00:06:37.440 --> 00:06:40.560
unsecure configuration, embedded secrets,

136
00:06:40.560 --> 00:06:43.890
outdated or unpatched software and libraries,

137
00:06:43.890 --> 00:06:45.990
and end-of-life software.

138
00:06:45.990 --> 00:06:49.290
Directory service misconfigurations are improper setup

139
00:06:49.290 --> 00:06:51.600
or management of directory services,

140
00:06:51.600 --> 00:06:53.370
such as active directory.

141
00:06:53.370 --> 00:06:56.190
Directory service misconfigurations can lead

142
00:06:56.190 --> 00:07:00.270
to security vulnerabilities and unauthorized access.

143
00:07:00.270 --> 00:07:04.500
Unsecure configurations are improperly set system settings

144
00:07:04.500 --> 00:07:07.350
or defaults that can leave a system vulnerable

145
00:07:07.350 --> 00:07:08.760
to exploitation.

146
00:07:08.760 --> 00:07:12.270
Unsecure configurations may also include the default

147
00:07:12.270 --> 00:07:14.760
enabling of unnecessary services

148
00:07:14.760 --> 00:07:18.030
and can result in system exploitation.

149
00:07:18.030 --> 00:07:22.470
Embedded secrets, such as hard-coded passwords or API keys,

150
00:07:22.470 --> 00:07:24.660
are sensitive credentials stored directly

151
00:07:24.660 --> 00:07:27.540
in source code or configuration files,

152
00:07:27.540 --> 00:07:30.480
making them easily accessible to attackers

153
00:07:30.480 --> 00:07:32.940
who gain access to the code base.

154
00:07:32.940 --> 00:07:36.960
The impact of exposed embedded secrets can be severe

155
00:07:36.960 --> 00:07:41.040
as attackers may misuse them to gain unauthorized access

156
00:07:41.040 --> 00:07:43.620
to systems, escalate privileges,

157
00:07:43.620 --> 00:07:45.990
or compromise sensitive data.

158
00:07:45.990 --> 00:07:48.000
Outdated or unpatched software

159
00:07:48.000 --> 00:07:51.180
and libraries often contain known vulnerabilities

160
00:07:51.180 --> 00:07:53.670
that have not been addressed by updates.

161
00:07:53.670 --> 00:07:54.870
The use of outdated

162
00:07:54.870 --> 00:07:56.940
or unpatched software can result

163
00:07:56.940 --> 00:08:00.300
in attackers gaining unauthorized system access,

164
00:08:00.300 --> 00:08:02.160
executing malicious code,

165
00:08:02.160 --> 00:08:05.910
or compromising the security of the entire system.

166
00:08:05.910 --> 00:08:08.370
End-of-life software are applications

167
00:08:08.370 --> 00:08:10.680
or systems that are no longer supported

168
00:08:10.680 --> 00:08:13.080
with security updates by the vendor.

169
00:08:13.080 --> 00:08:15.720
End-of-life software can be easily exploited

170
00:08:15.720 --> 00:08:18.540
by attackers due to the lack of patches

171
00:08:18.540 --> 00:08:20.670
for newly discovered threats.

172
00:08:20.670 --> 00:08:24.600
Next, we will explore authorization vulnerabilities.

173
00:08:24.600 --> 00:08:26.880
Authorization vulnerabilities occur

174
00:08:26.880 --> 00:08:30.480
when a system improperly manages access controls,

175
00:08:30.480 --> 00:08:32.430
allowing users to process

176
00:08:32.430 --> 00:08:35.910
and perform actions beyond their intended permissions.

177
00:08:35.910 --> 00:08:39.600
Authorization vulnerabilities include a confused deputy,

178
00:08:39.600 --> 00:08:42.930
weak ciphers, and vulnerable third parties.

179
00:08:42.930 --> 00:08:46.110
The confused deputy vulnerability arises when a program

180
00:08:46.110 --> 00:08:49.470
with higher privileges is tricked into performing actions

181
00:08:49.470 --> 00:08:51.270
on behalf of an attacker.

182
00:08:51.270 --> 00:08:54.840
Confused deputies can bypass authorization checks.

183
00:08:54.840 --> 00:08:57.000
Weak ciphers in encryption can lead

184
00:08:57.000 --> 00:08:59.670
to ineffective protection of sensitive data,

185
00:08:59.670 --> 00:09:03.330
enabling attackers to intercept or manipulate information

186
00:09:03.330 --> 00:09:05.490
that should be securely transmitted.

187
00:09:05.490 --> 00:09:08.280
Vulnerable third parties are external services

188
00:09:08.280 --> 00:09:12.030
or partner organizations that, if compromised, can be used

189
00:09:12.030 --> 00:09:15.930
to gain unauthorized access to a system's resources or data.

190
00:09:15.930 --> 00:09:18.570
For example, if a web application

191
00:09:18.570 --> 00:09:22.110
uses a vulnerable third party service with weak ciphers

192
00:09:22.110 --> 00:09:23.760
for secure communications,

193
00:09:23.760 --> 00:09:26.040
an attacker might exploit this weakness

194
00:09:26.040 --> 00:09:28.050
to intercept encrypted data

195
00:09:28.050 --> 00:09:32.280
or manipulate a confused deputy to gain unauthorized access

196
00:09:32.280 --> 00:09:35.670
to restricted functions within the application.

197
00:09:35.670 --> 00:09:39.120
Following that, we will look at malicious code attacks.

198
00:09:39.120 --> 00:09:42.390
Malicious code attacks are the insertion of harmful software

199
00:09:42.390 --> 00:09:46.102
or code into a system to disrupt, steal,

200
00:09:46.102 --> 00:09:49.320
or manipulate data and operations.

201
00:09:49.320 --> 00:09:51.180
Malicious code attack concepts

202
00:09:51.180 --> 00:09:53.670
include implants and poisoning.

203
00:09:53.670 --> 00:09:55.500
Implants are malicious code

204
00:09:55.500 --> 00:09:59.520
or hardware inserted into a system, often stealthily.

205
00:09:59.520 --> 00:10:01.950
Implants may create a persistent backdoor

206
00:10:01.950 --> 00:10:05.130
that attackers can use for ongoing access

207
00:10:05.130 --> 00:10:07.230
and control to a machine.

208
00:10:07.230 --> 00:10:10.350
Poisoning occurs when attackers tamper with the data

209
00:10:10.350 --> 00:10:13.050
or environment used by a system.

210
00:10:13.050 --> 00:10:15.300
For example, poisoning could be used

211
00:10:15.300 --> 00:10:18.180
to corrupt a machine learning model's training data

212
00:10:18.180 --> 00:10:19.920
to alter its behavior,

213
00:10:19.920 --> 00:10:23.730
or injecting malicious code into software updates.

214
00:10:23.730 --> 00:10:27.480
Then we will explore hardware and firmware attacks.

215
00:10:27.480 --> 00:10:30.960
Hardware and firmware attacks exploit vulnerabilities

216
00:10:30.960 --> 00:10:34.950
in the physical components or embedded software of a system.

217
00:10:34.950 --> 00:10:36.990
Firmware attacks could allow attackers

218
00:10:36.990 --> 00:10:39.600
to gain deep access, control,

219
00:10:39.600 --> 00:10:43.500
or disrupt operations at a fundamental machine level.

220
00:10:43.500 --> 00:10:46.320
Hardware and firmware attacks may be recognized

221
00:10:46.320 --> 00:10:49.740
by threat actor tactics, techniques and procedures,

222
00:10:49.740 --> 00:10:54.740
or TTPs, such as firmware tampering, BIOS and UEFI attacks,

223
00:10:55.650 --> 00:10:57.963
and USB-based attacks.

224
00:10:57.963 --> 00:11:01.860
Firmware attacks involve modifying the embedded software,

225
00:11:01.860 --> 00:11:05.040
called firmware, that controls hardware devices.

226
00:11:05.040 --> 00:11:07.140
Firmware attacks are often used

227
00:11:07.140 --> 00:11:09.480
to create persistent back doors

228
00:11:09.480 --> 00:11:11.700
or alter device behavior in ways

229
00:11:11.700 --> 00:11:13.620
that are difficult to detect.

230
00:11:13.620 --> 00:11:17.100
BIOS and UEFI attacks specifically target

231
00:11:17.100 --> 00:11:21.180
the low-level firmware responsible for booting up a system.

232
00:11:21.180 --> 00:11:24.510
BIOS and UEFI attacks may give attackers control

233
00:11:24.510 --> 00:11:28.620
over the device before the operating system even loads,

234
00:11:28.620 --> 00:11:32.011
making these attacks especially hard to remove.

235
00:11:32.011 --> 00:11:34.830
USB-based attacks use compromised

236
00:11:34.830 --> 00:11:39.300
or malicious USB devices to deliver harmful code directly

237
00:11:39.300 --> 00:11:41.190
to a system's hardware.

238
00:11:41.190 --> 00:11:44.654
USB-based attacks bypass many traditional security measures

239
00:11:44.654 --> 00:11:47.790
by exploiting the direct physical USB connection

240
00:11:47.790 --> 00:11:49.020
to the system.

241
00:11:49.020 --> 00:11:51.870
This direct connection may allow malicious code

242
00:11:51.870 --> 00:11:54.150
to be executed at a low level even

243
00:11:54.150 --> 00:11:57.810
before software-based defenses like antivirus programs

244
00:11:57.810 --> 00:11:59.243
or firewalls can detect

245
00:11:59.243 --> 00:12:01.260
or intercept the threat.

246
00:12:01.260 --> 00:12:05.550
In application, an attacker might use a tampered USB drive

247
00:12:05.550 --> 00:12:08.820
to introduce malicious code that modifies the BIOS

248
00:12:08.820 --> 00:12:12.900
or UEFI firmware gaining control over a system at startup

249
00:12:12.900 --> 00:12:16.980
and compromising the entire device at the lowest level.

250
00:12:16.980 --> 00:12:19.950
Next, we will look at memory-based attacks.

251
00:12:19.950 --> 00:12:22.400
Memory-based attacks exploit vulnerabilities

252
00:12:22.400 --> 00:12:26.250
in a system's memory management to execute malicious code,

253
00:12:26.250 --> 00:12:29.550
manipulate data, or cause system crashes.

254
00:12:29.550 --> 00:12:33.180
Memory-based attacks include attacker tactics, techniques,

255
00:12:33.180 --> 00:12:36.660
and procedures specific to memory and shimming.

256
00:12:36.660 --> 00:12:40.410
These attacks often target the way a program allocates

257
00:12:40.410 --> 00:12:42.690
and manages memory taking advantage

258
00:12:42.690 --> 00:12:45.240
of vulnerabilities like buffer overflows

259
00:12:45.240 --> 00:12:47.820
to inject or execute harmful code.

260
00:12:47.820 --> 00:12:51.330
Shimming works by placing a malicious layer of code

261
00:12:51.330 --> 00:12:54.270
that intercepts communication between the application

262
00:12:54.270 --> 00:12:55.770
and the operating system,

263
00:12:55.770 --> 00:12:58.590
allowing the attacker to modify inputs,

264
00:12:58.590 --> 00:13:00.810
outputs, or system calls.

265
00:13:00.810 --> 00:13:04.438
This manipulation can lead to unauthorized actions such

266
00:13:04.438 --> 00:13:07.710
as privilege escalation, data theft,

267
00:13:07.710 --> 00:13:10.290
or bypassing security controls,

268
00:13:10.290 --> 00:13:12.300
all while remaining undetected

269
00:13:12.300 --> 00:13:14.610
by traditional security measures.

270
00:13:14.610 --> 00:13:17.550
For example, an attacker might exploit

271
00:13:17.550 --> 00:13:21.210
a buffer overflow vulnerability in a vulnerable application

272
00:13:21.210 --> 00:13:24.960
to inject a shim into the program's memory space.

273
00:13:24.960 --> 00:13:28.860
This shim could then intercept and redirect system calls,

274
00:13:28.860 --> 00:13:31.920
enabling the attacker to escalate their privileges

275
00:13:31.920 --> 00:13:34.710
from a standard user to an administrator

276
00:13:34.710 --> 00:13:37.800
or to exfiltrate sensitive data like passwords

277
00:13:37.800 --> 00:13:39.330
or encryption keys,

278
00:13:39.330 --> 00:13:42.720
all while bypassing standard security checks.

279
00:13:42.720 --> 00:13:46.770
Finally, we will explore electromagnetic attacks.

280
00:13:46.770 --> 00:13:50.130
Electromagnetic attacks use electromagnetic interference

281
00:13:50.130 --> 00:13:53.340
or EMI or electromagnetic pulses

282
00:13:53.340 --> 00:13:58.320
or EMP to disrupt, damage, or manipulate hardware and data.

283
00:13:58.320 --> 00:14:00.540
Electromagnetic interference attacks

284
00:14:00.540 --> 00:14:04.110
involve the deliberate emission of electromagnetic signals

285
00:14:04.110 --> 00:14:06.480
that can interfere with the normal operation

286
00:14:06.480 --> 00:14:08.130
of electronic devices.

287
00:14:08.130 --> 00:14:11.670
Electromagnetic interference attacks can cause malfunctions

288
00:14:11.670 --> 00:14:14.430
or data corruption in critical systems such

289
00:14:14.430 --> 00:14:17.550
as medical devices, industrial control systems,

290
00:14:17.550 --> 00:14:20.730
or communication networks, potentially leading

291
00:14:20.730 --> 00:14:24.900
to significant operational disruptions and safety risks.

292
00:14:24.900 --> 00:14:28.050
An electromagnetic pulse is a powerful burst

293
00:14:28.050 --> 00:14:30.000
of electromagnetic energy,

294
00:14:30.000 --> 00:14:33.750
often generated by specialized devices that can damage

295
00:14:33.750 --> 00:14:36.480
or permanently disable electronic circuits

296
00:14:36.480 --> 00:14:38.940
and components by overwhelming them

297
00:14:38.940 --> 00:14:41.130
with a sudden surge of energy.

298
00:14:41.130 --> 00:14:44.640
Electromagnetic pulse attacks may be used as a form

299
00:14:44.640 --> 00:14:47.070
of denial of service attack to disrupt

300
00:14:47.070 --> 00:14:49.350
or disable critical systems.

301
00:14:49.350 --> 00:14:51.120
For example, an attacker

302
00:14:51.120 --> 00:14:53.640
might use an electromagnetic pulse device

303
00:14:53.640 --> 00:14:57.390
to disable a target facility's electronic security systems,

304
00:14:57.390 --> 00:15:00.000
rendering alarms and cameras inoperative,

305
00:15:00.000 --> 00:15:04.230
while simultaneously leveraging electromagnetic interference

306
00:15:04.230 --> 00:15:06.060
to interfere with the operation

307
00:15:06.060 --> 00:15:08.520
of sensitive equipment in data centers

308
00:15:08.520 --> 00:15:12.270
or communication networks leading to significant disruption

309
00:15:12.270 --> 00:15:15.960
and potential data loss across critical infrastructure.

310
00:15:15.960 --> 00:15:18.750
To finish things off, we'll take a short quiz to see

311
00:15:18.750 --> 00:15:21.330
what you learned during this section of the course,

312
00:15:21.330 --> 00:15:24.840
and we'll review each of those quiz questions fully

313
00:15:24.840 --> 00:15:28.140
to ensure you can explain why the right answers were right

314
00:15:28.140 --> 00:15:29.970
and the wrong answers were wrong.

315
00:15:29.970 --> 00:15:33.090
So let's get ready to dive into vulnerabilities

316
00:15:33.090 --> 00:15:35.553
and attacks in this section of the course.