Database Reference
In-Depth Information
Chapter11>java testojs.TestOracleJavaSecure 1234-5678-9012
Domain: ORGDOMAIN, Name: OSUSER
Domain: ORGDOMAIN, Name: OSUSER
osuser
APPUSR
127.0.0.1
OSUSER
OSUSER
HRVIEW_ROLE
Oracle success 2)
100, Steven, King, SKING, 515.123.4567, 2003-06-17 00:00:00, AD_PRES, 24000, null, null, 90
Chapter Review
Our goal in this chapter has been to enhance the security of everything we had built so far. We
accomplished that goal on the following fronts:
We programmed Java to encode the
appver
user password (connection string).
•
•
We obfuscated the Java program that does encoding/decoding.
•
We accomplished secured data encryption for data being stored in the database—
specifically our lists of connection strings.
•
We established an administrative role that limits who can update connection
strings for applications.
•
We moved the application verification processes to a new, hardened Oracle
database instance,
apver.
In addition to working toward enhancing the security, we also delved into the following timely
topics:
•
Securing an Oracle user password by various means
•
Using the Oracle client wallet
•
Using Oracle client trace logging
•
Using Oracle thin client (JDBC) trace logging
•
Using the Oracle wrap utility to obfuscate Oracle functions
•
Copying application connection strings from a previous version to the current
application version
•
Adding other authentication credentials, such as FTP passwords, to our
application connection strings list
•
Reviewing weaknesses in PUBLIC access to the data dictionary views
•
Using database links to read data from another database instance
