Study guide
11.3 Zero Trust Packet Routing (ZPR): Security Attributes & Intent-Based Policy
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
11.3 Zero Trust Packet Routing (ZPR): Security Attributes & Intent-Based Policy
Key Takeaways Explain This Topic AI
ZPR enforces intent-based network policy using security attributes applied to resources, and the policy keeps working when the network topology changes.
A packet reaches its target only if a route exists and it passes every NSG, security list, and ZPR policy rule; failing any one of them drops the traffic.
ZPR enforces policy on VCN traffic, including traffic through local peering and DRGs, but it does not enforce policy on traffic from the internet or on-premises networks.
ZPR allows 1,000 security attributes per tenancy, 1 per VCN, 5 per VNIC, and 3 per other resource.
ZPR is a network-layer (L4) control, while IAM policy is an application-level (L7) control over which principals may call OCI APIs.
Last updated: October 2026
Why ZPR Exists
Network security groups and security lists are written in terms of IP addresses and CIDR blocks . When an architecture changes, for example when a subnet is re-addressed, a VCN is peered, or a route table is edited by mistake, IP-based rules can silently allow more than intended. Zero Trust Packet Routing (ZPR) lets you express security intent about resources themselves: "trusted application servers may connect to sensitive databases on the database port." ZPR enforces that intent at the network level for every access attempt, regardless of later changes to the network design.
Building Blocks
- Concept Meaning
- Security attribute namespace A container for a set of security attributes, such as data or networks
- Security attribute A label that ZPR policy can reference, such as data:sensitive or hosts:trusted
- ZPR policy A rule that governs communication between endpoints identified by their security attributes
- ZPR Policy Language (ZPL) The language used to write ZPR policy statements
- ZPR Visualizer A view of the relationships between attributes, protected resources, and policies in a region
The workflow has three steps:
Create security attribute namespaces and security attributes.
Write ZPR policies that use the attributes.
Add the security attributes to resources.
Resources that support security attributes include compute instances and instance configurations, VNICs, VCNs, DB systems and Autonomous AI Databases, load balancers and network load balancers, Network Firewall, OCI Cache clusters, Search with OpenSearch clusters, File Storage mount targets, Functions applications, bastions, stream pools, Recovery Service subnets, and private endpoints for services such as Resource Manager and DevOps.
Writing ZPL Policies
Within one VCN. Oracle's basic example lets trusted hosts reach sensitive data inside the VCN that carries the networks:internal attribute: in networks:internal VCN allow hosts:trusted endpoints to connect to data:sensitive endpoints
Restricting the protocol and port. Policies can limit a connection to a protocol and port. Oracle's Base Database guidance uses statements like: in networks:app VCN allow apps:frontend endpoints to connect to db:orders endpoints with protocol='tcp/1521'
Reaching Oracle services. A resource such as a DB system needs to reach the Oracle Services Network for backups and management: in networks:app VCN allow db:orders endpoints to connect to 'osn-services-ip-addresses'
Across two VCNs in the same region. When both VCNs have security attributes, a policy can name both: allow networks:net1:App1 endpoints in networks:net1 VCN to connect to DB-Server:App1 endpoints in networks:net2 VCN
Across regions, or to VCNs without attributes. Traffic between VCNs in different regions, or to a VCN that has no security attribute, must be written with CIDR or IP-based policy, for example allowing an attribute-tagged client to connect to a standby VCN's CIDR block for Data Guard.
Clustered databases. For RAC, the database nodes must be allowed to connect to each other, so Oracle's guidance includes a statement letting endpoints with the database attribute connect to endpoints with the same attribute.
How ZPR Fits With Other Controls
ZPR is built on top of existing network controls. For a packet to reach a target:
A route table entry must exist.
Every applicable NSG and security list must allow it.
The ZPR policy must allow it.
If any of these is missing, the traffic is dropped. ZPR therefore adds protection; it never opens a path that the other controls block.
- Control Applies to How it is attached Limit
- Security list All VNICs in a subnet Associated with the subnet 5 per subnet
- Network security group Selected VNICs in one VCN VNICs join or leave the NSG 5 per VNIC
- ZPR Selected resources in one or more VCNs A security attribute on the resource 3 per resource, 5 per VNIC
ZPR also differs from IAM . ZPR is a network-layer (L4) control that looks at the security attributes of the source and target, the IP address, the protocol, and the port. IAM is an application-level (L7) control that decides which principals can call which OCI APIs. A user may have IAM permission to manage a database and still be blocked by ZPR from opening a network connection to it from an untrusted host.
What ZPR Does Not Cover
ZPR enforces policy on VCN traffic, including traffic routed through local peering gateways and DRGs . It does not enforce policy on traffic arriving from the internet or from on-premises networks . For those paths, use NSGs, security lists, the Network Firewall, and WAF. Oracle also suggests running Network Path Analyzer before applying security attributes to peered VCNs, to find routing problems first.
In OKE, ZPR security attributes are supported for managed and self-managed nodes in clusters that use the VCN-native CNI plugin, but not for virtual node pools or flannel clusters.
Limits
- Item Limit
- Security attributes per tenancy 1,000
- Security attributes per VCN 1
- Security attributes per VNIC 5
- Security attributes per other resource 3
- Policy statements per policy object 50
- Policy objects per tenancy 100
- Policies for peered VCNs per tenancy 200