Throughout this series, we have examined how Oracle Cloud Infrastructure services and security practices can help organizations address the Cloud Security Alliance’s Treacherous 12 cloud threats.

Part 1 focused on establishing a secure foundation through identity management, least privilege, data protection, and recovery. Part 2 examined network security, API protection, and the detection of suspicious activity. Part 3 addressed the ongoing work of governance, vulnerability management, and continuous security assurance.

These are not independent activities. Protecting an OCI tenancy requires preventive controls, visibility into security-relevant activity, and regular validation that those controls remain effective.

The following matrix brings the three articles together, illustrating how OCI security services and operational practices contribute to reducing the risks associated with each of the Treacherous 12 threats.

CSA Treacherous 12: Illustrative Mapping to OCI Services and Operational Controls:

#CSA Treacherous 12 ThreatPart 1 — Foundation, Identity & RecoveryPart 2 — Network, APIs & DetectionPart 3 — Governance & Continuous Assurance
1Data BreachesLeverage OCI’s built-in encryption and tenant isolation. Enforce least-privilege IAM policies, protect sensitive data using appropriate encryption and access controls, and use Security Zones to prevent supported insecure configurations.Use NSGs, ZPR, and Network Firewall to restrict unnecessary network connectivity and reduce data-exfiltration paths. Monitor OCI Audit logs, VCN Flow Logs, Cloud Guard findings, and relevant application or database logs through an enterprise SIEM or OCI Logging Analytics, as applicable.Conduct periodic data security assessments using Oracle Data Safe for supported databases, including sensitive-data discovery and Crypto Posture Assessment. Review excessive permissions, public exposure, and configuration drift, and remediate identified gaps.
2Weak Identity, Credential and Access ManagementFollow OCI IAM Identity Domains best practices, enforce MFA for interactive users, configure federation where appropriate, apply least-privilege IAM policies, maintain separation of duties, and secure break-glass administrator accounts.Monitor OCI Audit logs and Cloud Guard findings through an enterprise SIEM or OCI Logging Analytics to identify suspicious administrative activity and security-sensitive IAM changes. Include identity-domain audit events where appropriate.Conduct periodic access reviews and certifications using Oracle Access Governance, third-party identity governance tools or established manual processes. Review IAM policies, group memberships, privileged access, and user lifecycle changes, and revoke unnecessary permissions.
3Insecure APIsEnforce least-privilege OCI IAM policies to control access to OCI service APIs. Secure credentials used for programmatic access and follow OCI identity and authentication best practices.Use OCI API Gateway for authentication, authorization policies, supported request validation, rate limiting, and logging. Apply OCI WAF to appropriate internet-facing applications and use private endpoints where public access is unnecessary.Periodically review API exposure, authentication and authorization configurations, API Gateway and WAF policies, and logging coverage. Identify configuration drift through Terraform reviews and security assessments and remediate identified gaps.
4System and Application VulnerabilitiesLeverage OCI’s built-in platform security protections, including hardware root of trust, tenant isolation, and off-box network virtualization, while following shared responsibility principles for securing customer workloads.Use OCI WAF to help protect web applications against supported attacks. Apply NSGs, ZPR, and Network Firewall to restrict unnecessary connectivity, reduce exposure, and limit lateral movement if a workload is compromised.Perform regular vulnerability assessments using OCI Vulnerability Scanning Service or third-party scanning tools. Use OS Management Hub to manage patching on supported systems, prioritize critical vulnerabilities, and verify remediation.
5Account HijackingEnforce MFA for interactive user sign-ins, follow OCI IAM Identity Domains best practices, apply least-privilege IAM policies, and secure API signing keys and other credentials.Monitor OCI Audit logs, API Gateway logs and Cloud Guard findings through an enterprise SIEM or OCI Logging Analytics to identify suspicious API activity, IAM credential changes, and unauthorized administrative actions.Conduct periodic reviews of user accounts, privileged permissions, API signing keys, other authentication tokens. Rotate or revoke unnecessary or outdated credentials, and review Cloud Guard findings for credential-related risks.
6Malicious InsidersEnforce least-privilege OCI IAM policies, MFA, and separation of duties. Restrict privileged administrative access and scope IAM permissions to only the resources and compartments required for authorized tasks.Monitor OCI Audit logs OCI Alerts, Cloud Guard findings, and notifications generated by OCI Events rules through an enterprise SIEM or OCI Logging Analytics, where integrated, to identify suspicious privileged activity, sensitive configuration changes, and unexpected resource creation. Use NSGs and ZPR to restrict unnecessary network connectivity.Conduct periodic access reviews and certifications using Oracle Access Governance, third-party identity governance tools, or established manual processes. Review privileged OCI IAM permissions, use Oracle Data Safe to audit activity in supported databases, and remediate excessive or unnecessary access.
7Advanced Persistent Threats (APTs)Apply OCI IAM Identity Domains best practices, enforce MFA and least privilege, maintain separation of duties, and secure and periodically test break-glass administrator accounts to preserve emergency administrative access during a security incident.Use network segmentation with VCNs, NSGs, ZPR, and Network Firewall to restrict lateral movement. Monitor OCI Audit logs, VCN Flow Logs, and Cloud Guard findings through an enterprise SIEM or OCI Logging Analytics to help detect suspicious activity.Perform regular vulnerability assessments using Vulnerability Scanning Service, manage patching with OS Management Hub, review access permissions, detect configuration drift, and remediate weaknesses that attackers could exploit or use to maintain access.
8Data LossProtect backups using immutable storage configurations and locked Object Storage retention rules where applicable. Maintain isolated recovery environments and perform regular restoration testing.Monitor OCI Audit logs for supported changes to backup access, retention policies, and recovery configurations. Use Cloud Guard or third-party CSPM tools to identify supported misconfigurations, and correlate findings with relevant service logs where available.Conduct periodic reviews of backup protection, retention policies, and recovery configurations. Perform regular restore testing and remediate identified gaps.
9Insufficient Due DiligenceEstablish a security baseline using shared responsibility principles, OCI Landing Zones, Security Zones, CIS-aligned architecture, and least-privilege IAM policies.Review network and API security configurations and verify security logging and monitoring coverage. Integrate relevant logs with an enterprise SIEM or OCI Logging Analytics.Conduct regular OCI Security Health Checks and CIS-aligned assessments. Review Terraform configuration drift, quota policies, and OCI Events rules. Track remediation and maintain evidence of control effectiveness.
10Abuse and Nefarious Use of Cloud ServicesEnforce least-privilege OCI IAM policies to restrict unauthorized resource creation and management. Configure quotas for supported resources at compartment or tenancy scope, review applicable Oracle-defined service limits, and use OCI Events and Notifications to alert administrators when selected resources are created.Monitor OCI Audit logs, Cloud Guard findings, and OCI Events notifications to identify unexpected resource creation or configuration changes. Correlate these signals with relevant service logs, VCN Flow Logs, and resource-usage metrics to investigate potential cloud abuse.Periodically review quota policies, OCI service-limit utilization, budget alerts, and unusual resource consumption. Validate resource-creation notification rules, review IAM permissions for resource provisioning, and adjust governance controls as requirements change.
11Denial of ServiceLeverage OCI’s built-in platform protections and follow shared responsibility principles when designing resilient workloads.Use OCI Layer 3/4 DDoS protection, OCI WAF for supported Layer 7 protections, API Gateway rate limiting, Load Balancers, and resilient application architecture to reduce denial-of-service exposure.Review operational readiness and service-limit headroom to support legitimate workload scaling. Configure OCI Monitoring alarms and Notifications, assess capacity requirements, and periodically test incident response procedures.
12Shared Technology IssuesLeverage Oracle-managed tenant isolation, hardware root of trust, and off-box network virtualization to reduce risks associated with shared cloud infrastructure.Apply customer workload segmentation using VCNs, NSGs, and ZPR to provide additional network isolation between workloads.Conduct periodic security assessments and patching of customer-managed workloads, while recognizing Oracle’s responsibility for securing the underlying shared infrastructure.

Please note that this is an illustrative mapping based on the security controls discussed across the three-part series. The controls may prevent, detect, contain, or support recovery from threats; they do not individually eliminate those risks. As we know Cloud Security is a shared responsibility, it depends on Oracle’s platform responsibilities and the customer’s architecture, configuration, and operating practices.

The mapping reinforces three important lessons.

  1.  A single cloud security service cannot address a threat on its own. Identity, network, data protection, logging, and recovery controls must work together.
  2. Not every control has the same purpose. Some prevent unsafe actions, others detect suspicious activity, and others help organizations recover or verify that protections remain effective.
  3. Security does not end when the tenancy is deployed. Changes in workloads, users, permissions, and configurations require continued monitoring, governance, and remediation.