This sheet is past its review date. Deadlines or advice may have changed since 5 Nov 2026.
SAP and ERP: is the system that moves your money patched, closed and watched?
This month, take every ERP web component that doesn't need to be public off the internet, and apply each month's SAP Security Notes and Oracle patches within the patching sheet's deadlines. Then close the paths inside (RFC gateway, trusted connections, standard users, SAP_ALL in production) and keep the Security Audit Log on and in your SIEM, so someone reviews every emergency and admin session.
If you only do five things
Keep support packages under 24 months old.
SAP fixes new high and critical notes only for support packages shipped in the last 24 months1.
Handle each SAP Patch Day
Which notes apply to which system?
System Recommendations in SAP Solution Manager matches new Security Notes and HotNews against each system2; otherwise filter All Security Notes in SAP for Me1.
How fast must each one go in?
Use the patching sheet's tiers: exploited (in KEV5) within 72 hours on internet-facing systems and 7 days inside, other Critical and High notes within 14 and 30 days.
Did the fix reach production?
Implement ABAP corrections in development, transport them on28 and record each note's status per system12.
Is the server still talking to the internet?
Block non-essential outbound internet traffic from ERP servers, as Google advises for EBS; it can disrupt an attack even after a break-in7.
Exploited ERP flaws since 2025
- SAP Visual Composer, CVE-2025-31324 and -42999. Ransomware used both uploader flaws; in KEV since 29 April and 15 May 20255.
- Oracle EBS, CVE-2025-61882. Google saw likely zero-day attacks from 9 August 2025 and data theft7; in KEV since 6 October5.
- Oracle PeopleSoft, CVE-2026-35273. ShinyHunters exploited it from 27 May 2026, before Oracle's 10 June alert8; in KEV since 12 June5.
- Oracle Payments in EBS, CVE-2026-46817. An unauthenticated takeover rated 9.8, fixed on 28 May 202611; in KEV since 15 July5.
Close the paths inside
- Block function modules nobody calls. In UCON's final phase, remote-enabled function modules not assigned to a communication assembly can't be called from outside17.
- Treat trusted RFC like a stored password. We extend BSI's stored-password rule12: production never trusts development or test systems.
- Lock the standard users. Lock SAP*, DDIC and EARLYWATCH but keep SAP* in every client, and check with report RSUSR00318.
- Run jobs as technical users. Background jobs run as System users, not Dialog users12. Move the transport job RDDIMPDP off DDIC, so DDIC can stay locked18.
Powerful rights and emergency access
- Remove debug and replace. S_DEVELOP for DEBUG with change rights lets users alter accounting data in memory, bypassing the audit trail14.
- Remove all-table access. No production user should display every table through SE16 with S_TABU_DIS for all groups14.
- Review every firefighter session. Unlock emergency users per ticket and log everything12. SAP Access Control sends each session's logs to a reviewer, if the system records them19.
- Protect vendor bank details. Mark bank fields as sensitive, so a second user must confirm changes before the automatic payment run20; manual payments aren't blocked21.
Logs, transports and custom code
- Send the audit log to your SIEM. Microsoft Sentinel for SAP charges per production system and needs SAP Integration Suite2425.
- Gate every transport. Build roles and code only in development12; the ABAP Test Cockpit checks code at transport release22. Its security checks, Code Vulnerability Analyzer, need a per-user license on premises or a BTP ABAP Environment23.
- Follow APP.4.6 in custom ABAP. Check AUTHORITY-CHECK results; avoid dynamic Open SQL, ADBC and INSERT REPORT13.
When ERP security fixes stop
- End of 2027. Mainstream maintenance ends for SAP ERP 6.0, EHP 6 to 826, and SAP Solution Manager2.
- 2028 to 2030. Optional extended maintenance, at 2 percentage points more26. Then, in customer-specific maintenance, SAP considers new high and critical notes for 12 months only1.
- RISE transition option. Security patches from 2031 to 2033, or with further prerequisites to 2035, for systems moved to SAP ERP, private edition on HANA by the end of 203027.
What to demand from RISE and partners
- Know what RISE leaves you. Without Cloud Application Services, you find and request notes; testing and the application's security concept stay yours28.
- Own the SIEM rules. LogServ is optional, and SAP doesn't confirm receipt, write correlation rules or watch alerts28.
- Write it into the contract. Monthly patch status, deadlines for exploited and Critical notes, personal accounts; see the third-party-risk sheet.
What changed in 2026
- Oracle patches monthly. Critical Security Patch Updates, first on 28 May, now fill the months between quarterly updates9.
- SAP's own npm packages were poisoned. Malicious CAP database packages and MTA Build Tool versions appeared in April3. See the supply-chain sheet.
- ECC on RISE until 2035. Since 13 October, the transition option may run to the end of 2035, with further prerequisites27.
What you can skip
- Buying threat detection first. Sentinel for SAP or SAP Enterprise Threat Detection sees little while the audit log is off and notes lag.
- Applying every note on Patch Day. Support Package Security Notes can wait for the next support package1.
- A full SoD rule set first. Removing SAP_ALL and debug and replace cuts more risk, sooner.
Mistakes that cost the most
- Leaving unused components installed. Visual Composer, exploited in 2025, got another 9.9 note in October 20264.
- Falling behind on cumulative patches. Oracle's fix for CVE-2025-61882 needed the October 2023 Critical Patch Update first10.
- Relying on a WAF alone. Google warns WAF body-inspection rules can be bypassed8.
What this looks like at your size
Small team, no security staff
Growing, with IT or security staff
- Run Patch Day with System Recommendations and track each note into production.
- Move to restrictive gateway files, start UCON logging and alert on emergency user logons.