Maintenance of SAP licenses
Monitoring of the SAP system landscape through regular system checks according to defined schedules and workflows
Costs: 75% savings on subsequent corrections. Significant reduction in development and maintenance costs. ABAP code: 84% faster and more fail-safe programs. Improved performance reduces runtime and hardware utilization. Targeted corrections minimize system errors and downtime.
SAP administrators are present wherever SAP systems are used. This is now true for many industries and business sectors. SAP systems can be found in the areas of accounting, cost accounting, activity-based costing and controlling. In all of these areas, they ensure smooth operation and further development, helping the company to make internal processes more efficient and thus save costs and resources.
SAP Performance Optimization
So-called Access Control Lists (ACL) offer a good possibility to secure your gateway in order to exclude unwanted external accesses to the database of the application server. With the help of the ACL files reginfo and secinfo an access control can be implemented, in which allowed as well as forbidden communication partners can be defined. The reginfo file controls the registration of external programs on the gateway, which means that rules can be defined that allow or prohibit programs. With the help of the file secinfo you can define which users are allowed to start an external program. To be able to use these files, you must set the parameters gw/reg_info and gw/sec_info (transaction RZ11). For more information, refer to SAP Note 1408081.
A secure SAP system does not only include a good role concept. It is also necessary to check whether a user should (still) have a specific role. Regular verification of role assignment is called recertification. In this blog post, I'd like to introduce you to the need for recertifications and our own tool, EasyReCert. The need for recertification - scenarios: Example 1: The "apprentice problem" Imagine the following scenario: A new employee (e.g. apprenticeship or trainee) will go through various departments as part of his or her training and will work on various projects. Of course, an SAP User will be made available to your employee right at the beginning, which is equipped with appropriate roles. As each project and department passes, the employee repeatedly needs new permissions to meet the requirements. After the employee has successfully completed his or her induction and is now in a permanent position, he or she still has permissions that are not necessary to perform his or her duties. This violates the principle of "last privilede" and represents a potential security risk for your company. Example 2: The change of department The change of department is one scenario that probably occurs in every company. If a change of department does not automatically involve a complete reallocation of roles and the employee simply takes his old permissions with him, critical combinations of permissions can occur very quickly. For example, an employee who has permissions in accounts payable and accounts receivable violates the SoD ("Segregation of Duties") principle and poses a potential security risk to your company. Recertification as part of a revision: The two examples above show that a regular review of role allocation identifies potential security risks for your business and can be addressed.
"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.
This is the approach I'll describe to you in the following post.
Further details on the recommendation can be found in the Master's thesis in chapters 7.5 and 9.3.