Huw Evans's questions

I have had the following suggestion for my Servers on the insights client.

SSH security is decreased when insecure cipher or hmac is enabled in the crypto policy

The playbook remediation doesn't seem to work. Neither does the linked red hat knowledge base article. https://access.redhat.com/articles/7041246

More concerning is that I have never touched these policies, the incident reports that the systems had this issue as of 3 days ago but the 'Modified date' was 18th July 24

What happened to my servers to suddenly allow these insecure ciphers? Does this indicate a data breach? Or could it be AWS changing things?

When a browser connects to my website by entering it's FQDN the connection is encrypted using the site's SSL Certificate.

However it has come to my attention that it is possible to bypass the SSL and initiate an unencrypted connection by entering the load balancer IP Address (in which case you get an error saying it could not be encrypted).

The link below suggests that I could solve this with a redirect.

Apache reverse proxy so that SSL browser requests for IP of server are redirected to FQDN

Is this good practice or should I really be tying the certificate to the IP address in addition to the FQDN?