Remember to modify your "hosts" file to create a realistic test environment. Click here for details.

Be sure to start a new browser session after editing the "hosts" file as many browsers cache domain resolutions. You want to make sure the browser uses the localhost IP address, not the one published in DNS.

It is also a good idea to clear the browser document cache as well.

Refer to the "Evaluation Installation Examples" section in the User Guide ("Start->Programs->webScurity->webApp.secure PE->User Guide") for example installation scenarios to evaluate webApp.secure.

To verify webApp.secure is working properly in terms of blocking activity that is not allowed, simply enter a URL that you know is not legitimate for the Web site ("http://www.MyDomainName.com/aaa.bbb" for example) into the browser's address bar.

A "403 Forbidden" error indicates webApp.secure successfully blocked the request. Not because it matches a known attack signature, but because it simply does not meet the Intended Use Guidelines™ of the Web site.

If you have any questions and/or comments, please do not hesitate to contact us.

webScurity Inc. 9298 Central Ave NE Suite 402 Minneapolis MN 55434 USA

866-SCURITY (728-7489) Toll Free (USA) +1 763-786-2009 Twin Cities Metro/International +1 763-786-3680 Fax support@webscurity.com Email