- OWASP Top Ten vulnerabilities
- Cross-site scripting
- SQL injection
- Cross-site request forgery
- Storing secrets
- Encrypting Web.config settings
- Password hashing
- Authenticating in the app
- Securing cookies and sessions
- Error handling
Skill Level Intermediate
- [Christian] According to a recent study, nine out of 10 web applications have security vulnerabilities. Most of the time, it's the developer's fault, unfortunately. In other words, making a web application secure seems to be virtually impossible. Fortunately, there is hope. ASP.net comes with some built-in security features, some that are activated by default, but some need configuration, or even some coding to work. These security features are countermeasures for the most common and dangerous attacks. As you will see, ASP.net is highly configurable in terms of web application security. In this LinkedIn Learning course, I dive into all the risks and ASP.net application phases and how developers can mitigate them. My name is Christian Wenz. I started with web application security in the late 1990s and never looked back. Join me in making web applications more secure. Let's get started.
ASP.NET MVC: HTTP Request Life Cyclewith Janan Siam2h 32m Advanced
1. Mitigating Common Attacks
2. Storing Data
3. Starting with IdentityServer
4. Secure Configuration
Next steps2m 23s
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.Cancel
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.