Pratum Blog

For this last point on securing Oracle E-Business Suite (11i) I want to talk about the infrastructure. My last couple of posts have been database specific from a software perspective. I now want to look at securing our databases from a hardware perspective.

Lots of companies deploy internet facing firewalls. They create a DMZ or demilitarized zone which houses their web, email, DNS and other internet facing servers. This DMZ area is virtual wasteland. It’s more secure than the internet but less secure than our internal networks. In essence it really shouldn’t be trusted.

Our internal networks however are usually fully trusted and considered safe and secure. You couldn’t be more wrong. It’s akin to putting up a privacy fence all the way around your property and locking the gate. In this scenario, you assume that your yard on the inside is more secure than the street on the outside but you still lock your front door. Even inside your house you may have important areas secured such as a small safe, file cabinet, jewelry or firearm storage, you get the picture.

What we often do in securing our networks is to put up a fence, lock the gate, lock the front door and then leave the cash, bank info, jewelry, firearms and other valuables out on the living room floor with a huge sign reading “All the good stuff is right here, take what you need.”

Databases are treasure troves of information yet we rarely wrap additional protection around them on internal networks. I recommend every database server should be placed behind a firewall. The access control list (ACL) should explicitly allow only connections from the application servers, backup servers or other critical components. In today’s environments, end users should rarely need direct access to the actual database. They will typically get their access via a web application of some sort.

By limiting direct access to the database you are reducing the chance that someone who can bypass your application and database level logical controls, such as usernames/password, granted privileges, roles, etc. the ability to interface with it on a hardware or system level. Just like putting your jewelry in a safe inside your locked house. Not everyone who needs access to your network needs access to your databases.

As we start to realize that our internal networks aren’t a whole lot safer than the DMZ or even the internet, we need to provide additional security zones. This will help provide another layer of protection for our most critical assets. Does this create a little more administrative work? Does it cost a little more money? Sure. Is it worth it? Only your risk assessment can tell you that. You have done a risk assessment haven’t you?


Get our blog posts delivered to your inbox:

The information we track while users are on our websites helps us analyze site traffic, optimize site performance, improve our services, and identify new products and services of interest to our users. To learn more please see our Privacy Policy.