Study guide
10.1 Cloud Guard: Detector Recipes, Problems, Scores & Responders
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.1 Cloud Guard: Detector Recipes, Problems, Scores & Responders
Key Takeaways Explain This Topic AI
OCI Cloud Guard is a unified cloud security posture management (CSPM) service that continuously monitors resources, detects vulnerabilities, and executes automated remediations across tenancies.
Configuration detectors check resource settings, activity detectors flag risky actions recorded in Audit, and the threat detector looks for rogue-user behavior such as impossible travel.
Oracle-managed recipes allow only a few settings to change, so teams clone them into user-managed recipes to adjust rules, risk levels, and conditions.
The security score is the percentage of examined resources not flagged as problems, while the risk score is normalized from 0 to 9,999, and both reflect the past 30 days.
Responder rules such as Make Bucket Private run as user actions by default or as automatic actions, and each needs an IAM policy that lets the cloudguard service act.
Last updated: October 2026
- 7.3 Cloud Guard: Managed Detector Recipes, Security Scores & Responder Recipes
- OCI Cloud Guard Architecture: Core Entities and Governance Fabric
As enterprise cloud footprints expand across dozens of compartments, regions, and development teams, maintaining continuous security compliance becomes an intractable manual challenge. Misconfigurations—such as accidentally exposed Object Storage buckets, volumes without customer-managed keys, permissive security list rules, or compromised IAM credentials—can emerge and persist undetected for weeks. OCI Cloud Guard is a native, cloud-scale Cloud Security Posture Management (CSPM) service that delivers continuous, automated security surveillance and remediation across your tenancy.
Cloud Guard works through four main concepts:
Targets : A Target defines the scope of resources that Cloud Guard monitors. A target can be scoped to the root compartment (encompassing the entire tenancy across all subscribed geographic regions) or granularly restricted to specific departmental compartments (e.g., Finance-Production or DevOps-Sandbox ).
Detector Recipes : A Detector Recipe contains an inventory of security rules that define what misconfigurations, policy violations, or behavioral anomalies to detect. When a detector rule identifies a violation, Cloud Guard raises an actionable Problem .
Problems : A Problem represents an active, identified security issue. Each problem records the offending resource OCID, geographic region, compartment path, detection timestamp, risk severity level ( Critical, High, Medium, Low, or Minor ), and status, such as open, resolved, or dismissed.
Responder Recipes : A Responder Recipe defines the specific remediation action executed when a Problem is identified. Actions range from automated containment (e.g., flipping a public bucket to private) to generating security alerts for human verification.
Detector Recipes: Configuration, Activity, Threat & Instance Security Detectors
Cloud Guard provides specialized detector engines to inspect distinct layers of the cloud ecosystem:
1. Configuration Detectors
Configuration detector rules check how resources are set up. Examples from Oracle's detector reference include:
Bucket is public (Object Storage).
Instance has a public IP address (risk level High) and Instance is publicly accessible (Compute).
Instance is not running an Oracle public image .
VCN has Internet Gateway attached and security rules that allow traffic from 0.0.0.0/0 to restricted ports such as 22 or 3389.
Policy gives too many privileges and Tenancy admin privilege granted to group (IAM).
Database is not backed up automatically and Key has not been rotated .
Many rules are labeled with the CIS OCI Foundations Benchmark controls they support.
2. Activity Detectors
Activity detector rules watch actions recorded in OCI Audit that may be risky even when they are legitimate, for example a bastion or bastion session being created, a certificate authority being deleted or revoked, an image being exported, an instance or DB system being terminated, or changes to IAM and networking resources such as security list ingress rules.
3. Threat Detectors
The threat detector looks for patterns of malicious behavior, such as a rogue user whose recent actions combine indicators like impossible travel or password spraying .
Cloud Guard also offers Instance Security detection for compute hosts. OCI provides Oracle-managed recipes for detectors and responders. Oracle maintains and updates them, and you can change only a few settings in their rules. For broader customization, you create a user-managed recipe , usually by cloning an Oracle-managed one.
To tailor Cloud Guard to enterprise requirements, architects employ the Clone-and-Customize pattern:
The architect clones the Oracle-Managed Recipe into a custom User-Managed Recipe .
In the user-managed recipe, specific rules can be enabled or disabled (e.g., disabling public bucket alerts in a specialized web-hosting compartment while keeping them critical in database compartments).
Trigger conditions and risk thresholds can be modified (e.g., elevating SSH port exposure from High to Critical).
The custom recipe is bound to the appropriate Target compartment.
Security Posture Scoring: Security Score vs. Risk Score
Cloud Guard synthesizes thousands of individual resource evaluations into executive-level posture metrics:
1. Security Score
The Security Score is the percentage of resources that Cloud Guard examined and did not flag as potential problems:
A higher score is better, and 100 means no problems were detected.
It reflects monitoring over the past 30 days and is updated continuously.
2. Risk Score
The Risk Score estimates the risk posed by the problems Cloud Guard has detected:
It reflects the number of problems , the risk level of each, and the sensitivity of the resource types involved.
The raw value is normalized to a range of 0 to 9,999 , where 0 means no problems were detected.
It covers the past 30 days and is recalculated every 15 minutes .
Because it grows with the "surface area" of risk, a large tenancy can have an excellent security score and still a high risk score. Fixing high and critical problems on the most sensitive resources reduces it the most.
Responder Recipes: Automated vs. User-Approval Remediation
A responder is an action Cloud Guard can take when a detector identifies a problem. Responder recipes group responder rules, and you can use Oracle's defaults, clone them, enable or disable individual rules, and add conditions that limit where a rule applies.
Oracle-Managed Responder Rules
Oracle's responder recipe includes these rules:
- Responder rule Action Example detector it addresses
- Cloud Event Publishes problem details to the Events service All problems (runs automatically)
- Make Bucket Private Changes a public bucket to private Bucket is public
- Delete Public IP(s) Removes public IPs from an instance Instance has a public IP address
- Stop Compute Instance Gracefully shuts down an instance Instance has a public IP address
- Terminate Compute Instance Terminates an instance, preserving its boot volume Instance has a public IP address
- Delete Internet Gateway Removes an internet gateway from a VCN VCN has Internet Gateway attached
- Delete IAM Policy Deletes an overly permissive policy Policy gives too many privileges
- Disable IAM User Disables a user's capabilities Suspicious IAM, networking, or bastion activity
- Enable DB Backup Turns on automatic database backups Database is not backed up automatically
- Rotate Vault Key Creates a new key version Key has not been rotated
Each responder needs an IAM policy that lets the Cloud Guard service act, for example allow service cloudguard to manage buckets in compartment Finance for Make Bucket Private, or manage instance-family for the compute responders. Enabling responders gives Cloud Guard permission to change your environment, so grant only what your security policy allows.
Execution Modes
Responder rules run in one of two modes:
User action (default for remediation rules) : Cloud Guard shows the problem and the suggested responder, and an authorized engineer reviews it and chooses to remediate. This suits production, where an automatic stop or termination could cause an outage.
Automatic action : the responder runs as soon as the problem is detected, without waiting for a person. Use it for high-confidence, high-impact problems such as a public bucket containing sensitive data. The Cloud Event responder already runs this way by default.
Integration with OCI Events, Notifications, and SIEM/SOAR Ecosystems
Cloud Guard integrates seamlessly with OCI's event-driven architecture, enabling enterprise-grade alert routing and external tool orchestration:
OCI Events Service : Cloud Guard automatically emits structured, CloudEvents-compliant JSON events for state changes, including Problem - Detected , Problem - Remediated , and Problem - Dismissed .
Fan-Out via OCI Notifications (ONS) : Events trigger ONS notification topics, broadcasting critical alerts via email, SMS, PagerDuty, or Slack webhooks to on-call incident response engineers.
Custom Automation via OCI Functions : When complex, multi-system remediation is required (e.g., quarantining an entire VCN, capturing instance memory forensics, or opening a high-priority incident in ServiceNow or Jira), an OCI Events rule routes the problem event to an OCI Function for programmatic execution.
SIEM/SOAR Ingestion via OCI Streaming : For organizations operating centralized Security Operations Centers (SOC), Cloud Guard events are routed to OCI Streaming (providing a managed Apache Kafka API) to continuously ingest security findings into external platforms like Splunk, Microsoft Sentinel, IBM QRadar, or Datadog.
Loading diagram... OCI Cloud Guard End-to-End Posture Governance & Remediation Architecture
Architectural Comparison: Cloud Guard Detector Types
The following table contrasts the functional characteristics, telemetry sources, and primary use cases of Cloud Guard detector recipes:
- Capability Dimension Configuration Detectors Threat Detector Activity Detectors
- What it evaluates Resource settings Patterns of user behavior Individual actions recorded in Audit
- Typical input Resource configuration Audit activity across a user's actions Audit events
Example problems Bucket is public; instance has a public IP Rogue user (impossible travel, password spraying) Bastion session created; CA deleted; image exported
Example responders Make Bucket Private; Delete Public IP(s) Disable IAM User Disable IAM User
Customization Clone to change risk levels, conditions, and settings Oracle-managed threat recipe Clone to enable, disable, or condition rules