A BYO key setup on Salesforce lets you supply your own encryption material for Data 360 (formerly Data Cloud) so the keys that protect AI data stay under your direct control rather than Salesforce-managed defaults. This approach supports strict data sovereignty needs when AI features such as vector search and generative models process sensitive records.
The term “BYO key AI portal” does not appear as an official product name, yet the underlying capability is Bring Your Own Key (BYOK) extended to Data 360 root keys. It encrypts the data stores that feed Einstein and Agentforce while preserving the protections of the Trust Layer.
What does BYOK actually control in a Data 360 environment?
BYOK gives you authority over key generation, rotation, and revocation for the root keys that wrap data encryption keys across Data 360 stores. These stores include fields, files, search indexes, and vector embeddings used by AI workloads. Salesforce never receives the plaintext key; you wrap it externally with a 4096-bit RSA certificate before upload.
The feature became available in the Winter ’26 release through a UI path in Setup under Key Management. You can now upload, rotate, and archive root keys for Data 360 without leaving the platform, and prior keys move to an archived state automatically. Limits allow up to 50 active or archived tenant secrets per type.
This matters for AI because vector-based search and generative features rely on the same encrypted data layer. When a key is rotated, new data uses the updated key while existing records remain accessible through the archived key metadata.
How does the key preparation and upload process work?
You begin by creating a BYOK-compatible certificate inside Salesforce Setup. The certificate can be self-signed or signed by your own certificate authority. Next you generate the key material in your own environment—using an HSM, enterprise KMS, or approved crypto library—and wrap it according to the published specification: 256-bit key size, OAEP padding, PKCS#8 format, and Base64 encoding.
Salesforce provides the public key from the certificate so the wrapping step happens entirely outside the platform. Once wrapped, you upload the material through the Key Inventory screen, selecting the Data 360 Root Key type and supplying the required import or session token. The platform records metadata such as creation time and uploader but never exposes the key itself.
After upload, Data 360 applies the new root key to subsequent operations. Existing data continues to decrypt with previously active keys, so the transition does not interrupt running AI processes.
Which Data 360 AI capabilities rely on this encryption layer?
Vector search, segmentation, personalization, and generative AI prompts all draw from Data 360 stores protected by these keys. When you enable Platform Encryption for Data Cloud (the add-on required for BYOK on Data 360), the same root key secures the embeddings and calculated insights that Agentforce agents reference during reasoning.
The setup also aligns with Bring Your Own Model patterns. External LLMs connected through the Trust Layer can still access Data 360 records because the encryption remains under your key control rather than a shared Salesforce key. This separation supports residency and audit requirements that treat the encryption root as customer-managed infrastructure.
When is BYOK the wrong choice for a Data 360 rollout?
If your organization does not operate under regulatory mandates that require direct control over key lifecycle and revocation, the standard Customer Managed Keys option already available in the UI provides adequate protection without the external wrapping steps or certificate management.
What are the licensing and permission requirements?
You need an Enterprise, Performance, or Unlimited Edition plus either Salesforce Shield or the Shield Platform Encryption add-on. Data 360 support specifically requires the Platform Encryption for Data Cloud add-on. The permission set “Manage Encryption Keys” plus “Customize Application” for certificate handling are necessary. Developer Edition instances include limited testing capacity.
Migrations between Customer Managed Keys, External Key Management, and BYOK are supported, though re-encryption behavior differs depending on the direction of the move. Always validate the target state in a sandbox before changing production root keys.
How do you get started with BYOK for Data 360?
First confirm the required editions and add-ons are active. In Setup, locate Encryption Settings or Key Management. Generate the 4096-bit RSA certificate, then prepare the wrapped key material following the exact encoding rules published in the help documentation. Upload the wrapped key through the Key Inventory interface, selecting the Data 360 Root Key option. Enable the Manage Data 360 Keys permission for the users who will monitor statistics and perform rotations.
Test the full flow in a sandbox that mirrors your production Data 360 configuration, including any vector indexes or Agentforce topics that query the encrypted stores. Monitor the Encryption Statistics page after upload to verify new records are protected under the supplied key.
What operational considerations remain after the initial upload?
Key rotation follows the same upload path and automatically archives the prior key. You can revoke access on demand if a key is suspected of compromise. Backups of the original key material must be stored securely outside Salesforce, because the platform cannot recover a lost wrapped key.
The feature works alongside existing Shield Platform Encryption settings for fields, files, and Event Bus. No changes to Agentforce agent definitions or Einstein prompt templates are required; the encryption layer sits beneath those surfaces.
Frequently asked questions
How does BYOK differ from Customer Managed Keys in Data 360?
Customer Managed Keys are generated inside Salesforce and remain under platform control for lifecycle events. BYOK requires you to generate and wrap the key externally, then upload only the wrapped material, giving you direct authority over creation, rotation, and revocation.
Can I use BYOK with external models connected to Data 360?
Yes. External LLMs linked through the Trust Layer continue to access records because the root key protecting the underlying data stays under your control. The connection itself uses the same Trust Layer safeguards that apply to native Einstein features.
What happens to existing data when I upload a new root key?
Existing records remain accessible through the archived key. New records and new vector embeddings created after the upload use the newly supplied root key. No bulk re-encryption occurs at the moment of upload.
Which compliance scenarios most commonly drive BYOK adoption?
Organizations handling regulated personal data, financial records, or health information often adopt BYOK to satisfy requirements that mandate customer-controlled key generation and the ability to revoke keys without Salesforce involvement.
Does BYOK affect Agentforce agent performance or response times?
The encryption and decryption operations occur at the storage layer and are transparent to agent execution. No measurable change in agent reasoning speed or topic response times has been documented as a result of switching to customer-supplied root keys.
Book an intro call.
Integrations & Data Cloud
Connect your systems. Unify your data. Power smarter AI.
Read Next

People Paste Customer Data Into Personal AI Accounts
Salesforce built strong controls for its own AI tools, yet employees still paste customer records into consumer ChatGPT accounts. Here is exactly what the platform does, where it stops, and what must come next.

What controls do you need to keep Salesforce AI data sovereign?
Learn the essential controls for Salesforce AI data sovereignty, including BYO Key for models, Trust Layer, regional deployment, Shield encryption, and Data 360 governance.

Agentforce ROI: What Actually Moves the Needle
Agentforce has moved past pilots. Here's a simple way to prove ROI: pick one process, capture a baseline, and track leading and lagging metrics.

