The video lists common web app security best practices. Most are solid advice, but the API-key/origin claim is oversimplified.
Claim-by-claim breakdown
Accurate (96% confidence): Apps should enforce proper access control so users cannot change an ID in the URL and access someone else’s data. OWASP recommends object-level authorization checks and warns against relying on user-controlled IDs in URLs.
Misleading (72% confidence): An API should not accept random cross-site requests just because they come from a website other than your own. Security for browser-based requests depends on more than origin checks; CORS is not an authentication mechanism, and Stripe-style public keys are not secret credentials.
Accurate (95% confidence): Updating packages is an important security practice. Dependency updates are a core defense against known vulnerabilities in third-party libraries.
Accurate (96% confidence): File uploads should be checked for file type and size. OWASP recommends validating file type and controlling file size for uploads.
Accurate (98% confidence): Database queries should be parameterized. OWASP recommends parameterized queries/prepared statements as the preferred protection against injection.
Accurate (86% confidence): Login tokens are generally safer in secure, HttpOnly cookies than in localStorage. Secure/HttpOnly cookies are recommended for many session tokens; localStorage is readable by JavaScript and is more exposed to XSS.
Accurate (98% confidence): Stripe webhooks should be verified before trusting them. Stripe documents signature verification as the correct way to authenticate webhook events.
Accurate (90% confidence): Basic security headers should be enabled on a web app. OWASP provides a dedicated HTTP security headers cheat sheet recommending common protective headers.
Accurate (97% confidence): An API should not return other users' information. OWASP access-control guidance emphasizes enforcing object-level authorization on every request.
Accurate (74% confidence): Your account, hosting, database, and domain should all have two-factor authentication enabled where supported. 2FA is widely recommended for administrative accounts, but the exact availability and implementation vary by service.