It depends how seriously you expect someone to try & hack the numbers out.
If the scheme must withstand *serious attack from knowledegable individuals
or groups*, you should:
- encrypt the #s with a well-known, cryptographically secure cipher such as
RC4, 3DES, AES etc;
- ensure the encryption key(s) are large enough, and *not stored anywhere
within the database*, and
- have your whole scheme evaluated by a professional cryptgrapher, becase
there are *many traps for the unwary*.
If the scheme need *not* withstand serious attack from knowledegable
individuals or groups, there are various simple things you could do, but I
am reluctant to suggest them, because they would not provide a level of
security which is appropriate for credit card numbers!
HTH,
TC
"Jamie" <ja********@hotmail.com> wrote in message
news:a0*************************@posting.google.co m...
I am using Microsoft's Acsess database. The problem is I working with
credit card #s and need to encrypt these #s from other employees. The
only field I want to encrypt is that particular field. If any
individual can help resolve this issue please lend a hand.
