Study guide
12.4 Vault Secrets: Versions, Rotation States, Automatic Generation & Rotation
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.4 Vault Secrets: Versions, Rotation States, Automatic Generation & Rotation
Key Takeaways Explain This Topic AI
A Vault secret is encrypted with a symmetric master encryption key, and its contents are sent to the service base64-encoded.
Secret versions can be marked current, pending, latest, previous, or deprecated, and only deprecated versions can be deleted.
Automatic secret rotation can run on an interval from 1 to 12 months and integrates with Autonomous AI Database and OCI Functions.
A rotation function runs four steps: VERIFY_CONNECTION, CREATE_PENDING_VERSION, UPDATE_TARGET_SYSTEM, and PROMOTE_PENDING_VERSION.
Applications on compute instances can read secrets with instance principals, and functions can read them with resource principals, so no credentials are stored on the host.
Last updated: October 2026
Why Secrets Belong in Vault
Hardcoded passwords in source code, container images, or environment files are among the most common causes of breaches. Vault secrets keep credentials in a managed, audited store:
A secret is encrypted with a master encryption key from a vault, and that key must be symmetric (AES).
Secret contents are base64-encoded before they are sent to the service. The Console lets you type plain text and encodes it for you.
Access is controlled with IAM on the secret-family resources, such as read secret-bundles for applications that only need to retrieve values, and every access is recorded by Audit .
Retrieving Secrets Without Stored Credentials
Applications should authenticate to Vault with an OCI identity rather than a stored API key:
Workload Identity used Example policy
Compute instance Instance principal (instance in a dynamic group) Allow dynamic-group app-servers to read secret-bundles in compartment Secrets
OCI Function Resource principal ( resource.type = 'fnfunc' ) Allow dynamic-group fn-apps to read secret-bundles in compartment Secrets
OKE pod Workload identity or the Secrets Store CSI driver A policy conditioned on the cluster, namespace, and service account
Container Instance Registry credentials stored as a Vault secret Used to pull images from private registries
The application calls the Secrets API at run time to read the current version, often caching it briefly.
Secret Versions and Rotation States
A secret is a container for one or more secret versions . Each version can carry one or more rotation states :
- State Meaning
- Current The version applications receive by default
- Pending A new version uploaded but not yet promoted, for example during rotation
- Latest The most recently created version
- Previous The version that was current immediately before the most recent rotation
- Deprecated A version that is not current, pending, or previous
When a secret is first created, its single version is both current and latest . During rotation, a new version is added as pending , and applications keep using current until the pending version is promoted. Any version other than a deprecated one can be marked current again to roll back, and only deprecated versions can be deleted .
Automatic Secret Generation
Since February 2024, Vault can generate secrets for you , such as passwords and SSH keys, using templates that define the format, so humans never see or choose the value. The Console shows whether a secret is auto-generated and auto-rotated, and work requests let you track secret operations.
Automatic Secret Rotation
Automatic rotation changes a secret on a schedule with an interval from 1 to 12 months . It integrates with Autonomous AI Database and OCI Functions , so the new value is applied to the target system and not just stored in Vault.
The Rotation Function Contract
For a target that a function updates, Vault calls the function with the secret OCID, the current version number, and a step . The function must implement four steps:
VERIFY_CONNECTION : confirm the existing credentials in the secret still work against the target system.
CREATE_PENDING_VERSION : create a new pending secret version (or reuse an existing pending version).
UPDATE_TARGET_SYSTEM : change the credential on the target system to the pending value.
PROMOTE_PENDING_VERSION : move the pending version to current .
If a step fails, for example because the database cannot be reached during UPDATE_TARGET_SYSTEM, the pending version is never promoted. Applications keep using the unchanged current version, so a failed rotation does not lock them out.
Pre-Built Rotation Functions
Oracle provides pre-built functions in OCI Functions for database credentials: Database Secret Rotation with Wallet (mutual TLS to the database) and Database Secret Rotation without Wallet (TLS). When you create one from the Pre-Built Functions page, OCI Functions can create the dynamic group and IAM policy the function needs. You must also allow the Vault secret rotation service to invoke the function, and the database must allow network access from the function's application subnet.
Common Mistakes
Encrypting a secret with an asymmetric key: secrets require a symmetric master encryption key.
Giving applications manage instead of read permissions on secrets, which lets a compromised application change or delete them.
Caching a secret value forever, so a rotated password breaks the application until it restarts.
Rotating the value in Vault without changing it in the target system. Automatic rotation with a rotation function avoids this, because the target is updated before the new version becomes current.
Designing for Rotation
Store one credential per secret, and point applications at the secret OCID rather than a version number.
Make applications re-read the secret when authentication fails, so they pick up a newly promoted version.
Use separate secrets for each environment and region, and replicate or recreate them in the DR region alongside the keys that encrypt them.
Restrict manage secret-family to the security team, and give applications only read secret-bundles .