ASD ISM 1922 Use OWASP standards in mobile app development
What it says
The OWASP Mobile Application Security Verification Standard is used in the development of mobile applications.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Use the OWASP Mobile Application Security Verification Standard in developing mobile applications, as the security requirements each app is built and checked against.
The OWASP Mobile Application Security Verification Standard (MASVS) must be used in the development of mobile applications, meaning apps for mobile operating systems, such as on smartphones and tablets. The MASVS sets security requirements for such apps in areas such as data storage, cryptography, authentication, network communication, interaction with the operating system, code quality and resistance to tampering. Used means its requirements shape the design and the app is checked against them, not that the standard is only cited. It applies whether apps are built in-house or by a contractor.
Free. Save your status, tasks and notes.
Why it matters
A mobile app runs on devices the organisation may not control, where data left on the device, weak certificate checking or a tampered copy can expose accounts and data. Building to the MASVS catches such flaws before release, not after users install the app.
How to implement
List the mobile applications developed by or for the organisation.
Include apps built in-house and by contractors, and compare the list with your app store developer accounts, device management app catalogue and code repositories, so none is missed.
Set each app's MASVS requirements before design starts.
For an existing app, set them before work on its next release. Record which requirements apply and why any do not, based on the data the app handles and how exposed it is, with the MASVS version used. Keep this with the app's other software security requirements (ISM-2033).
Hold contractors to the standard.
Agree the applicable MASVS requirements and the evidence you expect before a contractor starts work. Where an existing contract does not mention the MASVS, test the delivered app against it yourself and raise gaps before release.
Build to the requirements and check them during development.
Use them in threat modelling (ISM-1238), design reviews and code reviews, for example storing secrets only in the operating system's secure key store and validating server certificates. ISM-2108 separately requires mobile applications to encrypt sensitive or classified data sent over public network infrastructure using ASD-approved cryptography.
Verify each release against the requirements.
Test the built app with static and dynamic analysis and on a real device, recording a result for each applicable requirement, alongside the SAST, DAST and SCA testing ISM-0402 requires before each release. Fix each failure, or record a decision on it, before release.
Keep it running
When OWASP publishes a new MASVS version, check each app against the changed requirements at its next release. A new app, a major feature or a change of contractor should prompt a fresh look at which requirements apply.
Evidence and audit
- Check 1 of 3What an auditor asks for
Ask for
The list of mobile applications developed by or for the organisation, compared with its app store developer accounts, device management app catalogue and code repositories.
Look at
Whether every app developed by or for the organisation appears on the list, and whether each has a record of the MASVS requirements that apply.
Good evidence
Every app developed by or for the organisation that appears in the stores, catalogue or repositories is on the list, and each has a record of the MASVS version and requirements that apply, with reasons for any excluded.
- Check 2 of 3What an auditor asks for
Ask for
The verification results for the latest release of a sampled app.
Look at
Whether each applicable MASVS requirement was checked for that release, and how failures were handled.
Good evidence
Each applicable MASVS requirement has a result for that release, and every failure was fixed or had a recorded decision before release.
- Check 3 of 3What an auditor asks for
Ask for
An independent spot check of the released app on a test device, such as inspecting its stored data and network traffic.
Look at
Whether the app behaves as its verification results claim.
Good evidence
The app matches its verification results, for example storing no credentials or sensitive data unprotected on the device and sending no traffic unencrypted.
Mappings
Closest match in ISO/IEC 27001: A.8.25, Secure development life cycle, which this control partially meets.
ISO/IEC 27001: 3 mappings
This control partially meets A.8.25.
ISM-1922 requires the OWASP Mobile Application Security Verification Standard (MASVS) to be used when developing mobile applications. ISO/IEC 27001:2022 Annex A 8.25 requires a secure development lifecycle to be established and applied across software and systems development. Using OWASP MASVS is a specific secure-SDLC standard/practice for the mobile application context, while Annex A 8.25 is broader and technology-agnostic.
This control partially meets A.8.28.
Annex A 8.28 requires secure coding principles to be applied in software development. ISM-1922 supports this by requiring use of the OWASP Mobile ASVS in mobile app development, which provides concrete secure coding and verification requirements for common mobile risks. ISM-1922 is scoped to mobile applications and is a prescriptive standard, while Annex A 8.28 is a general secure coding principle requirement across software types.
This control partially overlaps A.8.29.
ISM-1922 requires development teams to use OWASP MASVS as a security standard for mobile application development. ISO/IEC 27001:2022 Annex A 8.29 requires defined and implemented security testing processes within the development lifecycle. MASVS includes verification requirements and testing/validation expectations that can inform mobile app security testing, but Annex A 8.29 applies to security testing more generally and is not limited to OWASP or mobile.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




