Operations

4/23/2016
09:00 AM
Sean Martin
Sean Martin
Slideshows
Connect Directly
LinkedIn
RSS
E-Mail
50%
50%

10 Tips for Securing Your SAP Implementation

Without clear ownership of security for a critical business platform like SAP, it should come as no surprise that SAP cybersecurity continues to fall through the cracks among IT, admin, security and InfoSec teams.
Previous
1 of 11
Next

Image Credit: imsmartin/Onapsis/Ponemon Institute

Image Credit: imsmartin/Onapsis/Ponemon Institute

Companies can’t afford downtime, for even minutes, yet they often leave their most critical business infrastructure components at risk and open to attack or misuse. The widely used SAP platform appears to be no different in this regard.

According to a recent Ponemon Institute report, on average, companies reported at least two breaches in the past 24 months related to their SAP platform -- a little secret many companies don’t share publicly -- and an under-documented situation that barely tends to make the news.

  • Why aren’t companies taking this seriously?
  • Are they worried about the downtime associated with implementing security changes?
  • Or have they simply not considered the risk involved, and therefore haven’t taken the step-by-step actions required to begin mitigating that risk?

In this collection of slides, we review 10 actions organizations can take to improve their security posture as it relates to their SAP platform and applications. Some of these tips will be obvious to the information security professional responsible for traditional mobile, desktop, and server security; but the tips need to be applied to their SAP implementation as well.

Note: The team at imsmartin would like to thank Onapsis and the Ponemon Institute for their contributions and research that led to this collection.

 

Sean Martin is an information security veteran of nearly 25 years and a four-term CISSP with articles published globally covering security management, cloud computing, enterprise mobility, governance, risk, and compliance—with a focus on specialized industries such as ... View Full Bio

Previous
1 of 11
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Valentine's Emails Laced with Gandcrab Ransomware
Kelly Sheridan, Staff Editor, Dark Reading,  2/14/2019
High Stress Levels Impacting CISOs Physically, Mentally
Jai Vijayan, Freelance writer,  2/14/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-20782
PUBLISHED: 2019-02-17
The GloBee plugin before 1.1.2 for WooCommerce mishandles IPN messages.
CVE-2019-8407
PUBLISHED: 2019-02-17
HongCMS 3.0.0 allows arbitrary file read and write operations via a ../ in the filename parameter to the admin/index.php/language/edit URI.
CVE-2019-8408
PUBLISHED: 2019-02-17
OneFileCMS 3.6.13 allows remote attackers to modify onefilecms.php by clicking the Copy button twice.
CVE-2016-10742
PUBLISHED: 2019-02-17
Zabbix before 2.2.21rc1, 3.x before 3.0.13rc1, 3.1.x and 3.2.x before 3.2.10rc1, and 3.3.x and 3.4.x before 3.4.4rc1 allows open redirect via the request parameter.
CVE-2019-8393
PUBLISHED: 2019-02-17
Hotels_Server through 2018-11-05 has SQL Injection via the API because the controller/api/login.php telephone parameter is mishandled.