SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Auditor Knowledge of Database Environment


Auditor Knowledge of Database Environment

Author
Message
JunkMail Victim
JunkMail Victim
SSC Rookie
SSC Rookie (36 reputation)SSC Rookie (36 reputation)SSC Rookie (36 reputation)SSC Rookie (36 reputation)SSC Rookie (36 reputation)SSC Rookie (36 reputation)SSC Rookie (36 reputation)SSC Rookie (36 reputation)

Group: General Forum Members
Points: 36 Visits: 33

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.


Angel Garcia
Angel Garcia
Grasshopper
Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)

Group: General Forum Members
Points: 13 Visits: 28
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
JunkMail Victim
SSC Rookie
SSC Rookie (36 reputation)SSC Rookie (36 reputation)SSC Rookie (36 reputation)SSC Rookie (36 reputation)SSC Rookie (36 reputation)SSC Rookie (36 reputation)SSC Rookie (36 reputation)SSC Rookie (36 reputation)

Group: General Forum Members
Points: 36 Visits: 33
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
Ramon Jimenez
SSChasing Mays
SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)

Group: General Forum Members
Points: 608 Visits: 121
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
chrisn-585491
SSCrazy
SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)

Group: General Forum Members
Points: 2005 Visits: 2441
Most auditors are clueless, IMHO. Many times I think they focus on paperwork instead of actually examining the environment.
GilaMonster
GilaMonster
SSC Guru
SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)

Group: General Forum Members
Points: 90439 Visits: 45284
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
Ninja's_RGR'us
SSC-Dedicated
SSC-Dedicated (30K reputation)SSC-Dedicated (30K reputation)SSC-Dedicated (30K reputation)SSC-Dedicated (30K reputation)SSC-Dedicated (30K reputation)SSC-Dedicated (30K reputation)SSC-Dedicated (30K reputation)SSC-Dedicated (30K reputation)

Group: General Forum Members
Points: 30037 Visits: 9671
GilaMonster (9/13/2010)
Please note: 4 year old thread.



Are they any less clueless now?

Not from what I've seen here.
GilaMonster
GilaMonster
SSC Guru
SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)

Group: General Forum Members
Points: 90439 Visits: 45284
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
Eric M Russell
SSChampion
SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)

Group: General Forum Members
Points: 12670 Visits: 10693
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.


"The universe is complicated and for the most part beyond your control, but your life is only as complicated as you choose it to be."
JunkMail Victim
JunkMail Victim
SSC Rookie
SSC Rookie (36 reputation)SSC Rookie (36 reputation)SSC Rookie (36 reputation)SSC Rookie (36 reputation)SSC Rookie (36 reputation)SSC Rookie (36 reputation)SSC Rookie (36 reputation)SSC Rookie (36 reputation)

Group: General Forum Members
Points: 36 Visits: 33
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.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search