Auditor Knowledge of Database Environment

Question

Auditor Knowledge of Database Environment

JunkMail Victim

Old Hand

Points: 392
More actions
September 1, 2006 at 5:13 am

#172346

Now that most companies have gone through at least one round of SOX, I'm wondering what everyone's assessment of the auditor's understanding of the database environment is.
I've found them to concentrate on the compiled executables of the client applications, but not think much about the unencrypted business logic that resides in stored procedures and triggers in the database environment. In our case, they seem to think of databases as only data storage, and don't consider how powerful and immediate the environment really is.
There's probably a mosaic of response depending on what auditor companies have had, but I'm curious what everyone's experience has been.
Thanks.
September 4, 2006 at 8:00 am

This was removed by the editor as SPAM

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply

Angel Garcia SSC Journeyman Points: 75 More actions · Answer 1

seems pretty obvious to me that the auditors we got really have no understanding of what they are asking for. most of things they ask for or find are being read from a list of common best practices in the industry

JunkMail Victim Old Hand Points: 392 More actions · Answer 2

The last thing I want to do is push an auditor into doing a deeper audit, but they don't seem to understand tiered architecture. I would agree with you that they're working with a checklist, and don't know when they should look deeper.

Ramon Jimenez Default port Points: 1467 More actions · Answer 3

I've experienced some auditories, and my conclusion is that in many of the cases auditors don't have a deep knowledge of whatever are they auditing and they are following a checklist.

Regards Ramon

chrisn-585491 SSCoach Points: 16006 More actions · Answer 4

Most auditors are clueless, IMHO. Many times I think they focus on paperwork instead of actually examining the environment.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 5

Please note: 4 year old thread.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Ninja's_RGR'us SSC Guru Points: 294069 More actions · Answer 6

GilaMonster (9/13/2010)
Please note: 4 year old thread.

Are they any less clueless now?

Not from what I've seen here.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 7

Ninja's_RGR'us (9/13/2010)
GilaMonster (9/13/2010)
Please note: 4 year old thread.
Are they any less clueless now?
Not from what I've seen here.

Doubt it. That would violate the law of conservation of cluelessness.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Eric M Russell SSC Guru Points: 125560 More actions · Answer 8

JunkMail Victim (9/1/2006)
I've found them to concentrate on the compiled executables of the client applications, but not think much about the unencrypted business logic that resides in stored procedures and triggers inthe database environment. In our case, they seem to think of databases as only data storage, and don't consider how powerful and immediate the environment really is.

The fact that stored procedures, triggers, views and other database objects containing SQL are not encrypted (or at best weakly encrypted) is really not an issue. By default, a user account that is not a member of the DBO or sysadmin role doesn't have VIEW SCHEMA, ALTER TRACE, VIEW SERVER STATE, etc. permission unless you explicitly grant it to them, so they shouldn't be able to see the SQL. A user account for use by the application should be a member of a role that grants them only exec permission on specific stored procedures and maybe access to some tables. That's what the auditor should be looking for.

"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

JunkMail Victim Old Hand Points: 392 More actions · Answer 9

Thanks Eric. In the four years the thread has been open that's probably the most effort anyone has put into the answer. It's not what I was really looking for, but at least you didn't descend into insulting the auditors. I think they largely do a responsible job under varying levels of cooperation.

My interest was in knowing whether people were experiencing something similar to what I experienced at the time. Auditors appeared to put greater emphasis on application security, configuration and change management than they did on the database environment. I'm also curious whether DBAs who understand the power of the environment they work in think that is appropriate.

Thanks again.