AI Shrinks the SAP Patch Window to Hours
17m
AI is shrinking the SAP patching window from months to hours. Mike Vizard talks with Ivan Mans, co-founder and board member of SecurityBridge, about why vulnerability disclosures in SAP environments are surging and what organizations must do to keep up.
AI drives a surge in SAP vulnerabilities
Researchers, including SecurityBridge's own team, now use AI to find new vulnerabilities. As a result, patches are getting bigger. However, many customers still carry patching debt, and some have left known flaws unfixed for years. Meanwhile, attackers use AI without guardrails, so exploiting SAP no longer takes a deep specialist.
SAP patching: from months to hours
Ivan's research team turned seven SAP vulnerabilities into working exploits in three months using AI. Consequently, the traditional three-month patch cycle is far too slow. Even a three-day fix for high-severity notes is now too late. Fortunately, security patches are usually small and easy to test, so they rarely need the full functional test cycle.
Looking beyond severity scores
CVSS ratings still matter for SAP patching, but they should not drive every decision. Attackers chain medium-severity flaws together. Therefore, a known exploit in the wild can make an 8 more urgent than a 9.5.
Beyond SAP patching: harden and monitor
Ivan's advice is simple. First, track your patching debt and watch Patch Day on the second Tuesday of each month. Next, apply a strong hardening baseline using SAP's best practices. Finally, monitor in real time so you can respond at machine speed. In addition, disabling an unused vulnerable service is often quicker than a full fix. Ownership is shifting as well, as CISOs and IT security teams take responsibility for SAP patching.
SAP systems hold some of the most valuable assets in any business, so SAP patching has to be a priority. Explore more cybersecurity coverage and the latest Techstrong TV interviews.
For more information please visit securitybridge.com