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
Copy file name to clipboardExpand all lines: articles/sap/workloads/rise-integration.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -210,15 +210,15 @@ The solution allows you to gain visibility to user activities on SAP RISE/ECS an
210
210
For SAP RISE/ECS, the Microsoft Sentinel solution must be deployed in customer's Azure subscription. All parts of the Sentinel solution are managed by customer and not by SAP. Private network connectivity from customer's vnet is required to reach the SAP landscapes managed by SAP RISE/ECS. Typically, this connection is over the established vnet peering or through alternatives described in this document.
211
211
212
212
To enable the solution, only an authorized RFC user is required and nothing needs to be installed on the SAP systems. The container-based [SAP data collection agent](/azure/sentinel/sap/deployment-overview) included with the solution can be installed either on VM or AKS/any Kubernetes environment. The collector agent uses an SAP service user to consume application log data from your SAP landscape through RFC interface leveraging standard RFC calls.
213
-
- Authentication methods supported: SAP username and password or X509/SNC certificates
213
+
- Authentication methods supported in SAP RISE: SAP username and password or X509/SNC certificates
214
214
- Only RFC based connections are possible currently with SAP RISE/ECS environments
215
215
216
216
The following data sources may not available for a SAP RISE/ECS landscape:
217
-
- Client IP address information from SAP security audit log (*)
218
-
- DB table logs (preview), spool output log (*)
219
-
- SAPControl and JAVA application server logs
220
-
- Infrastructure and operating system logs (for example VMs running SAP). All aspects of the Azure infrastructure and operation system are monitored by SAP independently
221
-
Items noted with (*) require a change request with modifications and/or parameters for which SAP needs to be contacted.
217
+
- Client IP address information from SAP security audit log (*)
218
+
- DB table logs (preview), spool output log (*)
219
+
- SAPControl and JAVA application server logs
220
+
- Infrastructure and operating system logs (for example VMs running SAP). All aspects of the Azure infrastructure and operation system are monitored by SAP independently
221
+
*(*) Items noted with (*) require a change request with modifications and/or parameters for which SAP needs to be contacted.*
222
222
223
223
For more information on Microsoft Sentinel and SAP, including a deployment guide, see [Sentinel product documentation](/azure/sentinel/sap/deployment-overview).
0 commit comments