The access rules applied to the Web Application Firewall. Access rules allow custom content access policies to be defined and {@code ALLOW}, {@code DETECT}, or {@code BLOCK} actions to be taken on a request when specified criteria are met.
The settings used to limit the number of requests from an IP address.
A list of caching rules applied to the web application.
A list of CAPTCHA challenge settings. CAPTCHAs challenge requests to ensure a human is attempting to reach the specified URL and not a bot.
A list of the custom protection rule OCIDs and their actions.
The device fingerprint challenge settings. Blocks bots based on unique device fingerprint information.
The human interaction challenge settings. Detects natural human interactions such as mouse movements, time on site, and page scrolling to identify bots.
The JavaScript challenge settings. Blocks bots by challenging requests from browsers that have no JavaScript support.
The key in the map of origins referencing the origin used for the Web Application Firewall. The origin must already be included in {@code Origins}. Required when creating the {@code WafConfig} resource, but is not required upon updating the configuration.
The map of origin groups and their keys used to associate origins to the {@code wafConfig}. Origin groups allow you to apply weights to groups of origins for load balancing purposes. Origins with higher weights will receive larger proportions of client requests. To add additional origins to your WAAS policy, update the {@code origins} field of a {@code UpdateWaasPolicy} request.
The settings applied to protection rules.
A list of IP addresses that bypass the Web Application Firewall.
The Web Application Firewall configuration for the WAAS policy creation.