Security and privacy

Note: As you'll see below, this module is currently only a curriculum outline/syllabus, with some links provided to starter guides. We are intending to convert this into a full course in the future, as time allows.

It is vital to have an understanding of how you can and should protect your data and your user's data from would-be attackers who may try to steal it. This module covers both hardening websites to make it more difficult to steal data, and collecting user data in a respectful way that avoids tracking them or sharing it with unsuitable third parties.

Prerequisites

Before starting this module, you should be familiar with HTML and CSS.

Learning outcomes

5.1 Security and privacy basics

Note:

  • Conforming to all of the criteria in this module is not going to result in a student being a qualified security engineer, but equally it is important for web developers to understand the basics of web security and privacy.
  • It is also important for students to understand that a lot of security issues are caused by problems with server-side code, or a combination of client-side and server-side code. A lot of code should present very few security risks, provided the browser is doing its job properly.

Learning outcomes:

  • Understand the difference between security and privacy.

  • Understand the general HTTP model from a high-level.

  • Learn what HTTPS is, and why it is important.

  • Same-origin security:

    • Why this is fundamental to the web.

    • Ways of working around it safely, such as Cross-Origin Resource Sharing (CORS).

  • How cookies are stored, and their security and privacy implications, such as tracking.

  • Learn about situations where security issues generally occur:

    • When asking users to provide sensitive data (such as passwords or credit card data) and transmitting it to a server.

    • When requesting data from a server.

    • When transmitting data between servers (for example, if a server requests data from a web service).

    • When preserving user state by setting a cookie or other mechanisms.

  • Learn about common security threats and how to mitigate them:

    • Cross-site scripting (XSS).

    • Cross-site request forgery (CSRF).

    • Clickjacking.

    • Denial of service (DoS).

  • Understand the purpose of other important technologies, such as:

    • Content Security Policy (CSP).

    • Permissions-Policy.

    • The web model for user activation of "powerful features" (aka transient activation).

5.2 Data protection laws

Learning outcomes:

Note:: Conforming to the above criteria does not require students to become legal experts in privacy laws, but they should understand the implications of these laws, and how that affects their work.

Resources

See also