Broadcasting your Web server's identity allows intruders to complete their first task -- identifying your operating system, Web server, and application technology.
ServerMask modifies your IIS Web server's "fingerprint" by removing unnecessary HTTP header data and adjusting other response information.
Successful anti-reconnaissance makes it more likely attackers will try the wrong exploits first and be snared by firewalls and intrusion detection systems. ServerMask augments these defenses to build more secure networks, return better results on security audits, and mitigate the risk of attack.
ServerMask is already protecting thousands of customers around the world, including financial institutions, governments, and Fortune 1000 companies.
With easy installation and configuration in minutes, secure your Microsoft IIS Web servers by downloading ServerMask today.
ServerMask is fully COMPATIBLE with IIS 4, 5, and 6, IIS Lockdown, URLScan, FrontPage, Outlook Web Access, and major scripting platforms like ASP, ASP.NET, ColdFusion, PHP, JSP, and Perl. ServerMask is available for a free, fully functional 30-day trial.
New in v4.0 (Released Dec. 2008)
* Application-layer error suppression for PCI compliance
* Completely redesigned user interface, featuring 100% managed code
* Multiple default profiles and the ability to create custom profiles
* Per-site configuration, allowing unique settings to be applied per domain
* 64-bit support
* Auto-generated decoy cookies and headers
* One-to-many cookie masking
* Customizable HTTP error messages (CustomError functionality)
* Mask the Server name header in a number of ways:
o Remove altogether
o Replace with one of 30 other Web server signatures
o Replace with one a custom server name you create
o Select multiple false Web server signatures and randomize the response (you select how often a response is refreshed).
* Emulate Apache's HTTP header order
* Emulate the eTag and allow header formats of non-IIS servers
* Remove unnecessary HTTP headers, such as Public, X-Powered-By and others
* Rewrite identifying session cookie names such as ASPSessionID and ASP.NET_SessionId using one or more alternative names; fabricate decoy cookies to further confuse attackers
* Rewrite 404 and application-layer errors for PCI compliance; suppress info leakage by converting 500-range errors to 404 errors, then presenting custom 404 responses (CustomError functionality)
* Remove identifying file extensions such as .asp, .aspx and other Microsoft technologies from source code and URL display
IIS 4, 5, 5.1, or 6.0 and Windows NT, 2000, XP, or Server 2003