AQTRONIX WebKnight - Application Firewall for Web Servers

• What is it?
• Features
• Install
• Contact
• Copyright
• Latest information
• FAQ

What is it?

AQTRONIX WebKnight is an application firewall for IIS and other web servers and is released under the GNU General Public License. More particularly it is an ISAPI filter that secures your web server by blocking certain requests. If an alert is triggered WebKnight will take over and protect the web server. It does this by scanning all requests and processing them based on filter rules, set by the administrator. These rules are not based on a database of attack signatures that require regular updates. Instead WebKnight uses security filters as buffer overflow, SQL injection, directory traversal, character encoding and other attacks. This way WebKnight can protect your server against all known and unknown attacks. Because WebKnight is an ISAPI filter it has the advantage of working closely with the web server, this way it can do more than other firewalls and intrusion detection systems, like scanning encrypted traffic and blocking unwanted requests.

-Top-

Features

These are some features of WebKnight.

• Open Source
  WebKnight is free software under the terms of the GNU General Public License.
• Logging
  By default all blocked requests are logged. In addition all allowed requests can be logged as well, or you can run WebKnight in logging only mode. This last operation mode allows you to see the attacks in the log files without blocking them. WebKnight can also prevent blocked attacks from being logged to the web server log files. This way your web server log files will be kept clean and accurate.
• Customizable
  The firewall can be customized for any need, including blocking certain 0-day exploits before the vendor released a patch.
• Compatible with Web-Based Applications
  WebKnight is compatible with Frontpage Extensions, WebDAV, Flash, Cold Fusion, Outlook Web Access, Outlook Mobile Access, SharePoint...
• HTTP Error Logging
  WebKnight can be configured to log the HTTP errors from the web server. This way you can log common errors like '404 Not Found' or more severe ones like '500 Server Error' to the logfile. Doing so allows you to detect errors in scripts or attacks on them. You can also use it to simply find broken links in your web site or configuration mistakes.
• SSL Protection
  Unlike traditional firewalls, WebKnight can protect encrypted sessions over HTTPS.
• Third-Party Application Protection
  WebKnight not only protects the web server, but can also be configured to protect third-party web server applications, e-commerce web sites or your custom web site.
• RFC compliant
  WebKnight is RFC compliant and also includes the ability to scan the requests for RFC compliance.
• Low Total Cost of Ownership (TCO)
  WebKnight comes with a Windows Installer package and remote installation scripts making it easy to deploy WebKnight in your enterprise. WebKnight also comes with a graphical user interface for changing WebKnight settings.
• Run-Time Update
  Changes to the settings of WebKnight do not require restarting the web server and can thus be done without disrupting any services for your users. For performance reasons, detecting these changes only occurs every 1 minute.

• Improved scanning
  The scanning engine has been improved and extended. It is now also possible to scan the Referrer header and User Agent header for certain exploits or data.
• Authentication scanning
  Authentication scanning allows to scan for brute force attacks on accounts or DoS attacks on system accounts. It can also scan for weak passwords.
• Connection control/monitoring
  You can block or monitor traffic coming from certain ip addresses or ranges. You can also monitor access to certain important files or limit the number of requests coming from a single IP address.
• Blocking robots
  A large robot database makes it possible for blocking or only allowing certain types of robots. It is also possible to set up a bot trap for bad robots and to block aggressive robots.
• Prevent hot linking
  Hot linking or direct linking to certain types of files (like images or file downloads), can be prevented.

-Top-

How to install

Installation in IIS with Windows Installer: (for IIS 6.0 see note below!)

Double click the file WebKnight.msi. This will launch Windows Installer and install WebKnight on the local machine. This method will install WebKnight as a global filter on the local machine. If Windows Installer is not installed on your system, you can download it directly from Microsoft:
Windows Installer 2.0 Redistributable for Windows NT 4.0 and 2000
Windows Installer 2.0 Redistributable for Windows 95, 98, and Me

Installation in IIS with scripts:

To install/uninstall WebKnight on the local or remote machine you can use the file install.vbs/uninstall.vbs from the setup folder. This method will install WebKnight as a global filter on the selected host or localhost.

Manual installation as a global filter in IIS:

1. Copy all the files in the Setup folder to a local folder on the server (e.g. C:\Program Files\AQTRONIX WebKnight).
2. Open the IIS snap-in.
3. Right-click the server name (not the site name) (in IIS 6 right-click Web Sites) under Internet Information Services in the MMC, and then select Properties.
4. Verify that WWW Service is displayed in the Master Properties drop-down list, and click the Edit button. For IIS 6 go to next step.
5. Choose the ISAPI Filters tab, and then click the Add button.
6. In the Filter Properties window, type WebKnight, and enter the full path to WebKnight.dll in the Executable box.
7. Select OK to close each dialog.
8. Review any settings of WebKnight, by running config.exe that you copied locally.
9. Restart IIS.

Manual installation as a site filter in IIS:

1. Copy all the files in the Setup folder to a local folder on the server (e.g. C:\Program Files\AQTRONIX WebKnight\W3SVC1). Note: it is important to have a unique folder for each WebKnight installation!
2. Open the IIS snap-in.
3. Right-click the site name (not the server name) under Internet Information Services in the MMC, and then select Properties.
4. Choose the ISAPI Filters tab, and then click the Add button.
5. In the Filter Properties window, type WebKnight, and enter the full path to WebKnight.dll in the Executable box.
6. Select OK to close each dialog.
7. Review any settings of WebKnight, by running config.exe that you copied locally. (Make sure global filter capabilities are disabled: uncheck 'Is Installed As Global Filter')
8. For IIS 6 you need to make sure that each site for which you installed WebKnight as a site filter, has its own application pool. This is because only one instance of WebKnight can be run in any application pool. By default all sites are run in the DefaultAppPool and can only contain one instance of WebKnight, so you can only have one site filter, unless you specify a different application pool for any additional site on which you are running WebKnight as a site filter.
9. Restart IIS.

If you want to import your settings from urlscan, you can do that by copying the file urlscan.ini to the WebKnight directory. Delete WebKnight.xml (or rename it) and your settings from urlscan.ini will be imported in a new WebKnight.xml file when you restart your web server. This can be useful if you experienced problems with your urlscan installation and you had to customize the settings of urlscan and want to keep using these settings. If you want to load the default settings again, you can do that by deleting the files WebKnight.xml and urlscan.ini in the directory WebKnight and a new WebKnight.xml will be made with the default settings when you restart your web server.

Installation in IIS 6.0: to run WebKnight as a global filter in IIS 6.0, you have two options:

1. Run IIS in IIS 5.0 Isolation mode (recommended)
2. Continue running IIS in worker process mode but without the global filtering capabilities of WebKnight, and you need a unique log file per process. So you have to make sure you:
   • uncheck 'Is Installed As Global Filter' under Global Filter Capabilities
   • check 'Per Process Logging' under Logging (each application pool will load its own instance of WebKnight, if you only have one pool, this is not required.)
   • Make sure the account NETWORK SERVICE (or whatever account(s) you set the application pool(s) to use) has change permission on the WebKnight folder and subfolders
   • Restart IIS after doing the above changes.

Non-IIS: Look at the documentation of your web server (Note: only web servers with ISAPI filter support can run WebKnight).

-Top-

Contact Information

Website: http://www.aqtronix.com/webknight

-Top-

Copyright

AQTRONIX WebKnight - ISAPI Filter for securing web servers
Copyright 2002-2007 Parcifal Aertssen

This file is part of AQTRONIX WebKnight.

AQTRONIX WebKnight is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License as
published by the Free Software Foundation; either version 2 of the
License, or (at your option) any later version.

AQTRONIX WebKnight is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with AQTRONIX WebKnight; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

-Top-