Securing the object and field data is really important for any customer so that the users can only see the data which they intended to see. There would be a data leak and data security issue if we do not provide the proper Object & Field Level Access.
When we talk about data security in Salesforce that means we need to make sure that we are taking care of the object(s) and field(s) level security because these are the first level of security and after that, the record level of security comes into the picture.
For Example, if you make the OWD of any object private and do not provide any field-level security then in that case if the user has access to any record then he/she will be able to access all the fields even if they do not need to see the fields.
There are multiple ways from which you can control field-level access inside Salesforce.
The profile is the first level of Security for objects and fields. And we can control the field security from the profile where we can set if the field is visible/readable or editable by the users who are assigned to a particular profile.
For Example, You have a requirement to provide read-only access to the Industry field of Account at the profile level so that any user having a “Custom Support Profile” can only read the Industry field but can not modify it.

When to provide field-level access at the profile levelAs a best practice, we should not provide any field-level access at the profile level and always extend the permission from the Permission Set level.
However, if all the users under any profiles require at least read access then provide the read access at the profile level and if there are some exceptional users who needed edit access then provide edit access at the permission set level and assign it to the users who are required to edit the fields.
As we talked about that providing field-level security at the permission set level is very important because we can control which all users can read/edit/view any field related to Salesforce.
If you do not have a permission set in the Salesforce org then the first step is to create the permission set. To Create the Permission Set follow the below steps
once you have created the permission set and provided the required access to the object(s) and field(s). Now, we have to assign the permission set to the required users.
There are many scenarios where we can access the field Level Access from the Page Layout as well. However, we can only make the field read-only and required from the Page Layout but we can not hide the field.
With the help of page layout in Salesforce, we can make a field read-only, or required which again comes as handy when we wanted to make a field read only for specific record type or wanted to make sure user fills out a field when creating a new recod from UI.
With the help of dynamic forms, we can show/hide the fields dynamically, or event we can make the field read-only or required.
To learn more about dynamic forms please go through the following links
Your feedback is really appreciated.
Happy learning!