

Attribute Based Access Control (ABAC) – Data Block (Suppression) Scenario in Hie...
source link: https://blogs.sap.com/2022/09/30/attribute-based-access-control-abac-data-block-suppression-scenario-in-hierarchical-sequential-list-report/
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 configure Data Block/Suppression in Hierarchical Sequential List Report to block access of certain sensitive document records.
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).
Before Data Block/Suppression Configuration:
Document records highlighted in the below image need to be suppressed in S_ALR_87012347 Report.

After Data Block/Suppression Configuration:
After suppression configuration, highlighted Document records in above image has been suppressed and unauthorized users cannot access those records anymore.

Prerequisite
UI Data Protection Masking for SAP S/4HANA is a solution that allows you to protect restricted and sensitive data values at field level by masking, clearing, or disabling fields for those users who are not authorized to view or edit this data.
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 Data Block/Suppression
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 -> Sensitive Attribute Configuration -> Maintain Metadata Configuration -> Maintain Logical Attributes
Hierarchical Sequential List

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 -> Sensitive Attribute Configuration -> Maintain Metadata Configuration -> Maintain Attributes and Ranges for Policy -> List of Values Definition – Follow below mentioned steps:
Sensitive Document List
- Click on “New Entries” button
- Enter “List of Values” as “VR_SENSITIVE_DOCS”
- Enter “Description” as “List of Sensitive Documents”
- Click on “Save” button

Enter following entries in “VR_SENSITIVE_DOCS” Value Range
IMAGE
Follow below mentioned steps:
- Execute Transaction Code “/UISM/V_RANGE”
- Click on “VR_SENSITIVE_DOCS” 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



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 -> Sensitive Attribute Configuration -> Maintain Metadata Configuration -> Maintain Technical Address
Follow below mentioned steps:
Under “SAP GUI (Table Field) Field Mapping”, maintain technical address for following fields.

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 -> Sensitive Attribute Configuration -> Masking and Blocking Configuration -> Maintain Policy Details for Attribute based Authorizations – Follow below mentioned steps:
- Click on “New Entries” button
- Enter “Policy Name” as “POL_BLOCK_HIRSEQLIST”
- Select “Type” as “Data Blocking”
- Enter “Description” as “Data Blocking in Hierarchical Sequential List”
- Click on “Save” button
IMAGE
Write following logic into Policy

Maintain Data Blocking 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 -> Sensitive Attribute Configuration -> Masking and Blocking Configuration -> Maintain Data Blocking Configuration
Follow below mentioned steps:
- Click on “New Entries” button
- Enter “Sensitive Entity” as “LA_HIRSEQLIST” 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_BLOCK_HIRSEQLIST”
- Click on “Save” button

Conclusion
In this blog post, we have learnt how Data Block/Suppression is achieved in Hierarchical Sequential List Report to block access of certain sensitive document records.
Recommend
-
8
Attribute Based Encryption for Secure Access to Cloud Based...
-
5
Block access to Control Center when iPhone and iPad are locked [Pro tip]Keep Control Center protected by your passcode.Image: Killian Bell/Cult of MacWe want to help you master Control Center, one of the most power...
-
53
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...
-
12
This is a detailed blog post as part of a related series of blog posts of SAP Business ByDesign capabilities addressing the topic of active budget control. See main blog post
-
17
Stefan Mueller May 13, 2022 4 minute read
-
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
-
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