password

passwordHash

Gain insights into securing Node.js applications: sanitize inputs, use HTTPS, encryption, explore authentication, access control, and protect against XSS, CSRF, and popular hacks.

Working_SNA_Docker.tar.gz

psql

psql-copy

run_spa

run_spa_node

run_spa_hash

compose

compose-copy

compose-copy-copy

run_spa-copy

app-demo-psql

This course is your guide for securing Node.js applications. You'll start by properly sanitizing user input and output, and then move on to some fundamental protocols, such as HTTPS and SHA. Passwords and encryption will be discussed next. More specifically, you will learn about different hashing algorithms and protecting your application from brute force attacks.

Following that, you'll explore concepts like authentication, access control, and obfuscation. You will also learn about XSS, CSRF, and other popular hacks near the end of the course.

By the end of this course, you will know how to secure a Node.js application, an in-demand skill to put on your resume!

A Guide to Securing Node.js Applications

How do you upgrade your existing system that has MD5 passwords with no salt?

I'm going to give you two options.

*	Path 1 - As each user logs in, silently upgrade their hash to use BCrypt.  They won't even know the difference.  Soon enough, you will have a database of well-secured passwords.

*	Path 2 - Use BCrypt to hash the existing MD5 hashes in the database.  New passwords will be hashed with MD5 first and then BCrypt.


## Upgrade Path 1
Path 1 is the traditional advice for migrating to new authentication schemes. It is by far the best option in most circumstances. To implement, do something similar to this:

How do you upgrade your existing system that has MD5 passwords with no salt?

I'm going to give you two options.

*	Path 1 - As each user logs in, silently upgrade their hash to use BCrypt.  They won't even know the difference.  Soon enough, you will have a database of well-secured passwords.

*	Path 2 - Use BCrypt to hash the existing MD5 hashes in the database.  New passwords will be hashed with MD5 first and then BCrypt.


# Upgrade Path 1
Path 1 is the traditional advice for migrating to new authentication schemes. It is by far the best option in most circumstances. To implement, do something similar to this:

Introduction

Never Trust Your Users. Sanitize ALL Input!

HTTPS and Other Random Letters

Password Encryption and Storage for Everyone

Authentication, Access Control, and Safe File Handling

Safe Defaults, Cross Site Scripting, and Other Popular Hacks

Upgrading Legacy Systems

Upgrade Path 1