How owasp/webgoat works
Project type and purpose
• This is OWASP WebGoat: a standalone, monolithic Java‑based insecure web application used for teaching security lessons.
• It bundles a collection of “lesson” modules (vulnerable endpoints) plus instructors’ versions, documentation, and scripts.
File structure
• Top‑level:
• pom.xml / build.xml → Maven + Ant build definitions
• webgoat.sh / .bat → startup scripts for Tomcat or SQL Server
• src/main/java → Java source
• org.owasp.webgoat.servlets.Controller.java → central servlet dispatcher
• org.owasp.webgoat.lessons.* → individual lesson implementations (AbstractLesson + concrete classes)
• org.owasp.webgoat.session.* → session, user tracking, DB utilities
• org.owasp.webgoat.util.* → helper classes (HTML encoder, interceptors, etc.)
• src/main/webapp → Web resources
• WEB-INF/web.xml, *.properties, *.sql → configuration, property files, schema scripts
• jsp pages under /lessons, main.jsp, webgoat.jsp → front‑end views
• css, javascript folders → static assets for UI and client‑side demos
• /lesson_plans, /lesson_solutions → static HTML documentation
• Scripts & configs
• server_*.xml → embedded server definitions
• tomcatconf/tomcat‑users.xml → Tomcat user roles for basic authentication
• No microservices — pure monolith following a loose MVC pattern (Controller → Java beans → JSP views).
README
• Placeholder pointing to external repo; no architectural details here.