Skip to content

Archive

Certificate Pinning

3 articles
Cybersecurity 20 Sep 2026 6 min read

TLS SPKI Pinning Needs a Rotation Path

TLS SPKI Pinning Needs a Rotation Path Certificate pinning adds a local trust constraint to the certificate checks already performed by a TLS client. Instead of accepting any certificate that satisfies the configured PKI and service-identity rules, a pinned client also requires the connection to present cryptographic material that matches a value already embedded in, provisioned to, or otherwise trusted by the client. That narrower policy can reduce exposure to certificate issuance outside the intended key set. It also creates a new operational dependency: the client must carry a valid path from the key accepted today to a key that can be used after rotation.

Cybersecurity 14 Sep 2026 7 min read

Certificate Pinning Trades Broad Trust for Operational Coupling

A mobile application can reject a perfectly valid TLS certificate even when the hostname matches, the certificate is current, and its chain terminates at a trusted public root. That rejection can be intentional. A pinning policy adds another condition: some element of the authenticated certificate chain must match identity material that the application already expects. The extra check narrows trust, but it also changes failure ownership. Normal Web PKI validation delegates a large part of certificate trust to platform root stores and certification authorities. Pinning moves part of that decision into application configuration and release management. A certificate rotation that is routine for a browser can become an outage for a pinned client.

Cybersecurity 09 Sep 2026 11 min read

Treat Certificate Pinning as a High-Cost Trust Decision

TLS normally lets a client authenticate a server through a certificate chain anchored in a trusted certificate authority. A developer may look at that broad trust model and decide to add certificate pinning: require the server to present not only a normally valid certificate, but also certificate or public-key material that the application already expects. That extra restriction can reduce risk in a narrow threat model. It can also turn an ordinary certificate or key rotation into an outage if the application has no usable replacement pin. For many applications, especially ordinary websites, the operational risk is not justified.