Other popular blogs
OWASP (Open Web Application Security Project) Foundation is an community focused in security testing standards. OWASP Mobile specification is focused on mobile testing standards. Though OWASP is focused on testing, Developer's need not be aware of these test cases and their respective development aspects. This article provides basic tips to each security requirement in OWASP Mobile checklist.
V1
|
Architecture, design and threat modelling
|
|
Security Requirement
|
Development tips
|
|
1.1
|
Verify all application components are identified and are known to be needed.
|
|
1.2
|
Verify all third party components used by the mobile app, such as libraries and frameworks, are identified, and checked for known vulnerabilities.
|
|
1.3
|
Verify that security controls are never enforced only on the client side, but on the respective remote endpoints.
|
|
1.4
|
Verify that a high-level architecture for the mobile app and all connected remote services has been defined and security has been addressed in that architecture.
|
|
1.5
|
Verify that data considered sensitive in the context of the mobile app is clearly identified.
|
|
1.6
|
Verify all app components are defined in terms of the business functions and/or security functions they provide.
|
|
1.7
|
Verify that a threat model for the mobile app and the associated remote services, which identifies potential threats and countermeasures, has been produced.
|
|
1.8
|
Verify all third party components have been assessed (associated risks) before being used or implemented. Additionally verify that a process is in place to ensure that each time a security update for a third party component is published, the change is inspected and the risk evaluated.
|
|
1.9
|
Verify that all security controls have a centralized implementation.
|
|
1.10
|
Verify that all components that are not part of the application but that the application relies on to operate, are clearly identified and the security implications of using those components are known.
|
|
1.11
|
Verify that there is an explicit policy for how cryptographic keys (if any) are managed, and the lifecycle of cryptographic keys is enforced. Ideally, follow a key management standard such as NIST SP 800-57.
|
|
1.12
|
Verify that remote endoints ensure that connecting clients use the current version of the mobile app.
|
|
1.13
|
Verify that security testing is performed as part of the development lifecycle. If some or all of the testing is automated, the configuration of the testing tools must be tailored to the specific app.
|
|
V2
|
Data Storage and Privacy
|
|
2.1
|
Verify that system credential storage facilities are used appropriately to store sensitive data, such as user credentials or cryptographic keys.
|
|
2.2
|
Verify that no sensitive data is written to application logs.
|
|
2.3
|
Verify that no sensitive data is shared with third parties unless it is a necessary part of the architecture.
|
|
2.4
|
Verify that the keyboard cache is disabled on text inputs that process sensitive data.
|
|
2.5
|
Verify that the clipboard is deactivated on text fields that may contain sensitive data.
|
|
2.6
|
Verify that no sensitive data is exposed via IPC mechanisms.
|
|
2.7
|
Verify that no sensitive data, such as passwords and credit card numbers, is exposed through the user interface or leaks to screenshots.
|
|
2.8
|
Verify that no sensitive data is included in backups.
|
|
2.9
|
Verify that the app removes sensitive data from views when backgrounded.
|
|
2.10
|
Verify that the app does not hold sensitive data in memory longer than necessary, and memory is cleared explicitly after use.
|
|
2.11
|
Verify that the app enforces a minimum device-access-security policy, such as requiring the user to set a device passcode.
|
|
2.12
|
Verify that the app educates the user about the types of personally identifiable information processed, as well as security best practices the user should follow in using the app.
|
|
V3
|
Cryptography
|
|
3.1
|
Verify that the app does not rely on symmetric cryptography with hardcoded keys as a sole method of encryption.
|
|
3.2
|
Verify that the app uses proven implementations of cryptographic primitives.
|
|
3.3
|
Verify that the app uses cryptographic primitives that are appropriate for the particular use-case, configured with parameters that adhere to industry best practices.
|
|
3.4
|
Verify that the app does not use cryptographic protocols or algorithms that are widely considered depreciated for security purposes.
|
|
3.5
|
Verify that the app doesn't re-use the same cryptographic key for multiple purposes.
|
|
3.6
|
Verify that all random values are generated using a sufficiently secure random number generator.
|
|
V4
|
Authentication and Session Management
|
|
4.1
|
Verify that if the app provides users with access to a remote service, an acceptable form of authentication such as username/password authentication is performed at the remote endpoint.
|
|
4.2
|
Verify that the remote endpoint uses randomly generated access tokens to authenticate client requests without sending the user's credentials.
|
|
4.3
|
Verify that the remote endpoint terminates the existing session when the user logs out.
|
|
4.4
|
Verify that a password policy exists and is enforced at the remote endpoint.
|
|
4.5
|
Verify that the remote endpoint implements an exponential back-off, or temporarily locks the user account, when incorrect authentication credentials are submitted an excessive number of times.
|
|
4.6
|
Verify that biometric authentication, if any, is not event-bound (i.e. using an API that simply returns "true" or "false"). Instead, it is based on unlocking the keychain/keystore.
|
|
4.7
|
Verify that sessions are terminated at the remote endpoint after a predefined period of inactivity.
|
|
4.8
|
Verify that a second factor of authentication exists at the remote endpoint and the 2FA requirement is consistently enforced.
|
|
4.9
|
Verify that step-up authentication is required to enable actions that deal with sensitive data or transactions.
|
|
4.10
|
Verify that the app informs the user of all login activities with his or her account. Users are able view a list of devices used to access the account, and to block specific devices.
|
|
V5
|
Network Communication
|
|
5.1
|
Verify that data is encrypted on the network using TLS. The secure channel is used consistently throughout the app.
|
|
5.2
|
Verify that the TLS settings are in line with current best practices, as far as they are supported by the mobile operating system.
|
|
5.3
|
Verify that the app verifies the X.509 certificate of the remote endpoint when the secure channel is established. Only certificates signed by a valid CA are accepted.
|
|
5.4
|
Verify that the app either uses its own certificate store, or pins the endpoint certificate or public key, and subsequently does not establish connections with endpoints that offer a different certificate or key, even if signed by a trusted CA.
|
|
5.5
|
Verify that the app doesn't rely on a single insecure communication channel (email or SMS) for critical operations, such as enrollments and account recovery.
|
|
V6
|
Environmental Interaction
|
|
6.1
|
Verify that the app only requires the minimum set of permissions necessary.
|
|
6.2
|
Verify that all inputs from external sources and the user are validated and if necessary sanitized. This includes data received via the UI, IPC mechanisms such as intents, custom URLs, and network sources.
|
|
6.3
|
Verify that the app does not export sensitive functionality via custom URL schemes, unless these mechanisms are properly protected.
|
|
6.4
|
Verify that the app does not export sensitive functionality through IPC facilities, unless these mechanisms are properly protected.
|
|
6.5
|
Verify that JavaScript is disabled in WebViews unless explicitly required.
|
|
6.6
|
Verify that WebViews are configured to allow only the minimum set of protocol handlers required (ideally, only https). Potentially dangerous handlers, such as file, tel and app-id, are disabled.
|
|
6.7
|
Verify that the app does not load user-supplied local resources into WebViews.
|
|
6.8
|
Verify that if Java/Swift/Obj C objects are exposed in a WebView, verify that the WebView only renders JavaScript contained within the app package.
|
|
6.9
|
Verify that object serialization, if any, is implemented using safe serialization APIs.
|
|
6.10
|
Verify that the app detects whether it is being executed on a rooted or jailbroken device. Depending on the business requirement, users are warned, or the app is terminated if the device is rooted or jailbroken.
|
|
V7
|
Code Quality and Build Settings
|
|
7.1
|
Verify that the app is signed and provisioned with valid certificate.
|
|
7.2
|
Verify that the app has been built in release mode, with settings appropriate for a release build (e.g. non-debuggable).
|
|
7.3
|
Verify that debugging symbols have been removed from native binaries.
|
|
7.4
|
Verify that debugging code has been removed, and the app does not log verbose errors or debugging messages.
|
|
7.5
|
Verify that the app catches and handles possible exceptions.
|
|
7.6
|
Verify that error handling logic in security controls denies access by default.
|
|
7.7
|
Verify that in unmanaged code, memory is allocated, freed and used securely.
|
|
7.8
|
Verify that security features offered by the compiler, such as stack protection, PIE support and automatic reference counting, are activated.
|
|
7.9
|
Verify that Java bytecode has been minified.
|
|
V8
|
Resiliency Against Reverse Engineering Requirements
|
|
App Isolation
|
||
8.1
|
Verify that the app provides a custom keyboard whenever sensitive data is entered.
|
|
8.2
|
Verify that custom UI components are used to display sensitive data. The UI components should not rely on immutable data structures.
|
|
Impede Dynamic Analysis and Tampering
|
||
8.3
|
Verify that the app implements two or more functionally independent methods of root detection and responds to the presence of a rooted device either by alerting the user or terminating the app.
|
|
8.4
|
Verify that the app implements multiple functionally independent debugging defenses that, in context of the overall protection scheme, force adversaries to invest significant manual effort to enable debugging. All available debugging protocols must be covered (e.g. JDWP and native).
|
|
8.5
|
Verify that the app detects, and responds to, tampering with executable files and critical data.
|
|
8.6
|
Verify that the app detects the presence of widely used reverse engineering tools, such as code injection tools, hooking frameworks and debugging servers.
|
|
8.7
|
Verify that the app detects, and response to, being run in an emulator using any method.
|
|
8.8
|
Verify that the app detects, and responds to, modifications of process memory, including relocation table patches and injected code.
|
|
8.9
|
Verify that the app implements multiple different responses to tampering, debugging and emulation (requirements 9.2 - 9.6), including stealthy responses that don't simply terminate the app.
|
|
8.10
|
Verify all executable files and libraries belonging to the app are either encrypted on the file level and/or important code and data segments inside the executables are encrypted or packed. Trivial static analysis should not reveal important code or data.
|
|
8.11
|
Verify that obfuscating transformations and functional defenses are interdependent and well-integrated throughout the app.
|
|
Device Binding
|
||
8.12
|
Verify that the app implements a 'device binding' functionality when a mobile device is treated as being trusted. Verify that the device fingerprint is derived from multiple device properties.
|
|
Impede Comprehension
|
||
8.13
|
Verify that the app uses multiple functionally independent means of emulator detection that, in context of the overall protection scheme, force adversaries to invest significant manual effort to run the app in an emulator (supersedes requirement 9.5).
|
|
8.14
|
Verify that if the architecture requires sensitive information be stored on the device, the app only runs on operating system versions and devices that offer hardware-backed key storage. Alternatively, the information is protected using obfuscation. Considering current published research, the obfuscation type and parameters are sufficient to cause significant manual effort to reverse engineers seeking to comprehend or extract the sensitive data.
|
|
8.15
|
Verify that if the architecture requires sensitive computations be performed on the client-side, these computations are isolated from the operating system by using a hardware-based SE or TEE. Alternatively, the information is protected using obfuscation. Considering current published research, the obfuscation type and parameters are sufficient to cause significant manual effort to reverse engineers seeking to comprehend the sensitive portions of the code and/or data.
|
|
