~/talk

Fuzzing API to identify API1: broken object level authorization control

Talkat Apidays Live Hong Kong 2020 · on Thursday, 2020-10-08· [security]
links:none on file
slides:none on file

Fuzzing identifies API1 broken object-level authorization and API5 broken function-level authorization by iterating ID patterns and replacing body values derived from the OpenAPI spec, flagging endpoints that return 200 or 500 instead of 4xx. Uses open source tools like Wfuzz and OWASP ZAP, integrates generation-based fuzzing into DevSecOps (scheduled off-peak), separates QA from security testing, and experiments with machine learning to improve test-vector accuracy and raise true-positive rates.

AI-written summary · about

  1. 0:00Intro
  2. 3:28Agenda
  3. 3:47Recent Incidents
  4. 5:01Access Control
  5. 7:28API 5 and API 1
  6. 11:08How can we identify
  7. 13:02Fuzzy factor type
  8. 15:19Fuzzing procedure
  9. 18:32Open source fuzzing tool
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.