# Oracle Database Security Myths

- URL: https://www.integrigy.com/security-resources/oracle-database-security-myths
- Published: 2012-12-19
- Type: Webinar
- Products: Oracle Database
- PDF: https://www.integrigy.com/sites/default/files/Integrigy%20Security%20Myths%20and%20the%20Oracle%20Database.pdf
- Recording: https://www.youtube.com/watch?v=4UrmfuSDrr0

> Webinar on common Oracle Database security myths, such as that the database is secure out of the box or that upgrades include the latest security patches, with practical guidelines for securing it.

Is the Oracle Database secure out of the box? Do database upgrades include the latest security patches? We test eight common Oracle Database security myths against the reality, from security checklists, go-live hardening and database security tools to password hashes and audit data, along with practical guidelines for securing your Oracle Database.

DBAs, IT security and internal audit teams can then see where their databases fall short and work together to close the gaps.

## Key Points

- Oracle improved 11g's default installation, setting passwords, locking accounts and adding better password profiles, but securing it still takes significant effort, and checklists such as Oracle's Database Security Checklist, the DoD DISA STIG and the CIS Oracle Benchmarks (for 9i to 11g, all now desupported) are only a base minimum, often in conflict with application configuration.
- Security decays over time with customization, upgrades and published exploits, and falls between the cracks when DBAs put performance and uptime first, IT security doesn't understand Oracle Database security and internal audit focuses on application controls, so have them work together, learn what sensitive data each database holds, and periodically validate security and configuration.
- A database install or upgrade includes only the CPU that was latest when its patch set was released, such as January 2009 for 11.1.0.7 and July 2011 for 11.2.0.3 (releases now desupported), so a fresh installation or upgrade almost always needs the latest CPU applied.
- No database security tool solves database security: monitoring and auditing tools are only part of a program covering inventory, configuration, access, auditing, monitoring, vulnerability and encryption, which moves from planning through implementation to ongoing work such as living database and data inventories and periodic vulnerability scans.
- The password hash algorithm is published and a hash is common across all versions and platforms (SYSTEM/MANAGER is always D4DF7931AB130E37), so hashes cloned to development can be brute forced: 8 characters take 42 days on a desktop or 10 hours on a GPU; 11g, now desupported, added SHA-1 but kept the old DES hash.
- Most audit data fields can be spoofed: of the session values audit trails record, only the database user name and IP address cannot be, while OS user name, schema name, machine, terminal, program, client process ID, module, action, client info and client ID all can.
