skip to main content
Close Icon We use cookies to improve your website experience.  To learn about our use of cookies and how you can manage your cookie settings, please see our Cookie Policy.  By continuing to use the website, you consent to our use of cookies.
Global Search Configuration

Introduction

Force.com, Salesforce’s platform-as-a-service (PaaS) offering, is evolving into an application, data, and people integration hub. The foundation of its hub ambitions is its multilayered flexible approach to user, application, and data security, with a particularly granular approach to data security.

Highlights

  • In a public cloud context you cannot rely only on cloud service provider assurances. Encrypt and back up your data on premise using a mix of Force.com and third-party technology.

Features and Benefits

  • Gain a short, concise, but nonetheless detailed overview of Force.com's security capabilities.
  • Receive recommendations on how to make the best of Force.com's security features.

Key questions answered

  • Which security features does Force.com make available to users? How do these relate to one another?
  • What are the strengths and limitations of Force.com's security features?

Table of contents

Summary

  • Catalyst
  • Ovum view
  • Key messages

Recommendations

  • Recommendations for enterprises
  • Recommendations for vendors

Combine multiple security layers to secure Force.com implementations

  • Like Salesforce, combine security layers
  • Force.com is reliable but do backup regularly
  • Ask about Salesforce’s data center security
  • Keep in mind data location issues and work around them
  • Combine Force.com and third-party technology

Mix multiple access management techniques

  • Use Force.com’s password and login policy management capabilities
  • Leverage Force.com’s SSO capabilities

Carefully manage Force.com’s data access mechanisms

  • A flexible layered design that combines top-down and bottom-up security
  • A design that can quickly become complex, so needs careful planning and management
  • Leverage Force.com’s monitoring facilities

Start with profiles and permission sets for data access

  • Use profiles to grant access then tweak with permission sets
  • Manage carefully and consider all possible consequences

Add bottom-up object, field, and record-level data access settings

  • Start with object and field permissions then adjust
  • Combine field-level and page layouts security
  • Define record-type security via profiles and permission sets
  • Define record-level security via organization-wide sharing settings
  • Refine record-level security via hierarchies
  • Refine record-level security via automatic and manual sharing rules
  • Carefully combine permission sets and sharing rules
  • Apply sharing rules to groups, besides role hierarchies
  • If nothing works you can always define sharing programmatically
  • Keep the processing impact of sharing rules in mind

Appendix

  • Further reading
  • Author

Recommended Articles

;

Have any questions? Speak to a Specialist

Europe, Middle East & Africa team - +44 (0) 207 017 7700


Asia-Pacific team - +61 (0)3 960 16700

US team - +1 646 957 8878

Email us at ClientServices@ovum.com

You can also contact your named/allocated Client Services Executive using their direct dial.
PR enquiries - Call us at +44 788 597 5160 or email us at pr@ovum.com

Contact marketing - 
marketingdepartment@ovum.com

Already an Ovum client? Login to the Knowledge Center now