× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. March 2016

Re: Track all records read from a table

On Wed, Mar 23, 2016 at 4:28 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:


The only reason to use a read trigger is for compliance purposes.


Wouldn't a read trigger be necessary, irregardless of whether the event
were output to a journal or physical file? My understanding is that the
only way to trap a read event would be via trigger. No?


​Correct...what I'm saying is that _IF_ you need a read trigger for
compliance, then it's better to have the trigger write to a journal since
journals are protected by the OS; you can't update or delete an entry in a
journal.

It'd be relatively easy to ​

​prove to an auditor that​ your journal is complete.

If you stick your read log in a DB table, then to prove it's complete you
have to have it journaled so that you can prove that no records in it were
updated or deleted.

Charles

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.