Re: Encrypting Credit Card Numbers
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 58804
interpreted = N
texte = Thanks Christian and Donavon. I'll work the encryption into my customer database. -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf Of Christian F. Gurney Sent: Friday, July 16, 2004 9:05 AM To: WebDNA Talk Subject: Re: Encrypting Credit Card Numbers Allen: It is essential, from a business perspective (as well as common sense) that you encrypt the credit card numbers and personally identifiable information in the database. New laws in California stipulate that if you have a database with any California resident or business in it and it is somehow compromised and you DID NOT have encryption, you must inform ALL Californians in your system that there was a compromise. Use the ENCRYPT function in WebDNA. It will likely be the most difficult thing you do with WebDNA in that the documentation is so poor on the topic, but it will work. Review the TalkList archive carefully. Set up a simple set of templates to get encryption working before you implement it into your stream. Look at making the encrypt/decrypt of your data elements as include files with the .tpl or .inc extension. We further encypt these include files for protection of the SEED value. Others may have tips as well. Christian F. Gurney Managing Director KG InterDev, LLC cfgurney@kginterdev.com -----Original Message----- From: Allen Frye [mailto:allen@allenfrye.com] Sent: Thursday, July 15, 2004 3:20 PM Subject: Encrypting Credit Card Numbers I'm setting up my own database of orders and customer information to use in addition to the shopping cart files. Should I encrypt the customer information in the database, like their card numbers and other billing info? Is there a standard way to handle this security issue? I'm running Webstar 5 on OSX and webdna 5.1g. Allen Frye Zambooie http://www.zambooie.com ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Thanks Christian and Donavon. I'll work the encryption into my customer database. -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf Of Christian F. Gurney Sent: Friday, July 16, 2004 9:05 AM To: WebDNA Talk Subject: Re: Encrypting Credit Card Numbers Allen: It is essential, from a business perspective (as well as common sense) that you encrypt the credit card numbers and personally identifiable information in the database. New laws in California stipulate that if you have a database with any California resident or business in it and it is somehow compromised and you DID NOT have encryption, you must inform ALL Californians in your system that there was a compromise. Use the ENCRYPT function in WebDNA. It will likely be the most difficult thing you do with WebDNA in that the documentation is so poor on the topic, but it will work. Review the TalkList archive carefully. Set up a simple set of templates to get encryption working before you implement it into your stream. Look at making the encrypt/decrypt of your data elements as include files with the .tpl or .inc extension. We further encypt these include files for protection of the SEED value. Others may have tips as well. Christian F. Gurney Managing Director KG InterDev, LLC cfgurney@kginterdev.com -----Original Message----- From: Allen Frye [mailto:allen@allenfrye.com] Sent: Thursday, July 15, 2004 3:20 PM Subject: Encrypting Credit Card Numbers I'm setting up my own database of orders and customer information to use in addition to the shopping cart files. Should I encrypt the customer information in the database, like their card numbers and other billing info? Is there a standard way to handle this security issue? I'm running Webstar 5 on OSX and webdna 5.1g. Allen Frye Zambooie http://www.zambooie.com ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
"Allen Frye"
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Re1000002: Setting up shop (1997)
Getting Values into Cart the easy way?* (1998)
WebCat2b14MacPlugIn - [include] doesn't hide the search string (1997)
READFILE command? (1998)
Here's how to kill a Butler Database. (1997)
executing via commandline (2003)
Frustration with formulas.db (1999)
easy numfound search? (2001)
Universal root for WC errors? (1997)
Adding more than one item and QTY to cart (2000)
Trouble with Category search (2000)
Sendmail truncation in Eudora Clients (1998)
Internet Explorer 6 Form problems (2005)
Problems appending to database (1997)
How long until WebDNA makes the list? :( (2004)
[Repost] Triggers, again (2000)
hmmm (2006)
change the number format (1997)
Date search - yes or no (1997)
docs for WebCatalog2 (1997)