SAP System Analysis
DOCUMENTATION / ARCHIVING
Why should we even have an individual SAP Security Check performed? Your SAP authorisation concept is designed to ensure the security and protection of data against unauthorised access and abuse. The technical complexity of SAP systems and the ongoing adaptations of business processes often lead to unknown security vulnerabilities. In addition, the increasing digital networking with business partners offers further attack points on your SAP system. SAP Security Check gives you an overview of the security situation of your SAP systems. This will identify potential risks that could jeopardise the safe operation of your IT landscape. Your starting situation The ongoing changes in your IT systems lead to unrecognised security vulnerabilities and your auditors will regularly report to you in the final report on abuses in the authorisation concept. The legal requirements (e.g. EU guidelines) to secure your business processes and IT systems have not yet been implemented and the increasing networking with business partners presents new challenges to your security system. The security-related system settings and permissions settings applied to your SAPS systems are poorly documented, which in many cases causes the system settings to allow extensive critical access unchecked. Critical SAP permissions, profiles, and roles identify permissions that allow critical operations to be performed in terms of security or from a legal or business perspective are called "critical permissions" by SAP. The granting of critical allowances must therefore generally be carried out with particular care and should therefore be planned in advance. Technical and organisational measures and processes must then ensure that the desired level of safety is implemented.
The SAP Patch Manager offers two scenarios for inserting support packages or queues: Test Scenario Use the test scenario to determine whether conflicts or problems occur (e.g., unreleased repairs) or whether a modification match is necessary before the actual insertion. This scenario allows you to estimate and minimise the time and effort required to load support packages. In this scenario, no data is imported into the system, and you can continue to play in the event of an error without the error being corrected. You must select the test scenario explicitly. Note that once the test scenario has passed, the queue is empty and needs to be redefined. You must also explicitly choose the default scenario.
Mentioning the SUM tool leads us to another part of SAP Basis: system updates and upgrades. Since SAP software receives updates from SAP at regular intervals - in the case of R/3 in the form of SPS (Support Package Stacks) and in the case of S/4HANA in the form of FPS (Feature Pack Stacks) - a large part of an SAP Basis administrator's job is to import these packages into the SAP system.
The implementation of a cross-sectional function will promote and safeguard the operation of the SAP systems that form the backbone of the company. By coordinating the SAP basis with other IT departments, the optimisation is always done in the overall context of the company or the IT organisation. Eliminating the separation of SAP and non-SAP topics in areas where it is considered useful will lead to expert groups and synergy effects through centralisation.
With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.
For the SAP basis, the content is an essential feature of the market communication.
Application layer: The application layer is the core of an R/3 SAP Basis system.