Node.js Security Best Practices: JWT blacklisting, rate limiting, schema validation

Поділитися
Вставка
  • Опубліковано 28 вер 2024

КОМЕНТАРІ • 35

  • @SoftwareDeveloperDiaries
    @SoftwareDeveloperDiaries  10 місяців тому

    Check out Docuo 👉 bit.ly/3SaTsQV

  • @vineetsingh904
    @vineetsingh904 10 місяців тому +12

    I fell weird when I see less subscriber You at least deserve 1-2 million subscribers. Your channel is the best because no one tell these things and you not only talk about these things but also tell what to use in real world projects. Even paid courses don't teaches or even tell about these thing. You a great

  • @wishmeheaven
    @wishmeheaven 9 місяців тому +3

    Thanks!
    I was actually looking for other topics such as NoSQL injection, sanitize, XXS protection, security headers, rate limiting (indeed included here), HPP and CORS.
    I'm a backend development student looking to dig further at security issues...
    Thank you very much for this series, and I can hardly wait to find out what other topics will it maneuvering through...

  • @icaromendes1250
    @icaromendes1250 Місяць тому

    Is the kind of content everyone needs but no one is mentioning

  • @babayaga6172
    @babayaga6172 10 місяців тому +1

    Can u please make a video about multithreading clustering twice by quoting a example of large project scaling

  • @koningguidokip
    @koningguidokip 7 місяців тому

    I've learned so much from this!

  • @mrunalvaidya388
    @mrunalvaidya388 9 місяців тому

    Amazing content as always🙌

  • @OCEMTechZone
    @OCEMTechZone Місяць тому

    Great one

  • @NPCtoHero
    @NPCtoHero 5 місяців тому

    🎉 Great video !

  • @codermeloman3030
    @codermeloman3030 10 місяців тому

    Super content!!!

  • @jeremyccc
    @jeremyccc 10 місяців тому

    Thanks for this!

  • @elmasx
    @elmasx 10 місяців тому

    Hello, Guseyn. You're so sweet. I just discovered your channel and I admire it, I learned a lot. I wonder if there will be a classic nodejs, deno and bun comparison? I would like to know your opinion, regards.

    • @SoftwareDeveloperDiaries
      @SoftwareDeveloperDiaries  10 місяців тому

      Really happy to hear that! 🙂I will keep those in mind 😉

    • @elmasx
      @elmasx 10 місяців тому

      @@SoftwareDeveloperDiaries Thank you so much!

  • @taras0varty0m
    @taras0varty0m 10 місяців тому +3

    instead of bcrypt, it is better to use a scrypt that is embedded in node.js

    • @aliarslanansari
      @aliarslanansari 10 місяців тому +1

      reason?

    • @taras0varty0m
      @taras0varty0m 10 місяців тому

      @@aliarslanansari
      With scrypt in addition to increasing computation you can increase the amount of memory needed to compute the hash. This doesn't bother software implementations much but is much harder to implement with hardware - which is what a dedicated attacker is likely to develop and use.
      bcrypt (and PBKDF2) use constant, and small, amounts of memory.

    • @taras0varty0m
      @taras0varty0m 10 місяців тому

      @@aliarslanansari answer from stackoverflow

    • @taras0varty0m
      @taras0varty0m 10 місяців тому

      @@aliarslanansari and an additional library, this is a greater weight of the bundle or the final container after the application is built.

    • @SoftwareDeveloperDiaries
      @SoftwareDeveloperDiaries  10 місяців тому +1

      Thanks for the hint, you're totally right, it's a better option for most use-cases

  • @ismaildeveloper
    @ismaildeveloper 10 місяців тому +1

    great

  • @thomasr22272
    @thomasr22272 9 місяців тому

    Just one thing, hashing is not technically encryption

  • @ratedr278
    @ratedr278 5 місяців тому

    Bro, get rid of that background music, it's unprofessional. (Distracting and out of place)

  • @liammullan2197
    @liammullan2197 2 місяці тому +1

    A piece of advice on the sound... there is a noise gate over your voice and it is way too aggressive and keeps on cutting off bits of your words.

  • @danielson9490
    @danielson9490 10 місяців тому +2

    NodeJS Security Best Practices:
    - 1. Rate Limiting
    - 2. Password Encryption
    - 3. JWT Blacklisting
    - 4. JSON Schema Validation
    - 5. Escaping HTML & CSS
    - 6. ORM/ODM agains Injections
    - 7. Security Linter

  • @babayaga6172
    @babayaga6172 10 місяців тому

    Literally U r doing amazing job 👏🏼

  • @tarekalkhatib5619
    @tarekalkhatib5619 8 місяців тому

    great content, do you plan on releasing part 3 any time soon