Course contentsShow
← Security
Lesson 1862 of 3,05237. Cloud Security - Network ArchitectureFree lesson

CDN Architecture and Threat Model

Understanding CDN distributed architecture, edge nodes, origin shielding, and the unique threat landscape for content delivery networks.

CDN Architecture and Threat Model

What you'll learn: How content delivery networks are structured and what unique security challenges they face as distributed global infrastructure.

What Is a CDN?

A Content Delivery Network (CDN) is a geographically distributed network of edge servers that cache and deliver content closer to end users. Think of it as a chain of strategically placed warehouses that stock popular items nearby, instead of shipping everything from a single distant factory.

CDN Architecture Components

Edge Nodes

These are geographically dispersed servers (often called Points of Presence or PoPs) that cache content. When a user requests a video or webpage, the nearest edge node serves it, dramatically reducing latency and origin server load.

Origin Server

The authoritative source of content. The CDN fetches content from here when it's not cached at the edge.

Origin Shielding

An intermediary layer between edge nodes and the origin server. Instead of 100 edge nodes all requesting uncached content directly from your origin (potentially overwhelming it), they request from a shield server, which then makes a single request to the origin. It's like having a regional distribution center buffer your main warehouse.

The CDN Threat Landscape

CDNs face unique security challenges:

  • Cache poisoning: Attackers inject malicious content into edge caches, affecting thousands of users
  • Distributed attack surface: Each edge node is a potential entry point
  • SSL/TLS complexity: Managing certificates across hundreds of global nodes
  • Origin exposure: Attackers may try to bypass the CDN and attack the origin directly
  • Data leakage: Cached sensitive content might persist longer than intended
  • Geographic compliance: Content must respect regional data laws across all edge locations

Key Takeaway: CDNs improve performance and resilience but introduce a distributed attack surface requiring cache integrity controls, origin protection, distributed certificate management, and careful content security policies across all edge nodes.