Which of the following is NOT a security requirement unique to mobile applications?

Checking source code for programmatic and stylistic errors using tools like linters is a universal software development best practice for maintaining code quality and consistency. It is not a security requirement that is unique to mobile applications; it applies equally to web, desktop, and backend development. In contrast, securing on-device secrets for backend calls, designing for operation on untrusted public networks, and preventing data leakage between sandboxed applications are all security challenges that are particularly prominent and specific to the mobile application environment.

B. Securely storing secrets (e.g., API keys, tokens) on a user-controlled device is a critical and specific challenge for mobile security.
C. Mobile applications are inherently designed to run outside a secure corporate perimeter on untrusted networks, a primary security design constraint.
D. Preventing data leakage between applications through mechanisms like insecure storage or clipboard access is a core security concern for mobile OS platforms.

1. OWASP. (2016). Mobile Top 10 Security Risks. M1: Improper Platform Usage, M2: Insecure Data Storage, M4: Insecure Authentication. These risks highlight security concerns specific to the mobile context, such as handling secrets, data, and network connections on the device. Checking for stylistic errors is a general coding standard, not a unique mobile security risk.

2. Enck, W. (2014). CSC 495/591: Mobile and Cloud Security. North Carolina State University. Lecture 2: Android Security Architecture. Discusses application sandboxing and inter-component communication as a core, mobile-specific security design.