53

Attribute Based Access Control – Field Masking Scenario in SE16 and BP transacti...

 3 years ago
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.
neoserver,ios ssh client

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

958.png

Masking is also supported in DisplayDetailDouble-ClickPrint, and Download scenario for SE16 ALV Grid Display in this scenario.

SE16 – ALV List

959.png

Masking is also supported in DisplayDetailDouble-Click, and Download scenario for SE16 ALV List in this scenario.

SE16 – Standard List

960.png

Masking is also supported in DisplayDetail, and Double-Click scenario for SE16 Standard List in this scenario.

SE16N

961.png

Masking is also supported in DetailDouble-Click, Views-List Output, View-Excel In-place, and Download scenario for SE16N in this scenario.

BP – Identification tab – Tax Numbers section

962.png

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

966.png

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

967.png

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

968.png

969.png

970.png

971.png

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.

952.png

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.

978.png

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

973.png

980.png

974.png

981.png

979.png

982.png

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_TAXNUM
  • Select “Type” as “Field Level Masking
  • Enter “Description” as “Mask Tax Number based on Tax Type
  • Click on “Save” button

975.png

Write following logic into Policy

976.png

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

977.png

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

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK