Inside Track | Microsoft Digital
When infrastructure operations shift, security visibility must evolve with the operating model
Four years ago, we told the story of how Microsoft became Customer Zero for using Microsoft Sentinel as the SIEM for its own SAP estate, pairing a then-new product “Sentinel Solution for SAP” with our existing SOAR platform and proving out cross-correlation between SAP and the rest of the enterprise. The ambition was stated plainly at the time: an internally managed and configured SIEM that could baseline user behaviors and detect anomalies across SAP, spanning the OS and network layer, the database layer, and the application and business logic layers.
Then we moved to RISE with SAP on Azure. With that move, responsibility for instrumenting one of those layers transitioned to SAP under the RISE operating model.
The visibility challenge shared responsibility creates
In RISE with SAP, SAP operates the underlying infrastructure, operating system, and database as part of the managed service. This changes how customers obtain security telemetry from those layers and raises an important shared-responsibility question: how can the customer SOC maintain end-to-end visibility while SAP operates the platform? The layers remain relevant to security monitoring, so visibility must extend across both SAP-managed and customer-managed parts of the landscape.
What changed: SAP LogServ meets Sentinel for SAP
SAP LogServ is SAP's centralized log service for RISE-managed landscapes, carrying the security-relevant telemetry from the layers SAP now operates. Microsoft Sentinel for SAP ingests it directly, authenticated with managed identity for Azure. There is no stored secret, no rotation calendar and no bespoke connector for a future engineer to inherit and maintain. The integration is a configuration, not a project.
“RISE with SAP introduces a shared operating model in which SAP manages the infrastructure while customers remain responsible for maintaining end-to-end security oversight. The integration of SAP LogServ with Microsoft Sentinel for SAP, secured through managed identity for Azure, brings telemetry from SAP-managed layers together with application-layer signals and the wider enterprise context. Our SOC can continue using familiar detections and workflows without a separate integration or credential-management process. At Microsoft, we believe in being Customer Zero, so we are putting this approach to work in our own RISE with SAP on Azure environment.”
— Narasa Reddy Pekety, Principal Platform Lead, Microsoft Commerce Financial Platforms (CFP)
For our SOC, the practical effect is that almost nothing about the working day changed. Events from SAP-managed layers land in the same tables queried by existing analytics rules based on Microsoft’s Advanced Security Information Model (ASIM), so detections tuned before the move can continue operating after it. Analysts remain in one console rather than managing a separate SAP queue and specialist on-call rotation. Cross-correlation – the ability to examine the points where SAP meets Dynamics 365 and the rest of our IT estate – remains especially important because it preserves the context that could otherwise be lost when telemetry is distributed across operating boundaries.
“What I appreciate most is that we did not have to create a parallel operating model for SAP. We can reuse the analytics, investigation workflows, and response processes our SOC already knows, while adding the signals we were missing.”
— Satya Veera Phaneendra Bonda, Platform Engineer, Microsoft Digital
Who runs what, and where the signal comes from. An opinionated excerpt:
|
Layer |
Operated by |
Signal path into our ISOC in Microsoft Defender |
|
Application and business logic |
Microsoft |
Microsoft Sentinel for SAP, as before the move |
|
Database |
SAP, Global Cloud Operations |
SAP LogServ |
|
Operating system and infrastructure |
SAP, Global Cloud Operations |
SAP LogServ |
|
Identity, endpoint and the wider cloud estate |
Microsoft |
Existing Microsoft Defender connectors, correlated with the above |
Co-engineering, in the open
The part that matters most here is not the connector. It is a standing engineering relationship. The SAP LogServ team and the Microsoft Sentinel for SAP team work as one co-engineering group, shipping new security content on a continuous cadence: detections, analytics rules, watchlists and normalization for log sources as SAP exposes them.
“By co-engineering SAP LogServ with Microsoft Sentinel for SAP, we turn SAP-managed telemetry into security insights customers can use immediately – and continue improving together as threats and landscapes evolve.”
— Lalit Patil, EVP & CTO Global Cloud Operations, SAP
That cadence is the direct continuation of the commitment made in the original solution, that the SAP and Sentinel teams would keep expanding threat-detection capabilities and the risk scenarios the product addresses as it evolves.
“We built this as a co-engineering relationship rather than a connector handover, and that is what makes the estate legible to our perception agents. A security AI agent is only as good as the signal and the semantics it is handed. An agent reasoning over an unlabeled log stream is guessing; an agent reasoning over normalized, curated, continuously refreshed detection content is making an informed decision about what to escalate, what to correlate and what to close. Every piece of content the two teams ship raises the floor for every AI agent downstream of it.”
— Martin Pankraz, Product Manager, SAP Security, Microsoft
That work also attacks a problem we named in the first edition and never stopped working on: separating permissible activity from genuine threats, and improving alert fidelity rather than drowning analysts in false positives. Content that arrives already tuned to the layer it describes is the most direct lever we have on that ratio.
Find the latest guidance always on the running engineering blog series on the SAP community.
The foundation we need for the Agentic SOC
This work also lays the groundwork for what comes next. Project Perception, Microsoft Security’s model for multi-agent defense, relies on blue team agents that detect, triage and respond to incidents, and those agents are only as effective as the signals they can reason over. SAP LogServ and Microsoft Sentinel for SAP provide exactly that: normalized, curated telemetry from the SAP-managed layers and the application layer, correlated with the wider enterprise estate in Sentinel. With that foundation in place, blue team agents can handle incidents involving SAP with the same context as any other part of our environment, rather than treating SAP as a black box.
What comes next
We intend to do what we did in 2022. We will share the challenges and the remedies as the work proceeds, so that customers can accelerate their own implementations with what we learn rather than rediscovering it. RISE with SAP does not have to mean less security visibility, but it does mean visibility has to be designed in rather than assumed, and designed in early enough that the SOC never works a period without it.
We are running it ourselves first, as always.
Final words
We encourage all fellow RISE with SAP customers to verify their own cloud security posture, integrated SIEM practices, and choose to integrate with SAP LogServ as foundational service. Till next time.
Related reading
- The first edition of this story: “Protecting Microsoft's SAP workload with Microsoft Sentinel,” Inside Track, February 4, 2022 — www.microsoft.com/insidetrack/blog/protecting-microsofts-sap-workload-with-microsoft-sentinel/
- Microsoft Sentinel solutions for SAP | Microsoft Learn
- SAP LogServ integration with Microsoft Sentinel Solution for SAP overview | Microsoft Learn
-
Microsoft Ignite 2026 Sentinel Connector announcments | TechCommunity
Microsoft Sentinel is an industry-leading SIEM & AI-first platform powering agentic defense across the entire security ecosystem.