Feedback from consultants who are experts in the technology;
SE80 ABAP Workbench
In order to escape the checks carried out by the iris scanners and ultimately his own arrest, a doctor illegally reuses his eyes and acts under a new identity. With the help of the new eyes he finally succeeds in entering the secured area of the "Precogs" and he can begin his investigation. Through this "biohacking" he not only deceives the biometric security systems - he compromises the highest police control system. All stories!? "Great stories!" think now. But: No one will ever fall for a simple trim. And anyway: Biometric security systems and eye transplantation? It's not for nothing a science fiction movie! What does this have to do with RFC security? All right, I can understand your doubts. But how do you like the following story, for example? RFC Security and the Art of Identity Change Germany, everywhere, 2017: Johannes Voigt has been a medium-sized company employee for several years. He is considered a reliable and conscientious developer from the IT department. In fact, he is increasingly unfairly treated. He decides that he no longer wants to carry his frustration with him.
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.
SM62 Event History
Cross-client tables can be modified. The control system of another, productive client can thus be undermined and undermined. Quite a lot of power! Did you also know that the SAP system provides a feature that deletes table change protocols (DBTA BLOG table) and that it is effective across all clients? If the table change logs have not been additionally archived via the BC_DBLOGS archiving object, traceability is no longer available. That way, every criminal act within your company can be beautifully covered up. Similarly, full access to batch management allows you to manage all background jobs in all clients with the permission. This allows you to delete old background jobs that have gone unauthorised. There are also some points to consider when managing print jobs. Typically, the following two SAP access permissions are enabled to protect print jobs: S_SPO_DEV (spooler device permissions) S_SPO_ACT (spooler actions). Why? Confidential information in print jobs is not protected against unauthorised disclosure. (Strictly) sensitive print jobs can be read unauthorised or redirected to external printers and printed out. Print jobs are unprotected unless additional SAP access permissions are enabled to protect print output. The print jobs are multi-tenant, which means that the authorisation award should also be well thought through at the point.
In every company with an SAP system, there is someone who is responsible for the SAP Basis. This person ensures the trouble-free operation of the SAP system. He or she accompanies maintenance work and intervenes in special situations, such as poor performance. Even for companies that hand over the operation of Basis to an external service provider, there are often still tasks from the user and authorization management environment at this point.
For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.
Examples of names are: SAP Cross-Application, SAP Innovation & Technology, SAP Services & Innovation, SAP Operations & Innovation or SAP Service Provider & Business Innovator.
Then switch to the Permissions tab to generate the current profile of the permission objects with the new Fiori permission.