Application security, in the open

Where application security gets researched and taught.

Original research from apisec Labs, courses from apisec University, live events and masterclasses, and open-source tools. Pick a view to see what's here for you.

WHAT'S HERE FOR YOUPICK A VIEW
THE BRIEF · FROM APISEC LABS2 MIN

One changed number exposes another customer's data.

WHAT HAPPENS
A signed-in user changes an ID in a request and reads records that belong to a different customer. The application never checks who owns them.
WHY IT MATTERS
Broken object-level authorization is the top risk on the OWASP API Security list, and code review rarely catches it.
ASK YOUR TEAM
Do we test every endpoint for ownership checks, on every release, and can we show the evidence?
LAB 01 · OBJECT-LEVEL AUTHORIZATIONSIMULATED

Signed in as user_a · tenant A · account 1041

This endpoint returns your own account. Send it, then change the ID to someone else's.

// response appears here

RESULT not tested yet

NO PROOF YET
Read the Labs research behind it: BOLA, object-level authorization analysis →Go deeper: API Penetration Testing, advanced course with certificate →
THE PATH · APISEC UNIVERSITYSTART FREE
  1. 01

    API Security Fundamentals

    How APIs work, how they break, and the controls that matter. Free, with a certificate.

  2. 02

    OWASP API Security Top 10 and Beyond

    Where you learn the flaw practitioners exploit in the lab, with real exploits and fixes.

  3. 03

    Certification, then masterclasses

    A credential employers can verify, then live, hands-on masterclasses when you're ready.

apisec
Labs

A working map of how applications actually break.

Every point is a finding published by apisec Labs. Pick a territory for the leadership brief, or a point for the research, the course that goes deeper and the tool that finds it.

All research →
21 FINDINGS · 5 TERRITORIES

For every application you run

Find what's deployed and prove which exploits are real.

Go to apisec.ai