Q: Your mobile application uses HTTPS to securely communicate with its backend. However, a security researcher installs a custom root CA on their phone, proxies the traffic through a tool like Burp Suite, and successfully intercepts the plaintext API calls. What security control is the mobile app missing?
By default, mobile OS environments and browsers unconditionally trust any certificate signed by a Root CA located in their system trust store.
Master cloud-native security and container runtime defense: Prepare with KodeKloud's CKS course with live browser-based terminal sandboxes.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "When an interviewer asks how I respond to this security vulnerability, I emphasize immediate blast-radius containment. The interviewer is testing: Certificate Pinning, mobile app security, MITM proxies.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Production Solution & Architecture
By default, mobile OS environments and browsers unconditionally trust any certificate signed by a Root CA located in their system trust store. Because the researcher installed their own malicious Root CA into the phone's trust store, the app blindly accepts the proxy's forged certificates, allowing the MITM attack. To prevent this, the mobile application must implement Certificate Pinning (or Public Key Pinning). The app's source code is hardcoded ("pinned") to only trust the specific cryptographic hash of the backend server's true certificate (or its true CA). When the proxy presents its forged certificate, even if it's considered "valid" by the phone's OS, the application logic will instantly reject the connection because the hash does not match the hardcoded pin.
- Immediate Triage: By default, mobile OS environments and browsers unconditionally trust any certificate signed by
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Revoking compromised credentials immediately without analyzing forensic audit trails for active exploitation when configuring Security mobile application Deactivating a compromised access key prevents abuse while preserving forensic identity for CloudTrail investigations to assess blast radius.
- Terminating compromised instances immediately during incident triage without isolating volatile RAM state when configuring Security mobile application Terminating compromised instances immediately destroys volatile memory evidence (RAM dumps) required to establish intrusion timelines.
-
Injecting plaintext secrets into container environment variables rather than fetching from dynamic secret vaults when configuring Security mobile application
Container environment variables are visible via
docker inspector Kubernetes API queries, leaking sensitive API tokens to developers. - Failing to enforce automated credential rotation for third-party SaaS integration tokens when configuring Security mobile application Static long-lived API tokens shared across internal services represent the highest-probability vector for supply-chain credential compromise.