One of the most common problems that our teams deal with ensuring that SSL certificates are working correctly. We’ve all had that urgent call in telling us that the web site is down or some key API or authentication function is offline – only to find out it was caused by an expired certificate.
An easy way of preventing this situation would have been to set up a task that continuously tests your SSL endpoints (internal and external web apps and sites, REST API’s etc.) and warns us if:
- The certificate is about to expire (with x days).
- The SSL endpoint is using safe SSL protocols (e.g. TLS 1.2).
- The certificate is using SHA256.
View original post 606 more words