learning path

Application and API Security

build and test software that holds up

For developers, testers and aspiring AppSec engineers: how web applications and APIs fail, how to find those flaws safely, and how to design them out.

Beginner to intermediateAbout 4 to 8 months part-time (a rough guide)

Roles this can lead to: Application security engineer · Secure developer · Web and API tester

  1. 1

    Web foundations

    Understand the platform before you secure it.

  2. 2

    How web apps fail

    Learn the common flaws and why they happen.

    • Not read yet
      The OWASP Top 10Infodle topic · 2 min — the web's most common ways to get hacked, in plain language
    • Not read yet
      SQL InjectionInfodle topic · 2 min — when a form field becomes a database command
    • Not read yet
      Cross-Site Scripting (XSS)Infodle topic · 2 min — when a website runs an attacker's script in your browser
    • Not read yet
      How Passwords Get BrokenInfodle topic · 2 min — guessing, stuffing, spraying and cracking, and what stops each
  3. 3

    APIs and identity

    Modern apps are mostly APIs and tokens.

  4. 4

    Test and manage

    Find issues, rank them and get them fixed.

  5. 5

    Practice

    Break things you own.

External links go to third-party sites that Infodle does not control; some resources there are paid. Ticking an external step is just for your own tracking and is stored only on this device.