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.
RC4-128
Encryption algorithm Rivest Cipher 4[370][371][372][373] is a stream cipher[182][183] that is more malleable[134] than a block cipher[78][79][80][81]. It has multiple vulnerabilities[375][376][377][378][379] (eg: related-key attack[68], distinguishing attack[60], ...), so attacker can apply statistical analysis against it to recover the encrypted text.
Remove the cipher suite from the list of cipher suites supported by your server.
128
The symmetric key[185][186][187] withkey size[184] more than 128 bits as it is should be according to National Institute of Standards and Technology[470][471] so it is not vulnerable to preimage attack[67] 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[61].
Remove the cipher suite from the list of cipher suites supported by your server.
SHA-1
message authentication code[135][136][137][138] is a hashed message authentication code[139][140][141][142][143][144][145] which is considered secure[462], despite the fact that the underlayingcryptographic hash function[94][95][96][97] (Secure Hash Algorithm 1[202][203][204]) is considered insecure[205][206][207][208][209][210][211].
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 Secure Hash Algorithm 1[202][203][204].
