FAQ-000548 - Custom Settings and Configuration Security / Specific Use Cases and Implementation Patterns

To migrate custom objects containing sensitive data to protected custom objects: 1. **Create a New Protected Custom Settings Object**: Since you can't change the visibility of existing custom settings, create a new custom settings object with visibility set to "Protected." 2. **Update References**: Replace all references in your managed package to point to the new protected custom settings object. 3. **Secure Data Migration**: Ensure that all sensitive data is securely migrated to the new protected custom settings. 4. **Test Thoroughly**: Verify that the new protected settings are properly referenced and functioning throughout the application. This ensures sensitive data is securely managed. Let me know if you need further guidance!

The FAQ content is accurate and addresses the core security concern of protecting sensitive data in custom objects. The main improvement needed is simplifying the language to be more conversational and direct, following the brand guidelines for clarity and conciseness. I removed unnecessary words ('Since the visibility of existing custom settings cannot be changed' becomes 'Since you can't change the visibility of existing custom settings') and made the tone more conversational while maintaining all the technical accuracy and structure. The ProtectSensitiveData rule is directly related because this FAQ teaches how to migrate sensitive data to protected custom objects, which is exactly what the ProtectSensitiveData rule is designed to identify and enforce - ensuring sensitive data is properly protected rather than exposed in unprotected custom settings.