You already know enough about SAP ERP Security and realize a real impact of having insecure SAP implementation.
Recently, Crowd Research Partners have released ERP Cybersecurity Survey 2017 conducted across almost 2000 respondents of different roles from various industries. According to this research, 89% of security professionals predict that the number of attacks on SAP systems will increase. Moreover, the average damage of an SAP Security breach is estimated at $5 million. It’s unthinkable, isn’t it?
Let’s start with the oldest and most known SAP Security area – SAP Segregation of Duties, or the SAP SoD. I will try to embrace it in general, without in-depth details.
Plenty of articles that cover various aspects of SAP Security, especially concerning vulnerabilities and risks, paved the way for today’s discussion on how we can protect SAP (which is of particular importance now given the upcoming GDPR).
SAP, like any other large vendor, is evolving towards greater mobility and providing access to its applications from different devices located anywhere in the world. Therefore, its product portfolio includes solutions that allow mobile users to interact with business applications such as those based on ABAP, Java or HANA platforms. In this article, you will learn the most relevant explanatory notes about SAP Mobile Platform and SAP Afaria, their vulnerabilities and security trends.
In the previous article, we discussed SAP NetWeaver ABAP Platform and its vulnerabilities. Today’s topic is the J2EE platform, its architecture, vulnerabilities, and the latest trends in its cybersecurity.
The previous articles of SAP Security for CISO series covered examples of potential attacks on these systems, so now it is high time to learn how these attacks can be conducted via vulnerabilities discovered in SAP systems.