Skip to main content

HSTS in IIS

In our continuous effort to improve the security of the solutions we build, we activated HSTS at one of our clients. However I noticed that there was a lack of understanding on what HSTS exactly is and how it helps to improve security. Hence this blog post.

What is HSTS?

Let’s ask Wikipedia:

HTTP Strict Transport Security (HSTS) is a policy mechanism that helps to protect websites against man-in-the-middle attacks such as protocol downgrade attacks and cookie hijacking. It allows web servers to declare that web browsers (or other complying user agents) should automatically interact with it using only HTTPS connections.

In short HSTS tells a browser to only access a site through HTTPS.

Enabling HSTS in IIS

Let me first show you to enable it in IIS before I get into more detail.

  • Open IIS (InetMgr)

  • Click on the website where you want to activate HSTS.
    • Remark: HSTS is always activated at the site level.

    • On the Manage Website section, click on HSTS…
    • On the Edit Website HSTS they are multiple values we can configure after checking the Enable checkbox:
      • Max-Age: The amount of time in seconds that this website will be served over HTTPS
      • IncludeSubDomains: Specify if HSTS should apply to all subdomains as well
      • Preload: It is possible to make your domain part of a preload list. By doing this you are sure that browsers will connect to your domain only via secure connections. (This is not directly part of the HSTS specification and only applies when Max-Age is at least 1 year and IncludeSubDomains is set to true)
      • Redirect Http to Https: Enable this to let IIS redirect from HTTP to HTTPS when visiting this site

    More information: IIS 10.0 Version 1709 HTTP Strict Transport Security (HSTS) Support | Microsoft Learn

    What HSTS doesn’t do…

    After activating HSTS I noticed that there was some confusion on what HSTS exactly does and how it works.

    If you visit a website using HTTP, no HSTS response header is returned and nothing happens. It is only AFTER you have visited the website using HTTPS that HSTS will kick in. I really want to emphasize this because I noticed that this was not what some people expected.

    This means that either the user has directly browsed to the website using HTTPS or he/she is redirect to the HTTPS version. This can be done for example through the URL Rewrite Module in IIS or by selecting the ‘Redirect Http to Https’ checkbox as mentioned above.

    Now the browser will remember for the max-age specified that this site should be served from HTTPS. So if you attempt to browse to the HTTP endpoint, the browser itself will rewrite the url to use the HTTPS endpoint and no connection is made over HTTP.

    Also be aware that HSTS won’t let you click through certificate warnings. So, if the certificate is not correct, HSTS won’t work.

    Hope that helps…

    Labels:

    Popular posts from this blog

    Podman– Command execution failed with exit code 125

    After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
    Read more

    Cache stampede: when our cache turned against us

    While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
    Read more

    A complex system designed from scratch never works

    A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...
    Read more