SAP Basis SolMan - the Solution Manager takes over the monitoring of the system status and enables central application management

Direkt zum Seiteninhalt
SolMan - the Solution Manager takes over the monitoring of the system status and enables central application management
System Guides
In this article on SAP Security Automation I would like to take a look at the future of automated processes in the SAP Security area. For many companies, the topic of security automation still offers a lot of potential in terms of time savings and process optimisation. Our daily work environment offers numerous tasks that could be handled excellently automatically. For this reason, in this article I present two of the possibilities that already exist in the broad area of security automation. Security Automation via SAP Security Check The first option of Security Automation, which I want to introduce here, is the automatic verification of the existing permissions. Have you ever wondered who has critical permissions in your SAP system? And have you ever tried to do this by hand? Depending on the level of expertise and experience of the privilege administrator, this is a time-consuming work. If an audit is also announced and the SAP system is to be checked for critical permissions and segregation of duties, then it is very difficult to meet all requirements and secure the eligibility landscape in this respect. For this reason, various vendors provide solutions to automate the verification of the permission system with regard to critical permissions and segregation of duties using tool support. This allows permission administrators to use their valuable time to correct the errors rather than just looking for them. For example, we use a tool that runs through the verification of over 250 rules. We then get an evaluation of which rules are violated and which points are correct. A simple example of such rules is the use of the SAP_ALL profile. Another would be to grant the jump permission in debugging (S_DEVELOP permission object with the ACTVT = 02 field). These are two relatively simple examples of Security Check tools' rulebook. In addition, queries are also made, which are located in the field of Segregation of Duties. Using this tool allowed us to move from manual validation of critical permissions to an automatic process.

As an interface to the user, the presentation layer contains software components (the SAP GUI) by means of which the user is presented with the application. During its runtime, an SAP GUI component is always permanently linked to a user logon to the NetWeaver AS ABAP.
ABAP®/ABAP® OO
Before SAP HANA was released, there was no SAP database - you had to install SAP ERP (or the application you were using) on a third-party database, such as Oracle or SQL Server. SAP developed the HANA database to fully leverage the power of SAP's next-generation S/4 software.

The SAP Basis & Technology department deals intensively with SAP technologies and their application. The possibilities and limits are examined and corresponding specifications and tools are developed in order to use the technologies profitably. The results and findings are made available to the other alogis areas and implemented in real-life customer projects.

"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.

ADJUST SAP basis NAMING The original definition and naming of the SAP basis no longer meets today's task.

This distinction must also be drawn in the direction of application development.
SAP Corner
Zurück zum Seiteninhalt