r/owasp • u/BlackDiamondSolution • May 21 '13
r/owasp • u/ghostheadx9 • May 30 '18
How do I use OWASP broken web application project to learn from WAHH?
I want to use the OWASP Broken Web Application Project to go through the 2nd edition of the Web Application Hackers Handbook. Then maybe I could try to complete the broken web application project on my own.
How do I know which exercises are WAHH? Thanks.
r/owasp • u/psiinon • Oct 23 '12
OWASP Zed Attack Proxy: ZAP Weekly Releases
zaproxy.blogspot.co.ukr/owasp • u/DinisCruz • Oct 21 '12
Let's make this happen: "Investing in Developing Software Security Talent"
r/owasp • u/ghostheadx9 • May 30 '18
Once I complete the OWASP Broken Web Application Project then would it be practical to do Web Goat without walk throughs once I have learned the techniques? I want to challenge myself.
Doing this in a few months after I earn some certs.
r/owasp • u/[deleted] • Oct 28 '19
Best XSS scanner?
Hey guys,
After doing some research on finding an XSS scanner for our product, XSStrike seems to be the best option at this point but I know sometimes features like vulnerability scanning comes bundled up as part of other software.
What would you recommend for XSS scanning?
Thanks!
r/owasp • u/sarciszewski • Nov 25 '15
OWASP phpsec ships with a remotely exploitable crypto library, please don't use it
r/owasp • u/iherbtechnology • Sep 05 '18
[Hiring] Web Application Security Engineer (Irvine,CA)
r/owasp • u/danlinto • Apr 21 '20
OWASP Zap Force browse differences
I'm trying to understand what the difference is between the three provided options
- Forced browse site
- Forced browse directory
- Forced browse directory (and children)
Can someone please elaborate?
r/owasp • u/Ecstatic_Endorian • Jul 17 '19
Hands on OWASP Course!
Hey all, ISACA made a course that lets you work with each of the OWASP Top 10 directly for CPE credit for your certs! It's pretty fun and I liked the practical engagement part. Thought I'd pass along.
r/owasp • u/kerberosmansour • May 17 '26
I built a SAST/DAST security-agent workflow and tooling around Semgrep + ZAP while recovering from medical treatment and would love your feedback
Hey everyone,
I've been recovering from major medical treatment, and while I am out sick I ended up keeping myself busy by building some technical projects.
This security one in particular is something I thought you'd be intrested in, and I'd very much love your feedback.
The main pieces are:
zaprun— a unified command-line tool for running OWASP ZAP headlessa hardened ZAP container image — built for repeatable CI-style scans, browser-backed testing, and predictable artifacts - includes PTK for better detection of DOM based security vulnerabilities.
SunLit Orchestra AI security skills
/slo-sast— threat-model-aware Semgrep skill for scanning/slo-dast-tuner— authenticated ZAP scanning driven throughzaprun/slo-rulegen— generates or extends Semgrep rule packs/slo-ruleverify— verifies the rule pack against a deterministic gate
TL;DR: I built a set of security agent skills for Semgrep and ZAP, I also added ZAP tooling that try to continuously tune security testing as a project evolves to:
reduce false negatives
reduce false positives
keep SAST rules (semgrep) aligned with the threat model
make sure DAST is actually authenticated and testing the right routes
connect static findings to dynamic tests
make scanner results easier to trust, review, and repeat
What zaprun does
There several community scripts for running OWASP ZAP headless. I kept running into the same patterns, so I folded them into one CLI:
zaprun Also available on crates.io
The goal is to make ZAP runs more predictable. zaprun gives you a stable artifact contract, so a scan produces the same kinds of files every time: plans, summaries, coverage, observations, and reports that CI or a human reviewer can reason about.
It supports normal ZAP scans, OpenAPI-driven API scans, and a browser-backed PTK lane as well.
PTK / client-side scanning
One thing I especially wanted to include was PTK support.
zaprun can run a PTK/client-side lane for DOM-heavy applications, where a traditional scan may not see what is happening in the browser.
That matters for modern front-ends. If the app is Angular, React, or otherwise heavy on client-side JavaScript, the scanner needs a browser-backed path. Otherwise it can miss DOM XSS and other client-side issues.
For this part I leaned heavily on the ZAP project's own published guidance — particularly their articles on authentication as scan-quality infrastructure and on using static analysis to guide ZAP — and tried to make PTK-style, authenticated testing easier to wire up and run repeatably.
More detail here:
The hardened ZAP image
I also built a hardened ZAP image:
It is designed for headless scanning and browser-backed DOM testing, so it includes Firefox. That makes the image larger than I would ideally like, but it means the PTK/browser path works properly (the browser-backed lane genuinely needs that image — the slim path can't run it).
I also worked on reducing the CVE/issue count, pinning the moving parts (the image is digest-pinned), and making the image behave cleanly behind the CLI.
The security-agent part
The part I am most interested in getting feedback on is the agent workflow inside SunLit Orchestra.
The idea is that security tooling should not be static. It should be tuned as the app changes.
So the security skills do a few things together:
/slo-sastreads the threat model and tunes Semgrep toward the bug classes that matter for the app./slo-rulegenhelps create or extend custom Semgrep rules./slo-ruleverifychecks that the rule pack still passes a deterministic gate./slo-dast-tunerruns ZAP throughzaprun, sets up authentication, chooses the right scan lane, and reports coverage honestly.
The goal is a continuous security-tuning loop rather than a one-off scan.
In plain English: if the app changes, the security checks should adapt. If the threat model says SSRF, IDOR, open redirect, or DOM XSS matter, the tooling should focus on those risks and show whether it actually tested them.
The SAST→DAST bridge
The most interesting bit, in my opinion, is the SAST→DAST bridge:
A static scanner might say:
Possible SSRF in
research.js, line 16.
But a dynamic scanner needs something different:
Send
GET /research?url=...— and you'll need to be logged in as a user first.
Those are not the same language.
The bridge tries to translate between them. It reads the code, maps the finding to the route and method, works out whether auth is needed, and then gives DAST a concrete place to test.
That means ZAP is not just crawling blindly. It is being pointed at routes the code already suggests are risky.
One honest caveat: the route-mapping is validated end-to-end on Express. Other frameworks (NestJS, Spring, Django, Rails, …) have documented resolver adapters and a generic fallback so it degrades gracefully, but they are not yet validated against a real vulnerable app the way Express was — treat those as hints until proven.
What I found
Important caveat: this is scoped.
These numbers are from public Semgrep registry packs on JavaScript/Node apps, mainly OWASP NodeGoat and Juice Shop. I am not claiming this generalises to every language, every scanner, or all of SAST as a category.
Full report & methodology: the complete test write-up (baseline vs tuned vs improved, the DAST decomposition, PTK, and full false-positive / false-negative analysis) is here: report/REPORT.md
With that said:
SAST
Stock public Semgrep registry rules caught about 33% of the documented bugs.
A generic custom pack focused on taint tracking and common Express patterns, including the const { x } = req.body style many apps use, raised that to about 63%, with one additional false positive. A later precision pass (splitting the DB-query rules by driver so SQL vs NoSQL get the right CWE) also removed a cross-ORM mislabel that had been inflating false positives on the second app.
The same custom pack, unchanged, also found 8 exact ground-truth sinks in a different JavaScript app.
DAST
On the same app, with scans authenticated:
bridge fed with the baseline SAST output:
2 testable endpoints
1 confirmed bug
bridge fed with the custom-pack SAST output:
8 testable endpoints
4 confirmed bugs:
IDOR
open redirect
SSRF
ReDoS
The unauthenticated default scan found 0 of those.
Obviously, "authenticate your scanner" is not a new idea. The point was to measure how much gets missed without it, and then make the authenticated setup automatic and repeatable.
DOM XSS
The PTK lane also caught DOM XSS that the traditional scan structurally could not see, including Angular innerHTML sinks.
That is why I wanted PTK support in zaprun rather than only the traditional scan path.
Why I built this
This came out of work on a few related projects:
SunLit Orchestra — an agentic development workflow with security built into each stage and an optional TLA+ gate for validating design with formal specification
Hulumi — hardened Pulumi components and policies
SunLit Secure Libraries — secure Rust building blocks
To trust those projects, I needed better SAST and DAST. That turned into the security skills, zaprun, and the hardened ZAP image.
Links
It is still early, and I am sure there is plenty to improve.
I would really appreciate feedback, especially on the SAST→DAST bridge and the idea of agent skills acting like a lightweight security team that keeps tuning SAST and DAST over time.
r/owasp • u/2blocksfromnowhere • Apr 01 '20
How do you five secure coding advice when you are not a developer?
Hi, I've been recently asked to help devs with remediation and secure coding. I have very little programming experience but do have some pentesting experience and familiar with vulnerabilities, etc. My initial thought is to learn javascript and then get to know OWASP stuff like the back of my hand.
Any ideas? Thanks!
r/owasp • u/DSotnikov • Mar 04 '20
Are You Properly Using JWTs? - Session recording from OWASP AppSec California 2020
r/owasp • u/[deleted] • Mar 04 '20
Can OWASP projects use copyleft licenses?
Would anyone know?
Say I wanted to use GPL or MPL licenses on my project, would OWASP accept it?
Thanks!
r/owasp • u/saltyironfag • Nov 14 '18
Problem with OWASP Zap and fuzzing results
I saved an OWASP session before exporting my fuzzing results, and the fuzzing results disappeared after the save finished. Based on the file size of the session (4 GB) I think they're still in there somewhere but I can't find a way to get them back. Have I lost them for good?
r/owasp • u/psiinon • Oct 04 '12
OWASP Initiatives: Global Strategic Focus (cross post to owasp_initiatives)
r/owasp • u/[deleted] • Oct 12 '12
Application Security Workshop - A quick writeup
piercecommunications.co.ukr/owasp • u/imacarpet • Sep 04 '12
Attacking DVWA
I'm learning about webapp security. I've downloaded Damn Vulnerable Web Application, and installed it.
I've selected the section on sql injection. I've read the tutorials in the links that are provided.
But I'm stuck:
The instructions are so thin as to be non-existent. There are no hints. Googling, I found a demonstration video that shows example attacks, but when I use the same strings, I don't get any result. Perhaps the video I found is for an older version.
I know that I should be able to figure out myself which strings get some kind of results from the application, but I'm stumped. I am pretty new to attacking webapps, after all.
The source for the application I'm attacking looks like this:
So how can I attack the application? What can I achieve?
r/owasp • u/[deleted] • Oct 04 '12
Redit Enhancement Suite
I find this tool to be very useful, and thought I would share it with the community in case you have not already heard of it:
The Reddit Enhancement Suite (RES) provides a suite of modules to enhance your Reddit browsing experience.
Currently available for Firefox (requires GreaseMonkey), Chrome, Safari and Opera, you can enable or disable any of the RES Modules, most of which have their own individual options that can be customized to suit your needs.
r/owasp • u/DinisCruz • Oct 02 '12
An Idea of a new model for OWASP
r/owasp • u/psiinon • Jan 09 '14
Poll: should OWASP give developer training at RSA? (OWASP members only - see comments)
owasp.orgr/owasp • u/DinisCruz • Sep 30 '12