Knowledge Base

C

Cipher Suite: TLS_­PSK_­WITH_­CAMELLIA_­256_­GCM_­SHA384

Summary

code:
(0xc0, 0x8f)
IANA Name:
TLS_PSK_WITH_CAMELLIA_256_GCM_SHA384

Check your host!

Type a URL to analyze a service

Get a prompt and clear overview of your security configuration. Right now!

Components

C
Key Exchange Method
Name
Pre-shared Key (PKS)
Security
The pre-shared key[124] key exchange[467] algorithms provide secure communication by establishing the key exchange based on symmetric key[193][194][195]s that are shared in advance among the communicating parties. Algorithm is especially suitable for performance-constrained environments, but there are weaknesses[481][482][483]. Pre-shared keys must be long and random to be secure. Pre-shared keys with low entropy[380], may caused by a weakness [359][360][361] of random number generator[1][2][3], can be easily broken in brute-force attack[555]. PSK key exchange has no forward secrecy[135][136][137][138], and does not protect past sessions against future compromises. If long-term secret keys or passwords are compromised, encrypted communications and sessions recorded in the past can be retrieved and decrypted. Leading client applications do not use this algorithm. Unless your application or requirements specifically call for their use, it is generally safer to avoid cipher suites that are not adopted and supported by a critical mass of the industry.
Recommendations
Always prefer cipher suites with PFS property over the non-PFS ones. If your application or requirements specifically call for the use of algorithms which are not used by the leading client applications set the cipher suite order explicitly and cipher suites used by the leading client applications be preferred over the ones which do not used by them.
C
Authentication Method
Name
Pre-shared Key (PKS)
Security
The pre-shared key[124] can ensure authenticity[201][202][203] of the communicating parties mutually based on symmetric key[193][194][195]s that are shared in advance among the parties. Combined with a key exchange[467] that has forward secrecy[135][136][137][138] property algorithm can protect against dictionary attack[504][505]s by passive eavesdroppers (but not active attackers). Pre-shared keys with low entropy[380], may caused by a weakness[359][360][361] of random number generator[1][2][3], can be easily broken in brute-force attack[555]. Leading client applications do not use this algorithm. Unless your application or requirements specifically call for their use, it is generally safer to avoid cipher suites that are not adopted and supported by a critical mass of the industry.
Recommendations
If your application or requirements specifically call for the use of algorithms which are not used by the leading client applications set the cipher suite order explicitly and cipher suites used by the leading client applications be preferred over the ones which do not used by them.
B
Encryption Type
Name
Camellia-256
Security
Encryption algorithm Camellia[17][18][19][20] is a block cipher[524][525][526][527] which is considered secure[342][343], but leading client applications do not use this algorithm. Unless your application or requirements specifically call for their use, it is generally safer to avoid cipher suites that are not adopted and supported by a critical mass of the industry.
Recommendations
Remove the cipher suite from the list of cipher suites supported by your server.
A+
Encryption Mode
Name
Galois/Counter Mode (GCM)
Security
block cipher mode of operation[293][294][295][296][297] Galois/Counter Mode[65][66][67][68] is considered secure. It provides authenticated encryption[563] which simultaneously assure the confidentiality[198][199][200] and authenticity[201][202][203] of data.
Recommendations
If your application or requirements specifically call for the use of a message authentication code[128][129][130][131] that does not provide authenticated encryption[563] prefer block cipher mode of operation[293][294][295][296][297] (eg: counter with CBC-MAC[266][267][268], Galois/Counter Mode[65][66][67][68] or message authentication code[128][129][130][131] (eg: Poly1305[289][290]) that proved authenticated encryption over the ones which does not provide it.
A+
Encryption Key Size
Name
256
Security
The symmetric key[193][194][195] withkey size[438] more than 128 bits as it is should be according to National Institute of Standards and Technology[428][429] so it is not vulnerable to preimage attack[215] and it cannreliably prove that message came from the stated sender (its authenticity) and has not been changed, so connection is not open for a man-in-the-middle attack[414].
Recommendations
Remove the cipher suite from the list of cipher suites supported by your server.
A+
Encryption Block Size
Name
128
Security
The block cipher[524][525][526][527] uses a block size[409] larger than 64 bits, so it is not vulnerable to sweet32 attack[496][497][498][499].
Recommendations
A+
Message Authentication Code
Name
SHA2-384
Security
message authentication code[128][129][130][131] is a hashed message authentication code[418][419][420][421][422][423][424] which is considered secure. The underlaying cryptographic hash function[510][511][512][513] (Secure Hash Algorithm 2[71][72][73]) is also considered secure.
Recommendations
If your application or requirements specifically call for the use of a message authentication code[128][129][130][131] that does not provide authenticated encryption[563] prefer block cipher mode of operation[293][294][295][296][297] (eg: counter with CBC-MAC[266][267][268], Galois/Counter Mode[65][66][67][68] or message authentication code[128][129][130][131] (eg: Poly1305[289][290]) that proved authenticated encryption over the ones which does not provide it. In case of a hashed message authentication code[418][419][420][421][422][423][424] prefer message authentication code[128][129][130][131] based on Secure Hash Algorithm 2[71][72][73] over the ones based on Secure Hash Algorithm 1[204][205][206].