Customers do not directly configure the Master Wrapping Key. The steps below cover the related customer-side concerns.
- Understand the role
Read Salesforce Shield documentation on key wrapping. The Master Wrapping Key is the layer protecting tenant secrets at rest.
- For BYOK upload, follow Salesforce protocol
Salesforce documents the BYOK upload format. Wrap the customer secret with the Salesforce wrapping key as specified.
- For Cache-Only, configure KMS
The customer KMS sends wrapped key material to Salesforce. Configure per Salesforce documentation.
- Document the wrapping protection
For compliance audits, reference the Master Wrapping Key role in Salesforce attestations. Customer-side documentation describes the chain.
- Monitor for wrapping-related errors
Key operations occasionally surface errors related to wrapping (corruption, version mismatch). Capture in support tickets if seen.
- Test BYOK rotation if applicable
BYOK rotation re-wraps under new Master Wrapping Key versions. Test in sandbox before production rotation.
- Reference in compliance reviews
Cite the Master Wrapping Key as evidence of multi-layer key protection in customer compliance documentation.
Standard algorithm used for wrapping. Customers do not configure; platform-managed.
Master Wrapping Key in Salesforce Master HSM.
For BYOK, customer HSM holds wrapping key for upload protocol.
Salesforce-managed for platform; customer-managed for BYOK.
Salesforce-provided evidence of wrapping protection.
- The Master Wrapping Key is not customer-configurable. Customers cannot inspect or replace it directly.
- BYOK upload protocol requires correct wrapping format. Mistakes here cause upload failures; follow Salesforce documentation carefully.
- Wrapping-related errors usually indicate a corruption or version mismatch. Open a support ticket rather than attempting local debugging.
- Cache-Only Key Service relies on the wrapping protocol for in-transit key protection. KMS connectivity issues can surface as wrapping errors.
- The wrapping key is part of the chain of trust. Compromise (rare in practice) would affect all customer secrets wrapped under it; Salesforce operates the HSM under strict controls.