Security for S/4 Hana migrations
"This is grossly negligent"
says Bodo Kahl, CEO Sast Solutions of Akquinet.
"S/4 Hana is completely new software and legacy systems open the door to hackers. The switch to S/4 is an opportunity to improve the security of SAP systems enormously."
Three aspects should be considered as part of a secure S/4 Hana migration, for example, technical security. After a security audit, hardening of the target systems takes place, followed by continuous real-time monitoring for critical incidents.
The adaptation of the authorization concept is also crucial. During migration, the existing authorization concept cannot be adopted one-to-one.
On this occasion, it is therefore more than sensible to check existing roles for critical authorizations and SoD conflicts and to transfer them without disruptions.
Finally, companies should clean up their Abap code. Experience shows that up to 70 percent of the customer's own code is obsolete and does not need to be migrated. Cleaned up in this way, S/4 Hana systems are then optimally protected against threats.
