Safety first:
SAP S/4 HANA Security

Building security by design into SAP S/4 HANA implementations

This very practical guide has been created to help SAP customers understand the new security considerations that come with implementing SAP S/4 HANA. We want you to side-step the mistakes of retrospective security work - so prevalent with past ERP projects. So, while there is still time to plan your migration, this guide will help you do so with security and compliance very much in mind.

The eBook will cover the following in detail:

• The difference between SAP ECC and SAP S/4 HANA security

SAP S/4 HANA removes the common obstacles associated with legacy ERP applications, such as batch latency, complex landscapes and manually driven processes. It's been designed to operate exclusively on SAP’s proprietary HANA in-memory database and significantly improve overall system performance.

• SAP S/4 HANA security

From a security perspective, you can expect significant involvement in an SAP S/4 HANA implementation, as there are some fundamental changes to the way in which these simple processes are delivered to users.

• SAP Fiori architecture and security

One of the biggest drivers for moving to SAP S/4 HANA is to embrace the significantly enhanced user experience provided by SAP Fiori. It's important however to recognise that the use of SAP Fiori introduces many new components of security.

• SAP HANA roles & privileges

SAP S/4 HANA relies upon the HANA database to deliver the huge value-adding features of performance, transparency and simplicity. The database itself becomes far more visible to end users, particularly in the context of reporting and analytics.

• The impact of SAP GRC on SAP S/4 HANA