Pinning adds restrictions for some threat models but can complicate certificate changes and availability. It is not an automatic requirement for every application.
Evaluation approach
Assess threats, operational capacity and current platform guidance. Pinning must not weaken ordinary TLS validation.
Application example
Test planned key transitions with older financial-app versions. Define how connectivity is maintained before users update.
Limits and considerations
Pinning is not an absolute defense against an attacker controlling the client.
What belongs in the decision record?
Record the rationale, covered endpoints and certificate-change owner. Requirements can evolve; do not embed permanent client assumptions without a migration plan.
Checks and decisions
- Justify the requirement
- Test key transitions
- Prepare recovery
Sources
The primary references above provide the technical basis. Example workflows and evaluation suggestions are this publication’s explanations, not independent test results for a particular product.