From the course: CompTIA Security+ (SY0-701) Cert Prep
3DES
- [Instructor] When researchers discovered attacks on DES that rendered the decades-old algorithm insecure, security professionals faced a dilemma. They had tons of old equipment designed to work with DES, but they weren't able to rely on that equipment's security. While the government worked to adopt the new advanced encryption standard, which I'll cover in the next video, practical security professionals around the world discovered a workaround. By using the DES algorithm on the same text multiple times, they could achieve greater security. Specifically, three rounds of DES encryption produces much stronger security than existed with standard DES. They called this approach Triple DES, sometimes written as 3DES. Here's how Triple DES works. The person encrypting a message feeds it into the DES algorithm using the first DES key, K1. This produces cipher text encrypted with the standard data encryption standard algorithm. The center then takes this output and feeds it into the DES algorithm again, this time using key two, producing a second cipher text that is double encrypted. The center then takes this final output and feeds it into DES a third time with a third key, producing the final Triple DES encrypted message. The recipient then reverses this process, feeding the message through the decryption function in the reverse order, with key three, key two, and key one. There are three different keying options for Triple DES. In the first option, key one, key two, and key three are different from each other. This is the strongest approach and it results in encryption with an effective key strength of 112 bits. In the second option, keys one and three are the same. This requires fewer keys, but it reduces the strength of the algorithm to 80 bits. And in the final option, all three keys are the same. This emulates the standard DES algorithm, and it's just as insecure as the standard approach. It's included for backwards compatibility with DES, but it is definitely not a good option. At this point, you might be asking yourself the question, why Triple DES? Why not just use DES twice? The answer is that using the algorithm twice is subject to an attack known as a meet-in-the-middle attack that makes it no more secure than the standard DES algorithm. Recent research in cryptography discovered new flaws in Triple DES that weaken the algorithm's security. For this reason, the federal government no longer recommends the use of Triple DES and is phasing it out for government applications. Here are some of the key facts that you should know about Triple DES. Like des, it's a symmetric encryption algorithm and a block cipher that works on 64-bit blocks. When used with three keys, Triple DES has an effective key length of 112 bits, but weaknesses in the algorithm now mean that it's being phased out.
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.
Contents
-
-
The goals of information security2m 11s
-
Authentication, authorization, and accounting (AAA)3m 31s
-
Categorizing security controls5m 11s
-
Conducting a gap analysis2m 34s
-
Zero Trust5m 32s
-
Physical access control4m 40s
-
Physical security personnel2m 12s
-
Deception technologies2m 55s
-
Change management6m 2s
-
-
-
Trust models2m 52s
-
PKI and digital certificates4m 5s
-
Hash functions7m 38s
-
Digital signatures3m 50s
-
Digital signature standard1m 27s
-
Create a digital certificate4m 55s
-
Revoke a digital certificate1m 28s
-
Certificate stapling2m 29s
-
Certificate authorities6m 13s
-
Certificate subjects3m 35s
-
Certificate types2m 55s
-
Certificate formats2m 30s
-
-
-
Preventing SQL injection4m 25s
-
Understanding cross-site scripting3m 17s
-
Request forgery4m 8s
-
Overflow attacks3m 21s
-
Explaining cookies and attachments4m 7s
-
Session hijacking4m 8s
-
Code execution attacks2m 43s
-
Privilege escalation1m 56s
-
OWASP Top Ten4m 45s
-
Application security4m 3s
-
Defending against directory traversal3m 4s
-
Race condition vulnerabilities2m 13s
-
-
-
Restricting network access2m 8s
-
Network access control4m 30s
-
Router configuration security4m 5s
-
Switch configuration security3m 42s
-
Maintaining network availability2m 32s
-
Network monitoring3m 41s
-
SNMP2m 54s
-
Isolating sensitive systems2m
-
Zero trust networking4m 9s
-
Secure access service edge (SASE)3m 50s
-
-
-
Operating system security8m 44s
-
Malware prevention7m 25s
-
Application management3m 46s
-
Host-based network security controls7m 44s
-
File integrity monitoring4m 9s
-
Data loss prevention5m 17s
-
Data encryption5m 39s
-
Hardware and firmware security5m 24s
-
Linux file permissions4m 2s
-
Web content filtering1m 47s
-
-
-
What is vulnerability management?5m 2s
-
Identify scan targets4m 24s
-
Scan configuration5m 20s
-
Scan perspective4m 24s
-
Security Content Automation Protocol (SCAP)2m 27s
-
Common Vulnerability Scoring System (CVSS )3m 31s
-
Analyzing scan reports4m 37s
-
Correlating scan results2m 20s
-
Vulnerability response and remediation2m 14s
-
-
-
Authentication factors3m 26s
-
Multifactor authentication2m 17s
-
Something you have4m 24s
-
Password policy4m 19s
-
Password managers2m 3s
-
Passwordless authentication3m 23s
-
Single sign-on and federation3m 9s
-
Kerberos and LDAP5m 18s
-
SAML2m 35s
-
OAUTH and OpenID Connect2m 55s
-
Certificate-based authentication5m 25s
-