Ethical Hacking with JavaScript

32mAdvanced2018-11-01

Authors

Emmanuel Henri

Executive with 20+ years of experience in programming and design

Course details

Web applications combine complexity and exposure to networks. JavaScript and the web offer great power, but also many opportunities to leave doors open to hackers. Ethical hacking lets you find those open doors before they can be exploited, and ensure that your sites and applications stay safe. This course was designed to equip JavaScript developers with ethical hacking techniques and tools that can help them boost the security of their JavaScript code. Instructor Emmanuel Henri shows how to put together an attack strategy and do some reconnaissance work using key tools, including Snyk, which automates finding and fixing vulnerabilities in projects. He also dives into some of the most common security threats out there, explaining what they are and how to spot them.
Learning objectives
What is ethical hacking?
Planning an attack strategy
Doing reconnaissance work in an app
Setting up and using Synk, Retire.js, and AppSensor
Preventing injection threats, broken authentication, and security misconfigurations
Protecting components with known vulnerabilities
Preventing insufficient logging and monitoring

Skills covered

Security TestingJavaScriptOracleCybersecurityProgramming LanguagesSoftware DevelopmentDeep Dive (X:Y)

Concepts

Welcome

01 - Ethical JavaScript hacking
02 - What you should know

1. Introduction and Setup

03 - What is ethical hacking
04 - Overview of the cyber kill chain
05 - Plan an attack strategy
06 - Base project setup

2. Reconnaissance

07 - Reconnaissance introduction
08 - Introduction and setup for Snyk
09 - Introduction and setup for Retire.js
10 - Introduction to AppSensor
11 - Review of the plan

3. Top Security Threats

12 - Injection threat
13 - Broken authentication
14 - Sensitive data
15 - XML external entities
16 - Security misconfiguration
17 - Insecure deserialization
18 - Components with known vulnerabilities
19 - Insufficient logging and monitoring

Conclusion

20 - Next steps