I am starting a series on Node.js/Javascript security best practices. I will share daily one best practice on application security.
Let's make our applications safe.
#Javascript#Nodejs#Security
The On-Page is the Pillar of any SEO activity. That’s not debatable.
STEAL my proven On-Page SEO strategy that has generated over 76895 visitors to this client’s website.
Just Follow, Like, RT & comment “SEO” to get it Now. (Limited copies)
Tech Twitter these days be like
- JavaScript is hard
- CSS makes me cry at night
- React is killing me
- Frontend is stressful
Seriously, have you tried debugging Server side code for hours forgetting to restart the server ????
@wahVinci I commit when one task is completed. Most of the time I see if commit is following the single responsibility principle in a way.
Too many commits should not be issue as you can always squash them later if you want. Also in the case of continuous code review, it's super useful
@Vinaystwt@_buildspace Yes, that should be sufficient to start. You will learn some concepts along the way. You can do some hands-on examples in the rust before starting if you haven't done it yet.
🔒 Security Practice 8
Evil regex can overload Node.js's single-thread execution. Some of the regexes can block the entire event loop for 6 seconds with a single request that validates 10 words.
#javascript#nodejs
🔒 Security Practice 7
Limiting concurrent requests & request body payload
It will help against brute-force or DDoS attacks. With large bodies, It will take more time to process the requests and be unable to process important works, leading to vulnerability towards DOS.
🔒 Security Practice 6
Run server process as a non-root user
If you run the process as a root user then attackers can have total control over your server machine. People do it to get access to 90/443 port or user docker container which by default runs as a root.
10 lines is a pull request. 500 lines is an issue ticket already assigned to the submitter just waiting to be filled out. 5000 lines is the submitter taking over responsibility for whatever QA finds and not my problem any longer.
@AbdulrahmanDev @Rapid_API - Most of the API keys provide have IP/Domain restrictions. Enable that.
- Or, you can generate a short-term token for the frontend and keep the actual API key on the backend so it's not exposed to the browser.
There are no golden arrows for making it invisible from console.
@almo_dev@Walfizer@BatsouElef According to one study, 82% of people experience imposter syndrome yet 76% of us don't know what it is and think we're the only ones quietly freaking out?
@BatsouElef 3. Celebrate successes
Keep a kudos file: Keep the messages of praise you receive - in emails or messages - where someone appreciates something you did, or how you did it. Read them out loud, especially when you feel doubt creep in.