Threat Modeling and Least Privilege

Module:Core concept

Identify assets, trust boundaries, entry points, abuse cases, and controls before implementation.

How to apply it

Consider account takeover, cross-tenant exposure, webhook forgery, malicious uploads, denial of service, and privilege escalation. Record prevention, detection, response, and residual risk. Apply least privilege to people, services, CI, and support tools.

Worked example

Provide support staff time-limited, audited access rather than permanent database administrator access.

Common mistakes to avoid

Assuming a compliance checklist alone proves security or ignoring abuse by authenticated users.

Practice task

Implement this concept in the capstone. Add one positive test, one negative or failure-path test, and a short note explaining the trade-off you chose.

Key Takeaways
  • Identify assets, trust boundaries, entry points, abuse cases, and controls before implementation.
  • Consider account takeover, cross-tenant exposure, webhook forgery, malicious uploads, denial of service, and privilege escalation.
Knowledge Check

What is the strongest production practice for Threat Modeling and Least Privilege?