CAS-005 · Question #66
A security analyst received a report that an internal web page is down after a company-wide update to the web browser. Given the following error message: Your connection is not private…
The correct answer is D. Discontinuing the use of self-signed certificates. The error NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM indicates the site’s certificate uses a deprecated/weak signing algorithm (commonly SHA-1). Modern browsers reject these. The practical fix is to replace the certificate with one signed using a modern algorithm (e.g., SHA- 256)…
Question
A security analyst received a report that an internal web page is down after a company-wide update to the web browser. Given the following error message:
Your connection is not private. internalwebsite.company.com. NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM Which of the following is the best way to fix this issue?
Options
- ARewriting any legacy web functions
- BDisabling all deprecated ciphers
- CBlocking all non-essential pons
- DDiscontinuing the use of self-signed certificates
How the community answered
(52 responses)- A13% (7)
- B4% (2)
- C10% (5)
- D73% (38)
Explanation
The error NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM indicates the site’s certificate uses a deprecated/weak signing algorithm (commonly SHA-1). Modern browsers reject these. The practical fix is to replace the certificate with one signed using a modern algorithm (e.g., SHA- 256) by a trusted CA (internal PKI or public). Moving away from self-signed certs ensures a valid trust chain and modern signatures.
Community Discussion
No community discussion yet for this question.