Comments on: Encrypted Fields in Salesforce http://nonprofitcrm.org/2008/05/31/encrypted-fields-in-salesforce/ Helping nonprofits use and leverage Salesforce.com Sun, 23 Nov 2008 15:20:57 +0000 http://wordpress.org/?v=2.5.1 By: Chris http://nonprofitcrm.org/2008/05/31/encrypted-fields-in-salesforce/#comment-259 Chris Tue, 03 Jun 2008 18:46:14 +0000 http://nonprofitcrm.org/?p=96#comment-259 Be careful about credit card info, though. The official word from Salesforce is that encrypted fields aren't "encrypted enough" to be fully compliant with industry standards. Encrypted field data isn't encrypted on the database itself. For PCI standards on credit card security, go here: https://www.pcisecuritystandards.org/tech/index.htm Be careful about credit card info, though. The official word from Salesforce is that encrypted fields aren’t “encrypted enough” to be fully compliant with industry standards. Encrypted field data isn’t encrypted on the database itself.

For PCI standards on credit card security, go here:
https://www.pcisecuritystandards.org/tech/index.htm

]]> By: David Schach http://nonprofitcrm.org/2008/05/31/encrypted-fields-in-salesforce/#comment-255 David Schach Sat, 31 May 2008 15:18:11 +0000 http://nonprofitcrm.org/?p=96#comment-255 Encrypted fields are great. They have another limitation: If you do not have the "View Encrypted Data" permission, you cannot pass the full value when creating a child record via a custom button/URL. The button will pass the masked value only. Encrypted fields are great. They have another limitation: If you do not have the “View Encrypted Data” permission, you cannot pass the full value when creating a child record via a custom button/URL. The button will pass the masked value only.

]]>