Questions and answers

Two. In a fix lab you get your own running copy of a vulnerable application and a code editor in the browser: you fix the weakness, rebuild the app and prove the fix with hidden tests. In a code review you read the code of a feature before it ships, mark each line where a weakness lives and name it; an answer key grades your review and, once you have found everything, explains each issue on the code. Code reviews open at once and have no timer.

A recent browser and an account. The application, its database and the code editor all run on the server; nothing is installed on your computer.

After you apply your change, the Studio rebuilds your copy of the application and runs the lab's hidden tests against it. Security checks try the attack again; functionality checks make sure the feature still works. Some checks must pass whatever the score, so you cannot pass by breaking the feature or by hiding the bug.

Each issue you mark on the right line and name correctly earns a full point; the right line with the wrong name earns half. A couple of marks on sound lines are allowed; each one after that costs points and keeps the review from passing, so marking every line does not pay. You solve the review by finding and naming every issue within that allowance.

No. Each session has its own containers, network and files, and its lab and editor open only for your account. Your instructor, if you belong to an organization, can open your sessions to help you.

Each lab sets a practice time, shown before you start. You can add time while the session runs, up to the limits of your plan. When the time is up the session is removed; your progress and your validation history stay.

Each lab declares its own stack in its manifest, so labs can use any language that runs in a container. See the lab catalog for what is published now.

Accounts are created by your instructor or by the administrator of this Studio. A licence code from them unlocks the labs of your plan.

Yes. An organization gets its own members, cohorts with assigned labs and due dates, progress and insights for its instructors, and seats for its members. Contact us to set one up.

Lab designers upload a lab as a package. The Studio checks it without running it, and an administrator reviews it before it is published.