Skip to main content

Webinar

DevSecOps in an Oracle E-Business Suite Environment

Download PDF (467 KB)

Webinar on building security into the Oracle E-Business Suite RICE/CEMLI customization lifecycle with DevSecOps, despite the many small development objects and languages EBS customizations involve.

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

Development in Oracle E-Business Suite (EBS) is different from building a custom application: it is many small development objects, such as reports, interfaces, conversions and extensions, built with Oracle Forms and Reports, JSP, OA Framework, Oracle APEX and concurrent manager programs, in at least nine languages. DevSecOps, the automation and integration of security into the development and operations process (DevOps), brings security into the EBS RICE/CEMLI customization lifecycle early.

We show EBS developers, DBAs and security teams how to apply DevSecOps techniques at each stage of the EBS development lifecycle and how to control and audit changes to the EBS environment.

Key Points

  • In our ERP security staffing reviews, developers, operations and IT security work in a ratio of 25:10:1 by hours, so DevSecOps relies on automated code analysis, security testing and compliance verification.
  • The EBS DevSecOps cycle puts security controls at each of eight stages, including threat modeling at plan, SAST, secrets scanning and peer code reviews at build, test data scrambling at test, release approvals at release, a web application firewall and security patching at operate, and file integrity monitoring at monitor.
  • All changes to EBS production must go through change management: define what counts as an EBS change, let only authorized users make changes or migrate code, give developers only read access to production and deploy customizations with an automated tool.
  • EBS changes fall into five types with different risks and processes: application security changes, application changes and patches, database security changes, database changes and patches, and customization and development changes.
  • Many database changes are made through generic, privileged accounts, which makes the named DBA hard to identify, and most organizations do not have an audit trail over the activities that should go through change management.
  • Harden the stack with the "Secure Configuration Guide for Oracle E-Business Suite" as a starting point, apply Critical Patch Updates to EBS, WebLogic and the database regularly, and use AppDefend for virtual patching where patches can't be applied regularly.