Connection encryption
Data transmitted between the browser and server is protected in transit via TLS, including authentications, forms, and other sensitive information.
What is an SSL certificate, how HTTPS works, automatic renewal and the use of wildcard certificates for subdomains.
ZebraByte context
A TLS/SSL certificate encrypts the connection between the browser and the server and enables the use of HTTPS. The previous ZebraByte page explained the difference between free and commercial certificates, automatic renewal, and wildcard certificates; we are retaining this information in the new ZebraByte experience.
Data transmitted between the browser and server is protected in transit via TLS, including authentications, forms, and other sensitive information.
Certificates like Let's Encrypt can provide standard encryption without the cost of the certificate; commercial products may add other forms of validation or support, depending on the issuer.
Certificate expiration can disrupt normal HTTPS access. In managed infrastructure, renewal and verification can be automated.
For architectures with multiple subdomains, wildcard certificates or SAN certificates can be used, depending on the structure and requirements.
We configure redirection to HTTPS and check that there are no important resources loaded insecurely or inconsistent TLS configurations.
Inventorying certificates, terms, and domains reduces the risk of a service being left with an expired or misconfigured certificate.
Process
We identify the areas and subareas that need to be covered.
We issue or import the appropriate certificate and validate the chain.
We force HTTPS and check the service configuration.
We automate renewal and monitor expiration where infrastructure allows.
Continue