TechKnowSurge
CompTIA Security+ 1.4 CompTIA SecurityX 2.3 ISC2 CISSP 4.3 NIST 800-53 SC-8 CompTIA SecurityX 3.4 ISC2 CISSP 3.6 EC-Council CEH 9.1
VideoSecurityFree

Cipher Suites

Cipher suites are preconfigured sets of cryptographic parameters that allow two devices to negotiate a common method for securing communications. They define the algorithms used for encryption, key exchange, authentication, and data integrity.

Complete this video to capture a CTF flag worth 1 point.

About this video

Secure communication between two devices requires agreement on several cryptographic parameters before any protected data can be exchanged. Rather than negotiating each parameter individually, the TLS protocol uses cipher suites, which are preconfigured bundles that define all the necessary components of a secure session in a single, standardized name. Each suite specifies a symmetric encryption algorithm and key length for protecting session data, an operating mode such as GCM, a key exchange method for establishing shared secrets, an authentication algorithm for verifying identity, and a hashing algorithm for integrity checks. Common choices for these components include Diffie-Hellman or RSA for key exchange, AES-256-GCM for session encryption, and SHA-256 or SHA-384 for integrity verification. The negotiation process begins when a client connects to a server and sends a list of all cipher suites it is capable of supporting. The server compares that list against its own supported configurations and selects the strongest option the two have in common, then communicates that choice back to the client. A real-world packet capture of this exchange would show the client advertising multiple suites, each one encoding a complete set of cryptographic preferences in a compact identifier. The server's selection from that list determines the exact algorithms that will protect every byte of application data sent during the session. Cipher suite support is not static. As cryptographic research advances and weaknesses are identified, specific suites are deprecated and removed from use. TLS 1.3, for example, dropped support for a number of older algorithms, including Triple DES, which no longer meets modern security standards. Staying current with which suites are considered secure and which have been retired is a practical concern for anyone configuring or auditing systems that handle encrypted communications.

What you'll learn

What's covered

Cipher Suites

Aligned to

CompTIA Security+
1.4 Explain the importance of using appropriate cryptographic solutions.
CompTIA SecurityX
2.3 Given a scenario, implement appropriate cryptographic protocols and algorithms.
3.4 Given a scenario, implement the appropriate cryptographic protocols and algorithms.
ISC2 CISSP
4.3 Implement secure communication channels according to design.
3.6 Select and determine cryptographic solutions.
NIST 800-53
SC-8 Transmission Confidentiality and Integrity
EC-Council CEH
9.1 Cryptography

Key terms

Transport Layer Security
TLS
A cryptographic protocol that provides secure communication over a network, successor to SSL.
Cipher
An algorithm used to encrypt and decrypt data.
Symmetric Encryption
An encryption method that uses the same key for both encryption and decryption.
Key Exchange
A method used to securely share cryptographic keys between parties over an insecure channel.
Authentication
The process of verifying the identity of a user, device, or system.
Hash Function
A mathematical algorithm that converts input data of any size into a fixed-size output value used to verify data integrity.
Advanced Encryption Standard
AES
A symmetric encryption algorithm widely used to secure data, supporting key sizes of 128, 192, and 256 bits.
RSA
An asymmetric encryption algorithm based on the difficulty of factoring large prime numbers, widely used for secure data transmission.
Cipher Suite
A preconfigured set of algorithms specifying the symmetric cipher, key length, mode of operation, hashing algorithm, and key exchange method used to secure TLS communication.

Topics

Cipher Suites Tls Cryptography Key Exchange Encryption Algorithms Data Integrity

Transcript

When two devices are communicating back and forth, there's a lot of different ways they can set up secure communication. There's a lot of different ways they can encrypt data, there's different ciphers out there, there's different key lengths, there's also different modes of encryption. When it comes to the integrity piece, there's different hashing algorithms, and when it comes to the key exchange, there's different ways they can exchange the keys. Not all devices have the same capabilities, so how do we establish a common set of capabilities? Well, we do that through cipher suites.

What Is a Cipher Suite

In TLS, the bulk of our communication is going to be encrypted, and it's going to be encrypted with this application data for the content type. So in this example right here, we're using the cipher AES, we're using a key length of 256, and we're using the mode of GCM. For our integrity piece we're using SHA-256. But there are a lot of different combinations that we have out there, and that's where our cipher suite comes into play. When two devices are talking back and forth, they're going to decide on some of the parameters of how they're going to secure the communication, and they do that through the use of cipher suites.

Parameters and Options

Here are some of the parameters that need to be established. One of those is going to be our encryption, and specifically it's going to be our symmetrical encryption. We may use asymmetrical encryption for things like key exchange, but the problem is that's very resource intensive and very slow, and so we'll want to transition to start using symmetrical encryption. That's what this specifies right here. We're going to choose a cipher to use, there's going to be a key size, and there's going to be a mode for that. We also want that integrity check, so then we have our hashing algorithm. Here we have the key exchange, like I mentioned, and then we also have that authentication piece.

There are a lot of different options that we can choose. For instance, with the key exchange maybe we choose one of the Diffie-Hellman, or maybe it's going to be RSA, or maybe it's going to be Pass key. For the authentication piece maybe we choose something like RSA. For the session cipher maybe we choose AES 256 with GCM, and then for the hashing algorithm perhaps we're going to choose SHA-384 or 256. So we're going to choose different options with this.

What cipher suites are is preconfigured sets of these options. For instance, we may have a Diffie-Hellman with RSA, AES 256 GCM and SHA-256 is going to be one of our cipher suites that we can choose. So it's a preconfigured set of these options.

Client and Server Negotiation

What the client will do is it will send a list of the cipher suites that the client can support. So now the server has all the cipher suites that the client can handle, and the server is going to match that up with its own set of capabilities and choose probably the best, most secure way of communicating, and then communicate that back to the client and say, this is how we're going to communicate, this is the cipher suite that we're going to use.

Here's a packet that was captured going from a client to a server, and the client's telling the server what its capabilities are. So we see in here the different cipher suites it will support, a total of 16 suites, and we can see a list of them right here. If we want to look more deeply, let's just take a look at this one right here. This one right here is saying that it is capable of supporting, for a key exchange, the Diffie-Hellman. It's capable, for the authenticity or authentication piece, it supports RSA. It will use AES 256 GCM for that session cipher and encryption, and then for the integrity piece it's going to use the hashing algorithm of SHA-384.

Cipher Suites Change Over Time

One of the things that happens over time is that these cipher suites will change. They will discontinue the use of them because there's found some sort of security issues, or it has some sort of security concerns. So TLS 1.3 doesn't have all support for a lot of the different ciphers. As an example, Triple DES is one of those things that it's not going to support, because it's not considered one of the more secure methods of communication.

About TechKnowSurge

TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.

Explore free tools and programs →