Skip to Content
Product Information
Author's profile photo Amit Kumar Singh

Attribute Based Access Control (ABAC) – Field Masking Scenario in DEBIX Search Help screen

Introduction

In this blog post, we will learn how to mask “Street”, “House No.”, “Postal Code”, and “City” fields in DEBIX Search Help screen based on “Country” information.

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 end result will appear as:

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:

Range of Countries
  • Click on “New Entries” button
  • Enter “Value Range” as “VR_COUNTRY
  • Select “Application Module” as “* Cross-Application
  • Enter “Description” as “Range of Countries
  • Click on “Save” button

Enter entries in “VR_COUNTRY” Value Range
  • Execute Transaction Code “/UISM/V_RANGE
  • Click on “VR_COUNTRY” Value Range
  • Click on “Display<- -> Change” button
  • Click on “Add New Entry” button
  • Add Value as “US” and Description as “USA” under “Include Value” tab
  • Click on “Save” button

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 “Data Element Field Mapping”, maintain technical address for following fields.

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_DEBIX
  • Select “Type” as “Field Level Masking
  • Select “Application Module” as “Y Customer Head Office
  • Enter “Description” as “Masking in DEBIX Search Help
  • 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_CITY_INFO” 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_DEBIX
  • Click on “Save” button

  • Click on “New Entries” button
  • Enter “Sensitive Entity” as “LA_HOUSE_NUMBER” 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_DEBIX
  • Click on “Save” button

  • Click on “New Entries” button
  • Enter “Sensitive Entity” as “LA_POSTAL_CODE” 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_DEBIX
  • Click on “Save” button

  • Click on “New Entries” button
  • Enter “Sensitive Entity” as “LA_STREET” 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_DEBIX
  • Click on “Save” button

Conclusion

In this blog post, we have learnt how Attribute-based masking is achieved in DEBIX Search Help for masking “Street”, “House No.”, “Postal Code”, and “City” fields based on “Country” information.

Note:

For information on masking in Search Help screen in UIM, please refer blog post Field Masking – Context based masking scenario in DEBIS Search Help screen.

Assigned Tags

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