CyberKit

Certificate Pinning

Also called Pinning, HPKP.

Hardcoding a known certificate or key so others are rejected.

What it is

A technique where an application is configured to accept only a specific certificate or public key for a server, rather than any certificate that chains to a trusted CA. Anything else is refused, even if otherwise valid.

Why it matters

Pinning defends against rogue or compromised CAs and man-in-the-middle interception, which is why malware analysts often must defeat it to inspect an app's encrypted C2 traffic.

In practice

A mobile app refusing to connect through a proxy because the intercepting certificate does not match its pinned key.

What to look for

  • Apps that fail only on corporate networks with TLS inspection.
  • Pinned keys with no backup pin.
  • Pinning bypass tools on mobile devices under test.

Common mistake

Pinning without a backup key. One rotation can lock every user out.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Burp Suite Commercial

    An intercepting proxy for testing web apps by hand and with its scanner.

  • ZAP Open source

    An open source web app scanner and proxy, often run in CI pipelines.

  • Cloudflare WAF Commercial

    Blocks common web attacks at the edge while the code gets fixed.

Read next

Sources