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
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19594
PUBLISHED: 2019-12-05
reset/modules/fotoliaFoto/multi_upload.php in the RESET.PRO Adobe Stock API Integration for PrestaShop 1.6 and 1.7 allows remote attackers to execute arbitrary code by uploading a .php file.
CVE-2019-19595
PUBLISHED: 2019-12-05
reset/modules/advanced_form_maker_edit/multiupload/upload.php in the RESET.PRO Adobe Stock API integration 4.8 for PrestaShop allows remote attackers to execute arbitrary code by uploading a .php file.
CVE-2019-3690
PUBLISHED: 2019-12-05
The chkstat tool in the permissions package followed symlinks before commit a9e1d26cd49ef9ee0c2060c859321128a6dd4230 (please also check the additional hardenings after this fix). This allowed local attackers with control over a path that is traversed by chkstat to escalate privileges.
CVE-2013-0243
PUBLISHED: 2019-12-05
haskell-tls-extra before 0.6.1 has Basic Constraints attribute vulnerability may lead to Man in the Middle attacks on TLS connections
CVE-2018-10021
PUBLISHED: 2019-12-05
Improper validation of URL redirection in the Kubernetes API server in versions prior to v1.14.0 allows an attacker-controlled Kubelet to redirect API server requests from streaming endpoints to arbitrary hosts. Impacted API servers will follow the redirect as a GET request with client-certificate c...