Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Operations

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

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.
2 of 11

Tip 1: Recognize the Risk

SAP runs some of the most critical business apps imaginable. They, in turn, hold quite a few of your company's crown jewels.

As with most challenges we face in life, the first step to solving a problem is recognizing that we, in fact, have a problem. The world of information security is no different. And as you might deduce, the world of securing your SAP platform is also the same.

Before you can get buy-in from the business and the technical teams to solve the problem, you first need to accept that you have a risk or a deficient process in your SAP implementation. One way to obtain this level of risk recognition is to think through your current situation by asking the following questions:



- How quickly do I apply critical (CVSS 8 or higher) patches for my Windows systems?
- How quickly are critical patches applied to my SAP systems, according to my SLA?
- If the latter is longer than the former, why am I willing to live with severe risk in my SAP systems for longer periods (sometimes significantly longer) than my Windows systems?
- What business processes and critical information flow through my SAP systems? 
- Is it acceptable for them to be exposed to this risk?



If you are fortunate enough to find your answers didn't send you into a full tailspin, a quick technical review at this point -- meaning, simply checking that each SAP system is running the latest service pack -- could change that perspective dramatically. Even if you have the latest service packs installed, it's probably wise to keep flicking through these slides to make sure you have some other tips covered as well.

Image Credit: imsmartin/Onapsis/Ponemon Institute

Tip 1: Recognize the Risk

SAP runs some of the most critical business apps imaginable. They, in turn, hold quite a few of your companys crown jewels.

As with most challenges we face in life, the first step to solving a problem is recognizing that we, in fact, have a problem. The world of information security is no different. And as you might deduce, the world of securing your SAP platform is also the same.

Before you can get buy-in from the business and the technical teams to solve the problem, you first need to accept that you have a risk or a deficient process in your SAP implementation. One way to obtain this level of risk recognition is to think through your current situation by asking the following questions:

  1. How quickly do I apply critical (CVSS 8 or higher) patches for my Windows systems?
  2. How quickly are critical patches applied to my SAP systems, according to my SLA?
  3. If the latter is longer than the former, why am I willing to live with severe risk in my SAP systems for longer periods (sometimes significantly longer) than my Windows systems?
  4. What business processes and critical information flow through my SAP systems?
  5. Is it acceptable for them to be exposed to this risk?

If you are fortunate enough to find your answers didnt send you into a full tailspin, a quick technical review at this point -- meaning, simply checking that each SAP system is running the latest service pack -- could change that perspective dramatically. Even if you have the latest service packs installed, its probably wise to keep flicking through these slides to make sure you have some other tips covered as well.

Image Credit: imsmartin/Onapsis/Ponemon Institute

2 of 11
Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
Data Privacy Protections for the Most Vulnerable -- Children
Dimitri Sirota, Founder & CEO of BigID,  10/17/2019
Sodinokibi Ransomware: Where Attackers' Money Goes
Kelly Sheridan, Staff Editor, Dark Reading,  10/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-18216
PUBLISHED: 2019-10-20
** DISPUTED ** The BIOS configuration design on ASUS ROG Zephyrus M GM501GS laptops with BIOS 313 relies on the main battery instead of using a CMOS battery, which reduces the value of a protection mechanism in which booting from a USB device is prohibited. Attackers who have physical laptop access ...
CVE-2019-18214
PUBLISHED: 2019-10-19
The Video_Converter app 0.1.0 for Nextcloud allows denial of service (CPU and memory consumption) via multiple concurrent conversions because many FFmpeg processes may be running at once. (The workload is not queued for serial execution.)
CVE-2019-18202
PUBLISHED: 2019-10-19
Information Disclosure is possible on WAGO Series PFC100 and PFC200 devices before FW12 due to improper access control. A remote attacker can check for the existence of paths and file names via crafted HTTP requests.
CVE-2019-18209
PUBLISHED: 2019-10-19
templates/pad.html in Etherpad-Lite 1.7.5 has XSS when the browser does not encode the path of the URL, as demonstrated by Internet Explorer.
CVE-2019-18198
PUBLISHED: 2019-10-18
In the Linux kernel before 5.3.4, a reference count usage error in the fib6_rule_suppress() function in the fib6 suppression feature of net/ipv6/fib6_rules.c, when handling the FIB_LOOKUP_NOREF flag, can be exploited by a local attacker to corrupt memory, aka CID-ca7a03c41753.