Study guide

12.1 OCI Web Application Firewall: Policies, Modules, Actions & Enforcement Points

OCI 2026 Architect Professional 1Z0-997-26

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Architecture Foundations

1.1 Exam Logistics, the 2026 Blueprint & How to Use This Guide 1.2 The OCI Well-Architected Framework & Architectural Tradeoffs

2 Chapter 2: High Availability & Resilient Design

2.1 Availability Domains, Fault Domains, Instance Pools & Load Balancers 2.2 OCI DNS Traffic Steering, Geolocation & Health Checks 2.3 Block Volume Replication, Volume Groups & Backup Policies 2.4 Object Storage Replication, Versioning & Retention Rules (WORM)

3 Chapter 3: Full Stack Disaster Recovery

3.1 Full Stack Disaster Recovery: Protection Groups, Members & Permissions 3.2 DR Plans: Switchover, Failover, Prechecks & Plan Execution 3.3 DR Drills, Plan Customization & Operational Readiness

4 Chapter 4: Container Instances, OCIR & OCI DevOps

4.1 Containerization, Microservices & OCI Container Instances 4.2 OCI Container Registry: Repositories, Push & Pull, and Image Management 4.3 OCI DevOps: Code Repositories, Build Pipelines & Deployment Strategies

5 Chapter 5: OCI Kubernetes Engine (OKE)

5.1 OKE Cluster Types, Node Options & Cluster Creation 5.2 OKE Networking: VCN-Native Pod Networking vs. Flannel, Subnet Sizing & Load Balancers 5.3 OKE Workload Identity, Secrets & Persistent Storage

6 Chapter 6: Serverless Functions & API Gateway

6.1 OCI Functions: Concepts, Invocation Modes, Integrations & Image Security 6.2 API Gateway: Authentication, JWT Validation, Rate Limiting & Usage Plans

7 Chapter 7: Messaging & Event-Driven Design

7.1 OCI Streaming, OCI Queue & Messaging Patterns for Microservices 7.2 OCI Events, Event Rules & OCI Notifications Fan-Out

8 Chapter 8: Infrastructure as Code with Terraform & Resource Manager

8.1 Infrastructure as Code with Terraform and the OCI Provider 8.2 OCI Resource Manager: Stacks, Jobs, Drift Detection & Private Endpoints

9 Chapter 9: Identity & Multi-Tenancy Governance

9.1 IAM Policy Design: Verbs, Conditions, Dynamic Groups & Principals 9.2 Organizations Management, Governance Rules & Compartment Quotas

10 Chapter 10: Security Posture with Cloud Guard & Security Zones

10.1 Cloud Guard: Detector Recipes, Problems, Scores & Responders 10.2 Security Zones & Vulnerability Scanning

11 Chapter 11: Secure Access & Network Protection

11.1 Layered Network Security: Security Lists, NSGs & Private Access to Services 11.2 OCI Bastion: Managed SSH, Port Forwarding & SOCKS5 Sessions 11.3 Zero Trust Packet Routing (ZPR): Security Attributes & Intent-Based Policy 11.4 OCI Network Firewall: Policies, Inspection Routing, Tunnel Inspection & Private NAT

12 Chapter 12: Application & Data Protection: WAF, Certificates & Vault

12.1 OCI Web Application Firewall: Policies, Modules, Actions & Enforcement Points 12.2 OCI Certificates: Private CAs, TLS Certificates, Renewal & Integrations 12.3 OCI Vault Key Management: Vault Types, Protection Modes, Dedicated KMS & External KMS 12.4 Vault Secrets: Versions, Rotation States, Automatic Generation & Rotation

13 Chapter 13: Base Database Service & Autonomous AI Database

13.1 Base Database Service: DB Systems, RAC, Data Guard, Cloning & Maintenance 13.2 Autonomous AI Database: Workload Types, Deployment Options, Services & Connectivity 13.3 Operating Autonomous AI Database: Scaling, Cloning, Backups, Patching & Self-Tuning 13.4 Autonomous Data Guard & Backup-Based Disaster Recovery for Autonomous AI Database

14 Chapter 14: Recovery Service, Global Distribution & OCI Cache

14.1 Autonomous Recovery Service: Protection Policies, Real-Time Protection & Retention Lock 14.2 Globally Distributed Autonomous AI Database: Sharding, Data Placement & Replication 14.3 OCI Cache: Valkey and Redis Clusters, Sharding, Security & Cross-Region Replication

15 Chapter 15: Monitoring, Alarms & Notifications

15.1 OCI Monitoring: Metrics, Namespaces, Custom Metrics & Monitoring Query Language 15.2 Alarms & Notifications: Trigger Rules, Absence Alarms, Split Messages, Suppression & Delivery

16 Chapter 16: Logging, Audit, Connector Hub & Search

16.1 OCI Logging: Log Groups, Service Logs, Custom Logs & the Unified Monitoring Agent 16.2 Logging Search, the Logging Query Language & OCI Audit 16.3 Connector Hub: Moving Logs, Metrics, Queue Messages & Streams Between Services 16.4 OCI Search with OpenSearch & Resource Search for Observability

12.1 OCI Web Application Firewall: Policies, Modules, Actions & Enforcement Points

Key Takeaways Explain This Topic AI

A regional WAF policy works as a plug-in for an OCI load balancer, connected through a firewall resource that links the policy to the enforcement point.

An edge policy is a global solution that requires pointing DNS at an Oracle-provided CNAME and allowlisting Oracle edge nodes.

WAF actions are Allow, which skips the remaining rules in the current module, Check, which only logs, and Return HTTP response.

Each WAF rule condition is written as a JMESPath expression evaluated against the HTTP request or response.

Collaborative protection capabilities require several individual capabilities to match, weighted against a threshold, to reduce false positives.

Last updated: October 2026

Why WAF Is Separate From the Network Firewall

The Network Firewall inspects all kinds of IP traffic in a VCN. Web Application Firewall (WAF) focuses on HTTP and HTTPS requests to web applications. It understands URLs, headers, query strings, and bodies, so it can stop application-layer attacks such as cross-site scripting (XSS) , SQL injection , and other OWASP -defined vulnerabilities, apply access rules by geography or request signature, and rate-limit abusive clients. Oracle describes WAF as a PCI-compliant service.

Two Ways to Deploy WAF

Option Scope How traffic reaches it Typical use

WAF policy Regional Works as a plug-in for an OCI load balancer Applications already behind an OCI load balancer

Edge policy Global DNS points the application at an Oracle-provided CNAME , and the origin allowlists Oracle's edge nodes Global edge protection in front of an origin

There is no automated tool to convert an edge policy into a WAF policy or the reverse; you recreate the settings manually.

For the regional option, a firewall resource (a WAF resource, not the Network Firewall) is the logical link between a WAF policy and an enforcement point such as a load balancer.

WAF Policy Modules

A WAF policy is organized into modules that inspect different parts of the transaction:

Module What it does

Request access control Inspects request properties, such as source IP, country, path, or headers, and can return a defined HTTP response

Request rate limiting Inspects connection properties and limits the frequency of requests for a key, such as each client IP

Request protection Enables OCI-managed protection capabilities that check request content for malicious patterns

  • Response access control Inspects response properties and can return a defined HTTP response
  • Response protection Enables OCI-managed protection capabilities for HTTP responses
  • Rules, Conditions, and Actions

Each rule has a condition written as a JMESPath expression that is evaluated against the HTTP request or response, and an action :

  • Action Behavior
  • Allow When the rule matches, skip all remaining rules in the current module

Check Do not stop rule processing; write a log entry documenting the result (useful for testing a rule before enforcing it)

Return HTTP response Return a defined HTTP response, such as 401 or 403 with a custom body

A safe rollout pattern is to create new rules with the Check action, review the logs for false positives, and then switch to Return HTTP response .

Network Address Lists

Network address lists hold public IP addresses and CIDR ranges, or private VCN addresses, that rules can reference. They make it easy to allow trusted partners, block known bad ranges, or exempt health checkers from rate limits.

Protection Capabilities

Request protection uses protection capabilities maintained by Oracle, each identified by a key and grouped by tags such as the attack type. You choose which capabilities to enable and what action to take when they match.

Collaborative protection capabilities reduce false positives. Instead of acting on one pattern, a collaborative capability runs a group of individual capabilities and adds up their weights . It acts only when the total reaches its action threshold . For example, a collaborative capability with key 9420000 runs individual capabilities such as 9421000, 9421400, and 9421600 for every request and takes action only if enough of them match.

Rate Limiting Design

Rate limiting protects login pages and APIs from brute-force and scraping attacks. Common choices:

Apply rate limits per client IP on sensitive paths such as /login .

Exempt monitoring systems through a network address list.

Return a clear HTTP response, such as 429, when the limit is exceeded.

Certificates and TLS

For the regional option, TLS is terminated on the load balancer , which can use certificates managed by the OCI Certificates service. WAF then inspects the decrypted HTTP request before it is forwarded to the backends.

Tuning WAF Without Breaking the Application

New WAF policies often block legitimate traffic at first, such as large JSON bodies that look like injection attempts or API clients that send unusual headers. A practical tuning cycle is:

Start new protection rules with Check so matches are only logged.

Review the logged matches for each protection capability and identify false positives.

Narrow conditions with JMESPath (for example, exclude a specific API path) or switch to a collaborative capability for noisy attack categories.

Switch the reviewed rules to Return HTTP response and keep watching the logs after each application release.

Putting It Together: A Layered Web Architecture

DNS resolves the application to a public load balancer, or to an edge policy's CNAME.

The load balancer terminates TLS with a certificate from OCI Certificates.

The WAF policy blocks injection attacks, enforces geography rules, and rate-limits abusive clients.

Backends sit in private subnets protected by NSGs , and optionally ZPR .

Traffic from the backends to databases can pass through a Network Firewall for deep inspection.

Logging captures WAF decisions, and Cloud Guard watches for risky configuration.

Each layer covers a gap in the others: WAF understands HTTP, the Network Firewall understands traffic between networks, and NSGs and ZPR limit which components can talk at all.

Loading diagram... WAF Policy Attached to a Load Balancer