dwc VS owasp-masvs

I'm a data librarian, so ideally the system would be built around the concept of collections, and support a solid metadata schema like Darwin Core.

With regards to longevity, when we're planning our infrastructure and how we're actually going to store our digital data we have to think in the long, long term (100+ years), much as we have to when considering how to store the physical specimens. Currently we manage our own data centre which stores all our collections and image data but we’re exploring cloud options currently. In terms of how we store the actual data, we try to map to well known standards and ontologies (such as Darwin Core - https://dwc.tdwg.org/) to ensure our data is interoperable with others and can be managed using community standards. On the Data Portal specifically, we use a versioning system to make sure that data is available long term, even if it’s been changed since it was originally made public (this happens regularly as taxonomists love to reclassify specimens!). This is particularly important when users cite our data using DOIs which should be persistent and always available.

https://github.com/OWASP/owasp-masvs :

> The OWASP MASVS (Mobile Application Security Verification Standard) is the industry standard for mobile app security.

owasp-masvs

There is an organization called OWASP that has a series of guidelines, one of which concerns itself with mobile app security. When I worked for a fintech startup, audits were executed based on this guideline, so maybe it's worth taking a look at it: https://github.com/OWASP/owasp-masvs

OWASP MASVS, MSTG, and WSTG.

Security falls under the category non-functional requirements. It should define the needed security functionality the software has to satisfy. To save up time and not re-invent the wheel on each new project, you can select security requirements from a catalog. There is a general one called "Application Security Verification Standard (ASVS)" and one for the mobile named "Mobile Application Verification Standard (MASVS)". They contain a collection of requirements which are best practices for each listed category. Fortunately they have mapped those requirements with CWE (common weakness enumeration which is basically a list of software and hardware weaknesses). Depending on the used tools, those CWEs can be automatically scanned in your code.

The project team of the OWASP Mobile Application Security Verification Standard (https://github.com/OWASP/owasp-masvs) is right in the middle of completely refactoring the document and it's requirements for mobile apps! We were re-visiting this topic in the last few months and tried to identify the current pain points and how they could be removed.

In order to move forward we are looking for your feedback! If you would like to share any feedback or comments of what should be changed in the MASVS, please do so by participating in our Github Discussion:

https://github.com/OWASP/owasp-masvs/discussions/553

I've only been able to scan through the MASVS L2 standard info which you sent. I'll review it more later.