Study guide
10.2 Security Zones & Vulnerability Scanning
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
10.2 Security Zones & Vulnerability Scanning
Key Takeaways Explain This Topic AI
Security zone policies are validated regardless of which user performs an operation, and you must enable Cloud Guard before creating security zones.
Every tenancy has an Oracle-managed Maximum Security Recipe that cannot be modified, and custom recipes can select individual policies.
Security zone policies cover resource movement and association, public access, required Vault encryption, database backups, data copying, and Oracle-approved configurations.
A VSS compute scan recipe sets agent scanning, a CIS benchmark level (None, Lightweight, Medium, or Strict), a public IP port scan level, and a daily or weekly schedule.
Last updated: October 2026
- 7.4 Security Zones & Vulnerability Scanning
- The Preventive Paradigm: OCI Security Zones
Cloud Guard is detective : a misconfigured resource exists for a while before Cloud Guard finds it. Security Zones are preventive : they stop the misconfiguration from being created at all.
A security zone associates a compartment (and, by default, its subcompartments) with a security zone recipe . When anyone creates, updates, or moves a resource in the zone, OCI validates the operation against every policy in the recipe. If a policy would be violated, the operation is denied . For example, if the recipe forbids public buckets, both creating a public bucket and changing an existing bucket to public fail with an error.
Key characteristics:
Validated for every user. A security zone policy is checked regardless of which user performs the operation, so even users with broad IAM permissions cannot create a non-compliant resource in the zone.
Deny-only. A security zone policy never grants permissions. IAM still decides who can act; the zone decides which configurations are allowed.
One zone per compartment. A compartment cannot belong to more than one security zone, but a subcompartment can be given its own zone.
Cloud Guard is required. You must enable Cloud Guard before creating security zones. A Cloud Guard security zone target then periodically checks for violations in resources that existed before the zone was created.
Governance of the zone itself. Users who can manage security zones can change a zone's recipe or remove a compartment from it, so restrict those permissions to a small security team.
Recipes: Maximum Security Recipe and Custom Recipes
Every tenancy has an Oracle-managed recipe named Maximum Security Recipe , which includes a curated set of policies. You cannot modify it, but you can create custom recipes that select the policies your organization needs.
Oracle groups security zone policies by security principle:
Principle Example policies
Restrict resource movement Block volumes, instances, buckets, subnets, and databases in the zone can't be moved to a compartment outside the zone
Restrict resource association A database in the zone can't have a Data Guard peer outside the zone; an instance in the zone can't use a subnet outside it
Deny public access deny public_subnets , deny internet_gateway , deny public_buckets , deny public_load_balancer , and policies that deny NAT, service, local peering, or dynamic routing gateways
Require encryption Boot volumes, block volumes, buckets, and file systems must use a Vault customer-managed key (for example, deny file_system_without_vault_key )
- Ensure data durability Databases must have automatic backups
- Ensure data security Data in the zone can't be copied (for example, cloned) to a compartment outside the zone
Use only Oracle-approved configurations For example, deny instances without a sanctioned image, load balancers with weak SSL configuration, and NSGs with insecure ingress rules
Database policies do not apply to Oracle Exadata Database Service on Cloud@Customer.
Designing With Security Zones
Because a zone can block more than you expect, plan the architecture before attaching it:
Put workloads that need internet-facing components (such as a public load balancer) in a separate compartment outside the zone, and keep data tiers inside it.
Create Vault keys first so encrypted resources can be launched in the zone.
Choose the recipe carefully: the Maximum Security Recipe suits the most sensitive data, while a custom recipe can allow, for example, a NAT gateway for patching.
Test Terraform stacks against the zone in a non-production compartment, because a denied operation fails the job.
OCI Vulnerability Scanning Service (VSS): Architecture & Engines
While Security Zones enforce architectural guardrails, software running on compute instances and inside container images is continuously susceptible to newly discovered Common Vulnerabilities and Exposures (CVEs) and configuration drift. OCI Vulnerability Scanning Service (VSS) provides fully managed, continuous, and automated vulnerability assessment across compute fleets and container registries.
VSS operates two specialized scanning engines:
1. Host Scanning Engine
The Host Scanning engine continuously assesses virtual machine and bare metal compute instances for operating system vulnerabilities and configuration flaws:
Agent-Based Scanning : Host scanning uses the Oracle Cloud Agent with the Vulnerability Scanning plugin enabled, so no third-party agent, SSH credentials, or inbound firewall rules are needed. Agent-based scanning is enabled by default in a scan recipe; Oracle notes that without it, VSS can only inspect open ports on public IPs. A recipe can also use Qualys VMDR as the agent-based scanner.
CVE Detection : Compares installed operating system packages with the public CVE database to report unpatched vulnerabilities.
CIS Benchmark Compliance : Evaluates instance OS configurations against Center for Internet Security (CIS) distribution-specific benchmarks, identifying insecure system settings, unhardened permissions, and compliance failures.
Open Port Detection : Scans listening network sockets on the instance, flagging listening services on unauthorized or dangerous network ports.
Scan Recipes and Targets : A compute scan recipe sets the agent scan level, the CIS benchmark level (None, Lightweight, Medium, or Strict), the public IP port scan level (None, Light, or Standard), and a daily or weekly schedule. A target applies the recipe to a compartment; targeting the root compartment covers every subcompartment.
2. Container Image Scanning Engine
The Container Scanning engine protects cloud-native microservice pipelines deployed on OCI Container Engine for Kubernetes (OKE):
Registry Integration : Integrates natively with Oracle Cloud Infrastructure Registry (OCIR) .
Scan on Push : After you add an image scanner to a repository, VSS scans every image pushed to it. If the repository already has images, the four most recently pushed images are scanned immediately. Scanning reports vulnerabilities; it does not block a deployment by itself, so pipelines should check the results.
Automatic Rescanning : Images in repositories with scanning enabled are rescanned when new vulnerabilities are added to the CVE database, so older images are flagged when new issues are published.
Vulnerability Remediation Workflows and OS Management Hub
VSS identifies vulnerabilities, but modern security governance requires automated remediation pipelines:
Posture Visibility : VSS reports individual CVE findings with Common Vulnerability Scoring System ( CVSS ) severity ratings, affected package versions, and vendor fix advisories.
Cloud Guard : Cloud Guard configuration detectors can raise problems for scanned hosts and container images that have vulnerabilities or open ports, so findings appear alongside other security problems.
Patching with OS Management Hub : VSS reports problems but does not patch. Teams use OS Management Hub to schedule package and security updates for the affected instances, typically promoting updates through development, test, and production lifecycle environments.
Loading diagram... Preventive (Security Zones) vs Detective (Cloud Guard) vs Assessment (VSS) Governance
Architectural Comparison: Security Zones vs. Cloud Guard vs. VSS
The following matrix contrasts the operational layers, enforcement mechanisms, and administrative capabilities of OCI's core security governance services:
Capability Dimension OCI Security Zones OCI Cloud Guard Vulnerability Scanning (VSS)
Security Paradigm Preventive Control (blocks non-compliant actions) Detective & Corrective Control (detects & remediates) Continuous Vulnerability Assessment (audits software)
Enforcement Point Validation of create, update, and move operations Continuous monitoring of resources and activity Agent scans of hosts and registry image scans
Who can bypass it No user can create a violating resource; only users who manage security zones can change the zone or recipe Administrators can change recipes or dismiss problems Administrators configure scan recipes and targets
Target Assets Compartments and enclosed OCI infrastructure resources Tenancy / Compartment resources and audit telemetry Compute instance OS (Linux/Windows) and OCIR images
Primary Threat Addressed Structural misconfigurations (public subnets, unencrypted data) Operational drift, threat actors, compromised credentials Unpatched software packages (CVEs), open ports, CIS drift
Remediation Method The operation is denied Responders (user action or automatic) Patch with OS Management Hub; rebuild images