Encrypt Sensitive Data while Preserving Platform Functionality

preview_player
Показать описание
Salesforce has led the industry with trust and security on our cloud platform. A new feature for Summer ‘15, Platform Encryption is now generally available* as part of Salesforce Shield. Use Platform Encryption so your company can confidently prove compliance with privacy policies, regulatory requirements, and contractual obligations for handling private data.

Platform Encryption helps address some concerns about protecting confidential information. It prevents sensitive data from residing in clear, decipherable form and allows you to manage your tenant secrets, which are used to derive the keys that protect your data. Salesforce is committed to high security standards and offers multiple data encryption options. Customers who want to adopt or extend their use of Salesforce can consider using Platform Encryption to comply with various standards.

*Note Platform Encryption and Salesforce Shield require additional licenses.

What you will learn:

Understand core concepts around the Salesforce Shield encryption as a service feature.

Hear how you can enable and manage Salesforce Shield for end users.

Learn to rotate and manage your key.

See use of Salesforce Shield with Search, Reports, and SOQL

Gain API Access to Platform Encryption Features
Рекомендации по теме
Комментарии
Автор

0:01- 4:01 Introductions (skip)
4:25-7:01 Shield offerings
. Specifically Platform Encryption
The Demo starts in the 25th Minute

srilankangenie
Автор

Hello, Thanks for this great information. I have a question.... We hace 2 customers who want to bring there own keys in our salesforce org. I wish to ask how is this possible in "BYOK" scenario ? we have to consider the fact that only 1 tenant key can be active at 1 time. consider this... Customer A brings there key in system... data is encrypted as per them... Now when customer B brings their key in system... Previous key of customer A is archived... and all records gets encrypted as per key og customer B... even when customer A inserts a record in their data table, it get's encrypted as per current active key of customer B... so how this scenario can be handled ?

saurabhagarwal
visit shbcf.ru