Oracle recently introduced a Web Application Firewall (WAF) to further enhance and secure Oracle Cloud Infrastructure offerings. The Oracle Cloud Infrastructure WAF is based on Oracle Zenedge and Oracle Dyn technologies. It inspects all traffic destined to your web application origin and identifies and blocks all malicious traffic. The WAF offers the following tools, which can be used on any website, regardless of where it is being hosted:
- Origin management
- Bot management
- Access control
- Over 250 robust protection rules that include the OWASP rulesets to protect against SQL injection, cross-site scripting, HTML injection, and more
In this post, I configure a set of access control WAF policies to a website. Access control defines explicit actions for requests that meet conditions based on URI, request headers, client IP address, or countries and regions.
Conditions can use regular expression and list comparison tools. Actions can be detections or blocks. The website that I use is ‘www.denzura.com’, previously created with Oracle Cloud Infrastructure Edge DNS services.
Create a WAF Policy Zone
- Sign in to your tenancy in the Oracle Cloud Infrastructure Console.
- Open the navigation menu. Under Solutions, Platform and Edge, go to Edge Services and click WAF Policies.
- Select a compartment for your WAF policy to reside in. If one is preselected, ensure that you want your WAF policy to reside there, or select another compartment.
- Click Create WAF Policy.
- For the policy name, enter a unique name for the policy (this example uses MyWAF).
- In the Domains section, for Primary Domain enter the naked domain of your website (this example uses denzura.com). In the Additional Domains field, enter a third-level domain. The default or the most commonly used third-level domain is www, which is what I’m using. The complete example entry to this field is ‘www.denzura.com’. If you want to add additional domains, click Additional Domain.
Note: The Additional Domains field hosts the subdomains where the policies are applied.
- In the WAF Origin section, for Origin Name, enter a name that is unique in your tenancy. The example in this post is DenzuraWAF.
- For the URI field, use either an IPv4 address or an FQDN. In this example, I’m using the IP address of the website: 126.96.36.199.
Note: For this example, I’m not using Advanced Origin Options or Tagging.
- Click Create WAF Policy.
In a few minutes, the policy is created.
Notice the message that indicates to visit your DNS provider.
In this example, I added the third-level domain www to the CNAME record that was output by the WAF Policy.
Add CNAME Record to your DNS Zone
The following instructions are for DNS zone management in Oracle Cloud Infrastructure Edge services. If your DNS zone is outside of Oracle Cloud Infrastructure, follow your provider instructions.
- Open the navigation menu in the Console. Under Solutions, Platform and Edge, go to Edge Services and click DNS Zone Management.
- Select your zone name (in this example, Denzura.com).
- Click Add Record.
- In the Add Record dialog box, select the CNAME record from the list.
- In the Name field, enter www.
- In the TTL (Time To Live) field, enter a value in milliseconds (for example, 10).
- Leave the RDATA field as basic.
- In the Target field, paste the CNAME string that resulted by adding your WAF policy. The string in this example is denzura-com.b.waas.oci.oraclecloud.net.
- Click Submit.
- Click Publish Changes.
After the policy becomes active, verify that the WAF is serving the website.
Verify WAF coverage.
- Open a web browser (this example is using Google Chrome).
- Enter the web address of your domain name (for example, ‘www.denzura.com’).
- When the website is displayed, right-click and select Inspect.
- Click the Network tab.
- Click All.
- In the Name column, select ‘www.denzura.com’.
- Click the Headers tab.
The Server field should display ZENEDGE. This indicates that your website is being inspected by Oracle Cloud Infrastructure WAF.
Configure WAF Access Control rules
Now it’s time to create the access control rules. In this example, I block all traffic coming from the USA, with the exception of one IP address. To prove that the access control works, I access the ‘www.denzura.com’ website from a host located in the US and verify that access is blocked and that a custom message is displayed. Then I access the website from that one exception and verify that it loads normally. Finally, I access the same website from an Oracle Cloud Infrastructure Windows instance located in the Frankfurt region, with the IP address 188.8.131.52, and verify that it loads normally.
- Open the navigation menu in the Console. Under Solutions, Platform and Edge, go to Edge Services and click WAF Policies.
- Open the policy that you created (in this example, DenzuraWAF).
- Click Access Control.
- Click Add Access Rule.
- Enter a unique name for the access rule (in this example, Cease_and_Desist).
- Under Conditions, select Country/Region is from the Rule Conditions menu.
- From the Country/Region menu, select United States.
- Click Additional Condition.
- From the Rule Conditions menu, select IP Address in not.
- Enter the IP address from a host located anywhere in the US that will be the one exception for accessing the website (in this example, 146.140.71).
- Under Action, select Block.
- Under Block Action, select Show Error Response.
- As needed, customize the messages that open. In this post, I’ll modify the Block Error Page Description with the following message: “Access blocked by website owner. CEASE AND DESIST.”
- Click Add Access Rule.
- Under WAF Policy, click Unpublished Changes.
- Click Publish All. In the Publish Changes dialog box, click Publish All.
Access your website.
It takes about 10 minutes for a WAF policy access control rule to become active. After it does, test the policy by accessing the website: www.denzura.com
Both the exception and the host in the Frankfurt region work; the website can be accessed as expected. You can download screenshots that show this access from https://bit.ly/2PdSXCX. They are hosted in Oracle Cloud Infrastructure Object Storage, and the link will be active until December 31, 2020.