Course contentsShow
← Security
Lesson 186 of 3,0524. Asymmetric Cryptography and PKIFree lesson

Certificate Pinning Techniques

Implementing certificate and public key pinning to prevent CA-based MITM attacks.

Certificate Pinning Techniques

What you'll learn: How to lock your application to specific certificates or public keys so attackers can't use fraudulent CA-issued certificates to intercept your traffic.


The Problem: Trusting Too Much

When your application connects to a server over TLS, it normally trusts any certificate signed by any root CA in your device's trust store. That's hundreds of CAs! If even one CA is compromised or issues a fraudulent certificate, an attacker can perform a man-in-the-middle attack and your app won't notice.

What is Certificate Pinning?

Certificate pinning means your application explicitly checks that the server's certificate (or its public key) matches a specific, pre-approved value that you've "pinned" into your code. Think of it like only accepting packages from a delivery person whose face you've memorized—no ID badge forgery will fool you.

Instead of trusting the entire CA system, you create a direct trust relationship with your server's specific certificate or key.

Two Pinning Approaches

1. Certificate Pinning: Store the exact certificate (or its hash). This pins to the entire X.509 certificate, including issuer and validity period.

  • Downside: Must update your app when certificates are rotated (typically every 1-2 years).

2. Public Key Pinning: Store just the public key from the certificate (or its hash). Since organizations often use the same key pair across certificate renewals, this survives certificate rotation.

  • Better flexibility: Works across certificate renewals as long as the key stays the same.

Implementation Pattern

You typically pin backup keys too—if your primary certificate is compromised, you can switch to a backup without releasing a new app version.

Key Takeaway: Certificate pinning prevents CA-based MITM attacks by hardcoding trust in specific certificates or public keys, bypassing the entire certificate authority trust model for your critical connections.