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
10 Ways to Keep a Rogue RasPi From Wrecking Your Network
Curtis Franklin Jr., Senior Editor at Dark Reading,  7/10/2019
The Security of Cloud Applications
Hillel Solow, CTO and Co-founder, Protego,  7/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-0234
PUBLISHED: 2019-07-15
A Reflected Cross-site Scripting (XSS) vulnerability exists in Apache Roller. Roller's Math Comment Authenticator did not property sanitize user input and could be exploited to perform Reflected Cross Site Scripting (XSS). The mitigation for this vulnerability is to upgrade to the latest version of ...
CVE-2018-7838
PUBLISHED: 2019-07-15
A CWE-119 Buffer Errors vulnerability exists in Modicon M580 CPU - BMEP582040, all versions before V2.90, and Modicon Ethernet Module BMENOC0301, all versions before V2.16, which could cause denial of service on the FTP service of the controller or the Ethernet BMENOC module when it receives a FTP C...
CVE-2019-6822
PUBLISHED: 2019-07-15
A Use After Free: CWE-416 vulnerability exists in Zelio Soft 2, V5.2 and earlier, which could cause remote code execution when opening a specially crafted Zelio Soft 2 project file.
CVE-2019-6823
PUBLISHED: 2019-07-15
A CWE-94: Code Injection vulnerability exists in ProClima (all versions prior to version 8.0.0) which could allow an unauthenticated, remote attacker to execute arbitrary code on the targeted system in all versions of ProClima prior to version 8.0.0.
CVE-2019-6824
PUBLISHED: 2019-07-15
A CWE-119: Buffer Errors vulnerability exists in ProClima (all versions prior to version 8.0.0) which allows an unauthenticated, remote attacker to execute arbitrary code on the targeted system in all versions of ProClima prior to version 8.0.0.