← Back to CoursesCyber Security: PhD Level

Neuroanatomy Explorer

Drag to rotate · scroll to zoom · click regions to explore

View
Loading 3D model…

Click a region
to explore it

Memory Deck

Flip each card and rate whether you knew it. Your score is saved.

Term
Definition

Deck complete — score saved.

Match the Pairs

Match each term to its definition. Finish the board to earn your score.

All matched — score saved.

Concept Constellation

Every key idea in this course, mapped as an explorable 3D constellation. Drag to rotate, scroll to zoom, click a node.

Click a node to read its definition.

Web, Cloud, and Container Security at Scale

Manual: General · Subject: Cyber Security

Examine multi-tenant isolation, web application threats, supply-chain risks, and cloud-native defense patterns in modern distributed systems.

Why Web and Cloud Security Are Distinctly Hard

Scale, heterogeneity, and shared responsibility

Web and cloud systems combine browsers, APIs, identity providers, orchestration layers, storage services, and third-party dependencies. Security is complicated by multi-tenancy, elastic scaling, ephemeral infrastructure, and the shared responsibility model, where misconfigurations often create vulnerabilities even when core services are sound.

Common attack classes

Web application attacks

  • Injection, XSS, CSRF, SSRF, auth bypass.
  • Often exploit trust in untrusted input.

Cloud misconfiguration

  • Overpermissive IAM, exposed storage, insecure metadata access.
  • Often caused by complexity and automation errors.

Which vulnerability class most directly arises from treating untrusted input as code or query structure?

What is the security risk of overly permissive IAM policies?

Secure Software Supply Chains

From source to deployment

A secure software supply chain protects code, dependencies, build systems, package registries, signing keys, and deployment pipelines. Recent incidents have shown that trusted update channels and CI/CD infrastructure are lucrative targets because compromising them can silently reach many downstream environments.

Supply-chain hardening checklist

  1. 1

    Step 1: Pin and verify dependencies where possible.

  2. 2

    Step 2: Protect build systems and signing keys with strong access controls.

  3. 3

    Step 3: Use reproducible or auditable builds when feasible.

  4. 4

    Step 4: Segment CI/CD secrets and enforce short-lived credentials.

  5. 5

    Step 5: Continuously monitor provenance and package integrity.

Why are software supply-chain attacks so dangerous?

Name one benefit of short-lived credentials in cloud environments.

Runtime Isolation and Multi-Tenancy

Isolation under shared infrastructure

Cloud providers rely on a mixture of hypervisors, microVMs, namespaces, cgroups, network policies, and identity controls. Researchers study cross-tenant leakage, noisy-neighbor effects, metadata service abuse, and the security impact of control-plane compromise.

What is a core goal of multi-tenant isolation?

Why is the control plane a high-value target in cloud security?