Update/upgrade of databases
SM20 Evaluation of the Security Auditlog
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 basic SAP Basis operation includes the operational readiness of the SAP system, management of system changeability, configuration and administration of system profiles, analysis of system failures, operation and monitoring of technical interfaces, scheduling and monitoring of SAP standard jobs, and much more. The optional services as an extension include activities whose implementation and frequency depends on the existing system environment and which can be optionally booked (client copies, implementation of client transports and homogeneous/heterogeneous system copies, etc.). These include performing release upgrades, installing enhancement packages, adapting new printer types, device drivers or character sets, and much more.
On www.sap-corner.de you will also find useful information about SAP basis.
Support for Basis Projects
Using various user, administration and monitoring tools, the SAP Basis system is controlled and managed by an administrator, who is thus responsible for its trouble-free operation. Many companies hand over these tasks to an external service provider.
SAP on Azure or on Amazon Web Services (AWS) is a scalable, reliable platform for your current and future SAP HANA requirements. Achieve optimal performance for your entire system by migrating to Azure or AWS. Get the best of both worlds!
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
Similarly, a bot can create incidents or notifications when something goes wrong.
So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.
You can also install any patches here.