Skip to main content

Webinar

Security Considerations When Running Oracle E-Business Suite in the Cloud

Download PDF (576 KB)

Webinar on how Oracle E-Business Suite security changes on Oracle Cloud Infrastructure or Amazon Web Services: architecture, provisioning, separation of duties, patching, encryption and privilege management.

Play the Recording: Security Considerations When Running Oracle E-Business Suite in the Cloud
The recording plays from YouTube (youtube-nocookie.com) once you start it.

How does Oracle E-Business Suite security change when you move to the cloud? Running EBS at Oracle Cloud Infrastructure (OCI) or Amazon Web Services (AWS) brings security advantages and disadvantages, but you still own your data and are still responsible for keeping it secure.

We first discuss the security differences between running EBS in the cloud and on-premise, then review the advantages and disadvantages in architecture, provisioning, separation of duties, patching, encryption and privilege management. DBAs, security teams and auditors will know what to require of a cloud provider and what to secure themselves when running EBS at OCI or AWS.

Key Points

  • Our first recommendation is in the contract: before signing, require a SOC 1 report every year, push for SOC 2 and Cloud Security Alliance Cloud Controls Matrix (CCM) controls, read the SOC report carefully, and vet the provider's supply chain for insiders, since clouds create more insiders.
  • At OCI, the EBS application tiers run on Compute Cloud Service and the database runs there with your own licenses or on a VM or Exadata DB System, where Enterprise Edition includes TDE and Data Masking and Subsetting, but Database Vault, Data Redaction and Label Security come only with High Performance, Extreme Performance or Exadata.
  • Secure the provider's console with separate admin accounts for production and test/development, and at AWS with multi-factor authentication and IAM super admins rather than the root account, send all operating system access through a bastion host, and terminate SSL/TLS at a load balancer, since the EBS SSL stack is dated and needs periodic patching.
  • OCI Database Cloud Service enables SQL*Net encryption and TDE by default, leaving you to rotate the TDE master key and possibly to encrypt lift-and-shift databases, while on Compute Cloud Service and at AWS you set SQLNET.ENCRYPTION_SERVER = required and SQLNET.CRYPTO_CHECKSUM_SERVER = required yourself and license TDE separately.
  • TDE protects only data at rest and DBAs still have full access, so consider Database Vault, included with OCI High and Extreme Performance but licensed separately at AWS, to stop privileged users' ad-hoc access to sensitive data, separate DBA and security administrator duties, and limit each type of account by IP address with command rules.
  • CPU patches are available quickly for OCI Database Cloud Service through the Service Console or dbaascli, while Compute Cloud Service and AWS are patched as on-premise, and since OCI keeps the alert log, audit files and listener logs only 14 days by default, feed them to a log and audit framework such as the Integrigy Guide to Auditing and Logging in Oracle E-Business Suite.