A vulnerability scanner report shows that a client-server host monitoring solution operating in the credit card corporate environment is managing SSL sessions with a weak algorithm which does not…

Question

Options

• AThe X509 V3 certificate was issued by a non trusted public CA.
• BThe client-server handshake could not negotiate strong ciphers.
• CThe client-server handshake is configured with a wrong priority.
• DThe client-server handshake is based on TLS authentication.
• EThe X509 V3 certificate is expired.
• FThe client-server implements client-server mutual authentication with different certificates.

• A
  18% (4)
• B
  45% (10)
• D
  5% (1)
• E
  27% (6)
• F
  5% (1)

Explanation

The client-server handshake could not negotiate strong ciphers. This means that the system is not configured to support the strong ciphers provided by later versions of the SSL protocol. For example, if the system is configured to support only SSL version 1.1, then only a weak cipher will The client-server handshake is configured with a wrong priority. The client sends a list of SSL versions it supports and priority should be given to the highest version it supports. For example, if the client supports SSL versions 1.1, 2 and 3, then the server should use version 3. If the priority is not configured correctly (if it uses the lowest version) then version 1.1 with its weak algorithm

No community discussion yet for this question.