Skip to content
learn
  1. Learn
  2. High Level System Design
  3. Security in System Design

HLD-M16

Security in System Design

Security as a design property: authentication and authorization, OAuth and tokens, encryption and secrets, tenant isolation and defending against abuse.

5 lessonsabout 55 min

Security is not a feature added at the end; it is a set of design decisions about who can do what, where secrets live, how data is protected and how the system holds up when someone attacks it on purpose. Getting these decisions wrong is expensive to fix later, because they shape APIs, data models and infrastructure.

This module covers the security topics every system designer needs. You will separate authentication from authorization and choose between role-based and attribute-based access, follow the OAuth 2.0 and OpenID Connect flows and learn what a JWT can and cannot do, protect data with encryption, key management and secret managers, isolate tenants in shared infrastructure, and absorb DDoS attacks and abuse at the edge.

Lessons

  1. HLD-16.01 Authentication vs authorization Authentication proves who someone is, for example with a password, passkey or single sign-on. Beginner 10 min
  2. HLD-16.02 OAuth 2.0, OpenID Connect and JWT OAuth 2.0 lets an app act on a user's behalf without seeing their password: the user logs in with an authorization server, which issues the app an access token. Intermediate 16 min
  3. HLD-16.03 Encryption, keys and secrets Data should be encrypted in transit with TLS and at rest on disk. Intermediate 10 min
  4. HLD-16.04 Multi-tenancy and isolation Multi-tenant systems serve many customers on shared infrastructure. Advanced 10 min
  5. HLD-16.05 DDoS protection and abuse prevention Volumetric DDoS attacks flood networks with traffic and are absorbed by large edge networks and anycast. Intermediate 10 min

Start with lesson 1