{"id":23652,"date":"2023-05-05T05:44:15","date_gmt":"2023-05-05T05:44:15","guid":{"rendered":"https:\/\/www.booksofall.com\/cn\/?post_type=product&p=23652"},"modified":"2023-05-05T05:44:15","modified_gmt":"2023-05-05T05:44:15","slug":"owasp-mobile-application-security-testing-guide","status":"publish","type":"product","link":"https:\/\/www.booksofall.com\/cn\/owasp-mobile-application-security-testing-guide\/","title":{"rendered":"OWASP Mobile Application Security Testing Guide"},"content":{"rendered":"
\n
\n

Introduction to the OWASP Mobile Application Security Project<\/h2>\n

New technology always introduces new security risks, and mobile computing is no exception. Security concerns for mobile apps differ from traditional desktop software in some important ways. Modern mobile operating systems<\/a> are arguably more secure than traditional desktop operating systems<\/a>, but problems can still appear when we don\u2019t carefully consider security during mobile app development. Data storage, inter-app communication, proper usage of cryptographic APIs, and secure network communication are only some of these considerations. The OWASP Mobile Application Security\u00a0Verification Standard\u00a0<\/i>(MASVS) defines a mobile app security model and lists generic security requirements for mobile apps. It can be used by architects, developers, testers, security professionals, and consumers to define and understand the qualities of a secure mobile app. The OWASP Mobile Application Security<\/a> Testing Guide\u00a0<\/i>(MASTG) maps to the same basic set of security requirements offered by the MASVS and depending on the context they can be used individually or combined to achieve different objectives.<\/p>\n

For example, the MASVS requirements can be used in an app\u2019s planning and architecture design stages while the checklist and testing guide may serve as a baseline for manual security testing or as a template for automated security tests during or after development. In the \u201cMobile App Security Testing\u201d chapter we\u2019ll describe how you can apply the checklist and MASTG to a mobile app penetration test.<\/p>\n<\/div>\n<\/div>\n

\n
\n

Key Areas in Mobile Application Security<\/h3>\n

Many mobile app penetration testers have a background in network and web app penetration testing, a quality that is valuable for mobile app testing. Almost every mobile app talks to a backend service, and those services are prone to the same types of attacks we are familiar with in web apps on desktop machines. Mobile apps differ in that there is a smaller attack surface and therefore more security against injection and similar attacks. Instead, we must prioritize data protection on the device and the network to increase mobile security. Let\u2019s discuss the key areas in mobile app security.<\/p>\n

Data Storage and Privacy (MASVS-STORAGE)<\/h4>\n

The protection of sensitive data, such as user credentials and private information, is crucial to mobile security. If an app uses operating system APIs such as local storage or inter-process communication (IPC)<\/a> improperly, the app might expose sensitive data to other apps running on the same device. It may also unintentionally leak data to cloud storage, backups, or the keyboard cache. Additionally, mobile devices can be lost or stolen more easily compared to other types of devices, so it\u2019s more likely an individual can gain physical access to the device, making it easier to retrieve the data. When developing mobile apps, we must take extra care when storing user data. For example, we can use appropriate key storage API<\/a>s and take advantage of hardware-backed security features when available. Fragmentation<\/a> is a problem we deal with especially on Android<\/a> devices. Not every Android device offers hardware-backed secure storage, and many devices are running outdated versions of Android. For an app to be supported on these out-of-date devices, it would have to be created using an older version of Android\u2019s API which may lack important security features. For maximum security, the best choice is to create apps with the current API version even though that excludes some users.<\/p>\n

Cryptography (MASVS-CRYPTO)<\/h4>\n

Cryptography<\/a> is an essential ingredient when it comes to protecting data stored on a mobile device. It is also an area where things can go horribly wrong, especially when standard conventions are not followed. It is essential to ensure that the application uses cryptography according to industry best practices, including the use of proven cryptographic libraries, a proper choice and configuration of cryptographic primitives as well as a suitable random number generator wherever randomness is required.<\/p>\n

Authentication and Authorization (MASVS-AUTH)<\/h4>\n

In most cases, sending users to log in to a remote service is an integral part of the overall mobile app architecture. Even though most of the authentication and authorization logic happens at the endpoint, there are also some implementation challenges on the mobile app side. Unlike web apps, mobile apps often store long-time session tokens that are unlocked with user-to-device<\/p>\n

authentication features such as fingerprint scanning. While this allows for a quicker login and better user experience (nobody likes to enter complex passwords), it also introduces additional complexity and room for error. Mobile app architectures also increasingly incorporate authorization frameworks (such as OAuth2) that delegate authentication to a separate service or outsource the authentication process to an authentication provider. Using OAuth2 allows the client-side authentication logic to be outsourced to other apps on the same device (e.g. the system browser). Security testers must know the advantages and disadvantages of different possible authorization frameworks and architectures.<\/p>\n

Network Communication (MASVS-NETWORK)<\/h4>\n

Mobile devices regularly connect to a variety of networks, including public Wi-Fi networks shared with other (potentially malicious) clients. This creates opportunities for a wide variety of network- based attacks ranging from simple to complicated and old to new. It\u2019s crucial to maintain the confidentiality and integrity of information exchanged between the mobile app and remote service endpoints. As a basic requirement, mobile apps must set up a secure, encrypted channel for network communication using the TLS protocol with appropriate settings.<\/p>\n

Interaction with the Mobile Platform (MASVS-PLATFORM)<\/h4>\n

Mobile operating system architectures differ from classical desktop architectures in important ways. For example, all mobile operating systems implement app permission systems that regulate access to specific APIs. They also offer more (Android) or less rich (iOS) inter-process communication (IPC) facilities that enable apps to exchange signals and data. These platform-specific features come with their own set of pitfalls. For example, if IPC APIs are misused, sensitive data or functionality might be unintentionally exposed to other apps running on the device.<\/p>\n<\/div>\n

……<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"