The attacker floods a public endpoint with network traffic, or sends HTTP requests at a rate or pattern that exhausts the application behind an OCI load balancer or API Gateway. Oracle scrubs layer 3 and 4 floods on its own, so find the layer 7 request pattern, block or rate-limit it in a web application firewall (WAF) policy, and keep the back ends up.
Look here
Log
Search for
WAF log, category all (enable it on the WAF firewall resource)
Top client addresses and countries. For the top sources, check data.action, data.request.path and data.requestProtection.matchedRules: search "<compartment-ocid>/<log-group-ocid>/<log-ocid>" | summarize count() as cnt by data.clientAddr, data.countryCode | sort by cnt desc
Load balancer access log (enable on the load balancer)
Top requests and user agents. data.clientAdd contains the client address and port, and data.forwardedForAddr the forwarded address: search "<compartment-ocid>/<log-group-ocid>/<log-ocid>" | summarize count() as cnt by data.request, data.userAgent | sort by cnt desc
Load balancer error log
Back-end timeouts and connection errors that show the application failing. Compare data.lbStatusCode with data.backendStatusCode in the access log
VCN flow logs on the network load balancer or the subnet
Top source addresses on the target port. A network load balancer has no access log: search "<compartment-ocid>/<log-group-ocid>/<log-ocid>" | where data.destinationPort = <port> | summarize count() as cnt by data.sourceAddress | sort by cnt desc
Audit, WAF and edge changes
Protection removed during the attack by someone with Console access: UpdateWebAppFirewallPolicy, DeleteWebAppFirewall, DeleteWebAppFirewallPolicy, UpdateNetworkAddressList, StopLogging
Current state
The policy's rate limiting and access control rules, in request-rate-limiting and request-access-control: oci waf web-app-firewall-policy get --web-app-firewall-policy-id <ocid>
Contain
#
Item
1
Enable the WAF log and the load balancer access and error logs now if they were off. Save a sample of attack requests as evidence
2
Attach a WAF policy to an unprotected load balancer: oci waf web-app-firewall create-for-load-balancer --compartment-id <ocid> --load-balancer-id <ocid> --web-app-firewall-policy-id <ocid>
3
Add a rate limiting rule. The file contains a rule with requestsLimit, periodInSeconds, actionDurationInSeconds and an action name, and the limit applies to each client IP address: oci waf web-app-firewall-policy update --web-app-firewall-policy-id <ocid> --request-rate-limiting file://rate.json
4
Block attack source ranges with a request access control rule and a Return HTTP response action. Use a condition such as: address_in(connection.source.address, ['<cidr>'])
5
Block attack countries or user agents the same way. Countries match on connection.source.geo.countryCode, and user agents on a condition such as: i_contains(http.request.headers."user-agent", '<value>')
6
Set a rate limit on API Gateway deployments. In the specification, set requestPolicies.rateLimiting with rateKey, CLIENT_IP and a rateInRequestsPerSecond value: oci api-gateway deployment update --deployment-id <ocid> --specification file://spec.json
7
If legitimate traffic is being dropped, raise the flexible load balancer's maximum bandwidth. Existing connections can drop during the change: oci lb load-balancer update-load-balancer-shape --load-balancer-id <ocid> --shape-name Flexible --shape-details file://shape.json
8
Report the attack through My Oracle Support and select the WAF product. Include the target IP addresses, times and sample requests
Eradicate and recover
#
Item
1
Replace broad blocks with narrow rules once the pattern is clear, and review blocked legitimate clients in the WAF log
2
Move the rules into infrastructure as code and keep a tested rate limiting rule in every public WAF policy
3
Create Monitoring alarms on request volume for each public load balancer and WAF policy
4
Remove public IP addresses from back ends so traffic reaches them only through the load balancer. Open OCI DNS records if names still point at retired endpoints
5
Ask your customer success manager about credits for excess consumption caused by the attack
6
Record the timeline, peak rates and customer impact for the Recover review
Watch out
Oracle manages layer 3 and 4 distributed denial-of-service (DDoS) protection for all customers, and customers cannot configure it. Reporting the attack through My Oracle Support is your responsibility.
An API Gateway rate limit applies to every route in the deployment. A limit set for the hottest route also throttles the others.
A WAF rate limiting rule counts requests for each client IP address. A botnet with many addresses can stay under the limit, so pair it with access control rules on path, country or user agent.
Oracle documentation: overview of Web Application Firewall, adding a rate limiting rule, understanding conditions, adding a firewall to a WAF policy, layer 7 DDoS mitigation, understand the DDoS layers, details for WAF logs, details for load balancer logs, VCN flow logs, details for VCN flow logs, WAF IAM policy details, limiting the number of requests to API Gateway back ends, OCI CLI reference for waf web-app-firewall-policy update, api-gateway deployment update and lb load-balancer update-load-balancer-shape. Checked September 2026. Rechecked October 2026: every command against OCI CLI 3.94.2, and the --shape-name allowed values in the CLI reference, which list Flexible.