Study guide

12.2 OCI Certificates: Private CAs, TLS Certificates, Renewal & Integrations

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.2 OCI Certificates: Private CAs, TLS Certificates, Renewal & Integrations

Key Takeaways Explain This Topic AI

OCI Certificates manages TLS certificates, certificate authorities, and CA bundles, including revocation and automatic renewal.

Creating a certificate authority requires a hardware-protected (HSM) asymmetric encryption key in OCI Vault.

Automatic renewal works only for certificates that the Certificates service issues and manages; imported certificates must be updated with new PEM contents.

The service does not support mixed certificate chains that combine RSA and ECDSA key algorithms in one chain.

Certificates can be associated with OCI services such as Load Balancer and API Gateway, and Audit tracks administrative actions on certificates and CAs.

Last updated: October 2026

Why Certificate Management Is a Security Objective

TLS protects data in transit, but expired or mismanaged certificates cause outages and security gaps. The exam objective "application and data security using WAF, Certificates, and KMS" expects you to know how OCI issues, stores, renews, and revokes certificates for internal and external services.

Core Concepts

Concept Meaning

Certificate A digital document confirming that its subject owns the public key in it. An end-entity (leaf) certificate cannot sign other certificates; TLS server and client certificates are examples.

Certificate authority (CA) Issues certificates and subordinate CAs. CAs form a hierarchy with a self-signed root CA at the top and subordinate CAs below it.

CA bundle A set of root and intermediate certificates used to validate chains; it can include CAs not managed by the service. Content is in PEM format.

Certificate chain The list of certificates from the end-entity certificate up to the root.

Certificate revocation list (CRL) A list, issued by a CA, of certificates and CAs it has revoked before their expiration.

For a certificate to be trusted, the client validating it must trust the root CA at the top of its chain. The service does not support mixed chains in which some certificates use RSA keys and others use ECDSA keys; Oracle recommends separate CA chains for each key algorithm family.

What You Can Do With the Service

Oracle lists these lifecycle capabilities:

Create root CAs, subordinate CAs, and subordinate CAs that are issued externally but managed internally, as well as certificates and CA bundles.

Import CAs and certificates issued by a third-party CA.

Configure rules for how long CAs and the certificates they issue are valid.

Configure rules to renew certificates automatically.

Choose which version of a CA, certificate, or bundle is current.

Revoke a CA or certificate version that has been compromised.

Tag resources and associate certificates with services such as Load Balancer.

Building a Private CA Hierarchy

Many organizations need certificates for internal services, such as internal web portals, service-to-service TLS, or private API endpoints, that should not be issued by a public CA. The Certificates service lets you run a private PKI:

Create or choose a Vault key. Creating a CA requires an HSM-protected asymmetric key (for example, RSA) in OCI Vault . The CA's private key never leaves the HSM.

Create a root CA with a long validity period. Oracle's tutorials recommend keeping the root separate from day-to-day issuance.

Create a subordinate (issuing) CA signed by the root. Separating root and issuing CAs increases security, because the root can stay unused while the subordinate issues certificates.

Issue certificates from the subordinate CA for internal hostnames.

Distribute the CA bundle (root and intermediate) to clients so they trust the internal certificates.

A dynamic group and IAM policies are typically used so instances or applications can retrieve certificate bundles without user credentials.

Issued vs. Imported Certificates and Renewal

Certificate source Who holds the private key Renewal

Issued by a CA in the Certificates service The service Automatic renewal rules can create new versions before expiry

Issued internally with an externally managed key (you supply a CSR) You Renew by providing a new CSR

Imported from a third-party CA You No automatic renewal ; update the certificate with new PEM files from the third-party CA

When a certificate expires without automatic renewal creating a new version, it can no longer be used. Monitoring expiration dates of imported certificates is therefore an operational must.

Versions

Each renewal creates a new certificate version . You can choose which version is current, which allows controlled rollouts and rollback. A compromised version can be revoked , and revocation is published through the CA's CRL.

Integrations

Load Balancer : associate a certificate from the Certificates service with a listener so the load balancer terminates TLS with a managed certificate.

API Gateway : use managed certificates for custom domain names on gateways.

Resource Manager private endpoints : when Resource Manager connects to a private Git server, the server's SSL certificate is imported into the Certificates service.

Network Firewall and WAF : TLS keys for firewall decryption use Vault mapped secrets; WAF inspects traffic after the load balancer terminates TLS.

Operational Practices

Prefer certificates issued and managed by the service for internal endpoints, so renewal rules replace them automatically.

Keep an inventory of imported certificates and their expiry dates, because they must be renewed by hand.

Use separate subordinate CAs for different environments, such as production and test, so a compromised test CA can be revoked without touching production.

Set validity rules that match your policy, for example short-lived leaf certificates with automatic renewal.

Security and Monitoring

IAM controls who and which services can use CAs, certificates, and bundles.

OCI Audit tracks administrative actions on CAs, certificates, and CA bundles.

Cloud Guard detects risky configurations and activity related to Certificates. Its activity detectors include rules such as "Certificate Authority (CA) deleted", "Intermediate Certificate Authority (CA) revoked", and "CA bundle updated".

Loading diagram... Private CA Hierarchy in OCI Certificates