OBIEE 12c Security

Security of Data, Integrity of Systems and Ease of Use are fundamental cornerstones of any system,
-and OBIEE is no exception.

This is the first blog in a series which demonstrates security features and design choices that can made when building your secure Oracle Business Intelligence system.

In the series of blogs I will cover

  1. Data Security
  2. System Integrity
  3. Code Security

Data Security

The security of data covers a wider spectrum from Legal requirement (Data Protection Laws), to simple need to know rules.  On the one hand, the penalty for exposing data to the wrong people could result in serious consequences, while on the other you get to annoy your customers/users.  The severe consequences include legal cost and fines, major damage to your company reputation and the loss of customer revenue.  These all apply internally too, so just because your OBI project is only on the company intranet, dont be lax with the data.

Just to confirm, for Data Security we mean making sure we know the right people have access to the right data.  What they do with that data, e.g. downloading, emailing etc, is up to your company policies and controls, but for us we will focus on who can see what.

 

System Integrity

Anyone running an internet facing business knows just how many people are trying, on a daily basis, to break in.  Whether its kids, fraudsters or government agencies they all have the potential to take down your system.

For internal based systems you could think that the chance of people hacking into your code are reduced, this is up for debate, but the possibility is still there, and what if rival companies have sent in spies to work in your company!

The system intregrity blogs will cover Authentication as well and Authorisation as well as the protocols in place to safeguard access to the components.

 

Code Security

 

Finally I will cover my thoughts on code development and therefore security of code.  This is mainly to ensure that you can develop in a fast way, unincumbered by too much overhead, but still leaves your system code safe and reliable.

 

 

The next blog will cover the many layers of data security…