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 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
Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: I think the boss is bing watching '70s TV shows again!
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-26244
PUBLISHED: 2020-12-02
Python oic is a Python OpenID Connect implementation. In Python oic before version 1.2.1, there are several related cryptographic issues affecting client implementations that use the library. The issues are: 1) The IdToken signature algorithm was not checked automatically, but only if the expecte...
CVE-2020-28206
PUBLISHED: 2020-12-02
An issue was discovered in Bitrix24 Bitrix Framework (1c site management) 20.0. An "User enumeration and Improper Restriction of Excessive Authentication Attempts" vulnerability exists in the admin login form, allowing a remote user to enumerate users in the administrator group. This also ...
CVE-2017-14451
PUBLISHED: 2020-12-02
An exploitable out-of-bounds read vulnerability exists in libevm (Ethereum Virtual Machine) of CPP-Ethereum. A specially crafted smart contract code can cause an out-of-bounds read which can subsequently trigger an out-of-bounds write resulting in remote code execution. An attacker can create/send m...
CVE-2017-2910
PUBLISHED: 2020-12-02
An exploitable Out-of-bounds Write vulnerability exists in the xls_addCell function of libxls 2.0. A specially crafted xls file can cause a memory corruption resulting in remote code execution. An attacker can send malicious xls file to trigger this vulnerability.
CVE-2020-13493
PUBLISHED: 2020-12-02
A heap overflow vulnerability exists in Pixar OpenUSD 20.05 when the software parses compressed sections in binary USD files. A specially crafted USDC file format path jumps decompression heap overflow in a way path jumps are processed. To trigger this vulnerability, the victim needs to open an atta...