Certificate Pinning
Pronunciation: sur-TIF-ih-kit PIN-ning
Definition
Certificate Pinning is a client security technique that restricts a connection to an expected certificate or public key instead of trusting any certificate accepted by the normal trust store. It is used to reduce exposure to compromised or misissued certificate authorities in selected high-risk connections. It differs from standard TLS certificate validation, which relies on the platform trust store and hostname verification.
Overview
Meaning and scope
Certificate Pinning is a client security technique that restricts a connection to an expected certificate or public key instead of trusting any certificate accepted by the normal trust store. It is used to reduce exposure to compromised or misissued certificate authorities in selected high-risk connections. It differs from standard TLS certificate validation, which relies on the platform trust store and hostname verification.
Mechanism and operation
A typical implementation works as follows: The client stores one or more approved pins, validates the server certificate chain, compares the relevant key or certificate, and rejects unmatched connections. Evidence for Certificate Pinning should record the credential or certificate identifier and decision result without retaining the secret itself. The Certificate Pinning boundary should identify the principal, credential or key, permitted audience, scope, lifetime, and revocation path. Operational evidence should include application version, host, pin set version, matched key, certificate chain, failure reason, and rotation date. Certificate Pinning should be documented alongside Access Token, API Base URL, and Certificate Management.
Practical payment example
A mobile payment app restricts which server certificates it accepts and plans a safe certificate rotation to avoid accidentally blocking valid backend connections.
Operational checks
Least-privilege configuration for Certificate Pinning should be verified against the operations used by each environment and consuming service. A compromise response for Certificate Pinning should support rapid revocation, replacement, affected-client identification, and review of prior use.
Distinctions and limits
Important failure modes include certificate renewal, key rotation, backup-pin errors, interception proxies, platform differences, and stale applications. Pin only with a justified threat model, include backup pins, plan rotation and recovery, monitor failures, and never disable normal hostname and chain validation.
Related reading
Related definitions: Access Token, API Base URL.
Example
A mobile payment app restricts which server certificates it accepts and plans a safe certificate rotation to avoid accidentally blocking valid backend connections.
Comparison
It is used to reduce exposure to compromised or misissued certificate authorities in selected high-risk connections. It differs from standard TLS certificate validation, which relies on the platform trust store and hostname verification.
Key Takeaway
Pin only with a justified threat model, include backup pins, plan rotation and recovery, monitor failures, and never disable normal hostname and chain validation.
Sources
- Certificate and Public Key Pinning — OWASP (2026-08-03)
- Network Security Configuration — Android Developers (2026-08-03)
- TLS Server Certificate Management — NIST (2026-08-03)