# How to Audit the Top Ten Oracle E-Business Suite Security Risks

- URL: https://www.integrigy.com/security-resources/how-audit-top-ten-oracle-e-business-suite-security-risks
- Published: 2012-10-25
- Type: Webinar
- Products: Oracle E-Business Suite
- Focus areas: Auditing, Security Strategy and Standards
- Compliance: Sarbanes-Oxley (SOX)
- Audience: Auditor
- PDF: https://www.integrigy.com/sites/default/files/How%20to%20Audit%20the%20Top%20Ten%20E-Business%20Suite%20Security%20Risks.pdf
- Recording: https://www.youtube.com/watch?v=5iIOmCssG8M

> First webinar in the ERP Risk Advisors series “In-Source Your IT Audit”, on auditing the top ten Oracle E-Business Suite security risks, based on two of Oracle's best practice security documents.

ERP Risk Advisors opens its "In-Source Your IT Audit" educational webinar series, presented with Integrigy, with how to audit the top ten Oracle E-Business Suite (EBS) security risks. The presentation is based on two of Oracle's "best practice" security documents, interspersed with practical real-world steps for complying with them.

We show how the ten risks lead to data theft, fraud or loss of availability, and how to check six of them, by hand or with our [AppSentry](https://www.integrigy.com/products/appsentry) tool. Auditors can then audit these risks in-house and recommend continuous monitoring of them.

## Key Points

- EBS is delivered with up to 40 seeded application accounts, most with default passwords, some active and some with significant privileges, so check them by decrypting all passwords, by logging in to each of the 25 to 40 accounts, or with AppSentry, which checks every seeded account for default or weak passwords and that it is locked.
- Reviewing who accesses the database requires auditing to be enabled to determine generic database access, and as there is no standard method to review database privileges, they must be reviewed manually, with enough understanding of the data model to know what the granted privileges can access.
- To check the external configuration, review the DMZ web architecture (SSL, network firewall, reverse proxy, a web application firewall such as our [AppDefend](https://www.integrigy.com/products/appdefend), load balancing and caching), consider a penetration test, review the URL firewall configuration, and review the 8 major configuration steps by hand, or with AppSentry, which automates checking 6 of them.
- Over 30 forms, such as Alerts and Collection Plans, allow ad-hoc SQL statements; reviewing access to them is difficult without an SoD tool, which can analyze access to high-risk single functions, but look for use of high-risk seeded responsibilities such as Application Developer, Alert Manager and Quality.
- The signon System Profile Options are weak by default (password length 5 in 11i, now desupported, and 6 in R12, with no hard-to-guess or reuse rule), so validate them, query `FND_USER` for users whose `PASSWORD_LIFESPAN_DAYS` differs from policy and for the password encryption patch, and review account creation and reset workflows with the administrator.
- Most of these risks are ongoing while most audits are point in time, so auditors should recommend continuous controls monitoring (CCM) of them and audit the CCM; tools such as AppSentry are preferable to manual checks, as they integrate all tests in one interface and are updated as the applications and technology stack change.
