In this short article I want to describe a use case in which trusted context is a main part and which allows me to zoom in on a few of the options that are not that commonly described. My use case can also be a good alternative to Oracle and Sybase roles using passwords.
Some DBAs end up creating dozens of views on the same table just to manage the security requirements. It can be difficult to track the purpose of all these views and manage them accordingly. Row and column access control may be used as an alternative to views to manage security requirements.
When using LDAP in DB2 to check who had access to a database and which items are available to a user works fine even though looking at db2diag.log you might wonder. The number of messages passing by in that file makes you aware how many checks are done while going thru the data in your databases.
A few days ago, I received an urgent question about how to protect sensitive data stored in a table on their database server. Her boss wanted to make it easy for team members to get the information so they could do testing.
This month, we’re going to talk about security. Maintaining good security in our applications is extremely important. If you’ve read any of the recent reports of credit card theft, identify theft, or just plain data theft, then you have a glimmer of why it is so important.