<p>Your security department wants you to do this to make the server type harder to identify. This may lessen the barrage of automated hacking tools and make it more difficult for people to break into the server.</p>
<p>Within IIS, open the web site properties, then go to the HTTP Headers tab. Most of the X- headers can be found and removed here. This can be done for individual sites, or for the entire server (modify the properties for the Web Sites object in the tree).</p>
<p>For the Server header, on IIS6 you can use Microsoft’s <a href="https://docs.microsoft.com/en-us/iis/extensions/working-with-urlscan/urlscan-3-reference">URLScan</a> tool to remote that. Port 80 Software also makes a product called <a href="http://www.port80software.com/products/servermask/">ServerMask</a> that will take care of that, and a lot more, for you.</p>
<p>For IIS7 (and higher), you can use the <a href="https://www.iis.net/downloads/microsoft/url-rewrite">URL Rewrite Module</a> to rewrite the server header or blank it’s value. In web.config (at a site or the server as a whole), add this content after the URL Rewrite Module has been installed:</p>
<pre><code class="lang-auto"><rewrite>
<outboundRules rewriteBeforeCache="true">
<rule name="Remove Server header">
<match serverVariable="RESPONSE_Server" pattern=".+" />
<action type="Rewrite" value="" />
</rule>
</outboundRules>
</rewrite>
</code></pre>
<p>You can put a custom value into the rewrite action if you’d like. This sample sourced from <a href="https://www.saotn.org/remove-iis-server-version-http-response-header/">this article</a> which also has other great information.</p>
<p>For the MVC header, in Global.asax:</p>
<pre><code class="lang-auto">MvcHandler.DisableMvcResponseHeader = true;
</code></pre>
<p>Edited 11-12-2019 to update the IIS7 info since the TechNet blog link was no longer valid.</p>