ASP.NET Core meets OWASP Top 10 2025
summary
Compares OWASP Top 10 2025 item by item and shows which risks ASP.NET Core actually mitigates: data protection API handles IVs/keys and authenticated encryption but requires explicit key storage to avoid production breaks; built-in anti-forgery plus same-site defends CSRF; authorization policies, resource-based checks and a RequireAssertion false fallback enable secure-by-default access control; SQL and XSS risk drop thanks to LINQ and automatic escaping; supply chain remains weak (example: a malicious NuGet source-generator risk); audit logging and transactional error flows still need custom design.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:10OWASP Top 10 2025 overview
- 3:16Broken access control
- 12:24Open redirects and CSRF
- 20:11Security misconfiguration
- 21:58Supply chain failures
- 26:53Cryptographic failures
- 34:01Injection vulnerabilities
- 38:15Insecure design
- 40:47Authentication failures
- 44:39Integrity failures
- 46:56Logging limitations
- 51:08Exception handling
- 55:24Final verdict and Q&A
related talks
54mASP.NET Core Meets Owasp Top 10
52mSecuring Web Applications and APIs with ASP.NET Core 2.2 and 3.0
39mA guided tour of ASP.NET core security
58mSecurity in ASP.NET Core 2.0
01h 03mSecuring Web Applications and APIs with ASP.NET Core 2.2 and 3.0
47mAPIs Exposed!
01h 00mWeb Application Security Risks: A Look at OWASP Top Ten 2017
50mAttack Mitigation Mechanisms in ASP.NET Core
