Skip to content

Commit 9c9fc92

Browse files
Merge pull request #311543 from MartinPankraz/add-agentless-tooling-ref
tooling add
2 parents 9c43850 + 06dd0d1 commit 9c9fc92

2 files changed

Lines changed: 13 additions & 4 deletions

File tree

articles/sentinel/sap/collect-sap-hana-audit-logs.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,16 +15,15 @@ ms.collection: usx-security
1515

1616
# Collect SAP HANA audit logs in Microsoft Sentinel
1717

18-
This article explains how to collect audit logs from your SAP HANA database.
18+
This article explains how to collect audit logs from your SAP HANA database in customer managed environments.
1919

2020
Content in this article is intended for your **security**, **infrastructure**, and **SAP BASIS** teams.
2121

2222
> [!IMPORTANT]
2323
> Microsoft Sentinel SAP HANA support 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.
2424
25-
> [!NOTE]
26-
> This article is relevant only for the data connector agent, and isn't relevant for the [SAP agentless data connector](deployment-overview.md#data-connector).
27-
>
25+
> [!IMPORTANT]
26+
> For environments managed by SAP such as SAP RISE (S/4HANA Cloud, private edition), SAP HANA database audit logs are collected by SAP using the service **SAP LogServ** only. It integrates with Microsoft Sentinel for SAP applications natively re-using the built-in analytic rules. Learn more from the [Blog Series: SAP LogServ Integration with Microsoft Sentinel](https://community.sap.com/t5/enterprise-resource-planning-blog-posts-by-members/ultimate-blog-series-sap-logserv-integration-with-microsoft-sentinel/ba-p/14126401)
2827
2928
## Prerequisites
3029

articles/sentinel/sap/deploy-data-connector-agent-container.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -374,6 +374,16 @@ At this stage, the system's **Health** status is **Pending**. If the agent is up
374374
> [!IMPORTANT]
375375
> There may be some wait time on initial connect. Find more details to verify the connector [here](/azure/sentinel/create-codeless-connector#verify-the-codeless-connector).
376376
377+
## Mass-Onboard SAP systems at scale
378+
379+
To onboard SAP systems to the Sentinel Solution for SAP applications at scale, API and CLI based approaches are recommended. Get started with [this script library](https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/SAP/Tools/IntegrationSuite).
380+
381+
## Rotate the BTP client secret
382+
383+
We recommend that you periodically rotate the BTP subaccount client secrets used by the data connector. For an automated, platform-based approach, see our [Automatic SAP BTP trust store certificate renewal with Azure Key Vault – or how to stop thinking about expiry dates once and for all](https://community.sap.com/t5/technology-blogs-by-members/automatic-sap-btp-trust-store-certificate-renewal-with-azure-key-vault-or/ba-p/13565138) (SAP blog).
384+
385+
This [script library](https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/SAP/Tools/IntegrationSuite) demonstrates the automatic process of updating an existing data connector with a new secret.
386+
377387
## Customize data connector behavior (optional)
378388
379389
If you have an SAP agentless data connector for Microsoft Sentinel, you can use the SAP Integration Suite to customize how the agentless data connector ingests data from your SAP system into Microsoft Sentinel.

0 commit comments

Comments
 (0)