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

When a server does not include a `Domain` directive the cookie is to be considered `host-only`, meaning that its validity is restricted to the current domain only.


This is a sort of default behavior from browsers when they receive a cookie that does not have a `Domain` set. You can find a small example I wrote at [github.com/odino/wasec/tree/master/cookies](https://github.com/odino/wasec/tree/master/cookies). It's a simple web app that sets cookies based on URL parameters, and prints cookies on the page, through some JavaScript code.


```html
<html>
  <div id="output"/ >
  <script>
    let content = "none";

    if (document.cookie) {
      let cookies = document.cookie.split(';')
      content = ''

      cookies.forEach(c => {
        content += "<p><code>" + c + "</code></p>"
      })
    }

    document.getElementById('output').innerHTML = "Cookies on this document: <div>" + content + "</div>"
  </script>
<html>
```

If you follow the instructions in the `README` you will be able to access a webserver at [wasec.local:7888](http://wasec.local:7888), which illustrates how `host-only` cookies work.


In this lesson, we'll study host-only cookies.

Introduction

Understanding The Browser

HTTP

Protection through HTTP Headers

HTTP Cookies

Situationals

DDoS Attacks

Bug Bounty Programs

Conclusion

Deploy an API to Production Using Nginx

Host-only