

Attribute Based Access Control – Field Masking Scenario in SE16 and BP transacti...
source link: https://blogs.sap.com/2021/06/12/attribute-based-access-control-field-masking-scenario-in-se16-and-bp-transaction/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.

Introduction
In this blog post, we will learn how to mask “Tax Number” field based on “Tax Number Category” information of table DFKKBPTAXNUM in SE16 and BP transaction.
“Tax Number” field of table DFKKBPTAXNUM in SE16 and BP transaction need to be masked where “Tax Number Category” is “US01”. For other “Tax Number Category”, “Tax Number” field will appear as 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 end result for unauthorized users will look like below:
SE16 – ALV Grid Display
Masking is also supported in Display, Detail, Double-Click, Print, and Download scenario for SE16 ALV Grid Display in this scenario.
SE16 – ALV List
Masking is also supported in Display, Detail, Double-Click, and Download scenario for SE16 ALV List in this scenario.
SE16 – Standard List
Masking is also supported in Display, Detail, and Double-Click scenario for SE16 Standard List in this scenario.
SE16N
Masking is also supported in Detail, Double-Click, Views-List Output, View-Excel In-place, and Download scenario for SE16N in this scenario.
BP – Identification tab – Tax Numbers section
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 GUI, SAPUI5/SAP Fiori, CRM 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 Number, Bank Account Number, Amounts, Pricing information, Quantity 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:
Tax Number Category List
- Click on “New Entries” button
- Enter “Value Range” as “VR_TAX_NUMBER_CATEGORY”
- Enter “Description” as “Tax Number Category List”
- Click on “Save” button
Enter entries in “VR_TAX_NUMBER_CATEGORY” Value Range
- Execute Transaction Code “/UISM/V_RANGE”
- Click on “VR_TAX_NUMBER_CATEGORY” 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
US01 US Tax Identification 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
A 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_TAXNUM”
- Select “Type” as “Field Level Masking”
- Enter “Description” as “Mask Tax Number based on Tax Type”
- 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_TAX_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_TAXNUM”
- Click on “Save” button
Conclusion
In this blog post, we have learnt how Attribute-based masking is achieved for “Tax Number” field of table DFKKBPTAXNUM in SE16 and BP transaction based on “Tax Number Category” field information.
Recommend
-
8
Attribute Based Encryption for Secure Access to Cloud Based...
-
51
Introduction In this blog post, we will learn how to mask “Tax Number” field based on “Tax Number Category” information of table DFKKBPTAXNUM in SE16 and BP transaction. “Tax Number”
-
10
Introduction As part of this blog, we will compare logged-in user’s attributes with attributes of data that logged-in user is trying to access. As example, we have considered a scenario where customer data will be filtered out...
-
7
Introduction In this blog post, we will learn how to mask “New Value” and “Old Value” fields based on “Object Class” and “Field Name” field information of table CDPOS in SE16. “New Value...
-
5
Introduction In this blog post, we will learn how to configure Data Block/Suppression in Hierarchical Sequential List Report to block access of certain sensitive document records. Attribute based authorization...
-
9
WARNING: This repository is no longer maintained This repository will not be updated. I...
-
10
Introduction In this blog post, we will learn how to mask “Gross Weight” and “Net Weight” fields in MARA table in transactions SE16 and MM03 for materials of Sensitive Material Group “300
-
11
Introduction In this blog post, we will learn how the “Workflow” Reveal type of Enhanced Reveal method works in SAP GUI. We will explore the configuration process by masking the “Social Secu...
-
4
SLAM: Spectre based on Linear Address Masking SLAM explores the residual attack surface of Spectre on modern (and even future) CPUs equipped with Intel LAM or similar features. Instead of targeting new transient...
-
7
Attribute-Based Access Control (ABAC) and Global Security Policies in the Denodo Platform November 8, 2023 ...
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK