You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After you [deploy the SAP solution](sap/deployment-overview.md), you want to ensure proper functioning and performance of your SAP systems, and keep track of your system health, connectivity, and performance. This article describes how you can check the connectivity health manually on the data connector page and use a dedicated alert rule template to monitor the health of your SAP systems.
17
17
18
+
:::zone pivot="connection-agent"
18
19
> [!IMPORTANT]
20
+
> Monitoring the health of your SAP systems is currently in PREVIEW. The [Azure Preview Supplemental Terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
21
+
22
+
For a video demonstration of the procedures in this article, watch the following video:
> Monitoring the health of your SAP systems is currently in PREVIEW. The [Azure Preview Supplemental Terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
24
31
>
25
-
>:::zone pivot="connection-agentless"
26
32
> Microsoft Sentinel's **Agentless solution** is in limited preview as a prereleased product, which may be substantially modified before it’s commercially released. Microsoft makes no warranties expressed or implied, with respect to the information provided here. Access to the **Agentless solution** also [requires registration](https://aka.ms/SentinelSAPAgentlessSignUp) and is only available to approved customers and partners during the preview period. For more information, see [Microsoft Sentinel for SAP goes agentless ](https://community.sap.com/t5/enterprise-resource-planning-blogs-by-members/microsoft-sentinel-for-sap-goes-agentless/ba-p/13960238).
27
-
> :::zone-end
28
-
29
-
:::zone pivot="connection-agent"
30
-
31
-
For a video demonstration of the procedures in this article, watch the following video:
For the Microsoft Sentinel solution for SAP applications to operate correctly, you must first get your SAP data into Microsoft Sentinel. Do this by either deploying the Microsoft Sentinel SAP data connector agent, or by connecting the Microsoft Sentinel agentless data connector for SAP. Select the option at the top of the page that matches your environment.
22
22
23
-
This article describes the third step in deploying the Microsoft Sentinel solution for SAP applications. Make sure to perform the steps in this article in the order that they're presented.
23
+
This article describes the third step in deploying one of the Microsoft Sentinel solutions for SAP applications.
24
+
25
+
:::zone pivot="connection-agent"
24
26
25
27
:::image type="content" source="media/deployment-steps/deploy-data-connector.png" alt-text="Diagram of the SAP solution deployment flow, highlighting the Connect your SAP system step." border="false" :::
26
28
27
-
Content in this article is relevant for your **security**, **infrastructure**, and **SAP BASIS** teams.
29
+
Content in this article is relevant for your **security**, **infrastructure**, and **SAP BASIS** teams. Make sure to perform the steps in this article in the order that they're presented.
30
+
31
+
:::zone-end
32
+
33
+
:::zone pivot="connection-agentless"
34
+
35
+
:::image type="content" source="media/deployment-steps/deploy-data-connector-agentless.png" alt-text="Diagram of the SAP solution deployment flow, highlighting the Connect your SAP system step." border="false" :::
36
+
37
+
Content in this article is relevant for your **security** team, using information provided by your **SAP BASIS** teams.
38
+
39
+
:::zone-end
40
+
28
41
29
42
> [!IMPORTANT]
30
43
> Microsoft Sentinel's **Agentless solution** is in limited preview as a prereleased product, which may be substantially modified before it’s commercially released. Microsoft makes no warranties expressed or implied, with respect to the information provided here. Access to the **Agentless solution** also [requires registration](https://aka.ms/SentinelSAPAgentlessSignUp) and is only available to approved customers and partners during the preview period. For more information, see [Microsoft Sentinel for SAP goes agentless ](https://community.sap.com/t5/enterprise-resource-planning-blogs-by-members/microsoft-sentinel-for-sap-goes-agentless/ba-p/13960238).
@@ -35,22 +48,27 @@ Before you connect your SAP system to Microsoft Sentinel:
35
48
36
49
- Make sure that all of the deployment prerequisites are in place. For more information, see [Prerequisites for deploying Microsoft Sentinel solution for SAP applications](prerequisites-for-deploying-sap-continuous-threat-monitoring.md).
37
50
38
-
- Make sure that you have the Microsoft Sentinel solution for **SAP applications** or the **SAP Agentless** solution [installed in your Microsoft Sentinel workspace](deploy-sap-security-content.md).
51
+
:::zone pivot="connection-agent"
39
52
40
-
- Make sure that your SAP system is fully [prepared for the deployment](preparing-sap.md).
53
+
- Make sure that you have the Microsoft Sentinel solution for **SAP applications**[installed in your Microsoft Sentinel workspace](deploy-sap-security-content.md)
41
54
42
-
:::zone pivot="connection-agent"
43
-
If you're deploying the data connector agent to communicate with Microsoft Sentinel over SNC, make sure that you completed [Configure your system to use SNC for secure connections](preparing-sap.md#configure-your-system-to-use-snc-for-secure-connections).
55
+
- Make sure that your SAP system is fully [prepared for the deployment](preparing-sap.md).
44
56
45
-
:::zone-end
57
+
- If you're deploying the data connector agent to communicate with Microsoft Sentinel over SNC, make sure that you completed [Configure your system to use SNC for secure connections](preparing-sap.md#configure-your-system-to-use-snc-for-secure-connections).
46
58
47
-
:::zone pivot="connection-agentless"
48
-
If you're deploying the agentless data connector, make sure your DCR is configured as described in [Install the solution from the content hub](deploy-sap-security-content.md#install-the-solution-from-the-content-hub).
59
+
:::zone-end
49
60
50
-
:::zone-end
61
+
:::zone pivot="connection-agentless"
51
62
52
-
:::zone pivot="connection-agent"
63
+
- Make sure that you have the Microsoft Sentinel **SAP Agentless** solution [installed in your Microsoft Sentinel workspace](deploy-sap-security-content.md)
64
+
65
+
- Make sure that your SAP system is fully [prepared for the deployment](preparing-sap.md).
53
66
67
+
- Make sure your DCR is configured as described in [Install the solution from the content hub](deploy-sap-security-content.md#install-the-solution-from-the-content-hub).
68
+
69
+
:::zone-end
70
+
71
+
:::zone pivot="connection-agent"
54
72
55
73
## Watch a demo video
56
74
@@ -324,8 +342,6 @@ The system configuration you defined is deployed into the Azure key vault you de
324
342
325
343
At this stage, the system's **Health** status is **Pending**. If the agent is updated successfully, it pulls the configuration from Azure Key vault, and the status changes to **System healthy**. This update can take up to 10 minutes.
326
344
327
-
The deployment procedure generates a **systemconfig.json** file that contains the configuration details for the SAP data connector agent. For more information, see [SAP data connector agent configuration file](deployment-overview.md#sap-data-connector-agent-configuration-file).
Copy file name to clipboardExpand all lines: articles/sentinel/sap/deployment-overview.md
+31-17Lines changed: 31 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,20 +48,11 @@ Microsoft Sentinel supports a few options for storing your agent configuration i
48
48
49
49
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.
50
50
51
-
### SAP data connector agent configuration file
52
-
53
-
When using the data connector agent, the deployment procedure generates a **systemconfig.json** file that contains the configuration details for the SAP data connector agent. The file is located in the `/sapcon-app/sapcon/config/system` directory on your VM. You can use this file to update the configuration of your SAP data connector agent.
54
-
55
-
Earlier versions of the deployment script, released before June 2023, generated a **systemconfig.ini** file instead. For more information, see:
### [Agentless data connector (limited preview)](#tab/agentless)
61
52
62
53
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:
63
54
64
-
:::image type="content" source="media/deployment-overview/agentless-connector.png" alt-text="Diagram that shows the Microsoft Sentinel agentless data connector in a SAP environment.":::
55
+
:::image type="content" source="media/deployment-overview/agentless-connector.png" alt-text="Diagram that shows the Microsoft Sentinel agentless data connector in a SAP environment." border="false":::
65
56
66
57
By using the SAP Cloud Connector, the **Agentless solution** 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.
67
58
@@ -88,6 +79,10 @@ For more information, see [Microsoft Sentinel solution for SAP applications: sec
88
79
89
80
## Deployment flow and personas
90
81
82
+
Deploying the Microsoft Sentinel solutions for SAP applications involves several steps and requires collaboration across multiple teams, differing depending on whether you're using a data connector agent or the agentless solution. Select one of the following tabs to learn more:
83
+
84
+
### [Containerized data connector agent](#tab/agent)
85
+
91
86
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:
92
87
93
88
:::image type="content" source="media/deployment-steps/full-flow.png" alt-text="Diagram showing the full steps in the Microsoft Sentinel solution for SAP applications deployment flow." border="false":::
@@ -96,20 +91,15 @@ We recommend that you involve all relevant teams when planning your deployment t
96
91
97
92
**Deployment steps include**:
98
93
99
-
1.[Review the prerequisites for deploying Microsoft Sentinel solution for SAP applications](prerequisites-for-deploying-sap-continuous-threat-monitoring.md). Some prerequisites require coordination with your infrastructure or SAP BASIS teams.
94
+
1.[Review the prerequisites for deploying the Microsoft Sentinel solution for SAP applications](prerequisites-for-deploying-sap-continuous-threat-monitoring.md). Some prerequisites require coordination with your infrastructure or SAP BASIS teams.
100
95
101
96
1. The following steps can happen in parallel as they involve separate teams, and aren't dependent on each other:
102
97
103
98
1.[Deploy the Microsoft Sentinel solution for SAP applications from the content hub](deploy-sap-security-content.md). Make sure that you install the correct solution for your environment. This step is handled by the security team on the Azure portal.
104
99
105
100
1.[Configure your SAP system for the Microsoft Sentinel solution](preparing-sap.md), 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.
106
101
107
-
1.[Connect your SAP system](deploy-data-connector-agent-container.md) using one of the following methods, depending on the Microsoft Sentinel solution you deployed:
108
-
109
-
- Deploy a containerized data connector agent
110
-
- Use an agentless data connector with the SAP Cloud Connetor (limited preview)
111
-
112
-
This step requires coordination between your security, infrastructure, and SAP BASIS teams.
102
+
1.[Connect your SAP system](deploy-data-connector-agent-container.md) by deploying a containerized data connector agent. This step requires coordination between your security, infrastructure, and SAP BASIS teams.
113
103
114
104
1.[Enable SAP detections and threat protection](deployment-solution-configuration.md). This step is handled by the security team on the Azure portal.
115
105
@@ -124,6 +114,30 @@ If you're using the data connector agent and need to stop Microsoft Sentinel fro
124
114
125
115
For more information, see [Stop SAP data collection](stop-collection.md).
126
116
117
+
### [Agentless data connector (limited preview)](#tab/agentless)
118
+
119
+
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:
120
+
121
+
:::image type="content" source="media/deployment-steps/full-flow-agentless.png" alt-text="Diagram showing the full steps in the Microsoft Sentinel agentless solution for SAP applications deployment flow." border="false":::
122
+
123
+
We recommend that you involve both teams when planning your deployment to ensure that effort is allocated and the deployment can move smoothly.
124
+
125
+
**Deployment steps include**:
126
+
127
+
1.[Review the prerequisites for deploying the SAP agentless solution](prerequisites-for-deploying-sap-continuous-threat-monitoring.md).
128
+
129
+
1. The following steps can happen in parallel as they involve separate teams, and aren't dependent on each other:
130
+
131
+
1.[Deploy the SAP agentless solution from the content hub](deploy-sap-security-content.md). This step is handled by the security team on the Azure portal.
132
+
133
+
1.[Configure your SAP system for the Microsoft Sentinel solution](preparing-sap.md), 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.
134
+
135
+
1.[Connect your SAP system](deploy-data-connector-agent-container.md) 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.
136
+
137
+
1.[Enable SAP detections and threat protection](deployment-solution-configuration.md). This step is handled by the security team on the Azure portal.
0 commit comments