# Web and API Security

Web and API flaws by root cause, with the fix that removes each.

URL: https://insideout.sh/courses/web-api-security
Updated: 2026-11-16T12:26:01Z

## Lessons

1. [Untrusted input and injection](https://insideout.sh/courses/web-api-security/01): Keep data and code apart, so input can never become a command. Pro.
2. [The same-origin policy and CORS](https://insideout.sh/courses/web-api-security/02): What the browser lets one site read from another, and why. Pro.
3. [Cross-site scripting and content security policy](https://insideout.sh/courses/web-api-security/03): Encode output for its context, and back it with a strict content policy. Pro.
4. [Requests your server makes, and files it accepts](https://insideout.sh/courses/web-api-security/04): Let the server fetch only allowed hosts, and keep uploaded files inert. Pro.
5. [Designing a secure API](https://insideout.sh/courses/web-api-security/05): Secure an API endpoint by endpoint, including the ones nobody listed. Pro.
6. [Business logic and race conditions](https://insideout.sh/courses/web-api-security/06): Find the steps a user can skip or run twice, and close each one. Pro.
7. [Failing closed](https://insideout.sh/courses/web-api-security/07): Make every error path and default end in the safe state. Pro.
8. [Abuse, bots and account takeover](https://insideout.sh/courses/web-api-security/08): Stop credential stuffing and bots with limits sized from real traffic. Pro.
9. [Memory safety and language choice](https://insideout.sh/courses/web-api-security/09): Why memory bugs happen, and how a team plans its way out of them. Pro.
10. [Mobile apps and the APIs behind them](https://insideout.sh/courses/web-api-security/10): A phone app can't keep a secret, so its server has to. Pro.
