Security continues after go-live. The tenancy must remain governed, and its security posture must be continually measured and improved as workloads and risks evolve.

Parts 1 and 2 established a simple defensive progression. Part 1 focused on who can make critical changes to the tenancy and whether the business can recover if those controls fail. Part 2 focused on how far an attacker can move after gaining a foothold and how quickly the organization can detect suspicious activity.

The next challenge is keeping security effective as the tenancy changes.

An OCI tenancy evolves over time. Workloads, teams and administrator responsibilities change. Network rules are updated, and temporary exceptions can become permanent. Systems need patches as new vulnerabilities emerge. Services are enabled, applications are retired, and business needs change.

Can the organization keep its identity, network, data protection, recovery, and detection controls effective as the tenancy evolves? Is the right governance in place to manage these changes?

Several Treacherous 12 risks come into sharper focus here, particularly insufficient due diligence, system vulnerabilities, abuse and nefarious use of cloud services, and the broader risks created when security controls are allowed to drift over time. [1]

A secure architecture provides the starting point. Governance and continuous assurance determine whether the architecture remains secure after production begins.

OCI offers native security tools such as Cloud Guard, Vulnerability Scanning Service, and OS Management Hub. Organizations can also use third-party cloud security posture management (CSPM) platforms, vulnerability scanners, and SIEM tools. The goal is layered protection, with regular checks, clear ownership, and ongoing remediation, regardless of the tools chosen. A landing zone establishes the initial controls, but those controls must evolve as workloads and risks change.

A landing zone is the baseline, not the finish line

Part 1 focused on adapting an OCI Landing Zone to the organization’s security needs and operating model before production workloads are deployed. Part 3 builds on that foundation, focusing on how the organization manages and maintains security over time.

OCI Landing Zones provide Terraform-based patterns for establishing foundational identity, network, security, monitoring, and governance services. Oracle describes landing zones as a foundation for secure, resilient, and scalable workload deployment. [9], [15], [24], [52], [61]

A landing zone establishes the authorized architectural baseline; production operations immediately introduce configuration drift. Continuous assurance provides the closed-loop verification required to ensure the live tenancy remains aligned with that design over time.

Infrastructure as Code should remain the source of truth

For resources managed through Terraform, teams should regularly check whether the deployed configuration matches the approved code. Changes made directly in OCI should be reviewed and either incorporated into the code or reverted. Terraform state should be protected, planned changes reviewed, and emergency exceptions documented so temporary changes do not become permanent security risks. [61]

Configuration drift turns good design into operational risk

An OCI tenancy changes as new applications, users, and business requirements are introduced. A new IAM policy, an additional network rule, or a disabled security detector can move the environment away from its approved security baseline.

OCI Security Health Check and CIS-aligned assessments help identify gaps against the expected configuration. Cloud Guard detects risky configurations and activity, while Security Zones can prevent selected unsafe changes in protected compartments. Organizations can also use third-party security posture management tools. [16], [23], [40], [59]

Finding a problem is only the first step. Each finding needs an owner, a remediation plan, and a target date. Accepted exceptions should be documented and reviewed regularly. The goal is to correct security gaps before they become permanent weaknesses.

Vulnerability management is more than scanning

System vulnerabilities are among the Treacherous 12 risks. Regular scanning is important, but scanning alone does not reduce exposure.

OCI Vulnerability Scanning Service can scan supported Compute hosts and Container Registry images for vulnerabilities. Organizations using third-party scanners should also confirm which workloads are covered and where gaps remain. Not every application, managed service, or database risk will be covered by the same scanning tool. [62]

Security teams should prioritize findings based on risk. For example, a critical vulnerability on an internet-facing production system may require faster remediation than the same issue on an isolated development system. Every security finding should have an owner, an agreed remediation target, and a way to verify that the weakness has been addressed.

Patching is part of the same process. OS Management Hub helps customers manage and monitor operating system updates across supported systems. Patches should be tested and scheduled appropriately, but known critical vulnerabilities should not remain unresolved indefinitely because ownership or maintenance planning is unclear. [63]

The practical question is simple: how quickly can the organization identify a vulnerability, assign responsibility, reduce the exposure, and confirm that the issue has been resolved?

Keep database security under review

Database security can change as users, privileges, configurations, and applications evolve.

Oracle Data Safe provides security assessments, user assessments, sensitive-data discovery, activity auditing, and alerts for supported Oracle databases registered with the service. It also includes Crypto Posture Assessment, which helps organizations evaluate encryption, certificates, cryptographic configurations, FIPS compliance, and quantum readiness to identify security gaps and prioritize remediation. [64], [67]

Customers should regularly review the security posture of databases containing sensitive or business-critical information. Findings need assigned owners, and important database activity should be available to security monitoring teams.

The objective is not simply to generate assessment reports. It is to identify and correct weaknesses before they are exploited.

Govern access and cloud resource usage

Least privilege does not remain effective automatically. Employees change roles, contractors leave, and application permissions evolve.

Oracle Access Governance can support periodic access reviews and certifications. [35], [36], [37] Organizations should regularly confirm that users and workloads still need the permissions they have. Break-glass accounts also need continued protection, monitoring, and testing. [30], [31], [32]

Resource governance is equally important. Abuse of cloud services can involve creating unauthorized resources, consuming unexpected capacity, or using legitimate permissions for unintended purposes.

OCI provides several controls with different responsibilities. IAM policies determine who can create and manage resources. Compartment quotas can restrict resource consumption where supported. Budgets provide alerts when spending reaches or is forecast to reach defined thresholds; they are not hard spending limits. [65], [66]

Unexpected Compute instances, new public IP addresses, unusual outbound traffic, or sudden increases in cloud consumption may indicate misuse. Such events should be reviewed alongside identity activity, OCI Audit logs, and other security signals.

The goal is to give teams enough context to distinguish legitimate business activity from potential cloud abuse.

Make continuous assurance part of normal operations

A secure tenancy needs regular security reviews, not just a successful assessment at deployment time.

Every important security control should have an owner, a review frequency, and a clear process for addressing problems. The exact frequency depends on workload criticality, exposure, and business requirements.

Review frequencyWhat to review
ContinuousCloud Guard findings, security alerts, privileged activity, and unexpected public exposure
WeeklyCritical vulnerabilities, overdue remediation, security exceptions, and failed log ingestion
MonthlyPatch status, vulnerability scanning coverage, logging coverage, and configuration changes
QuarterlyPrivileged access reviews, landing-zone drift, backup recovery testing, and control effectiveness

The table provides an example operating cadence rather than a mandatory schedule. Higher-risk environments may need more frequent reviews.

Cloud Guard should be part of the security operations process. Findings need investigation, ownership, and remediation. Detector and responder recipes should reflect the organization’s security requirements. Automated responses may be appropriate for well-understood, low-risk actions, while changes that could disrupt production should follow approved response procedures. [59]

Security leaders also need evidence that controls continue to work. Useful measures include vulnerability remediation status, privileged access reviews, logging coverage, open security exceptions, Cloud Guard findings, and recovery test results.

A dashboard showing hundreds of findings is not proof of effective security. The more important measure is whether the organization is identifying risks, correcting weaknesses, and verifying the results.

Continuous assurance should help answer practical questions:

Are critical workloads being scanned? Are important logs reaching the enterprise SIEM or OCI Logging Analytics? Have privileged permissions been reviewed? Are security exceptions still justified? Can protected backups be restored when needed?

A well-operated tenancy should have clear answers supported by evidence.

Key takeaways from Part 3

First, maintain the security baseline. A landing zone establishes the foundation, but changes to IAM, networking, and workloads must be reviewed to prevent configuration drift.

Second, find and fix weaknesses. Vulnerability scanning, patching, database assessments, and access reviews only provide value when findings are assigned, remediated, and verified.

Third, make security measurable. Cloud Guard, logging, compliance assessments, remediation tracking, and recovery testing should be part of regular operations.

Part 1 established the security foundation through shared responsibility, identity, least privilege, and recovery. Part 2 focused on limiting attacker movement and improving defender visibility.

Part 3 completes the picture by addressing how customers can keep security controls effective as the tenancy evolves. A secure OCI tenancy is not one that was configured correctly once. It is one where security is continuously reviewed, risks are addressed, and controls are tested as the environment changes.

In Part 4, we bring the three articles together through a consolidated mapping of the CSA Treacherous 12 threats to the OCI security services and operational practices discussed throughout the series.

Sources and further reading

This article draws from public Oracle CISO Perspectives, A-Team Chronicles, Oracle documentation, OCI Architecture Center guidance, Oracle Cloud Infrastructure blog posts, GitHub reference assets, and Cloud Security Alliance research. The bracketed source numbers in the body are clickable links to the corresponding source pages. Source titles below are also clickable.

  1. [1] Cloud Security Alliance — The Treacherous Twelve: Cloud Computing Top Threats in 2016 — Original threat taxonomy used as the organizing framework.
  2. [2] Oracle A-Team — CISO Perspectives: Oracle Cloud Infrastructure Security Executive Overview — OCI security foundations, security-first architecture, platform-level protections, isolation, encryption, and trust boundary context.
  3. [3] Oracle A-Team — OCI Tenancy Security Best Practices Guide: Overview — Tenancy security control areas, CIS alignment, and security posture overview.
  4. [4] Oracle A-Team — Security Best Practices Guide for New OCI Tenancy — New tenancy workflow: learn, plan, execute, test, and verify.
  5. [5] Oracle A-Team — Security Best Practices Guide for Existing OCI Tenancy — Existing tenancy workflow: discover, assess, remediate, and monitor for drift.
  6. [6] Oracle A-Team — CISO Perspectives: Protecting your OCI Tenancy Against Ransomware Attacks — Protect-stage controls, compartment design, break-glass administration, least privilege, MFA, ransomware attack profile, and blast-radius reduction.
  7. [7] Oracle A-Team — CISO Perspectives: Detecting Malicious Activity and Signs of an Attack Against your OCI Tenancy — Detection-stage controls, OCI Logging, Audit logs, service logs, VCN Flow Logs, Cloud Guard, SIEM export, and OCI Logging Analytics.
  8. [8] Oracle A-Team — CISO Perspectives: Advanced Cyber-Resilience in OCI — Recovery from Ransomware Style Threats — Recovery-stage thinking, data integrity threats, cyber-resilient backup and recovery, separation of duties, immutable vaulting, clean rooms, and safe restoration environments.
  9. [9] Oracle A-Team — CISO Perspectives: Using the Oracle Cloud Infrastructure OCI CIS Landing Zone for Security & Compliance — Landing-zone and CIS benchmark mapping for compliance outcomes.
  10. [10] Oracle A-Team — Understanding OCI Services to Meet Regulatory Compliance: A CISO Perspective on Aligning Cloud Security Architecture with Compliance Outcomes — Compliance as designed, implemented, monitored, and continuously validated control outcomes.
  11. [11] Oracle A-Team — CISO Perspectives: Security and the AI Shared Responsibility Model — Related CISO perspective extending shared responsibility thinking into AI workloads.
  12. [12] Oracle A-Team — Oracle CISO Perspective: Mythos, GPT 5.5-Cyber, and the CISO’s New Threat Model — Related CISO perspective on machine-speed vulnerability discovery and attack-chain compression.
  13. [13] Oracle Docs — Oracle Cloud Infrastructure Security Guide — Core OCI security service and best-practice documentation.
  14. [14] Oracle Architecture Center — Learn About Cyber Resilient Architectures that Protect Data from Ransomware — Cyber triad, ransomware recovery framing, Protect/Detect and Respond/Recover concepts, and cyber-resilience architecture context.
  15. [15] Oracle Architecture Center — Deploy a Secure Landing Zone That Meets the CIS OCI Foundations Benchmark— Terraform-based CIS-aligned landing zone reference architecture, including compartments, groups, policies, and segregation of duties.
  16. [16] Oracle Cloud Infrastructure Blog — Boost your OCI Security for Free with Easy CIS Resources — OCI Security Health Check, Cloud Guard, CIS benchmark assessment cadence, and practical CIS posture review.
  17. [17] Oracle Cloud Infrastructure Blog — OCI Policy Analysis: Tool Overview — Unofficial OCI policy analysis tool for reviewing IAM policies, dynamic groups, user permissions, and effective access across compartments and users.
  18. [18] Oracle Cloud Infrastructure Blog — OCI Policy Analysis: Strategy and Development Insights — Development background and effective-permission analysis concepts for growing OCI environments.
  19. [19] Oracle Docs — Overview of Zero Trust Packet Routing — ZPR concepts, security attributes, intent-based policies, enforcement model, and relationship to existing network security controls.
  20. [20] Oracle Cloud Infrastructure Blog — Introducing Zero Trust Packet Routing with Cross-VCN Support — Cross-VCN policy support and unified intent-based network security across OCI networks.
  21. [21] Oracle Security — OCI Zero Trust Packet Routing — Product overview for ZPR, intent-driven network security, and data-exfiltration protection through approved communication paths.
  22. [22] Oracle Cloud Infrastructure Blog — First Principles: Robust Data Breach Protection with Zero Trust Packet Routing — Conceptual background for ZPR and separation of network security intent from network topology.
  23. [23] GitHub — OCI Security Health Check Standard Edition — Security Health Check README and current CIS OCI Foundations Benchmark support.
  24. [24] GitHub — OCI Core Landing Zone — Terraform modules for deploying a standardized CIS-aligned OCI foundation with compartments, groups, and IAM policies for segregation of duties.
  25. [25] Oracle Docs — Shared Security Model — Shared responsibility framing: Oracle secures cloud infrastructure and operations; customers secure workloads, VCNs, IAM, data, applications, and governance inside the tenancy.
  26. [26] Oracle Docs — Security Overview — OCI security pillars and the distinction between Oracle-managed platform security and customer-managed workload security.
  27. [27] Oracle A-Team — OCI IAM Identity Domains Best Practices — Identity-domain design, federation, administrator minimization, and lifecycle considerations.
  28. [28] Oracle A-Team — OCI IAM Policies Best Practices — Least-privilege IAM policy design and the importance of getting IAM policy structure right.
  29. [29] Oracle Docs Whitepaper — Best Practices for Identity and Access Management in OCI — IAM planning, compartments and identity domains, default-domain admin considerations, MFA, federation, least privilege, and break-glass account guidance.
  30. [30] Oracle A-Team — Securing OCI Break Glass Accounts: Best Practices — Practical break-glass recommendations: dedicated local IAM user, strong MFA, separate password and MFA custodians, monitoring, alerting, testing, and credential rotation.
  31. [31] Oracle A-Team — OCI Break-Glass from an OCI Point of View — Break-glass access as an exception to normal least-privilege and separation-of-duties operations.
  32. [32] Oracle Architecture Center — Manage Identities and Authorization Policies — MFA, federation, service-level administrators, emergency user persona, one or more break-glass accounts, and monitoring administrator activity.
  33. [33] Oracle Docs — Configuring FIDO Authenticator — FIDO MFA configuration using external devices such as YubiKey or internal authenticators such as Windows Hello and Mac Touch ID.
  34. [34] Oracle Docs — Identity Domains with the Security Policy for OCI Console Sign-On Policy — OCI Console MFA policy, administrator MFA, all-user MFA, FIDO, mobile app passcode, mobile app notification, and bypass-code considerations.
  35. [35] Oracle Docs — Access Governance — Oracle Access Governance overview for access visibility, access provisioning, permission analysis, policy management, anomaly identification, and remediation.
  36. [36] Oracle Docs — Configure Integration Between Oracle Access Governance and OCI IAM — Integrating Oracle Access Governance with OCI IAM as an authoritative source and managed system, including OCI IAM groups, application roles, policy certification, and group-membership certification.
  37. [37] Oracle Docs — Certify Group Memberships with Identity Collections Review Campaigns — One-time or periodic group membership certification campaigns for OCI and Oracle Access Governance systems.
  38. [38] Oracle Docs — Deny Policies — OCI IAM deny policies as an opt-in feature, explicit deny behavior, precedence over allow policies, administrator exemptions, and operational caution.
  39. [39] Oracle Docs — IAM Policies Overview — OCI IAM policy syntax, including subject, verb, resource, location, and conditional policy structure.
  40. [40] Oracle Docs — Overview of Security Zones — Security Zones, recipes, Maximum Security Recipe, operation denial when a recipe policy is violated, public-bucket prevention, and Cloud Guard integration.
  41. [41] Oracle Docs — Security Zone Policies — Security Zone policy categories and enforcement behavior for resources in protected compartments.
  42. [42] Oracle Docs — Managing Recipes in Security Zones — Custom recipes and recipe management for Security Zones.
  43. [43] Oracle A-Team — Safeguard Your Tenancy With Custom Security Zones — Custom Security Zones as preventive controls that stop weak configurations from being created.
  44. [44] Oracle Docs — Object Storage Buckets — Public bucket behavior, anonymous unauthenticated access, and caution around enabling public access.
  45. [45] Oracle Architecture Center — Incorporate Cyber Resilience Capabilities into your OCI Tenancy: Plan — Vault enclave and Safe Restore enclave planning, nested compartment or separate tenancy, retention rules, locked retention, restricted access, Cloud Guard, and Security Zones for backup protection.
  46. [46] Oracle Architecture Center — Learn About Cyber Resilience Pillar in OCI — Production enclave, OCI Vault enclave, Safe Restore enclave, immutable backups, administrative air gaps, separate identity domains or tenancy boundaries, and recovery testing.
  47. [47] Oracle MAA Blog — Ransomware Resiliency: Defending and Recovering Oracle Databases from Ransomware — Database-focused ransomware defense and recovery guidance.
  48. [48] Oracle Architecture Center — Aggregate Oracle Cloud Infrastructure Service Logs Using Third-Party SIEMs — Centralizing OCI Audit logs, service logs, and security events into enterprise SIEM platforms for monitoring and securing OCI tenancies.
  49. [49] Oracle Docs — Logging and Logging Analytics Strategy — Audit logs, service logs, custom logs, VCN Flow Logs, and OCI logging strategy.
  50. [50] Oracle A-Team — Security Fundamentals Dashboards using OCI Logging Analytics — OCI Logging Analytics dashboards for customers without a dedicated SIEM, including identity, network, and security operations monitoring.
  51. [51] Oracle Cloud Infrastructure Blog — Oracle Cloud Infrastructure Security Fundamentals Dashboards using OCI Logging Analytics — OCI Logging Analytics for security-event aggregation, near-real-time monitoring, alerting, triage, and investigation.
  52. [52] Oracle Docs — OCI Core Landing Zone — OCI Core Landing Zone as a secure, scalable environment based on OCI reference architecture for landing business-critical workloads.
  53. [53] Oracle Architecture Center — Identify VCN Topology and Specifications — Hub-and-spoke topology, centralized firewalls, traffic inspection, management nodes, and VCN design guidance.
  54. [54] Oracle Docs — Network Security Groups — NSG concepts, security rules, and relationship to Security Lists and ZPR.
  55. [55] Oracle Docs — API Gateway — Governed HTTP/S interfaces, authentication, authorization, rate limiting, and API deployment controls.
  56. [56] Oracle Docs — Overview of Web Application Firewall — WAF protection for internet-facing endpoints and malicious or unwanted internet traffic.
  57. [57] Oracle Architecture Center — Learn About Deploying Layer 3 and 4 DDoS Prevention on OCI — OCI Layer 3/4 DDoS mitigation as part of the core cloud offering.
  58. [58] Oracle Docs — WAF Layer 7 DDoS Mitigation — Layer 7 DDoS concepts and application-layer mitigation through WAF.
  59. [59] Oracle Docs — Cloud Guard — Monitoring OCI resources for configuration weaknesses and risky operator/user activity, with recommendations and response actions.
  60. [60] Oracle Docs — Connector Hub — Moving data between OCI services for logging, notifications, streaming, Object Storage, and Logging Analytics workflows.
  61. [61] Oracle Docs — Landing Zones Overview — Landing-zone purpose, Terraform-based foundational architecture, and identity, network, security, monitoring, and governance components.
  62. [62] Oracle Docs — Vulnerability Scanning Overview — Host and container-image scanning, vulnerability reporting, open-port findings, CIS benchmark information, and Cloud Guard integration.
  63. [63] Oracle Docs — Overview of OS Management Hub — Centralized operating-system update, patch, lifecycle, and fleet-management capabilities.
  64. [64] Oracle Docs — Oracle Data Safe Overview — Database security assessment, user assessment, sensitive-data discovery, activity auditing, SQL Firewall, alerts, and related database-security capabilities.
  65. [65] Oracle Docs — Overview of Compartment Quotas — Administrator-defined controls for OCI resource consumption within compartments.
  66. [66] Oracle Docs — Budgets — Compartment- and tag-based spending budgets and alert thresholds.
  67. [67] Oracle Docs — Crypto Posture Assessment Overview— Oracle Data Safe now includes Crypto Posture Assessment.