wstg
Infosec_Reference
Our great sponsors
| wstg | Infosec_Reference | |
|---|---|---|
| 27 | 9 | |
| 6,684 | 5,358 | |
| 3.5% | - | |
| 7.6 | 4.2 | |
| 5 days ago | 10 days ago | |
| Dockerfile | CSS | |
| Creative Commons Attribution Share Alike 4.0 | MIT License |
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.
Infosec_Reference
- How to improve documentation / technical writing skills?
- Manuals
-
Cybersecurity Repositories
Infosec Reference
- About Russia's Industrial Control System Attacks...
- Advise please?
- I'm preparing for the interview and I've curated a list of resources that might be helpful for you also.
-
Noob questions and advice
There’s this: https://github.com/rmusser01/Infosec_Reference
-
How to grt better/ homelab help
https://github.com/rmusser01/Infosec_Reference/blob/master/Draft/Building_A_Lab.md Has some ideas. The first things to decide on would be what do you want to use for your hosting environment. Do you want to run ESXi? HyperV? Xen? Something else? What do you want to learn? What sort of environments do you want to simulate?
- Cybersec Bootcamp
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.
API-Security-Checklist - Checklist of the most important security countermeasures when designing, testing, and releasing your API
owasp-masvs - The OWASP MASVS (Mobile Application Security Verification Standard) is the industry standard for mobile app security.
hackdroid - Security Apps for Android
red_team_attack_lab - Red Team Attack Lab for TTP testing & research
PayloadsAllTheThings - A list of useful payloads and bypass for Web Application Security and Pentest/CTF
the_cyber_plumbers_handbook - Free copy of The Cyber Plumber's Handbook - The definitive guide to Secure Shell (SSH) tunneling, port redirection, and bending traffic like a boss.
bugbounty-cheatsheet - A list of interesting payloads, tips and tricks for bug bounty hunters.
AlanFramework - A C2 post-exploitation framework
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.