--- schema_version: "1" id: 309e539f6326c1f3158a1cebb870a969c70fc9c09015b9bee6907f35326ef96d title: Security collection: developer version: current locale: en-us portal_url: https://docs.salesforce.com/developer/current/en-us/marketing-cloud/mc-core/guide/mc-security.md canonical_url: https://developer.salesforce.com/docs/marketing/marketing-cloud-growth/guide/mc-security.html source_site: developer.salesforce.com content_type: documentation content_hash: ca4223af3317d215943ffb59713e72187acf6060cbe5736f9fe804c0caf02e57 products: - Marketing Cloud Next - Marketing Cloud --- # Security Data privacy and trusted access are important considerations in the development of a secure marketing platform. To help improve the security of your marketing data, follow these guidelines. ## Create Separate Users Don’t share passwords or login information between multiple users, apps, or systems. If you work with integration partners, give each partner user a separate account. This step helps protect your customer data if a user’s credentials are compromised. It also makes it much easier to limit access and track actions that occur in your org. ## Follow the Principle of Least Privilege When you create user accounts or external client apps, follow the Principle of Least Privilege. The Principle of Least Privilege states that each user or other entity has the minimum level of permissions that are necessary to get the job done. Following this rule provides a layer of protection for your data against faults, unintentional actions, and unauthorized access. ## Monitor the Security of Your Org The Salesforce Platform provides several tools for monitoring the security of your org and data. - Track Login History - : To view login data for the past 6 months, use the [Login History page](https://developer.salesforce.com/docs/atlas.en-us.securityImplGuide.meta/securityImplGuide/users_login_history.htm) in the Salesforce web app. The Login History page shows the HTTP login methods used, connected app and external client app logins, and other login-related data. - Track Changes to Object Fields - : You can [track changes to fields in custom and standard objects](https://developer.salesforce.com/docs/atlas.en-us.securityImplGuide.meta/securityImplGuide/tracking_field_history.htm). Data is retained for at least 18 months, and it’s retained indefinitely when you turn on Field Audit Trail. - Track Setup Changes - : In orgs that have multiple admins, it can be helpful to see which user made a particular configuration change. To monitor configuration changes over the past 180 days, activate [Setup Audit Trail](https://developer.salesforce.com/docs/atlas.en-us.securityImplGuide.meta/securityImplGuide/admin_monitorsetup.htm) in your org. ## Use Sandboxes to Test and Experiment Protect your customer data and the availability of your org by testing in a sandbox. A sandbox org contains the same features and customer data as your production org. You can use a sandbox org for development, testing, and training, without worrying about compromising the data and apps in your production org. For more information, see [Sandboxes: Staging Environments for Customizing and Testing](https://help.salesforce.com/s/articleView?id=platform.deploy_sandboxes_parent.htm).