Use certificate pinning
Summary
Mobile applications should use certificate pinning to validate the endpoints. If a pinset is used, up to 2 certificates should be allowed.
Description
Certificate pinning establishes that the mobile application only connects to servers with valid and trusted certificates. This helps to protect against scenarios where an attacker might attempt to use a fraudulent or compromised certificate to intercept or manipulate the communication. Additionally, the application will accept connections from servers that present any of the specified certificates in the pinset.
Supported In
This requirement is verified in following services
| Plan | Supported |
|---|---|
| Essential | 🔴 |
| Advanced | 🟢 |
References
- CAPECâ„¢-94. Adversary in the middle (AiTM)
- CWEâ„¢-297. Improper validation of certificate with host mismatch
- OWASP TOP 10-A7. Identification and authentication failures
- OWASP-M TOP 10-M6. Insecure authorization
- MITRE ATT&CK®-M1040. Behavior prevention on endpoint
- CMMC-PE_L1-3_10_5. Manage physical access
- HITRUST CSF-10_c. Control of internal processing
- ISO/IEC 27002-8_1. User endpoint devices
- ISO/IEC 27002-8_26. Application security requirements
- ISA/IEC 62443-IAC-1_9. Strength of public key authentication
- ISA/IEC 62443-UC-2_3. Use control for portable and mobile devices
- PTES-7_4_2_7. Post exploitation - Pillaging (certificate authority)
- C2M2-9_3_b. Implement IT and OT asset security for cybersecurity architecture
- ISO/IEC 27001-8_1. User endpoint devices
- ISO/IEC 27001-8_26. Application security requirements
- OWASP MASVS-NETWORK-2. The app performs identity pinning for all remote endpoints under the developer's control
Vulnerabilities
Free trial
Search for vulnerabilities in your apps for free with Fluid Attacks' automated security testing! Start your 21-day free trial and discover the benefits of the Continuous Hacking Essential plan. If you prefer the Advanced plan, which includes the expertise of Fluid Attacks' hacking team, fill out this contact form.