Authenticate on a Separate Oracle Instance

I'm going to describe something now that reveals the extent to which we might want to pursue security. What if we segregated the application verification tasks from the actual application data? What security would that buy us? The primary benefits we will achieve are the following:

  • Fewer accounts with passwords, so fewer accounts to attack
  • Reduced ancillary functions (fewer optional database programs), so reduced vulnerabilities
  • Ability to revoke some PUBLIC access to particularly revealing data dictionary views without hampering database development
  • A first database hurdle for hackers to overcome before sensitive data in the second database can be pursued by attack

In this section, we will create ...

Get Expert Oracle and Java Security: Programming Secure Oracle Database Applications with Java now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.

Start your free trial