Re: Triggers - READ

[jlowary@xxxxxxxxxxxxx]

Loyd,

The application is Credit Card related.  They are wanting to be able to 
have the data encrypted so that only some one using a program with the 
decrypt API could get to the data.  Since I just started this job 3 weeks 
ago I can't get into the specifics as to why or why not using regular 
authority verses encryption.  But do know they only want certain people to 
see whole number, others only last 4 digits, and no one to be able to see 
the data raw (ie: queries, copyfiles, etc.), only way to get to it would 
be with program that calls the decrypt module.  I think this is being 
required by CC Co., but can't swear to it.

Sorry for the delay, been off for the Holidays.

-- Jim




Just wondering... how would the read trigger know when to decrypt the 
fields
and when not? Who does the trigger program trust? Is this a regulatory 
thing
(HIPPA) or a trust issue?

The encryption is of no use against the programmer(s) who have access to 
the
source. If the files contain the right permissions/authorities, only those
users who need to have access already know the contents of the encrypted
fields.

What business problem would this solve?

(I'm not trying to be mean here but you piqued my curiosity.)

Loyd