Using the latest Chrome browser, I get the following screen snapshot when I visit https//community.qualys.com/...whatever...
Why would that be regarded as obsolete and why is Chrome using it if your server allows more modern ciphers?
https//community.qualys.com does not support GCM-Siphers.
And Chrome only talk about "modern" Ciphers if the Connection is Encrypted with AES_GCM or CHACHA20_POLY1305
And of curse FS, SHA2 for both the CipherSuit and the Certificate.
Modern ciphers are AES_128_GCM and CHACHA20_POLY1305. Qualys Community supports only CBC encryption mode, it is obsolete.
Do you know the reasoning for them to support TLS1.2 but no GCM? Doesn’t make much sense to me.
This is probably Jive Software not supporting GCM.
Other communities have RC4 enabled, support ECDHE with the lowest priority and support client-initiated renegotiation. Looks like Qualys already did their best on hardening TLS configuration on the server they don't host themselves.
At least Jive’s website offers GCM with TLS 1.2. No excuses then
Retrieving data ...