Gain insights into enforcing web app security best practices, such as HTTPS, defending against XSS and clickjacking, managing HTTP cookies, and warding off DDoS attacks.

new.tar.gz

node

cookies

hsts

hsts-https

cookies-https

clickjacking

cors

There are more vulnerabilities than ever when creating applications for the web, so it is extremely important that software developers enforce security best practices such as, how to add protection through HTTP headers.

In this course, you will start off by learning how to prevent fraudulent SSL certificates from being served to clients, before moving on to how to defend against XSS attacks and clickjacking. 

In the latter half of the course, you’ll learn security practices related to HTTP cookies, and tips around security tradeoffs that you’ll make in your day-to-day work. Towards the end, you’ll learn how to ward off DDoS attacks, which is crucial when your application scales.

This course will demystify web security, and help you stay on top of important security-related concerns in your web apps.

Web Application Security for the Everyday Software Engineer

## Introduction
What if we were able to set a cookie on a top-level domain (TLD) such as `.com` or `.org`? That would be a huge security concern, for two reasons:

* **user privacy**: every website running on that specific TLD would be able to track information about the user in shared storage
* **information leakage**: a server could mistakenly store a sensitive piece of data in a cookie available to other sites

In the following code, by appending `?super=on` to the URL, the server is going to set a cookie on the domain local (e.g., wasec.local). Since it is a top-level domain, the client will refuse to process this cookie.



# Introduction
What if we were able to set a cookie on a top-level domain (TLD) such as `.com` or `.org`? That would be a huge security concern, for two reasons:

* **user privacy**: every website running on that specific TLD would be able to track information about the user in shared storage
* **information leakage**: a server could mistakenly store a sensitive piece of data in a cookie available to other sites

In the following code, by appending `?super=on` to the URL, the server is going to set a cookie on the domain local (e.g., wasec.local). Since it is a top-level domain, the client will refuse to process this cookie.



In this lesson, we'll study supercookies. 

Introduction

Understanding The Browser

HTTP

Protection through HTTP Headers

HTTP Cookies

Situationals

DDoS Attacks

Bug Bounty Programs

Conclusion

Supercookies

Introduction