Common API Security Pitfalls • Philippe De Ryck • GOTO 2019

แชร์
ฝัง
  • เผยแพร่เมื่อ 19 ม.ค. 2025

ความคิดเห็น • 9

  • @MuthuKumar-qi2um
    @MuthuKumar-qi2um 4 ปีที่แล้ว +3

    A super crisp talk by Phillepe on the API Security pitfalls. And here's some bookmarks from the talk for a ready reference.
    - OWASP Underprotected APIs vulnerabilities [2:10]
    - Brute force attack & Lack of using *different* rate limits for different APIs [6:08]
    - IDOR vulnerabilities & Lack of Proper Authorization [8:05]
    - Scaling Need to move authorization states a.k.a. sessions to clients using JWT [13:04]
    - JWT basics
    - Integrity checks for JWT
    - Mishandling client side auth headers [17:15]
    - HMAC based JWT Signatures [17:57]
    - Symmetric (Shared Secrets) vs Asymmetric JWT signatures [22:22]
    - Key Management [23:00]
    - Cookies vs Custom Authorization Headers [25:00]
    - CORS policies [30:00]
    - Enforcing strict CORS policies.
    - Input Validations [34:44]
    - Not the primary last line of defense
    - Not for Complex Data
    - Compartmentalizing your APIs [37:30]
    All in all a pretty good talk.

  • @ChristosGoros
    @ChristosGoros 5 ปีที่แล้ว +5

    Great talk. Concise analysis of the topic.

  • @divabanyuwigara3562
    @divabanyuwigara3562 5 ปีที่แล้ว +1

    This talk is really good.

  • @nero-kun-here
    @nero-kun-here 4 ปีที่แล้ว +1

    Great talk!
    Thanks 😊

  • @vadergrd
    @vadergrd 4 ปีที่แล้ว +1

    i will review his presentations a couple of times...

  • @hexatested
    @hexatested 5 ปีที่แล้ว +3

    Oh...
    Poor cameraman.

    • @phpdude
      @phpdude 4 ปีที่แล้ว

      After reading this comment, I lost all the focus on the presentation and was just watching the camera move.. hahaha 😂

  • @kashifbari8223
    @kashifbari8223 2 ปีที่แล้ว

    Such typical German lecture, extremely boring

    • @wingtungLeung
      @wingtungLeung 2 ปีที่แล้ว

      I know that Philippe's talks are usually not super-sexy and mind-blowing entertaining, but still really relevant. I am curious why you label it "typical German" though.