All HTTP traffic is encrypted through secured SSL/TLS protocols (e.g. https). Connections between the client and our load balancing proxies are secured through different CAs. Internal connections are secured by an internal certification authority.
Client: On the client-side, we ensure security through enforcing of different HTTP headers like the content security policy, expect certificate transparency, referrer policy, strict transport security, XSS protection, frame options, content type options and more. Look at our more up-to-date report.
SSL/TLS: On the server-side, SSL certificates are used and enforced on the client-server-side, but also on the server-server-side at the backend. On the client-server-side, we are enforcing standards like TLSv1.2+, different cyphers, strong keys, certificate transparency, DNS CAA records, OCSP stapling and more. Again, you can find a more up-to-date report here.
Client: On the client-side, we ensure security through enforcing of different HTTP headers like the content security policy, expect certificate transparency, referrer policy, strict transport security, XSS protection, frame options, content type options and more. Look at our more up-to-date report.
SSL/TLS: On the server-side, SSL certificates are used and enforced on the client-server-side, but also on the server-server-side at the backend. On the client-server-side, we are enforcing standards like TLSv1.2+, different cyphers, strong keys, certificate transparency, DNS CAA records, OCSP stapling and more. Again, you can find a more up-to-date report here.
Comments
0 comments
Please sign in to leave a comment.