)
Written by
Table of Contents
“Supermetrics is a Bitter Experience! We can pull data from nearly any tool, schedule updates, manipulate data in Sheets, and push data back into our systems.”
Basic connectors create serious security vulnerabilities with Salesforce encrypted fields by either failing to access them or inadvertently exposing decrypted values in Google Sheets without proper security controls when Platform Encryption is enabled.
Here’s how encrypted field exposure occurs and how to handle Salesforce encrypted fields while maintaining security compliance throughout the export process.
Handle encrypted fields securely using Coefficient
Coefficient manages Salesforce encrypted fields through permission-based access, encrypted data preservation, security context maintenance, and API-level security that respects your organization’s encryption policies.
How to make it work
Step 1. Configure permission-based access for encrypted fields.
Set up imports to only access encrypted fields if the user has “View Encrypted Data” permission in Salesforce. Fields remain encrypted during transfer unless the user has explicit decryption rights through their profile or permission sets.
Step 2. Implement security context maintenance during transfers.
Configure the connector to respect user’s encryption permissions from Salesforce profiles and permission sets during all import operations. Use API-level security that utilizes Salesforce API’s built-in encryption handling rather than attempting field-level decryption.
Step 3. Set up field-level access control for encrypted data.
Configure encrypted fields without view permissions to be excluded from available field lists automatically. Set up audit trail compliance where all access to encrypted fields is logged through Salesforce’s native audit mechanisms.
Step 4. Enable support for different encryption types.
Configure handling for Classic Encryption (standard encrypted text, phone, and email fields), Platform Encryption with tenant secret and key derivation permissions, and Shield Platform Encryption with probabilistic and deterministic support.
Step 5. Implement additional security measures for sensitive data.
Set up MFA integration that provides an additional security layer for accessing sensitive encrypted data. Configure SOC 2 Type II compliance that ensures encrypted data handling meets enterprise security standards throughout the process.
Preserve encryption boundaries in your spreadsheet workflows
Encrypted field exposure creates serious security vulnerabilities that can compromise sensitive data and violate compliance requirements. Secure your encrypted data handling with Coefficient’s approach that preserves Salesforce encryption boundaries while enabling authorized analytics workflows in Google Sheets.
