wstg
owasp-mastg
Our great sponsors
| wstg | owasp-mastg | |
|---|---|---|
| 27 | 22 | |
| 6,684 | 11,272 | |
| 3.5% | 1.4% | |
| 7.6 | 8.3 | |
| 4 days ago | 8 days ago | |
| Dockerfile | Python | |
| Creative Commons Attribution Share Alike 4.0 | Creative Commons Attribution Share Alike 4.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wstg
-
Where do you focus your time and energy?
At the beginning, I read all things in here https://owasp.org/www-project-web-security-testing-guide/, also gets familiars with owasp top 10. But later on, I focus on a few techniques only.
-
XSS
I highly recommend PortSwigger's Web Security Academy and have a look at the OWASP Web Security Testing Guide.
- Como identificar vulnerabilidades no código fonte?
- Internal pentesting course
-
I need some Help
You can follow OWASP web testing guide to learn about the test cases performed during testing.
-
Ask HN: Fallback remote job options for an experienced developer in the U.S.?
Most web app testing is performed using this guide https://owasp.org/www-project-web-security-testing-guide/
- Which security strategies can you recommend?
-
Pentest on web app priority
I highly recommend the OWASP Testing Guide: https://owasp.org/www-project-web-security-testing-guide/
-
Web App Pentesting Career
Hi, sit and learn https://owasp.org/www-project-web-security-testing-guide/ that's the best way, than may be EJPT.
-
Git branching for small teams
A short-lived branch-per-issue helps ensure that its resulting pull request doesn’t get too large, making it unwieldy and hard to review carefully. The definition of “short” varies depending on the team or project’s development velocity: for a small team producing a commercial app (like a startup), the time from issue branch creation to PR probably won’t exceed a week. For open source projects like the OWASP WSTG that depends on volunteers working around busy schedules, branches may live for a few weeks to a few months, depending on the contributor. Generally, strive to iterate in as little time as possible.
owasp-mastg
- More ways to identify independently security tested apps on Google Play
-
Google Play rolls out an "Independent security review" badge for apps
https://mas.owasp.org/ :
> The OWASP Mobile Application Security (MAS) flagship project provides a security standard for mobile apps (OWASP MASVS) and a comprehensive testing guide (OWASP MASTG) that covers the processes, techniques, and tools used during a mobile app security test, as well as an exhaustive set of test cases
- Need Help on Patching
- The Mobile Application Security Testing Guide (MASTG) is a comprehensive manual for mobile app security testing and reverse engineering. It describes the technical processes for verifying the controls listed in the OWASP Mobile Application Security Verification Standard (MASVS).
- Mobile game security - how to?
-
Are android bugs mostly api and web ?
Have a look at the OWASP Mobile Application Testing Guide https://github.com/OWASP/owasp-mastg
-
How can we get our Apps validated against OWASP's MASVS and does it shown on the PlayStore?
owasp-mastg
-
How do you check your app for security issues?
Be aware that this kind of tools shouldn't be seen as a substitute for a manual and thorough pentesting of the application. As u/StoryOfDavid suggested decompiling the application (I usually use jadx for this) and using Wireshark to check the network traffic are good ways to start assessing the security of your application. If you want to be thorough I suggest going through the OWASP-MSTG guide (now renamed to MASTG) which provides a categorization of possible security issues, with a description of the problem and actionable ways to statically/dynamically analyze your application.
-
Securing API keys, clientId, clientSecret etc while distributing to App Store? Ways to prevent reverse engineering?
Check out OWASP, they have plenty documentation about threat modeling and attack vectors for mobile apps. Regarding jailbreak detection, see the following: https://github.com/OWASP/owasp-mstg/blob/master/Document/0x06j-Testing-Resiliency-Against-Reverse-Engineering.md
-
Moving from Web application pentesting to mobile.
- OWASP is as usual a good resource: https://owasp.org/www-project-mobile-security-testing-guide/
What are some alternatives?
OWASP-Testing-Checklist - OWASP based Web Application Security Testing Checklist is an Excel based checklist which helps you to track the status of completed and pending test cases.
H4CKINTO - H4CKINTO - Remote Android Management Suite
owasp-masvs - The OWASP MASVS (Mobile Application Security Verification Standard) is the industry standard for mobile app security.
API-Security-Checklist - Checklist of the most important security countermeasures when designing, testing, and releasing your API
grapefruit - (WIP) Runtime Application Instruments for iOS. Previously Passionfruit
PayloadsAllTheThings - A list of useful payloads and bypass for Web Application Security and Pentest/CTF
linux-smart-enumeration - Linux enumeration tool for pentesting and CTFs with verbosity levels
bugbounty-cheatsheet - A list of interesting payloads, tips and tricks for bug bounty hunters.
hacktricks - Welcome to the page where you will find each trick/technique/whatever I have learnt in CTFs, real life apps, and reading researches and news.
Damn-Vulnerable-Bank - Damn Vulnerable Bank is designed to be an intentionally vulnerable android application. This provides an interface to assess your android application security hacking skills.
audiohq_module - Provide binary and apk for controlling each applications volume using Magisk