OWASP Mobile Top 10

SH1ELD Mobile ensures that your IOS/Android application complies against the latest OWASP Mobile Top 10 - 2016 that stands at their website as follows:

M1 - Improper Platform Usage

This category covers misuse of a platform feature or failure to use platform security controls. It might include Android intents, platform permissions, misuse of TouchID, the Keychain, or some other security control that is part of the mobile operating system. There are several ways that mobile apps can experience this risk.

M2 - Insecure Data Storage

This new category is a combination of M2 + M4 from Mobile Top Ten 2014. This covers insecure data storage and unintended data leakage. Insecure data storage vulnerabilities occur when development teams assume that users or malware will not have access to a mobile device's filesystem and subsequent sensitive information in data-stores on the device.

M3 - Insecure Communication

This covers poor handshaking, use of outdated SSL or TLS, weak negotiation, cleartext communication of sensitive data or assets.

M4 - Insecure Authentication

This category captures notions of authenticating the end user or bad session management. This can include:

  • Failing to identify the user at all when that should be required
  • Failure to maintain the user's identity when it is required
  • Weaknesses in session management

M5 - Insufficient Cryptography

The code applies cryptography to a sensitive information asset. However, the cryptography is insufficient in some way. Note that anything and everything related to TLS or SSL goes in M3. Also, if the app fails to use cryptography at all when it should, that probably belongs in M2. This category is for issues where cryptography was attempted, but it wasn't done correctly.

M6 - Insecure Authorisation

This is a category to capture any failures in authorization (e.g., authorization decisions in the client side, forced browsing, etc.). It is distinct from authentication issues (e.g., device enrolment, user identification, etc.).
If the app does not authenticate users at all in a situation where it should (e.g., granting anonymous access to some resource or service when authenticated and authorized access is required), then that is an authentication failure not an authorization failure.

M7 - Client Code Quality

This was the "Security Decisions Via Untrusted Inputs", one of our lesser-used categories. This would be the catch-all for code-level implementation problems in the mobile client. That's distinct from server-side coding mistakes. This would capture things like buffer overflows, format string vulnerabilities, and various other code-level mistakes where the solution is to rewrite some code that's running on the mobile device.

M8 - Code Tampering

This category covers binary patching, local resource modification, method hooking, method swizzling, and dynamic memory modification.
Once the application is delivered to the mobile device, the code and data resources are resident there. An attacker can either directly modify the code, change the contents of memory dynamically, change or replace the system APIs that the application uses, or modify the application's data and resources. This can provide the attacker a direct method of subverting the intended use of the software for personal or monetary gain.

M9 - Reverse Engineering

This category includes analysis of the final core binary to determine its source code, libraries, algorithms, and other assets. Software such as IDA Pro, Hopper, otool, and other binary inspection tools give the attacker insight into the inner workings of the application. This may be used to exploit other nascent vulnerabilities in the application, as well as revealing information about back end servers, cryptographic constants and ciphers, and intellectual property.

M10 - Extraneous Functionality

Often, developers include hidden backdoor functionality or other internal development security controls that are not intended to be released into a production environment. For example, a developer may accidentally include a password as a comment in a hybrid app. Another example includes disabling of 2-factor authentication during testing.

PCI App Security

SH1ELD Mobile tests mobile apps against the PCI mobile payment guidelines

The Guideline focuses on 3 major objectives:

Objective 1. Prevent account data from being intercepted when entered into a mobile device: This states either to use proper Point to Point Encryption(P2PE) solutions or else some other trusted path must exist between the data entry device (Manual or via a card reader) and the moile device.

Objective 2: Prevent account data from compromise while processed or stored within the mobile device: This states that any critical data on the device must be stored within a secure storage environment. It suggests an implementation of a sandbox out of which any critical data should be inaccessible.

Objective 3: Prevent account data from interception upon transmission out of the mobile device: Ensuring that account data is encrypted (i.e., using strong symmetric or asymmetric cryptography) per PCI DSS Requirement 4, prior to transmission out of the trusted execution environment of the mobile device.

Further more Sh1eld Mobile will check your mobile app against the following PCI Mobile Development Guidelines

Create server-side controls and report unauthorized access.
Prevent escalation of privileges.
Create the ability to remotely disable the payment application.
Prefer online transactions.
Protection against known vulnerabilities

HIPAA App Security

SH1ELD Mobile tests mobile apps for proper implementation of HIPAA Technical Safeguards

Unique User Identification: Assign a unique name and/or number for identifying and tracking user identity.
Emergency Access Procedure: Establish procedures for obtaining necessary ePHI during an emergency.
Automatic Logoff : Implement procedures that end the user session after preset time of inactivity.
Encryption and Decryption: Implement a mechanism to encrypt and decrypt ePHI.
Audit Controls: Implement hardware, software, and/or procedural mechanisms that log and audit user activity revolving around ePHI.
Mechanism to Authenticate ePHI: Implement methods to ensure that ePHI has not been altered or destroyed with an unauthorized access.
Authentication: Proper implementation of authentication mechanisms to ensure ePHI is returned to user to whom it belongs to and no one else
Integrity Controls: Implement security measures to ensure that transmitted ePHI is not altered without detection
Encryption: Proper implementation of ePHI encryption while transmission & storage.