One Course
Every lesson, project and mock exam in Application security.
Billed monthly. Cancel any time.
Level 1: Newcomer
0 points
Sign in to save your progress across devices.
Practice application security through the OWASP Top 10: trace untrusted input, reproduce a flaw and fix its cause. The course checks both security and ordinary behavior in a fictional browser app. Continue with Security Labs for separate Java, Python and TypeScript services.
Unit 1, Object-level access control: 1 lessons and 4 checked exercises, with no account or card.
Start the free unitThe rest of the course opens with a One Course or All Access plan. See plans and prices
Choose access here. Your course is already selected.
Learn application security by doing the work. Each lab is one small vulnerable web service running only in your browser. You send a saved request and watch the attack succeed, you edit the server code to close the hole, then you send the request again and watch it fail while a normal request still works. Nothing ever touches a real system.
Start with broken access control and injection, then move to authentication, tokens, cryptography, server-side request forgery, insecure design, the software supply chain, logging and secure code review. Every lab names its weakness by the OWASP Top 10:2025 category and a CWE number. Fixes are checked two ways: the attack must be refused and the feature must keep working.
Work one company brief through several tools. Your Application security stage reads the tables from the stage before.
See all projectsBeginner
Refuse a record to anyone who does not own it.
Keep untrusted input out of SQL and HTML.
Intermediate
Verify a token's signature and expiry before trusting its claims.
Recognize and fix the common weaknesses on fresh data.
Expert
Timed find-the-flaw tests in the shape of a secure code review.
A patch has two jobs: stop the unsafe operation and keep the intended feature working. Blocking every request can satisfy the first job while making the application useless. In Security Labs, the checks test both, then repeat the requests on a second dataset.
Choose the boundary you want to work on:
In the booking search lab, a search value becomes part of a SQL statement. An attacker can change the statement’s meaning and read rows outside the intended search. The repair keeps SQL structure separate from bound values. Rejecting a familiar attack string is weaker: a different input can reach the same unsafe concatenation.
Try role checks in an admin API next. SQL parameters protect query structure; they do not decide whether an authenticated analyst may close a financial period.
Trace the source, the identity and the destination before choosing a fix. For SQL, bind values. For a plain text label, use a text output. For intentionally formatted HTML, use a narrow sanitizer. Check the stored account’s permission before changing data. Keep credentials out of public assets and diagnostics.
Then test a bypass and an ordinary request. The DOM fragment lab uses URL decoding to show why a filter in the wrong place misses the dangerous value. The private key lab checks that a rotated server credential still works without reaching the browser.
The SOC analyst course practices fictional log searches and incident triage. Add networking practice for addressing and routes; the cybersecurity path puts the courses in order.
The official OWASP Top 10:2025 list is the category reference for the current labs.
It groups common application security risks. The exercises turn those risks into specific requests, code paths and checks. A category label helps organize the work; it does not prove an application is secure.
The course builds skills in sequence. Security Labs gives you separate fictional services to investigate, exploit, fix and verify, with questions after the checks. Start with the first lab in any path, which is free.
It records the labs you completed and links to the saved record. It is a Work Gym completion attestation, not an OWASP certification, an accredited qualification or proof of performance on an employer's test.
Use the Application security engineer rounds for secure design and code review, or the Security engineer rounds for broader security work. The scenarios are original practice, not questions attributed to an employer.