Microsoft Sentinel solution for SAP applications: Deployment overview

The Microsoft Sentinel agentless data connector for SAP uses the SAP Cloud Connector and SAP Integration Suite to connect to your SAP system and pull logs from it, as shown in the following image:

By using the SAP Cloud Connector, the agentless data connector profits from already existing setups and established integration processes. This means you don't have to tackle network challenges again, as the people running your SAP Cloud Connector have already gone through that process.

The agentless data connector is compatible with SAP S/4HANA Cloud, Private Edition RISE with SAP, SAP S/4HANA on-premises, and SAP ERP Central Component (ECC), ensuring continued functionality of existing security content, including detections, workbooks, and playbooks.

The agentless data connector ingests critical security logs such as the security audit log, change docs logs and user master data including user roles and authorizations.

For example, the following image shows a multi-SID SAP landscape with a split between production and nonproduction systems, including the SAP Business Technology Platform. All the systems in this image are onboarded to Microsoft Sentinel for the SAP solution.

The agent connects to your SAP system to pull logs and other data from it, then sends those logs to your Microsoft Sentinel workspace. To do this, the agent has to authenticate to your SAP system, using a user and role created specifically for this purpose.

Microsoft Sentinel supports a few options for storing your agent configuration information, including the configuration for your SAP authentication secrets. The decision of which option might depend on where you deploy your VM and which SAP authentication mechanism you use. Supported options are as follows, listed in order of preference:

• An Azure Key Vault accessed through an Azure system-assigned managed identity
• An Azure Key Vault accessed through a Microsoft Entra ID registered-application service principal
• A plaintext configuration file

You can also authenticate using SAP's Secure Network Communication (SNC) and X.509 certificates. While using SNC provides a higher level of authentication security, it might not be practical for all scenarios.

Deploying the Microsoft Sentinel solutions for SAP applications involves several steps and requires collaboration across your security and SAP BASIS teams. The following image shows the steps in deploying the Microsoft Sentinel solutions for SAP applications, with relevant teams indicated:

We recommend that you involve both teams when planning your deployment to ensure that effort is allocated and the deployment can move smoothly.

Deployment steps include:

1. Review the prerequisites for deploying the SAP agentless data connector.

2. Deploy the SAP applications solution from the content hub. This step is handled by the security team on the Azure portal.

3. Configure your SAP system for the Microsoft Sentinel solution, including configuring SAP authorizations, configuring SAP auditing, and more. We recommend that these steps be done by your SAP BASIS team, and our documentation includes references to SAP documentation. Some of the procedures in this step can be done by the SAP BASIS team before installing the solution.

4. Connect your SAP system using an agentless data connector with the SAP Cloud Connector. This step is handled by your security team on the Azure portal, using information provided by your SAP BASIS team.

5. Enable SAP detections and threat protection. This step is handled by the security team on the Azure portal.

Deploying the Microsoft Sentinel solutions for SAP applications involves several steps and requires collaboration across multiple teams, including the security, infrastructure, and SAP BASIS teams. The following image shows the steps in deploying the Microsoft Sentinel solutions for SAP applications, with relevant teams indicated:

We recommend that you involve all relevant teams when planning your deployment to ensure that effort is allocated and the deployment can move smoothly.

Deployment steps include:

1. Review the prerequisites for deploying the Microsoft Sentinel solution for SAP applications. Some prerequisites require coordination with your infrastructure or SAP BASIS teams.

2. The following steps can happen in parallel as they involve separate teams, and aren't dependent on each other:

   1. Deploy the Microsoft Sentinel solution for SAP applications from the content hub. Make sure that you install the correct solution for your environment. This step is handled by the security team on the Azure portal.

   2. Configure your SAP system for the Microsoft Sentinel solution, including configuring SAP authorizations, configuring SAP auditing, and more. We recommend that these steps be done by your SAP BASIS team, and our documentation includes references to SAP documentation. Some steps are also performed by the security team.

3. Connect your SAP system by deploying a containerized data connector agent. This step requires coordination between your security, infrastructure, and SAP BASIS teams.

4. Enable SAP detections and threat protection. This step is handled by the security team on the Azure portal.

Extra options include:

• Collect SAP HANA audit logs
• Deploy an SAP data connector agent manually

Stop SAP data collection

If you're using the data connector agent and need to stop Microsoft Sentinel from collecting your SAP data, stop log ingestion and disable the connector. Then remove the extra user role and any optional CRs installed on your SAP system.

For more information, see Stop SAP data collection.