Most security operations centers can tell you within minutes if a laptop starts talking to a known malicious server. Far fewer can tell you if someone in SAP just gave themselves SAP_ALL, switched off the Security Audit Log and ran a payment. That blind spot is what SAP Enterprise Threat Detection was built to close.
SAP Enterprise Threat Detection (ETD) is SAP’s own security monitoring tool for SAP systems. It collects logs such as the Security Audit Log, normalizes them, and runs attack detection patterns that raise alerts on suspicious activity, like a user unlocking SAP* or debugging with change in production. It runs on-premises, as an SAP-managed private cloud edition or as a SaaS cloud edition, optionally with SAP monitoring alerts around the clock.
In one sentence: SAP Enterprise Threat Detection reads SAP’s own logs, spots attack patterns that general SIEM tools usually miss, and alerts your team or SAP’s managed service.
Key takeaways
- ETD understands SAP log formats and SAP-specific attacks, which generic SIEM rules often don’t.
- It comes in on-premises, private cloud and SaaS cloud editions, plus a 24×7 managed service.
- Detection quality depends on the logs you feed it, especially the Security Audit Log.
- Users can appear as pseudonyms, which helps with privacy rules and works councils.
- ETD can forward alerts to a central SIEM such as Microsoft Sentinel or Splunk.
Why do SAP systems need their own threat detection?
A general SIEM sees network traffic, endpoint events and cloud logs. It usually doesn’t understand what a change to table T000 means, why a transaction start for SE16N with edit mode matters, or that an RFC call from an unknown host to a function that creates users is suspicious. SAP logs are also in formats many SIEM tools can’t parse without connectors.
ETD starts from the other side. It knows SAP’s logs and ships with patterns written for SAP attacks. SAP Learning notes that these patterns draw on sources including the DSAG ERP auditing guide, SAP’s anomaly detection research and SAP security notes.
Which editions of SAP Enterprise Threat Detection exist?
| Edition | Who runs it | Best fit |
|---|---|---|
| On-premises | You, on your own SAP HANA infrastructure | Organizations that must keep all log data in-house and have SAP and HANA skills |
| Private cloud edition | SAP, as a managed service within SAP Cloud Application Services | RISE and private cloud customers who want SAP to operate it |
| Cloud edition | SAP, as a multi-tenant SaaS on SAP BTP using SAP HANA Cloud | Most new customers; no infrastructure to run |
| Managed service | SAP security experts monitor alerts 24×7 on top of the cloud edition | Teams whose SOC lacks SAP knowledge |
The cloud edition collects logs from ABAP and HANA systems, both on-premises and in the cloud. SAP user group material from late 2025 describes roughly 150 out-of-the-box use cases in the public cloud edition, with customers able to build their own from scratch or from SAP templates.
How does ETD work?
- Collect. Logs flow from connected systems: the Security Audit Log, change documents, user change logs, HANA audit trails, gateway and HTTP logs, and others you add.
- Normalize and enrich. ETD maps different log formats into common fields and adds context such as system roles and user types.
- Detect. Attack detection patterns run on schedule or in near real time, comparing events against thresholds, value lists and anomaly baselines.
- Alert. Matches create alerts with a severity. Analysts group them into investigations.
- Investigate and respond. Forensic views let analysts trace what a user or system did before and after the alert.
- Forward. Alerts can go to a central SIEM or SOAR tool so the SOC works from one queue.
What kinds of activity can ETD flag?
The exact pattern list changes as SAP updates its content, so check the current catalog in your tenant. These are typical examples of what SAP-focused monitoring is set up to catch:
- Assignment of
SAP_ALLor other critical profiles to a dialog user. - Logons with standard users such as
SAP*orDDIC, or unlocking them. - Debugging with change in production, including the fields changed.
- Changes to Security Audit Log configuration, which attackers use to hide their tracks.
- Production client or system settings opened for changes.
- Brute-force patterns of failed logons across many users or systems.
- Calls to sensitive function modules over RFC from unusual hosts.
- Activity linked to vulnerabilities from recent security notes, through content SAP updates.
How does ETD protect user privacy?
Security monitoring means watching what employees do, which raises privacy and works council questions, especially in Europe. ETD can show users as pseudonyms. Analysts investigate with the pseudonym, and revealing the real identity needs a separate authorization, which can be limited to a small group and logged. Agree the rules with your privacy officer and employee representatives before go-live, not after the first alert.
SAP ETD vs Microsoft Sentinel or Splunk: which should you use?
It’s often both, with different jobs.
| Question | SAP ETD | Microsoft Sentinel solution for SAP or Splunk |
|---|---|---|
| Depth of SAP knowledge | Built for SAP logs and attacks | SAP content available through dedicated solutions and add-ons |
| Cross-domain correlation | Focused on SAP | Correlates SAP with identity, endpoint and cloud data |
| Who operates it | Your team, or SAP’s managed service | Your SOC |
| Common pattern | ETD detects SAP-specific threats and forwards its alerts to the central SIEM, where the SOC handles them with everything else | |
How do you get ready for ETD?
- Fix the logs first. Activate the Security Audit Log with sensible filters in every production client; SAP Note 2676384 describes recommended settings. ETD can’t detect what isn’t logged.
- Start with critical systems. Connect production ERP or S/4HANA, the systems that pay money and hold HR data.
- Agree privacy rules. Decide who can reveal pseudonyms and document it.
- Tune before scaling. Expect noise from batch users and support teams in the first weeks; adjust value lists rather than switching patterns off.
- Write response playbooks. Every high alert needs an owner and a first step, including who can lock a user or take a system offline.
Frequently asked questions
Is SAP Enterprise Threat Detection a SIEM?
Yes, it is SAP’s security information and event management tool focused on SAP landscapes. Many organizations run it alongside a general SIEM and forward ETD alerts there.
What logs does SAP ETD use?
The Security Audit Log is the most important source, together with change documents, user change logs, HANA audit trails and gateway and HTTP logs. You can add further SAP and non-SAP sources.
Does SAP offer ETD as a managed service?
Yes. With the managed service, SAP security experts monitor ETD alerts 24×7 and inform customers about real threats, which helps teams without SAP security specialists.
Can ETD hide user names from analysts?
Yes. ETD can display pseudonyms, and revealing real user identities requires a special authorization that you can restrict and log.
The bottom line
SAP Enterprise Threat Detection gives security teams eyes inside SAP: it reads SAP’s own logs and recognizes SAP attacks that general tools miss. Choose the edition that matches your skills, feed it good logs, agree privacy rules early and connect its alerts to your SOC. For the bigger picture, see what a SOC does and how SAP Basis supports security.
Sources: SAP Learning: Introducing SAP Enterprise Threat Detection; SAP: Enterprise Threat Detection product page; SAP user group session on ETD, December 2025.


