Microsoft Sentinel solution for SAP applications - functions reference

This article describes a selection of functions that are available in your workspace after you install the Microsoft Sentinel solution for SAP applications. Discover more functions by browsing in Microsoft Sentinel and loading the function code.

Find functions as follows:

• In the Azure portal, in the General > Logs page, on the Functions tab, and listed under Workspace functions.
• In the Defender portal, in the Investigation & response > Advanced hunting page, on the Functions tab, and listed under Sentinel workspace functions.

Content in this article is intended for your security teams.

Use functions in your queries instead of underlying logs or tables

We strongly recommend that you use the functions listed in this article as the subjects of their analysis whenever possible, instead of the underlying logs or tables.

These functions are intended to serve as the principal user interface to the data. They form the basis for all the built-in analytics rules and workbooks available to you out of the box. Using functions allows for changes to be made to the data infrastructure beneath the functions, without breaking user-created content.

SAPUsersAssignments

The SAPUsersAssignments function gathers data from multiple SAP data sources and creates a user-centric view of the current user master data, including the roles and profiles currently assigned.

This function summarizes the user assignments to roles and profiles, and returns the following data:

SAPUsersGetPrivileged

The SAPUsersGetPrivileged function returns a list of privileged users per client and system ID.

Users are considered privileged when they match any of the following descriptions:

• They're listed in the SAP - Privileged Users watchlist
• They're assigned to a profile listed in SAP - Sensitive Profiles watchlist
• They're added to a role listed in SAP - Sensitive Roles watchlist

Parameters:

The SAPUsersGetPrivileged function returns the following data:

SAPUsersAuthorizations

The SAPUsersAuthorizations function brings together data from several tables to produce a user-centric view of the current roles and authorizations assigned. Only users with active role and authorization assignments are returned.

Parameters:

The SAPUsersAuthorizations function returns the following data:

SAPConnectorHealth

The SAPConnectorHealth function reflects the status of the agent's and the underlying SAP system's connectivity. Based on the heartbeat log SAP_HeartBeat_CL and other health indicators, it returns the following data:

SAPConnectorOverview

The SAPConnectorOverview function shows row counts of each SAP table per System ID. It returns a list of data records per system ID, and their time generated.

Parameters:

The SAPConnectorOverview function returns the following data:

Use the following Kusto query to perform a daily trend analysis:

SAPConnectorOverview(7d)
| summarize count() by bin(TimeGenerated, 1d), SystemID_s

SAPUsersEmail

The SAPUsersEmail function allows for a performance oriented lookup of an SAP user's email address per SAP system and client, normally used to associate it with an active directory account.

The SAPUsersEmail function uses data extracted from SAP tables USR21 (User Name/Address Key Assignment) and ADR6 (E-Mail Addresses) to look for an email address. In case no email address is found, the user ID is returned instead.

This behavior ensures that SAP service accounts such as DDIC, which often aren't associated with an email addresses, are logged as pseudo AD accounts. This also opens up some UEBA features, aiding in the investigation of incidents and hunting activities.

The SAPUsersEmail function returns the following data:

SAPSystems

The SAPSystems function is used to centrally present the per-system configuration made using the SAP - Systems watchlist.

Parameters:

The SAPSystems function returns the following data:

SAPAuditLogConfiguration

The SAPAuditLogConfiguration function returns the local configuration of the SAP audit log alerts to the Log Analytics workspace enabled for Microsoft Sentinel. This configuration is used for SAP audit log-related alerts.

The SAPAuditLogConfiguration function joins the data in the SAP Dynamic Audit Log Monitor Configuration and SAP - Systems watchlists to provide a per-system configuration at a per-system-role effort.

Parameters:

The SAPAuditLogConfiguration function returns the following data:

For more information, see Available watchlists.

SAPAuditLogAnomalies

The SAPAuditLogAnomalies function uses Microsoft Sentinel's underlying Kusto database's built-in machine learning capabilities to help detect anomalous events observed on the SAP audit log.

The SAPAuditLogAnomalies function was developed for the SAP - (Experimental) Dynamic Anomaly based Audit Log Monitor Alerts analytics rule. While its original design is to alert on recent anomalies, it can also help to highlight historical anomalies. For more information, see Sample uses.

The SAPAuditLogAnomalies function learns the slice of the history defined by the different input parameters, at the following levels:

• User
• Network attributes
• System
• Seasonality
• Activity levels

The SAPAuditLogAnomalies function then judges events occurring within the last DetectingTime timespan according to what it learned, applying thresholds and other configurable exclusion criteria obtained from the SAP audit log configuration watchlist.

Once a sliding window of user activity is deemed anomalous, a second query returns the entire user activity as evidence supporting the decision.

Parameters:

The SAPAuditLogAnomalies function returns the following data:

Recommendations:

As with any machine learning solution, the SAPAuditLogAnomalies function performs better with time, and can be adjusted as needed as time goes on.

We recommend restricting the size of the learned database to be under 100 million records using the many available input parameters.

Sample uses include:

• To search for anomalies for events of high severity that occurred within the past hour on production systems for event types that are marked as AnomaliesOnly in the SAP_Dynamic_Audit_Log_Monitor_Configuration watchlist, run:

  SAPAuditLogAnomalies(LearningTime = 14d, DetectingTime=1h, SelectedSystemRoles= dynamic(["Production"]), 
  SelectedSeverities= dynamic(["High"]), SelectedRuleTypes= dynamic(["AnomaliesOnly"]))
  

• To search for all anomalies in the last 14 days in the BIP system, run:

  SAPAuditLogAnomalies(LearningTime = 14d, DetectingTime=0h, SelectedSystems= dynamic(["BIP"]))
  

For more information, see Built-in SAP analytics rules for monitoring the SAP audit log and Anomaly detection on the SAP audit log using the Microsoft Sentinel for SAP solution (blog).

SAPAuditLogConfigRecommend

The SAPAuditLogConfigRecommend is a helper function designed to offer recommendations for the configuration of the SAP - Dynamic Anomaly based Audit Log Monitor Alerts (PREVIEW) analytics rule.

For more information, see Monitor the SAP audit log.

SAPUsersGetVIP

The Microsoft Sentinel solution for SAP applications uses a concept of central user tagging and explicit exclusions, designed to help you lower false positives with minimal effort.

Use the SAPUsersGetVIP function to exclude users from triggering alerts by specifying SAP user roles, SAP user functions, or tags that represent those users. For more information, see Handle false positives in Microsoft Sentinel.

Tags specified as input for the SAPUsersGetVIP function exclude all users with a tag listed in the SAP_User_Config watchlist. The same functionality is extended to work with wildcards, allowing you to assign a single tag to a group of users with the same naming syntax.

1. Tag users in the SAP_User_Config watchlist as follows:

   • Add multiple tags to each user in the SAP_User_Config watchlist, as needed to cover various scenarios. Each alert rule has its own relevant tags, if any, and you can add custom tags as needed.

   • Use an asterisk (*) as a wildcard to include users with a specific naming syntax template.

2. Add the SAPUsersGetVIP function in your analytics rules to request the lists of users you've defined to be excluded from alerts. In the function call, add an array with the tags, SAP roles, and SAP profiles that you'd like to exclude.

For example, use the following KQL query in your analytics rule to exclude any users configured with the RunObsoleteProgOK tag in the SAP_User_Config watchlist, or any users with the sample SAP_BASIS_ADMIN_ROLE role or the sample SAP_ADMIN_PROFILE profile.

When copying this sample function call, replace SAP_BASIS_ADMIN_ROLE role and SAP_ADMIN_PROFILE profile with your own SAP roles or profiles as needed.

For example:

// Execution of Obsolete/Insecure Program
let ObsoletePrograms = _GetWatchlist("SAP - Obsolete Programs");
// here you can exclude system users which are OK to run obsolete/ sensitive programs
// by adding those users in the SAP_User_Config watchlist with a tag of 'RunObsoleteProgOK'
// can also specify SAP roles or SAP profiles that group the users you would like to exclude
let excludeUsersTagsRolesProfiles= dynamic(["RunObsoleteProgOK","SAP_BASIS_ADMIN_ROLE", "SAP_ADMIN_PROFILE"]);
let excludedUsers= SAPUsersGetVIP(SearchForTags= excludeUsersTagsRolesProfiles)| summarize by User2Exclude=SAPUser;
// Query logic
SAPAuditLog
| where MessageID == 'AUW'
| where ABAPProgramName in (ObsoletePrograms) // The program is obsolete
| join kind=leftantisemi excludedUsers on $left.User == $right.User2Exclude

The SAPUsersGetVIP function is commonly used in Deterministic and Anomalous Audit Log Monitor alerts. Associate a tag with an SAP audit log message ID, or extend the rule template to a custom rule that matches your organization's needs.

Parameters:

The SAPUsersGetVIP function returns the following output:

SAPUsersHeader

The SAPUsersHeader function is designed to provide a high-level view of the SAP user. It uses data extracted from both the SAP user master data tables and recent activity on the SAP audit log to gather email and IP addresses. It then returns last known email and IP addresses along with primary email and IP addresses.

Parameters:

For example:

SelectedSystemRoles:dynamic = dynamic(["All System Roles"]) SelectedSystems:dynamic = dynamic(["All Systems"]) SelectedUsers:dynamic = dynamic(["All Users"]) SelectedUser:string = "All Users"

The SAPUsersHeader function returns the following output:

Related content

For more information, see:

• Functions in Azure Monitor log queries
• Log and table reference for the Microsoft Sentinel solution for SAP applications