Damn-Vulnerable-Bank
wstg
| Damn-Vulnerable-Bank | wstg | |
|---|---|---|
| 3 | 27 | |
| 606 | 6,735 | |
| - | 2.1% | |
| 4.7 | 7.6 | |
| 5 months ago | 8 days ago | |
| Java | Dockerfile | |
| MIT License | 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.
Damn-Vulnerable-Bank
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.
What are some alternatives?
UnSAFE_Bank - Vulnerable Banking Suite
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.
AndroidLibrary - Android library to reveal or obfuscate strings and assets at runtime
owasp-masvs - The OWASP MASVS (Mobile Application Security Verification Standard) is the industry standard for mobile app security.
Insular - A sandbox environment to clone selected apps and isolate them from accessing your personal data outside the sandbox (including call logs, contacts, photos and etc) even if related permissions are granted. Device-bound data (SMS, IMEI and etc) is still accessible.
API-Security-Checklist - Checklist of the most important security countermeasures when designing, testing, and releasing your API
allsafe - Intentionally vulnerable Android application.
PayloadsAllTheThings - A list of useful payloads and bypass for Web Application Security and Pentest/CTF
remote-method-guesser - Java RMI Vulnerability Scanner
bugbounty-cheatsheet - A list of interesting payloads, tips and tricks for bug bounty hunters.
huntkit - Docker - Ubuntu with a bunch of PenTesting tools and wordlists
OWASP-Calculator - 🧮 An online calculator to assess the risk of web vulnerabilities based on OWASP Risk Assessment