It is very important to protect a customer's confidential information. This includes credit card numbers, social security numbers, bank account numbers, drivers license numbers and dates of birth.
Although it may be necessary to use some of this sensitive information to identify a specific customer, not all users need the same viewing or editing rights. This information can be protected by masking and by setting up user security permission profiles.
Masking
Masking means that a field of numbers is displayed with asterisks instead of the actual digits.
Complete masking of information means that the entire number is displayed as a series of *'s.
Partial masking means that only the last four digits display; the beginning digits are displayed with *'s.
Examples of Masked Confidential Information | |
Masked Date of Birth | **/**/**** |
Masked SS No. | *****1234 |
Masked Credit Card No. | ************2345 |
Security Permission Profiles
Confidential customer information is also protected by establishing security permission profiles for different types of users.
Here are examples of the different user permission settings for viewing/editing confidential information -- in this case, the Bank Account Number.
Notes:
Permissions for viewing and editing Credit Scoring are set up in Admin Console.
The following scenarios explain the different combinations of masking and editing permissions and are not necessarily commonly used settings.
Full Permission (Editing, no Masking)
With Full Permission, the Edit flag is green, indicating that edit permission is granted. The Mask flag is red, indicating the information is NOT masked; it is totally visible.
With permissions set like this, a user is able to view and edit the Bank Account Number. This user will see the Edit Bank Account Number dialog displayed as follows.
The Old Value is completely visible, and the New Value field displays the bank account number, which can be edited.
Edit Permission with Masking
With permissions set like this, both icons are green, the user is able to edit sensitive information, but masking is on, so data is masked.
The Old Value is masked, and the New Value field is blank and may be edited. Once the New Value is saved, it then becomes masked.
No Editing Permission, No Masking
With permissions set like this (both Edit and Mask icons are red), the user cannot edit, but can see the Bank Account Number unmasked.
The Edit button on the Account Number field window is grayed out, so the Edit function cannot be performed. Masking is off, so the entire Account Number is visible.
No Editing Permission, with Masking
With permissions set like this (Edit is red and Mask is green), the user cannot edit, and the data is masked.
The Bank Account Number is masked and the Edit button is grayed out.
These security permissions work similarly for other confidential information fields.
Search Return Screen - Confidential Information
Unlike data entry dialogs, all confidential information displayed in a search return grid is masked, regardless of the user's permissions. Here's an example.
The Account Numbers are masked on this search results screen, no matter what the user permissions are.
Note
This masking is done to safeguard your data. It serves to prevent anyone -- regardless of their permissions -- from being able to query the database for a large batch of data and export it.