Field security entities

 

Applies To: Dynamics CRM 2013

You use field security entities to apply field-level security, which restricts field access to specified users and teams. The scope of field-level security is global, which means that it applies to all records within the organization, regardless of the business unit hierarchical level to which the record or the user belongs. Field security works in all Microsoft Dynamics CRM clients, including the Web client, CRM for Outlook, and CRM for phones. It applies to all components, such as the Microsoft Dynamics CRM SDK, reports, search, offline, filtered views, auditing, and duplicate detection. For this version of Microsoft Dynamics CRM, field-level security is restricted to custom fields.

For more information about how secured fields change the behavior of methods, see How field security can be used to control access to field values in Microsoft Dynamics CRM 2013.

System_CAPS_security Security Note

Field level security profiles prevent unintended users from getting access to Microsoft Dynamics CRM data based on the profile definitions. If the Microsoft SQL Server ACLs are misconfigured, or if there is a SQL injection issue, adversaries can get direct access to data in Microsoft SQL Server thereby bypassing field level security restrictions. For more information, see Overview of Web Application Security Threats.

To use field security you must do the following:

  1. Create a field security profile record

  2. Add users or teams to the profile

  3. Create a custom attribute in either a default, out-of-the-box entity, or in a custom entity

  4. Secure the custom attribute, either when you create the attribute or by updating the attribute metadata

  5. Publish the attribute customizations

  6. Create a field permission record that defines what access (create, update, read) the profile will have for the custom attribute

For sample code about how to perform these steps, see Sample: Enable field security for an entity.

Use the following field permission attributes to set whether the specified field security profile can create, read, or update an attribute. You can set or compare the value for these attributes by using the A Yes or No Boolean (field_security_permission_type) global option set:

  • FieldPermission.CanCreate

  • FieldPermission.CanRead

  • FieldPermission.CanUpdate

System_CAPS_security Security Note

If low privilege users are given Read access to the field security profile entity, they can see what profiles other users have and find other users with access to secured attributes they are interested in. They can then use social engineering techniques to get assigned a profile with access to those secured attributes.

You can share secured fields much as you can share records. To do this, you create, update, or delete a PrincipalObjectAttributeAccess (field sharing) record, where you specify the user or team, the entity, and the permissions.

The following table lists the corresponding methods for securing a field compared to securing a record.

Record sharing

Field access sharing

Use GrantAccessRequest to grant record access for a user or team.

Use theCreateRequest message or the IOrganizationService.Create method to grant secured field access for a user or team.

Use ModifyAccessRequest to update record access for a user or team.

Use the UpdateRequest message or the IOrganizationService.Update method to update secured field access for a user or team.

Use RevokeAccessRequest to remove record access for a user or team.

Use the DeleteRequest message or the IOrganizationService.Delete method to remove secured field access for a user or team.

Show: