Re: Read Audit Trail

[Alan Campin <alan0307d@xxxxxxxxx>]

What wrong with a trigger? Also, you could just journal the file and extract
the data you need. Where they smart enough to put the value in a separate
table with just the key and the encrypted data?

On Thu, Apr 2, 2009 at 3:29 PM, Eftimios Pantzopoulos <
Mike.Pantzopoulos@xxxxxxxxxx> wrote:

> _______________________________________________________________________________________
>
> Note: This e-mail is subject to the disclaimer contained at the bottom of
> this message.
>
> _______________________________________________________________________________________
>
>
> The company I'm working for has asked me whether it's possible to track all
> accesses to a file which contains an (encrypted) credit card number.
>
> > From my research I've discovered that there is a READ trigger on the
> iSeries DB2 but it is highly recommended that it not be used, which I can
> understand.
>
>
> I've also come across a reference to a DB2 audit function, but
> unfortunately, only for the LUW version of DB2 (
> http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/admin/t0011540.htm
> )
> . I went searching for the function in iSeries DB2 and couldn't find it.
> Can anyone tell me if it exists, where any good documentation for it is, or
> if not, any alternatives to tracking access to important data. Perhaps there
> are better techniques using normal iSeries authority?
>
>
>
>
>
>
> _______________________________________________________________________________________
>
> The information transmitted in this message and its attachments (if any) is
> intended
> only for the person or entity to which it is addressed.
> The message may contain confidential and/or privileged material. Any
> review,
> retransmission, dissemination or other use of, or taking of any action in
> reliance
> upon this information, by persons or entities other than the intended
> recipient is
> prohibited.
>
> If you have received this in error, please contact the sender and delete
> this e-mail
> and associated material from any computer.
>
> The intended recipient of this e-mail may only use, reproduce, disclose or
> distribute
> the information contained in this e-mail and any attached files, with the
> permission
> of the sender.
>
> This message has been scanned for viruses with Symantec Scan Engine and
> cleared by
> MailMarshal.
>
> _______________________________________________________________________________________
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.