Get a prompt and clear overview of your security configuration. Right now!
KRB5 (Kerberos V5)
A Kerberos[215][216][217][218][219][220][221] cipher suite[189][190]s provide secure communication where the authentication and the establishment of a master secret will be done using the client's Kerberos credentials while client and server are mutually authenticated. The Kerberos protocol is considered secure, however it's authentication model is vulnerable to brute-force attack[54] against the key distribution center[132] and there are some protocol specific attacks [222][223]. 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.
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.
KRB5
A Kerberos[215][216][217][218][219][220][221] cipher suite[189][190]s provide secure communication where the authentication and the establishment of a master secret will be done using the client's Kerberos credentials while client and server are mutually authenticated. The Kerberos protocol is considered secure, however it's authentication model is vulnerable to brute-force attack[54] against the key distribution center[132] and there are some protocol specific attacks [222][223]. 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.
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.
DES
Encryption algorithm Data Encryption Standard[333][334][335][336][337] is considered obsolete[338][339][340][341][342][343]. It is weakened against brute-force attack[54]. It cannot provide confidentiality[91][92][93], so connection is available or disclosed to unauthorized individuals, entities, or processes.
Remove the cipher suite from the list of cipher suites supported by your server.
CBC
Encryption mode is cipher block chaining[28][29][30]. It is vulnerable[31] to timing attack[188] (eg: Lucky Thirteen attack[11][12]) and padding oracle attack[63][64][65][66] (eg: POODLE attack[13][14][15]).
Remove the cipher suite from the list of cipher suites supported by your server or at least set the cipher suite order explicitly and any cipher suite modes be preferred over ciphers suites with CBC modes.
56
Any symmetric key[185][186][187] with key size[184] less than 128 bits are disallowed by National Institute of Standards and Technology[470][471] as it is vulnerable to preimage attack[67] in theory. It cannot reliably prove that message came from the stated sender (its authenticity) and has not been changed, so connection is open for a man-in-the-middle attack[61].
Remove the cipher suite from the list of cipher suites supported by your server.
64
Any block cipher[78][79][80][81] uses a block size[87] of 64 bits is vulnerable to sweet32 attack[22][23][24][25].
Remove the cipher suite from the list of cipher suites supported by your server, or setup yout server to enforce changing session key regularly (rekeying[174]).
MD5
message authentication code[135][136][137][138] is a hashed message authentication code[139][140][141][142][143][144][145] which is considered secure[456][457], despite the fact that the underlaying cryptographic hash function[94][95][96][97] (MD5[197][198][199]) is considered insecure[200][201] as it vulnerable to collision attack[57] in practice and to preimage attack[67] in theory.
Leading client applications do not use this type of message authentication code[135][136][137][138]. 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. If your application or requirements specifically call for the use of a message authentication code[135][136][137][138] that does not provide authenticated encryption[74] prefer block cipher mode of operation[82][83][84][85][86] (eg: counter with CBC-MAC[32][33][34], Galois/Counter Mode[46][47][48][49] or message authentication code[135][136][137][138] (eg: Poly1305[458][459]) that proved authenticated encryption over the ones which does not provide it. In case of a hashed message authentication code[139][140][141][142][143][144][145] prefer message authentication code[135][136][137][138] based on Secure Hash Algorithm 2[212][213][214] over the ones based on MD5[197][198][199].
