Get a prompt and clear overview of your security configuration. Right now!
GOST_R3410_01
The GOST R 34.10-2001 (key exchange algorithm)[436] is a variant of Diffie-Hellman[99][100][101][102][103] key exchange based on elliptic-curve cryptography[118][119][120][121]. This algorithm creates a key encryption key (KEK) using 64 bit user key material (UKM), the sender's private key, and the recipient's public key (or the reverse of the latter pair). Key exchange method has forward secrecy[127][128][129][130], and does protect past sessions against future compromises. If long-term secret keys or passwords are compromised, encrypted communications and sessions recorded in the past cannot 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.
GOST R 34.10-94
The GOST R 34.11-94[274] is a digital signature[107][108][109][110] algorithm, part of the Russian GOST[566][567][568][569] standard, replaced by GOST R 34.10-2001[272]. 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.
Remove the cipher suite from the list of cipher suites supported by your server.
NULL
Encryption algorithm is a null encryption[360][361] that 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.
HMAC GOST R 34.11-94
The message authentication code[135][136][137][138] is a hashed message authentication code[139][140][141][142][143][144][145] where the underlaying cryptographic hash function[94][95][96][97] (GOST R 34.11-94 (hash function algorithm)[194] derives from GOST 28147-89 "imitovstavka"[195] which is considered secure[196], however it is vulnerable to collision attack[57] and to preimage attack[67] in theory. It does not provide authenticated encryption[74] which simultaneously assure the confidentiality[91][92][93] and authenticity[75][76][77] of data.
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 that encryption algorithm prefer a message authentication code[135][136][137][138] that does provide authenticated encryption[74] prefer cipher suites that are adopted and supported by a critical mass of the industry, like message authentication code[135][136][137][138] Poly1305[458][459] that proved authenticated encryption or block cipher mode of operation[82][83][84][85][86] counter with CBC-MAC[32][33][34] or Galois/Counter Mode[46][47][48][49] or which also provides authenticated encryption[74]. 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 other cryptographic hash function[94][95][96][97].
