SAP Basis Why do you need SAP Basis admins in your company? - SAP Basis

Direkt zum Seiteninhalt
Why do you need SAP Basis admins in your company?
Support for Basis Projects
A well-cared-for emergency user concept enables the audit-proof allocation of extended permissions in combination with the assurance of daily operations in your company. This article first addresses the fundamental issues that require an emergency user approach. It then briefly explains how such a concept works in general and how we implement it. An Emergency User is normally used when tasks are temporarily taken over outside the initial field of activity. I described the different scenarios of when such a user can be used and how to deal with them in this blog post for you. Why is an emergency user approach important? There are several scenarios in which the use of an emergency user with extended rights is useful: In urgent cases, it is often necessary to be able to quickly make changes to the system that are outside the user's actual field of activity. A key user who has the necessary permissions is on vacation and needs a representation. The same user suffers short-term illness and his/her representative must take over his/her duties to ensure the operation. We recommend developing a concept for the short-term allocation of the additional permissions. This will ensure the implementation of the above scenarios. How does an emergency user approach work? An emergency user concept in SAP works fundamentally via a temporary assignment of additional rights to a specific user. After the tasks have been completed, the user is deprived of the rights. The tasks performed with the extended permissions are logged and can then be evaluated by an auditor. However, there are a few things to keep in mind: A process for granting special rights should be defined. It must be specified which users can get special rights. The time period for which users can request an emergency user should be limited.

Remove weak password hashes from the system: Only updating the profile parameter does not provide you with the necessary security. There are still many weak hash values in your database that can be used to attack your system. These must be completely removed from the database. To do this, use the report CLEANUP_PASSWORD_HASH_VALUES. To do this, call the transaction SA38 and enter the name of the report in the input field. Run or F8 executes the programme and cleans your database Report CLEANUP_PASSWORD_HASH_VALUES This programme removes the outdated hash values across all clients. Have you already experienced this attack method or any other comments on this topic? Share your experiences with us in the form of a comment under this article.
Best Practice SAP Basis Administration: Batch Control
SWPM - the Software Provisioning Manager integrates the classical tools like sapinst, ehpup, etc. for the maintenance/installation of SAP systems.

In the SAP NetWeaver BI Authorization Concept lesson, the training participant is familiarized with the authorization functions of the SAP Business Information Warehouse. The differences between the authorization concept for ERP systems and the authorization concept for NetWeaver BI are taught.

"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.

Access to it is provided by the class methods of the CL_PERS_ADMIN class.

However, especially with large SAP landscapes, there are strict regulations regarding the permissions of technical RFC users.
SAP BASIS
Zurück zum Seiteninhalt