Mobile App MitM Prevention via Encryption
As the chief security officer at SecureMobile, you are overseeing the development of a mobile banking application. You are aware of the potential risks of man-in-the-middle (MitM) attacks where an attacker might intercept communication between the app and the bank's servers. Recently, you have learned about a technique used by attackers where they use rogue Wi-Fi hotspots to conduct MitM attacks. To prevent this type of attack, you plan to implement a security feature in the mobile app. What should this feature accomplish?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The core concept tested is how application-level security controls mitigate network-layer threats, specifically identifying that enforcing encryption prevents data interception even if the underlying network is compromised.
This question addresses Man-in-the-Middle (MitM) attack prevention in mobile banking applications by enforcing network encryption standards. It establishes that requiring encrypted connections is the primary defense against interception on public or rogue Wi-Fi networks.
Many candidates incorrectly choose Option B, believing the app should detect and block rogue access points. However, standard mobile operating systems and apps generally lack the capability to reliably distinguish between legitimate and rogue APs based solely on SSID or signal strength, making this an impractical requirement for a general feature.
Community Discussion (9 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Correct answer: C — The feature must prevent the app from connecting to any unencrypted Wi-Fi networks. By enforcing encryption (such as TLS/SSL), the application ensures that data transmitted over the network is protected from eavesdropping, regardless of whether the user is on a rogue hotspot or a legitimate but insecure network. This is the most reliable and standard method for mitigating MitM risks at the application layer.Why the Other Options Are Wrong
Option A (Two-factor authentication) secures the account but does not protect the confidentiality of data in transit. Option B (Detecting rogue APs) is technically flawed because apps cannot reliably identify rogue APs; attackers can clone SSIDs and credentials, making detection nearly impossible without advanced enterprise-grade solutions not implied here. Option D (Password rotation) is a policy control unrelated to network security or traffic interception.Community Comment Notes
Community consensus heavily favors Option C, with users noting that preventing connections to open/unencrypted networks is the practical way to stop MitM attacks on Wi-Fi. Some dissenting voices argue for Option B, claiming that detecting rogue APs is necessary, but this is often rebutted by the fact that apps cannot inherently trust the network infrastructure's identity without cryptographic verification. One commenter noted, "The app itself can not detect a rouge AP but can force an encryption to run," highlighting the technical limitation of Option B.Exam Strategy
When dealing with MitM questions, always look for encryption (TLS, SSL, IPsec) as the primary defense. Distinguish between authentication (who you are) and confidentiality (keeping data secret); encryption provides the latter.
Frequently Asked Questions
Why can't the app just detect rogue Wi-Fi hotspots?
Apps cannot reliably distinguish rogue APs from legitimate ones because attackers can mimic SSIDs and passwords. Encryption is the only consistent protection.
Does two-factor authentication stop MitM attacks?
No. 2FA secures login credentials but does not encrypt the data stream. An attacker can still intercept sensitive information sent after login.