When you access the Alert Logic Managed Web Application Firewall (WAF) web management interface the first time, you must add your websites and test the website proxy. After you configure and test your websites, the test attack should register in the deny log.
- In the Alert Logic Console, click Configuration, and then click the web application firewall (WAF).
- In the left navigation pane, click Appliances.
- In the item row of your appliance, click Manage Appliance.
- On the Manage Appliance page, in the left navigation pane, under Services, click Websites.
- On the Websites page, click Add Website.
- On the Add Website page, in the Deployment list, select either Reverse proxy or Routing proxy. For routing proxy deployments, make sure that IP forwarding is enabled. Under Services, click Network, and then under Network routing, select Enable IP forwarding.
- On the Add Website page, in the Web Server Protocol list, select one of the following:
- HTTP: Creates a website proxy that responds to HTTP requests.
- HTTPS: Creates a website proxy that responds to HTTPS requests. This will generate a temporary SSL certificate.
- Both: Creates a website proxy that responds to HTTP and HTTPS requests. This will generate a temporary SSL certificate. Click Manage your SSL Certificates to learn how to upload your own certificate.
- In Web server domain name, type the address of the website you want to protect. This address should be identical to the address users use to view your website in a browser.
- In the Listen IP section, perform one of the following actions to add IP addresses to the Active Listen list:
- Select one or more IPs, and then click Add.
- If the left column lists multiple IP addresses, you can select All Inbound, and then click Add to listen to all IP addresses.
- Select one or more IPs, and then click Add.
- HTTP(S) listen port field, type the port for the website you want listen to. The default ports are as follows:
- HTTP: 80
- HTTPS: 443
When enabled, the virtual host respond s to all requests for virtual hosts that are not otherwise configured for this IP address. The test your website proxy topic assumes is that this option is selected. This behavior is convenient for testing since it sends any request that is not a policy violation to the backend web server.
- In the Real web server protocol list, select the protocol you want Managed WAF to use to connect to the backend web server. If you want traffic to the backend web server(s) to be encrypted, change the protocol to http or both (for dual protocol configuration).
- Select Validate real servers.
Managed WAF sends an HTTP request to the backend web server on the port configured to verify that the server is live and responding to HTTP requests. If the server is not yet running, clear the check box.
- In Real server IP or public domain name, type the private IP address or DNS name the web server is listening to.
- In the Port field, type the port the web server is listening to. The default ports are as follows:
- HTTP: 80
- HTTPS: 443
- In the Role list, select one of the following:
- ActiveForwards requests to the backend web server
- Backup: Forwards requests to the backend web server if no other servers are active
- Down: Does not forward requests to the backend web server
- Under Initial configuration, select one of the following configurations to apply to the website proxy:
- WAF Default
- Load Balancer
- Click Save Configuration, and then click Apply changes.
Once you have added a website, you can test whether Managed WAF can connect to the backend web server. You can also test Managed WAF in Detect mode and Protect mode.
The following walkthrough assumes you have configured your website to be used as the default virtual host for the listen IP. You should also make sure that your website proxy is in Detect mode. You can change these settings after testing.
To set your website proxy in Detect mode, on the Websites page, for the website you want to test, in the Mode column, select Detect.
In your web browser's address bar, type your public IP. The browser should open the default website for your backend web server.
This test will not affect production traffic.
In your browser's address bar, type your public IP followed by "/?x=a%00" and press Enter (e.g. 188.8.131.52/?x=a%00). The browser should open the default website for your backend web server, however, this attack should be registered on the Deny log as a DOS attempt.
On the Websites page, click in the main menu, point to Log, and click Deny Log.
Attacks on your website proxy are registered here.
To view details of any Deny log entry, click the Details icon ().
Once you have tested the connectivity and Detect mode for your website, the next step is to test the Protect mode.
To test Protect mode:
- On the Websites page, for the website you want to test, in the Mode column, select Protect.
- In your browser's address bar, type your public (Elastic) IP followed by "/?x=a%00" and press Enter (e.g. 184.108.40.206/?x=a%00). The browser should show a 404 error message. This attack should also be registered on the Deny log as a DOS attempt.
When a website is first created, the default security policy is signature based. As the Learner maps the website, the policy shifts toward a positive security model for specific applications. The Learner analyzes incoming static requests, web applications, and input parameters to build a complete profile of the website.
To avoid learning from worms, attacks, and other unauthorized access, the Learner employs a combination of heuristic attack classification, statistics, and server responses.
When learning is enabled for the website, the Learner works in asynchronous mode to process a queue of traffic samples between 10,000 and 200,000 requests each. For each sample processed, the Learner builds a trial policy, compares it to the former trial policy, and records the number of changes. Once the continuous processed samples result in no change between trials, the learned policy is stable enough to commit to the WAF.
It is possible to have Managed WAF run in Protect mode while learning. This starts signature-based protection against known attacks. While this provides immediate protection, friendly traffic may be blocked if you start Managed WAF in Protect mode without a learning period.
The Websites page contains your Websites list. On this list, you will find all websites configured on your Managed WAF appliance.
To open the Websites page:
In the Managed WAF application, in the left navigation, under Services, click Websites.
Each website in the list is a proxy service that listens for incoming traffic for specific virtual host names (e.g. www.example.com). It then proxies it to the backend Real web server, which would typically be one or more web servers running in your VPC.
The Blackhole is the first in the Websites list. Managed WAFuses it to respond to requests for domain names that your other websites are not configured to listen to. These requests are blocked and logged in the deny log of the website proxy named, "Blackhole." This way of blocking requests for unknown host names automatically stops most attack probes from automated agents that traverse an entire IP range looking for vulnerable hosts.
Website proxies other than the Blackhole proxy can be configured to be the default website proxy for unknown host names. This allows the blocking from the Blackhole website proxy to be overridden.
|ID||The ID for the website, also indicates the sequence number of added websites.|
|Name||The internal name you give your website proxy.|
|Deploy||The proxy deployment mode. For Amazon Web Services, only Reverse proxies are allowed.|
|Virtual web server||The domain name and port number combination for the website you want protected.|
|Listens to||The IP address bound to the virtual host.|
|Real web server||The domain name for your backend web server.|
|Mode||Blocking mode. You can select either Detect, Protect, or Pass mode.|
On the Websites list, you can select a Block mode for your website. This determines how Managed WAF monitors your website traffic.
This mode blocks and logs all violations according to the access policy.
In the default Detect mode preset, only logging occurs and no blocking protection is activated. Blocking protection that would occur in Protect mode is logged and available for review in the deny log. Operating in the default detect preset is comparable to an intrusion detection system (IDS)—it detects and logs activities but does not protect or prevent policy violations.
When the WAF is first deployed in front of a production website, the recommended initial mode is Detect while the initial tuning takes place. This is the default mode when the WAF configuration is selected when creating the website.
In Pass mode, all requests are passed through the website proxy. No requests are blocked and no logging is performed. This mode is not configurable because no filters are active in this mode.