The a HTTP module is used when you need to intercept and examine the incoming HTTP requests before or after the page life cycle. The HTTPModule provides events where you can plug into to examine or alter the request or response within the asp.net cycle. HTTPModule are the perfect place the apply security checks.
HTTP headers leak technical information to potential attackers about a system. To harden the security of an application you need to disclose as little information about a system as possible. In this post I will show to remove the Asp.net version from HTTP server header responses.
As in .net framework it is just as important to adjust the Asp.net core security headers to harden the security posture of your web application.
Securing a website with HTTPS in Asp.net core is a bit different than with normal asp.net in IIS. In this post I will show to configure asp.net core so that it uses HTTPS.
I wrote this small single file aspx utility that can be dropped in a asp.net website. The utility will allow the user to view the claims within the token.
It can often be a problem to trace problems with SAML as WS-Federation. Here are some plugins that I have found that can make your live easier.
When it comes to access control in asp.net we are all familiar with the access control elements found in the web.config. Below I will cover the best way to secure a website with the authorization element?
Within the enterprise arena it is common to have a Identity provider for the organization. In this post I have a brief look at the industry standard protocols.
Custom error pages are used to hide technical information from end users. Often default error pages can leak technical information to potential attackers. In this post Ill show how to implement custom error pages for IIS and Asp.net to assist with hardening the security of a system.
TLS 1.3 is out and its time to take note and plan the retirement of TLS 1.2.