Sensitive data - JavaScript Tutorial

- [Instructor] Like a broken authentication, having a plan to properly hide sensitive user or obligation data is crucial. Take a look at all the data available in your application. What are the areas that would be safe for public consumption and the ones that are private or could be exploited? For example, in general, all user data should be considered sensitive and hidden from the public eye, and take a look at the data users generate. Can it be public or not? Once you have a plan, you need to implement some of the strategies mentioned in the previous video, proper crypto hashing, HTTPS protocols, and the use of advanced tools like JSS Scrambler. JSS Scrambler goes a step further than just a simple crypto. It works at a deeper level with your code logic and scrambles your code and data so it isn't easy to reverse engineer your minify code and figure out what function does what. At the end of the day, you need to have a…