How to use this playbook · START

How to Use This Playbook

This playbook is the manual-only (human engineers) execution path for enabling a new Oracle Cloud estate. It is deliberately generic: replace {Customer}, {tenancy}, {org} and {region} placeholders, then execute the six steps in order. Every step ends with explicit exit criteria — do not start the next step until they are met.

Scope model. A typical procurement contains two planes that must be governed separately but connected deliberately:

Co-tenanted vs isolated decision. Decide this in Step 1 and record it as a formal decision: (a) Co-tenanted — Fusion SaaS subscription and OCI IaaS/PaaS share one tenancy: simplest identity wiring (one identity domain topology serves both), single billing view, but requires strict compartment and policy separation so platform admins never acquire implicit reach into SaaS handles. (b) Isolated — separate tenancies for SaaS and IaaS/PaaS: stronger blast-radius separation and independent lifecycle, at the cost of cross-tenancy federation, network peering for integrations, and duplicated governance overhead. Default recommendation for a single customer estate: co-tenanted with hard compartment boundaries; choose isolated when regulatory segregation, M&A carve-outs, or independent operating organizations demand it.

OCI best-practice reference catalog

Use the following as the core OCI best-practice reference catalog for every engagement in this portal. It covers architecture, governance, security, ransomware resilience, disaster recovery, and operations. Most links are official Oracle guidance; CIS, NIST, and CISA provide independent security standards.

1. Architecture frameworks and assessments

The OCI Well-Architected Framework currently covers five pillars: security and compliance, reliability and resilience, performance and cost optimization, operational efficiency, and distributed cloud.

2. Governance, tenancy foundations, and landing zones

These references establish the tenancy structure and repeatable foundation before deploying workloads. Oracle's landing-zone guidance includes blueprints and modular deployment approaches.

3. Security checklists, hardening, and Zero Trust

Use the security checklist for review, the CIS benchmark for configuration baselines, and the service security guidance for implementation. These serve different purposes and work well together.

4. Ransomware protection and cyber recovery

Start with Oracle's Cyber Resilient Architecture playbook. It addresses protection, detection, response, and recovery. A DR replica can also replicate compromised data, so ransomware recovery requires protected backups and a verified clean recovery process.

The Block Storage, File Storage, and database recovery references describe distinct protection mechanisms; select them according to the data service being protected.

5. High availability, business continuity, and disaster recovery

Choose the architecture against business-approved RTO and RPO, workload dependencies, and recovery costs.

6. Security operations, monitoring, performance, and FinOps

Cloud Guard supports continuous posture monitoring and configurable corrective actions; operational and optimization guidance complements those security controls.