Cuneiform for Salesforce and Trust
- Mehmet Orun
- Abraham Lloyd
- Nickolette De Clerck
This document will share how Cuneiform® for Salesforce® products honor and respect trust requirements in their feature set, operating model, and architecture. Salesforce customers should use Cuneiform® for CRM and Cuneiform® for Data Cloud with confidence. It explains why these products should be considered trusted solutions.
APPLIES TO | CUNEIFORM FOR CRM CUNEIFORM FOR DATA CLOUD
Table of Contents
- 1 Trust Matters to Salesforce Customers
- 2 Trust Is a Core Value of Our Product
- 2.1 Your CRM and Data Cloud Data Never Leaves Your Org
- 2.2 Your CRM and Data Cloud Data Is Never Modified
- 2.3 Salesforce Security Best Practices are Incorporated
- 2.4 Data Profiling Is Always Performed in the Context of a Permission-ed User
- 2.5 No External Requests Are Made Via Our Product
- 2.6 Governor Limits Are Always Respected
- 2.7 Data Storage Impact Is Minimal
- 2.8 Profiling Results Access Is Managed through Existing Salesforce Security Features
- 3 PeerNova’s Commitment to Data Security
Trust Matters to Salesforce Customers
We recognize that, as a CRM or Data Cloud Administrator, your organization entrusts you with ensuring that:
Your Salesforce org is secure.
Your Salesforce org data is reliable and trustworthy.
Your company is using the Salesforce platform to its fullest potential.
As part of this responsibility, Admins want to ensure they don’t introduce applications that may negatively impact your org or business data.
We are committed to our customers and will always champion trust as a value in our solution. Our solution will evolve with your feedback – and any feature we implement will adhere to Salesforce best practices.
Trust Is a Core Value of Our Product
We’ve designed Cuneiform for CRM and Cuneiform for Data Cloud to profile your data in the most secure and performant way possible. Trust has been built into our product from day one – and you can always count on Cuneiform for Salesforce products to provide value while respecting these fundamental principles.
Your CRM and Data Cloud Data Never Leaves Your Org
All data profiling and analysis activities are performed in your Salesforce org. Cuneiform for CRM and Cuneiform for Data Cloud do not export or transfer your data outside of your org to generate data quality or data reliability insights.
All profiling and data quality analysis always occurs within your Salesforce org.
Cuneiform for Salesforce products never export or move your data off-platform to analyze it. They perform all profiling and data quality calculations within your Salesforce org.
Your CRM and Data Cloud Data Is Never Modified
All data is profiled and analyzed in read-only mode. Cuneiform for Salesforce products never modify or update data that is analyzed. All profiling and data quality insights captured by Cuneiform for CRM and Cuneiform for Data Cloud are written to a separate set of custom objects in our namespace.
Cuneiform for Salesforce products only write to the custom objects included in our namespace.
Cuneiform for Salesforce products do not modify your Salesforce object or field metadata. They also also do not change your Salesforce records. Our products read the data you specify – and captures insights into a separate set of custom objects.
Salesforce Security Best Practices are Incorporated
Cuneiform for CRM and Cuneiform for Data Cloud are Salesforce AppExchange security-approved and employ Salesforce Security best practices – including Salesforce Permission Sets, Connected Applications, and Custom Metadata to securely access your Salesforce org's data.
We follow the principle of least permission with our security configuration, do not leverage user sessions, validate data access with every profiling activity, and audit exceptions for Admins to review.
Cuneiform for Salesforce products validate data access before every profiling or data quality analysis activity. We only access the Salesforce objects, fields, and data available to our application's users via their provisioned permissions. No system-level permissions are used.
Data Profiling Is Always Performed in the Context of a Permission-ed User
Profiling is always performed within the context of a user – leveraging their assigned profiles and permission sets. This approach to profiling ensures that field-level security (FLS) and record access are always respected.
Cuneiform for Salesforce products always profiled in the context of a Salesforce user. This ensures that all Salesforce Object, Field, and record access is respected leveraging the user’s assigned permissions.
Cuneiform for CRM’s security design ensures that profiling is always performed against the fields and records a user can access. Cuneiform for Data Cloud’s security design ensures that profiling is always performed against the Data Lake Objects a user can access. Both products respect and adhere to user permissions – and never circumvents them through a System or Automated User context.
No External Requests Are Made Via Our Product
Cuneiform for Salesforce products make no external API requests from within your Salesforce org and require no remote site settings configuration. All processing and analysis occur within your Salesforce org.
No remote site settings are configured with Cuneiform for Salesforce products.
Cuneiform for CRM and Cuneiform for Data Cloud do not make any external requests as part of their profiling and data quality analysis capabilities. All Processing and analysis occurs within your Salesforce org.
Governor Limits Are Always Respected
Our profiling and data quality analysis features are created using the latest Salesforce Platform technologies and architected to respect the resources and Governor limits Salesforce enforces with customers.
We respect all SOQL and API timeouts, concurrency constraints, and usage limits. Our product includes multiple retry mechanisms to retry profiling gracefully processes a set number of times – if a failure occurs.
Cuneiform for Salesforce products work within Governor Limits to ensure that the resources available to your Salesforce org stay available – and allow your business to thrive. Governor Limits are incorporated into our product design and architecture.
Data Storage Impact Is Minimal
As we write profiling and data quality analysis results for our custom objects, these insights occupy storage, representing a potential cost to Salesforce customers. We have thoughtfully designed our data-model design and minimized the number of records written with insights.
We generate a record for every Salesforce object and field that is profiled. We also create a record for the top [x] and bottom [x] field values profiled and for every Data Quality and Business Impact KPI defined. These records are related via master/detail relationships.
Cuneiform for CRM and Cuneiform for Data Cloud create a predictable amount of records representing profiling results when profiling Salesforce objects and fields. We also provide customers with declarative automation to prune data quality insights that are outdated and no longer necessary (via Salesforce Flow).
Profiling Results Access Is Managed through Existing Salesforce Security Features
Profiling results are written to custom objects created when Cuneiform for Salesforce products are installed. Access to profiling objects can be managed through Salesforce Profiles and Permission-Sets. Access to specific profiling results can be controlled via Record-Level rights.
We include Administrator-level and Read Only User permission sets to manage access to our custom objects. These permission sets can be extended and customized to adhere to org-specific security needs.
Access Cuneiform for Salesforce’s custom objects and profiling results can be managed using existing Salesforce Security features. We include a set of starter permission sets that customers can extend based on their security and compliance needs.
PeerNova’s Commitment to Data Security
PeerNova, provider of Cuneiform for Salesforce products, has earned the International Organization for Standardization (ISO) 27001 certification and Service Organization Control (SOC) 2 Type II compliance.
To achieve the ISO 27001 certification, organizations must adhere to comprehensive security management standards that protect and manage sensitive company and customer information. Completing a SOC 2 Type II audit ensures that firms have a security-first mindset and culture of compliance across their organization. PeerNova has end-to-end real-time visibility, ensuring security and compliance across all its systems.
These certifications are emblematic of PeerNova’s and the Cuneiform for Salesforce product line’s total commitment to safeguarding customer data across its marketing, sales, and platform.
