Re: SOX Reporting Requirement

From: George Leonard - Business Connexion <George.Leonard_at_bcx.co.za>
Date: Tue, 9 Sep 2014 04:54:27 +0000
Message-ID: <0DBE0F85-EE5B-4EBF-80A0-29DBC01F5893_at_bcx.co.za>

Hi David.

Your life is about to get interesting, and oh, you're about to make a storage vendor/sales guy VERY happy.

Yours Sincerely

---

George Leonard
Oracle Engineered System Specialist

Mobile: +27.82 655 2466
eMail: george.leonard_at_bcx.co.za<mailto:george.leonard_at_oracle.com> Web: http://www.bcx.co.za<mailto:george.leonard_at_oracle.com>

[cid:6EA60917-E50D-422D-BF1F-E8C59EADC861]

On 28 Aug 2014, at 5:05 PM, David Barbour <david.barbour1_at_gmail.com<mailto:david.barbour1_at_gmail.com>> wrote:

Morning,

I was wondering how others might be handling the SOX reporting/auditing issue we've been assigned.

The audit folks want to know when DML occurs on a particular table and the original and new value(s). I've implemented FGA on the table and can capture the change. Using the transaction ID, I can then go back to the flashback_transaction_query and get the original values. Of course, the only guarantee of being able to pull the undo sql containing the original values is that the query is performed before the undo retention expires. Pre-supposing I have a job that queries dba_fga_audit_trail and grabs the undo in time, what might happen next? I was thinking of storing the values in a table created specifically for this purpose. Then I'd probably create a view to generate the report.

I'd appreciate any other ideas or refinements. This is a pretty busy database and I've got to be careful bumping undo retention too high. I'm undoubtedly missing something .............

--
http://www.freelists.org/webpage/oracle-l

Received on Tue Sep 09 2014 - 06:54:27 CEST