Company Blog Details How To Decrease SAP Attack Surfaces If No Patches Are Available
SAP security provider Security
On the second Tuesday of every month, SAP releases a list of security patches to help protect its software from malicious hacking attempts. The list of recommended patches can quickly accumulate causing IT personnel to lose track of the most crucial vulnerabilities as well as documenting the process of SAP patch analyzing, testing, and installing. As part of the SecurityBridge Platform, the new Security Roadmap for SAP not only has the ability to evaluate the resolution complexity of any security issue—as well as the probability of exploitation—but also group these patches in a logical hierarchy of importance. In addition, the Security Roadmap enhances the Security & Compliance Monitor that supports users to:
- Customize their own SAP Security baselines.
- Combine information from other platform sources and the online KB.
- Obtain insights on what may be missing—new SAP severity notes.
- Jump to patch management—supplement data to a risk tool.
- Experience a 360° view of activities and detected vulnerabilities to understand the impact in SAP.
- Create incidents from a finding, containing all information to report and initiate the remediation and document the status.
Recommended AI News: Danish Retailer Søstrene Grene Selects mParticle to Bring Hygge to Omnichannel Customer Data
“The best solution to a complex problem is often based on a simple idea,” said Christoph Nagy, CEO, SecurityBridge. “Given today’s unceasing corporate hacker environment, IT personnel must stay current on known SAP security issues and apply the recommended patches in a timely manner. SecurityBridge’s Roadmap for SAP utilizes a modern and structured SAP Fiori UI to bridge any communication gaps between IT stakeholders helping them to identify and categorize risks so vulnerabilities are remediated through a documented and logical mitigation process.”
Related Posts
SAP Zero-Day Exploitation
A zero-day vulnerability is a vulnerability (often a software flaw) that has been disclosed but is not yet patched. The Log4j vulnerability, for example—characterized as the single biggest, most critical vulnerability of the last decade—was identified in November 2021, made public in December 2021, but existed unnoticed since 2013!
February 8th, 2022, is another SAP Security Patch Day and new security patches will be revealed by SAP. This event starts the race between attackers and defenders—where defenders only win by installing the patch before the exploitation. However, even with this combined effort, Zero-Days can’t be eliminated.
As no patch is available for a Zero-Day scenario, there are a number of options companies may consider to protect themselves:
- Reduce the attack vectors, any connection point such as SAP Internet Communication Framework (ICF) services that are not used or needed, must be deactivated.
- Software components that do not serve a distinct purpose must be at least deactivated. For example, most SAP customers still run at least one SAP NetWeaver system where client 066 exists—this is no longer needed.
- Harden the SAP system, ensure the system is securely configured using a best practice and industry-proven security
baseline. - The recent Log4j incident and also the older RECON release, have proven that vulnerabilities exist for a long period of time without being noticed. Constant SAP system security monitoring is a key action to protect against severe damage.
Recommended AI News: Pittsburgh Drone Tech Company Provides Bridge Evaluation Resources
[To share your insights with us, please write to sghosh@martechseries.com]
Comments are closed.