Configuration and maintenance of all peripheral units
If all financial and sales activities as well as production, logistics and the personnel administrators run via one system, measures must be taken to ensure reliable functioning on the one hand and to protect the system internally and externally on the other. Due to the long history, the increased availability requirements often do not match the actual protection measures, so that security risks often arise at this point.
The following figure shows the logging for the SAP standard group "SUPER". For this group, all activities are recorded in all clients.
RSMEMORY: Dynamically Set Memory Parameters
This access method depends solely on the rights assigned to the user. System users: Users of this user group are comparable to SAP*. They act as administrator in the system. Therefore, they should be deactivated / set to inactive as soon as possible, as soon as the system operation is ensured. You should still be aware of the SAP ERP environment to address this security risk. In a HANA system, there are privileges instead of permissions. The difference is first of all in terms of terminology. Nevertheless, the permissions are assigned differently (directly / indirectly) via the assignment of roles. These are thus accumulations of privileges. As in older SAP systems, system users must be disabled and certain roles that already exist must be restricted. Compared to an SAP ERP system, small apps are allowed instead of large applications. In this case, attention should be paid to an individual authorisation. It should be a matter of course for users to have implemented secure password rules. Settings Securing the system also means securing the underlying infrastructure. Everything from the network to the host's operating system must be secured. When looking at the system landscape, it is striking that the new technology brings many connections that need to be secured. The SAP Gateway, which is responsible for the connection between backend and frontend, is also a security risk and must be considered. All security settings of existing and future components must be validated to HANA compatibility. Secure communication of connections is obtained when you restrict access where possible. Encryption of the data of a HANA system is disabled by default. Be sure to encrypt sensitive data anyway. Especially data that is archived. If an attack is made on your system, you should be able to run forensic analysis, so you should enable the audit log. Moreover, few users should have access to it.
The SAP Patch Manager (SPAM) is the online correction support (OCS) customer site. The SPAM transaction gives you the ability to easily and efficiently import support packages provided by SAP into your system. Depending on the system used or the configuration of your system, you must insert different types of Support Packages [page 8]. You will receive support packages in SAPNet - Web Frontend, in SAPNet - R/3 Frontend or on Collection CDs. Since SPAM runs within the SAP system, you do not need to know the operating system to handle the transaction. In the language usage of SAP, the term patch has been replaced by the term support package. Note that you can only work with this transaction in SAP GUI for Java and SAP GUI for Windows.
Use "Shortcut for SAP Systems" to accomplish many tasks in the SAP basis more easily and quickly.
On the other hand, a self-created e-learning offer offers the possibility to design it completely by itself and tailor it to the company's own needs.
A partner agreement must be entered into for each supplier in the transaction WE20.