Skip to main content

Webinar

Oracle E-Business Suite Security Myths

54 min recording

Applies to
  • EBS 11i
  • EBS 12.0
  • EBS 12.1

Download PDF (299 KB)

Webinar on common Oracle E-Business Suite security myths, such as that the application and database are secure out of the box, with practical guidelines for securing EBS.

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

Is Oracle E-Business Suite (EBS) secure out of the box? Will implementing Oracle's security best practices make it fully secure? Does your IT security team understand the security issues inherent in EBS? We test these and five other common EBS security myths against the reality, from seeded accounts and Critical Patch Updates to unused modules and network security, with practical guidelines for securing your EBS environment.

Securing EBS is hard and needs a focused effort from Oracle DBAs, the Oracle project team, IT security and internal audit working together. Each can then see which of these assumptions their own environment rests on.

Key Points

  • EBS takes significant effort to secure: seeded application accounts such as ASGADM and MOBILEADM (default password WELCOME) and MOBADM (MOBADM) are active with SYSTEM_ADMINISTRATOR, and R12 adds INDUSTRY DATA and ORACLE12.0.0 to ORACLE12.9.0, all active with invalid passwords; for R12 (then 12.0 and 12.1, now desupported) start with MOS Notes 403537.1, 380490.1 and 376700.1.
  • The Secure Configuration Guides we wrote for Oracle, 189367.1 for 11i (now desupported) and 403537.1 for R12, are a base minimum; Oracle's other notes cover SSL (123718.1 for 11i, 376700.1 for R12), network encryption with the Advanced Security Option (391248.1), TDE (403294.1 for 11i; 732764.1 and 828229.1 for R12) and Database Vault (950018.1).
  • An EBS installation or upgrade includes only the Critical Patch Update (CPU) that was latest at its release, such as October 2008 for 12.0.6 and January 2011 for 12.1.3 (both now desupported), so it almost always needs the latest CPU, and since every module is installed, every CPU must be applied, used modules or not.
  • EBS installs all modules (250+) and all web pages on every application server, in R12 some 8,000 JSP pages, 11,600 OA Framework pages and 4,000 forms, all reaching the database through the APPS account, so parts of every module can be accessed even if it isn't configured or licensed.
  • Firewalls, intrusion protection systems and web application firewalls have few if any rules for EBS, and a WAF must be heavily customized and can hardly block unused EBS modules; our AppDefend for R12 limits EBS modules, detects and reacts to SQL injection, XSS and known EBS vulnerabilities, and logs for PCI-DSS 10.2 (PCI DSS since replaced by 4.0).