Skip to Content
Product Information

Attribute Based Access Control – Field Masking Scenario in specific Sub-type of Personal IDs (0185) Info-type in SE16/PA20/PA30 transactions

Introduction

In this blog post, we will learn how to mask “ID Number field in Birth Certificate (BC), Driver’s License (DL), and Social Insurance Number (SN) sub-types of Personal IDs (0185) Info-type of transaction SE16/PA20/PA30. For other Sub-types, ID Number field will remain unmasked.

Attribute based authorizations are dynamic determination mechanism which determines whether a user is authorized to access specific data sets which can be based on the context attributes of the user and data (for example, price of certain sensitive materials are masked).

The result for Birth Certificate (BC), Driver’s License (DL) and Social Insurance Number (SN) sub-types will look like below:

The result for Company Security ID (CS), Passport (PP), and Work Visa (VI) sub-types will look like below:

Prerequisite

Product “UI data protection masking for SAP S/4HANA” is used in this scenario to protect sensitive data at field level and must be installed in the S/4HANA system.

The product is a cross-application product which can be used to mask/protect any field in SAP GUISAPUI5/SAP FioriCRM Web Client UI, and Web Dynpro ABAP.

Let’s begin

Configuration to achieve masking

Logical Attribute is a functional modelling of how any attribute such as Social Security NumberBank Account NumberAmountsPricing informationQuantity etc. should behave with masking.

Configure Logical Attribute

Follow the given path:

SPRO -> SAP NetWeaver -> UI Data Protection Masking for SAP S/4HANA -> Maintain Metadata Configuration -> Maintain Logical Attributes

Configure Value Range

Value Ranges are a set of pre-populated values which can be used to derive the context under which an action should be executed.

Follow the given path:

SPRO -> SAP NetWeaver -> UI Data Protection Masking for SAP S/4HANA -> Maintain Metadata Configuration -> Maintain Attributes and Ranges for Policy – Follow below mentioned steps:

Personal ID Subtypes
  • Click on “New Entries” button
  • Enter “Value Range” as “VR_SUBTYPE
  • Select “Application Module” as “P Human resources
  • Enter “Description” as “Personal ID Subtypes
  • Click on “Save” button

Enter entries in “VR_SUBTYPE” Value Range
  • Execute Transaction Code “/UISM/V_RANGE
  • Click on “VR_SUBTYPE” Value Range
  • Click on “Display<- -> Change” button
  • Click on “Add New Entry” button
  • Add following entries under “Include Value” tab and click on “Save” button

Value                   Description

BC                        Birth Certificate

DL                         Driver’s License

SN                        Social Insurance Number

Maintain Technical Address

In this step, we will associate the Technical Address of the fields to be masked with the Logical Attributes.

You can get the Technical Address of a GUI field by pressing “F1” on the field.

Follow the given path:

SPRO -> SAP NetWeaver -> UI Data Protection Masking for SAP S/4HANA -> Maintain Metadata Configuration -> Maintain Technical Address

Follow below mentioned steps:

Under “GUI Table Field Mapping”, maintain technical address for following fields.

Mass Configuration

For all the above entries, “Mass Configuration” report should be executed which is required to generate technical addresses.

Follow below mentioned steps:
  • Select the entry in GUI Table Field Mapping
  • Click on “Mass Configuration” button
  • Click on “Select All” button
  • Click on “Generate Customizing” button
  • Save the information

Policy Configuration

Policy is a combination of rules and actions which are defined in one or more blocks. The actions are executed on a sensitive entity (field to be protected) which has to be assigned to a Policy. The conditions are based on contextual attributes which help derive the context.

Context Attributes are logical attributes which are used in designing the rules of a policy. They are mapped to fields which are used to derive the context under which an action is to be executed on a sensitive entity.

Sensitive Entities are logical attributes which are sensitive and need to be protected from unauthorized access.

Follow the given path:

SPRO -> SAP NetWeaver -> UI Data Protection Masking for SAP S/4HANA -> Data Protection Configuration -> Maintain Policy Details for Attribute based Authorizations – Follow below mentioned steps:

  • Click on “New Entries” button
  • Enter “Policy Name” as “POL_MASK_IDNUM
  • Select “Type” as “Field Level Masking
  • Select “Application Module” as “P Human resources
  • Enter “Description” as “Mask ID Number based on Subtype information
  • Click on “Save” button

Write following logic into Policy

Maintain Field Level Security and Masking Configuration

Here, we will define how masking will behave with the logical attribute that we created in above step.

Follow the given path:

SPRO -> SAP NetWeaver -> UI Data Protection Masking for SAP S/4HANA -> Data Protection Configuration -> Maintain Field Level Security and Masking Configuration

Follow below mentioned steps:
  • Click on “New Entries” button
  • Enter “Sensitive Entity” as “LA_IDNUMBER” and press “Enter” key. “Description” and “Application Module” will get populated in corresponding fields
  • Check “Enable Configuration” check-box
  • Select “Attribute Based Authorization” option
  • Enter “Policy Name” as “POL_MASK_IDNUM
  • Click on “Save” button

Conclusion

In this blog post, we have learnt how Attribute-based masking is achieved for “ID Number” field of Birth Certificate (BC), Driver’s License (DL), and Social Insurance Number (SN) sub-types of Personal IDs (0185) Info-type of transaction SE16/PA20/PA30.

Be the first to leave a comment
You must be Logged on to comment or reply to a post.