Security in Vault CRM
The Vault platform includes an extensive set of security controls. These controls are documented in the Vault Platform Online Help.
Every customer will implement security in a slightly different way. This topic explains the most common ways to use Vault security controls to configure the Vault CRM application.
Device and Data Security
An MDM system must be able to get information from the device (iPad) and safeguard sensitive data in the event it is lost or stolen. Consumers can activate the Find My iPad feature for free through MobileMe©. This service allows a user to locate their iPad on a map, enable a passcode lock, or erase all data from the device remotely using any web browser. Many MDM solutions offer similar capabilities to centrally clear passcodes, or remotely wipe or lock devices.
Object Permission
Object Permissions control which profile for a user (Specialty Sales or MSL for example) can create, read, edit or delete (CRED) objects of a certain type. For example, a profile of a user that does not have the Delete permission on Accounts cannot delete any accounts.
In many ways, Object Permissions are the most simple security control. It operates on the entire object and all fields and rows of data in that object.
Field Permission
Field Permissions control which fields users can edit on objects. Use this to completely hide a field for a group of users or make the field read only for a group of users.
Field Permission is the next most simple security control. It operates on an entire field of an object. For example, to configure accounts so that only administrators can update the primary specialty on Account or to prevent primary reps from viewing fields used by MSLs, you would use Field Permissions.
Security Profiles and Permission Sets
Security profiles are the primary way that Vault applies permission sets to individual users. Permission sets grant users the ability to view or edit certain Admin areas, or to access certain end user features.
See Managing Security Profiles & Permission Sets for more information.
Third-Party Keyboards
Vault CRM does not prevent the use of third-party keyboards. Third-party keyboards have the potential to capture, leak, and misuse the keystroke data they process. Customers should rely on their own mobile device management to manage this.
FTP Connections
Vault CRM requires TLS 1.2 for all FTP connections.
Users who manually upload files using an FTP client should follow the instructions provided by the FTP client to configure it to use explicit TLS.
For example, customers using Filezilla as their client should select Required explicit FTP over TLS from the Encryption dropdown list.
The ftpes:// prefix can also be added to the host location. For example, ftpes://vf13.vod309.com.
Ensure TLS 1.2 encryption protocols are enabled in any integrations using FTP.
