March 11, 2005 at 10:37 am
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
March 14, 2005 at 8:00 am
This was removed by the editor as SPAM
March 14, 2005 at 4:17 pm
<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
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply