DATA SECURITY IN SALESFORCE
Salesforce is built with security to protect your data and applications. You can also implement your own security scheme to reflect the structure and needs of your organization. However, protecting your data is a joint responsibility between you and Salesforce. The Salesforce security features enable you to empower your users to do their jobs safely and efficiently.
▪ Salesforce Data security deals with the security and sharing settings of data
as well as visibility between users and groups of users across the
organization. Force.com platform provides a flexible sharing model
enabling us to assign different levels of access and visibility to different
sets of user.
▪ Data security in Salesforce is concerned, they ensure you provide a service
where only registered members of the organization are allowed to access
the stored data. This is why they provide a service, which eventually helps
keep data safe from corruption, unauthorized access and theft amid its
complete lifecycle.
After logging in, a user establishes a session with the platform. Use session security to limit exposure to your network when a user leaves the computer unattended while still logged in. Session security also limits the risk of internal attacks such as when one employee tries to use another employee’s session.
Access to object-level data is the only thing to control. By putting
permissions on a specific type of object, you could prevent a set of users
from creating, viewing, editing, or deleting any records of that object.
You also can use profiles to control the objects that user can access and the
permissions they’ve for every object. You also can use permission sets and
permission set groups to increase access and permissions without editing
users’ profiles.
For example, you could use object permissions to make sure that
interviewers can view positions and job applications but not edit or delete
them.
It determines the objects a user can access and the permissions a user has
on any object record. Profile is a collection of settings and permissions that
determine which data and features in the platform users have access to.
Settings determine what users can see for example apps, tabs, fields, and
record types whereas Permission determine what users can do for example
create or edit records of a certain type, run reports and customize the app.
Each of the standard profiles includes a default set of permissions for all of the
standard objects available on the platform.
OWD tells us to record security for each object. It is the baseline in terms of record-level security. One must always set the OWD as restrictive and open up the access by other solutions available for the record level security. OWD section comes under sharing settings in the security section in setup.
Role-HierarchyRole hierarchy in Salesforce means the user who will be on the top has the access to all of the users below. It follows a top to down approach. The user won’t have access of the above users but the users which are below his level as per the role hierarchy defined. Role hierarchy automatically grants access to the users
As mentioned above, role hierarchy follows the top to down approach whereas, Sharing rules provide the record-level access to those who are at the same level in the Role hierarchy. Sharing rules are used to provide horizontal access. Sharing rules can be applied on standard and custom objects. We can assign or create sharing rules/sharing settings by navigating to the OWD section and below there is a section where we can create a sharing rule for every object present in the org.
In this, we can share records manually to the individual users, roles, or public groups. It is available to the record owners, their managers, and system admin. If a user does not have access to any record which is owned by some other user then the owner of the record can manually share the record with the user.