Author: Robert Westervelt
While many companies think they're being proactive with security, too many are addressing security at the application level rather than the database level. Securing Oracle is not difficult, but some companies don't follow the most basic steps. It only takes a little bit of diligence and systematic thinking.
In this article I will discuss what steps companies can take to secure their oracle DBMS.
Oracle Security - Up to date Listener service:
Make sure that the Listener service is kept up to date.
Oracle Security - Password Protected Listener service:
Make sure that a password is set on the Listener service.
Oracle Security - Row-level security:
Oracle's row-level security feature provides access control at the individual row level. Rather than opening up an entire table to any individual user who has any privileges on the table, row-level security restricts access to specific rows in a table.
Oracle Security - Application Level Security:
The biggest concern is that database security is not being handled at the database level, but at the application level. That can cause a lot of holes. Companies are currently focusing on Sarbanes-Oxley compliance, HIPPA (Health Insurance Portability and Accountability Act) regulations, and credit card rules. Nearly all companies are working to create an audit trail to comply with Sarbanes-Oxley and they are working to ensure that their financial information is secure.
Oracle Security - Encrypted and safe data: Companies must ensure that customer data is encrypted and out of the reach of attackers.
Oracle Security - Process documentation and limitation:
In order to be a partner with Visa, Mastercard or American Express, companies must document their processes and show that access to customer information is limited.
Oracle Security - Documentation of security processes:
Companies must document their security processes. By doing this, they identify the potential holes. Always check to see if there is a policy that restricts access to information based on who an employee is. For example, a customer service representative shouldn't see all information except for the customers they handle.
Oracle Security - Protected networks:
Companies securing themselves must ensure that the network itself is protected. Protection is needed from an outsider who can come into a network and sniff or just view packets of information flowing across the network. Data can flow across encrypted to protect the information from spoofing, which is the modifying of that data. This is all very important and relatively easy to do.
More Oracle Articles, Database Articles and DBA Tips
Database Security: Step by step guideline
Expert Tips on Drop Temporary Tablespace Hangs!!
Inside Oracle Compression!!
Oracle 11g Enhanced Optimizer Statistics Maintenance!!
DBA Tips for Changing Column Order in Oracle!!
|