Node.js Security Best Practices #3: child processes, security hardening, leaking server information

Node.js security best practices such as security hardening of frameworks and libraries, managing env files and secrets, using child processes carefully are going to be covered in this video.

☕ Buy me a coffee: https://www.buymeacoffee.com/softwaredeveloperdiaries
🙌 Become my Patreon and get exclusive perks: https://patreon.com/softdevdiaries
💼 Follow me on LinkedIn and drop me a message if you'd like: https://linkedin.com/in/gusgadirov
💻 Also, let's connect on GitHub: https://github.com/gusgad

📚 Resources:
Node.js security best practices playlist: https://www.youtube.com/playlist?list=PL5Lsd0YA4OMHXXfwBrBGr6GlVooGNOHLe
Node.js worker threads: https://youtu.be/MuwJJrfIfsU
OWASP ASVS (PDF in the link): https://github.com/OWASP/ASVS
Express security hardening: https://dev.to/aminnairi/express-hardening-cheatsheet-p69
Nginx x-powered-by: https://www.iothreat.com/blog/server-leaks-information-via-x-powered-by-http-response-header-field-s
.npmignore: https://docs.npmjs.com/cli/v10/using-npm/developers#keeping-files-out-of-your-package
Node.js worker threads vs. child processes: https://amplication.com/blog/nodejs-worker-threads-vs-child-processes-which-one-should-you-use

🕒 Timestamps:
0:00 Intro
0:45 Security hardening
3:27 Leaking server information
5:10 .npmignore
6:51 Child processes

And don't forget to subscribe for more videos like this 😊