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


Auditing DB backend to webserver"


Auditing DB backend to webserver"

Author
Message
Barkingdog
Barkingdog
Hall of Fame
Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)

Group: General Forum Members
Points: 3501 Visits: 926

Users Browse to our site and enter sensitive data in our database backend (of course behind the firewall, etc.) The communication between the webserver and database backend is done via a single, anonymous, account as we don't know the identiy of the user using the Browser. So, from the perspective of SOX what type of auditing is required? (We certainly can't identify who has changed what -- only what has been changed.)

TIA,

Bill





Site Owners
Site Owners
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: Administrators
Points: 12709 Visits: 22
No one has responded to this topic yet. Even if you don't have a complete answer, the original poster will appreciate any thoughts you have!
Philip Kelley
Philip Kelley
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1595 Visits: 232

<important disclaimer> As I understand it </important disclaimer> SOX is about unauthorized access or meddling with financial data, or data upon which a companie's finances are based. As this data is coming in via an application or interface designed and written to permit authorized and controlled access to the database, is it in fact covered by SOX?

Hmm. But this is just tossing the onus of responsibility from the DBAs to the web developers, as now they have to determine what needs to be logged and what doesn't. Still, as it's their application, would they not be the most qualified to identify what needs to be logged for SOX purposes? (That's after the out$ide Auditor$ have brought them up to speed on SOX requirements, of course.)

As I've told folks around here, logging everything that SOX wants is, given the current state of technology and implementation, laughable impractical. Why hasn't Microsoft (or Oracle or IBM) jumped on this, as a quick fix and easy sale to all of corporate America? Or maybe they have, and I've missed it. Again, I am wildly uninformed on the subject, but I learn a bit more every day.

Philip





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