Study guide

12.3 OCI Vault Key Management: Vault Types, Protection Modes, Dedicated KMS & External KMS

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.3 OCI Vault Key Management: Vault Types, Protection Modes, Dedicated KMS & External KMS

Key Takeaways Explain This Topic AI

A virtual private vault is an isolated partition on a hardware security module, while other vaults share HSM partitions; Key Management HSMs meet FIPS 140-2 Security Level 3.

An HSM-protected key cannot be exported from the HSM, while a software-protected key is stored on a server, encrypted by an HSM root key, and can be exported.

Automatic key rotation is available for keys in a virtual private vault, with a rotation interval between 60 and 365 days.

Dedicated KMS provides a customer-managed, single-tenant HSM partition as a service, with an HSM cluster of three automatically synchronized partitions.

External KMS keeps master encryption keys in a third-party key management system outside OCI, and OCI stores only key references.

Last updated: October 2026

Why Key Management Matters

All OCI storage services encrypt data at rest by default with Oracle-managed keys . Many regulations and security policies require more: control over who can use the keys, the ability to rotate or disable them, and proof of where they are stored. OCI Vault (the Key Management service) provides customer-managed keys for services such as Block Volume, Object Storage, File Storage, and databases. Keys are used only by the services and principals that IAM policies allow.

Vault Types

Vault type Isolation Cost model Notes

Virtual private vault An isolated partition on an HSM, effectively a virtual independent HSM Includes 1,000 key versions Supports vault backup and automatic key rotation

Default (shared) vault Shares HSM partitions with other vaults Pay for key versions individually A lower-cost choice when the extra isolation is not required

Oracle's HSMs meet FIPS 140-2 Security Level 3 : the hardware is tamper-evident, has physical tamper resistance, requires identity-based authentication, and deletes keys when it detects tampering.

Protection Modes

Each master encryption key has a protection mode , chosen at creation. It affects pricing and cannot be changed later :

  • Protection mode Where the key lives Export Where cryptographic operations happen
  • HSM Stored on the HSM Cannot be exported Inside the HSM

Software Stored on a server, encrypted at rest by an HSM root key Can be exported On the server, or on the client after export

Key Algorithms

  • Algorithm Encrypt/decrypt Sign/verify Typical use
  • AES (symmetric) Yes No Encrypting data in OCI services; secrets must use a symmetric key
  • RSA (asymmetric) Yes Yes Wrapping keys, signing, image signing in OCIR
  • ECDSA (asymmetric) No Yes Digital signatures

Every vault also includes an RSA 4096-bit wrapping key used to wrap your own key material when you import keys (bring your own key, BYOK).

Envelope Encryption

Encrypting large volumes of data directly in an HSM would be slow. OCI services use envelope encryption : data is encrypted with a data encryption key (DEK) , and the DEK is itself encrypted with your master encryption key (MEK) in Vault. Services such as Object Storage, Block Volume, and File Storage store only the encrypted DEK alongside the data. To read the data, the service asks Vault to decrypt the DEK, which requires IAM permission to use the MEK. Disabling the MEK therefore makes the data unreadable by the service.

Two rules come up in scenarios:

Same region. An OCI service can use a master encryption key only when the service and the vault holding the key are in the same region . Cross-region copies, such as replicated volumes or copied backups, need a key in the destination region.

Service authorization. The service itself must be allowed to use the key, for example Allow service blockstorage, objectstorage-us-ashburn-1 to use keys in compartment Security where target.key.id = '<key-ocid>' .

Rotation and Key Versions

Rotating a key creates a new key version while the key's OCID stays the same , so services keep referring to the same key. New encryption uses the newest version, and older versions remain available to decrypt data they protected. For symmetric keys, the ciphertext records which version was used, so you do not need to track it; for asymmetric keys you must track which version encrypted or signed what.

Automatic rotation is available for keys in a virtual private vault . You set a rotation interval between 60 and 365 days and a start date. It works for HSM and software keys and for symmetric and asymmetric keys, the key must be enabled, and a failed rotation can trigger an event notification.

Disabling and Deleting Keys

Disabling a key immediately stops its use for cryptographic operations; you can enable it again.

Deleting a key is scheduled with a waiting period of 7 to 30 days (pending deletion), during which the deletion can be canceled. After deletion, data encrypted only with that key cannot be decrypted.

Resilience, Backup, and Replication

Vault keeps copies of keys across all availability domains in multi-AD regions (and across fault domains in single-AD regions), so keys stay available if an AD fails. For disaster recovery:

Cross-region vault replication creates a replica of a vault in another region in the same realm . Creating, updating, deleting, and moving keys and key versions in the source vault are synchronized to the replica. Keys travel only as encrypted objects between FIPS 140-2 Level 3 HSMs, and Audit logs the start and deletion of replication. All private vaults support replication; some older virtual vaults do not.

Backup and restore of virtual private vaults and keys can write encrypted backups to Object Storage or outside OCI.

Dedicated KMS

Dedicated KMS gives a customer-managed, highly available, single-tenant HSM partition as a service. The HSM cluster has three partitions by default , kept in sync automatically. You own the partition, its users, and its keys, and you manage them with client utilities and PKCS #11 libraries from OCI compute instances. Dedicated KMS supports HSM-protected keys only (no software keys) and AES, RSA, and ECDSA algorithms. Choose it when policy requires that you, not Oracle, administer the HSM partition.

External KMS: Hold Your Own Key

External KMS lets you keep master encryption keys in a third-party key management system hosted outside OCI . OCI stores only key references ; the actual key material stays in the external system, and you can disable the keys at any time to cut off OCI's ability to decrypt. This addresses regulations that require keys to be stored outside any cloud provider's premises.

Choosing an Option

  • Requirement Best fit
  • Customer-managed keys at low cost Default vault with HSM-protected keys
  • Isolation, vault backup, and automatic rotation Virtual private vault
  • Customer administration of the HSM partition through PKCS #11 Dedicated KMS
  • Keys must never be stored in OCI External KMS

Loading diagram... Envelope Encryption with a Customer-Managed Key