Provide (2) 200 words response with a minimum of 1 APA references for RESPONSES 1 AND 2 below. Response provided should further discuss the subject or provide more insight. To further understand the response, below is the discussion post that’s discusses the responses. 100% original work and not plagiarized. Must meet deadline.
Before I discuss with you how to secure Node.js Application, first let’s have an overview of Node.js and what is all about.
Now that we know what is Node.js, we will discuss how to keep your application secure from malicious dependencies.
There are some preventive action you can take to avoid your application being
– Lock your dependencies. Use package-lock.json or yarn.lock to prevent getting automatic updates when deploying (when doing npm/yarn install in your server). At least this way you will get fewer chances of getting a malicious update that the npm team hasn’t cleaned up yet.
However, this wouldn’t have prevented the event-stream from affecting you since the malicious code was available in the npm registry for weeks.
-Use npm audit, Snyk and/or GitHub security alerts to be notified when any of your dependencies could contain security vulnerabilities.
When perform all these action in order to secure your application not only is a important step to prevent attack but it also very important to know most type of attack to better secure your application.
Diogo Souza( August 12, 2020).Security Best Practices for Node.js. Retrieved from https://blog.appsignal.com/2020/08/12/security-best-practices-for-nodejs.html
TutorialPoints(2020).Node.js – Introduction. Retrieved from https://www.tutorialspoint.com/nodejs/nodejs_introduction.htm
The Node.js application at its core is Java Script just like the client side. The core of Node.js makes it a target for the same attacks as Java Script. The application itself is vulnerable to SQL injections, Cross-Site Scripting, and Cross-Site Forgery Requests like the client side. Securing Node.js from the server side is the same as client for these attack vectors.
Cross-Site attacks can be defended against by using input validation. Input validation or properly encoded is a basic form for Node.js. The purpose of input validation is for the system to validate to input forms and ensure they are coming from the correct person or system (Sulemani, 2020).
SQL injections are used to find or retrieve information from the server by injecting a SQL statement instead of the field’s normal content (Sulemani, 2020). The use of parameterized statements in the application ensures the inputs are distinguished between data and code (Sulemani, 2020).
The basic security principles also work when securing Node.js applications. Ensuring the account used on the Node.js account is one with the minimal amount of privileges to do the required task (Sulemani, 2020). Hashing and adding salts to passwords inside the Node.js application is a basic security technique to guard the Node.js application. Salts are added to the password before it is hashed to make the Hash longer than it truly is. This technique protects the passwords from dictionary attacks that uses hashes of different words to crack passwords (Sulemani, 2020).
Adding or Removing HTTP headers in Node.js is another method to secure the application. HTTP headers can leak sensitive information about the application if they are not removed or secured properly. The Helemet.js module for Node.js is a security module for HTTP headers that protects against leaks (Sulemani, 2020).
Sulemani, M. (2020, November 19). Best practices for securing your Node.js apps. Retrieved from Educative: Interactive Courses for Software Developers website: https://www.educative.io/blog/secure-nodejs-apps-best-practices