pwndoc VS owasp-masvs

No, but there is a Github Issue about the fact that there is no documentation ! https://github.com/pwndoc/pwndoc/issues/183 So if you want to do that I'm sure the community would love it lol

iirc I spent about 7-8 hours with my report. I used pwndoc with a custom template (based on the offsec template and modified a few things) I prepared beforehand.

This is a great project ! But did you know that https://github.com/pwndoc/pwndoc already exists and has the same features ..?

Please look into something like PwnDoc https://github.com/pwndoc/pwndoc or even paid things like Plextrac. Automated templates will save you so much time I guarantee it.

I've been trying to convert this into k8s with no success unfortunately. Frontend and Mongo pods run fine, but the backend always gives the error below. Essentially was following this tutorial minus the aspects specific to the node-project they downloaded.

Pwndoc is good: https://github.com/pwndoc/pwndoc

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.