milewski-ctfp-pdf VS owasp-masvs

Category Theory for Programmers by Bartosz Milewski (https://github.com/hmemcpy/milewski-ctfp-pdf/releases)

Strangely similar name to the well-known 'Category Theory for Programmers'

https://github.com/hmemcpy/milewski-ctfp-pdf

There's this, but the programmer doesn't have to be working:

https://bartoszmilewski.com/2014/10/28/category-theory-for-p...

Milewski's "Category Theory for Programmers".

(3) category theory. I was never advised to read any, but found that bartosz's introduction really good. https://bartoszmilewski.com/2014/10/28/category-theory-for-programmers-the-preface/. Helps to rewire the brain.

It's also possible to model programming languages using category theory, but I know less about that. If you're interested in following this up, then Benjamin Pierce has what I'm told is a good introduction to category theory for computer scientists, and Bartosz Milweski has an online book (it might be available in hard copy as well, I'm not sure) called Category Theory for Programmers. I believe simple programming languages like the simply typed lambda calculus end up being modelled as Cartesian closed categories.

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.