Skip to content

Commit c3971b9

Browse files
committed
Adding risky configuration parameters
1 parent 4fd8fff commit c3971b9

File tree

3 files changed

+91
-12
lines changed

3 files changed

+91
-12
lines changed

articles/sentinel/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -986,6 +986,8 @@
986986
href: sap/sap-solution-security-content.md
987987
- name: SAP audit log workbook
988988
href: sap/sap-audit-log-workbook.md
989+
- name: SAP risky configuration paramters
990+
href: sap/sap-risky-configuration-parameters.md
989991
- name: Kickstart script reference
990992
href: sap/reference-kickstart.md
991993
- name: Container update script reference
Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
---
2+
title: Microsoft Sentinel solution for SAP® applications - monitored parameters to detect risky configuration manipulation
3+
description: Learn about the security parameters in the SAP system that the Microsoft Sentinel solution for SAP® applications monitors as part of the risky configuration manipulation feature.
4+
author: limwainstein
5+
ms.author: lwainstein
6+
ms.topic: reference
7+
ms.date: 03/26/2023
8+
---
9+
10+
# Microsoft Sentinel solution for SAP® applications: security content reference
11+
12+
This article details the security parameters in the SAP system that the Microsoft Sentinel solution for SAP® applications monitors as part of the [risky configuration manipulation feature](sap-solution-security-content.md#risky-configuration-manipulation).
13+
14+
|Parameter |Description |Security value/considerations |
15+
|---------|---------|---------|
16+
|gw/accept_remote_trace_level |Controls whether or not the Central Process Integration (CPI) and Remote Function Call (RFC) subsystems adopt the remote trace level. When this parameter is set to 1, remote trace levels are accepted and adopted by the CPI and RFC subsystems. When set to 0, remote trace levels are not accepted and the local trace level is used instead.<br><br>The trace level is a setting that determines the level of detail recorded in the system log for a specific program or process. When remote trace levels are adopted, this means that the trace level setting for a program or process can be set from a remote system instead of only from the local system. This can be useful in situations where remote debugging or troubleshooting is required. | |
17+
|login/password_change_for_SSO |Controls how password changes are enforced in Single Sign-On (SSO) situations. |High, because enforcing password changes can help prevent unauthorized access to the system by an attackers who may have obtained valid credentials through phishing or other means. |
18+
|icm/accept_remote_trace_level |Determines whether the Internet Communication Manager (ICM) accepts remote trace level changes from external systems. |Medium, because allowing remote trace level changes can provide valuable diagnostic information to attackers and potentially compromise system security. |
19+
|rdisp/gui_auto_logout |Specifies the maximum idle time for SAP GUI connections before automatically logging out the user. | High, because automatically logging out inactive users can help prevent unauthorized access to the system by attackers who may have gained access to a user's workstation. |
20+
|rsau/enable |Controls whether the Security Audit log is enabled. |High, because the Security Audit log can provide valuable information for detecting and investigating security incidents. |
21+
|login/min_password_diff |Specifies the minimum number of characters that must differ between the old and new password when users change their passwords. |High, because requiring a minimum number of character differences can help prevent users from choosing weak passwords that can easily be guessed. |
22+
|login/min_password_digits |Sets the minimum number of digits required in a password for a user. |High, because the parameter increases the complexity of passwords and makes them harder to guess or crack. |
23+
|login/ticket_only_by_https |This parameter controls whether authentication tickets are only sent via HTTPS or can be sent via HTTP as well. |High, because using HTTPS for ticket transmission encrypts the data in transit, making it more secure. |
24+
|auth/rfc_authority_check |Controls whether authority checks are performed for RFCs. |High, because enabling this parameter helps prevent unauthorized access to sensitive data and functions via RFCs. |
25+
|gw/acl_mode |Sets the mode for the access control list (ACL) file used by the SAP gateway. |High, because the parameter controls access to the gateway and helps prevent unauthorized access to the SAP system. |
26+
|gw/logging |Controls the logging settings for the SAP gateway. |High, because this parameter can be used to monitor and detect suspicious activity or potential security breaches. |
27+
|login/fails_to_session_end |Sets the number of invalid login attempts allowed before the user's session is terminated. |High, because the parameter helps prevent brute-force attacks on user accounts. |
28+
|wdisp/ssl_encrypt |Sets the mode for SSL re-encryption of HTTP requests. |High, because this parameter ensures that data transmitted over HTTP is encrypted, which helps prevent eavesdropping and data tampering. |
29+
|login/no_automatic_user_sapstar |Controls the automatic login of the SAP* user. |High, because this parameter helps prevent unauthorized access to the SAP system via the default SAP* account. |
30+
|rsau/max_diskspace/local |Defines the maximum amount of disk space that can be used for local storage of audit logs. This is a security parameter because it helps to prevent the filling up of disk space and ensures that audit logs are available for investigation. | |
31+
|snc/extid_login_diag |Enables or disables the logging of external ID in Secure Network Communication (SNC) logon errors. This is a security parameter because it can help identify attempts of unauthorized access to the system. | |
32+
|login/password_change_waittime |Defines the number of days a user must wait before changing their password again. This is a security parameter because it helps enforce password policies and ensure that users change their passwords periodically. | |
33+
|snc/accept_insecure_cpic |Determines whether or not the system accepts insecure SNC connections using the CPIC protocol. This is a security parameter because it controls the level of security for SNC connections. | |
34+
|snc/accept_insecure_r3int_rfc |Determines whether or not the system accepts insecure SNC connections for R/3 and RFC protocols. This is a security parameter because it controls the level of security for SNC connections. | |
35+
|snc/accept_insecure_rfc |Determines whether or not the system accepts insecure SNC connections using RFC protocols. This is a security parameter because it controls the level of security for SNC connections. | |
36+
|snc/data_protection/max |Defines the maximum level of data protection for SNC connections. This is a security parameter because it controls the level of encryption used for SNC connections. | |
37+
|rspo/auth/pagelimit |Defines the maximum number of spool requests that a user can display or delete at once. This is a security parameter because it helps to prevent denial-of-service attacks on the spool system. | |
38+
|snc/accept_insecure_gui |Determines whether or not the system accepts insecure SNC connections using the GUI. This is a security parameter because it controls the level of security for SNC connections. | |
39+
|login/accept_sso2_ticket |Enables or disables the acceptance of SSO2 tickets for logon. This is a security parameter because it controls the level of security for logon to the system. | |
40+
|login/multi_login_users |Defines whether or not multiple logon sessions are allowed for the same user. This is a security parameter because it controls the level of security for user sessions and helps prevent unauthorized access. | |
41+
|login/password_expiration_time |Specifies the maximum time interval in days for which a password is valid. When this time elapses, the user is prompted to change their password. |Setting this parameter to a lower value can improve security by ensuring that passwords are changed frequently. |
42+
|login/password_max_idle_initial |Specifies the maximum time interval in minutes for which a user can remain logged on without performing any activity. After this time elapses, the user is automatically logged off. |Setting a lower value for this parameter can improve security by ensuring that idle sessions are not left open for extended periods of time. |
43+
|login/password_history_size |Specifies the number of previous passwords that a user is not allowed to reuse. |This prevents users from repeatedly using the same passwords, which can improve security. |
44+
|snc/data_protection/use |Enables the use of SNC data protection. When enabled, SNC ensures that all data transmitted between SAP systems is encrypted and secure. | |
45+
|rsau/max_diskspace/per_day |Specifies the maximum amount of disk space in MB that can be used for audit logs per day. Setting a lower value for this parameter can help ensure that audit logs do not consume too much disk space and can be managed effectively. | |
46+
|snc/enable |Enables SNC for communication between SAP systems. |When enabled, SNC provides an extra layer of security by encrypting data transmitted between systems. |
47+
|auth/no_check_in_some_cases |Disables authorization checks in certain cases. |While this may improve performance, it can also pose a security risk by allowing users to perform actions they may not have permission for. |
48+
|auth/object_disabling_active |Disables specific authorization objects for user accounts that have been inactive for a specified period of time. |Can help improve security by reducing the number of inactive accounts with unnecessary permissions. |
49+
|login/disable_multi_gui_login |Prevents a user from being logged in to multiple GUI sessions simultaneously. |This can help improve security by ensuring that users are only logged in to one session at a time. |
50+
|login/min_password_lng |Specifies the minimum length that a password can be. |Setting a higher value for this parameter can improve security by ensuring that passwords are not easily guessed. |
51+
|rfc/reject_expired_passwd |Prevents the execution of RFCs when the user's password has expired. |Can help improve security by ensuring that only authenticated and authorized users are allowed to execute RFCs. |
52+
|rsau/max_diskspace/per_file |Sets the maximum size of an audit file that can be created by SAP system auditing. Setting a lower value helps prevent excessive growth of audit files and thus helps ensure adequate disk space. |Setting an appropriate value helps manage the size of audit files and avoid storage issues. |
53+
|login/min_password_letters |Specifies the minimum number of letters that must be included in a user's password. Setting a higher value helps increase password strength and security. |Setting an appropriate value helps enforce password policies and improve password security. |
54+
|rsau/selection_slots |Sets the number of selection slots that can be used for audit files. Setting a higher value can help to avoid overwriting of older audit files. |Helps ensure that audit files are retained for a longer period of time, which can be useful in case of any security breach. |
55+
|gw/sim_mode |This parameter sets the gateway's simulation mode. When enabled, the gateway only simulates communication with the target system, and no actual communication takes place. |Enabling this parameter can be useful for testing purposes and can help prevent any unintended changes to the target system. |
56+
|login/fails_to_user_lock |Sets the number of failed login attempts after which the user account gets locked. Setting a lower value helps prevent brute force attacks. |Helps prevent unauthorized access to the system and helps protect user accounts from being compromised. |
57+
|login/password_compliance_to_current_policy |Enforces the compliance of new passwords with the current password policy of the system. Its value should be set to `1` to enable this feature. |High. |
58+
|rfc/ext_debugging |Enables the RFC debugging mode for external RFC calls. Its value should be set to `0` to disable this feature. | |
59+
|gw/monitor |Enables monitoring of gateway connections. Its value should be set to `1` to enable this feature. | |
60+
|login/create_sso2_ticket |Enables the creation of SSO2 tickets for users. Its value should be set to `1` to enable this feature. | |
61+
|login/failed_user_auto_unlock |Enables automatic unlocking of user accounts after a failed login attempt. Its value should be set to `1` to enable this feature. | |
62+
|login/min_password_uppercase |Sets the minimum number of uppercase letters required in new passwords. Its value should be set to a positive integer. | |
63+
|login/min_password_specials |Sets the minimum number of special characters required in new passwords. Its value should be set to a positive integer. | |
64+
|snc/extid_login_rfc |Enables the use of SNC for external RFC calls. Its value should be set to `1` to enable this feature. | |
65+
|login/min_password_lowercase |Sets the minimum number of lowercase letters required in new passwords. Its value should be set to a positive integer.
66+
|login/password_downwards_compatibility |Allows passwords to be set using old hashing algorithms for backwards compatibility with older systems. Its value should be set to `0` to disable this feature. | |
67+
|snc/data_protection/min |Sets the minimum level of data protection that must be used for SNC-protected connections. Its value should be set to a positive integer. | |

articles/sentinel/sap/sap-solution-security-content.md

Lines changed: 22 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: Microsoft Sentinel solution for SAP® applications - security content reference | Microsoft Docs
2+
title: Microsoft Sentinel solution for SAP® applications - security content reference
33
description: Learn about the built-in security content provided by the Microsoft Sentinel solution for SAP® applications.
4-
author: MSFTandrelom
5-
ms.author: andrelom
4+
author: limwainstein
5+
ms.author: lwainstein
66
ms.topic: reference
7-
ms.date: 01/24/2023
7+
ms.date: 03/26/2023
88
---
99

1010
# Microsoft Sentinel solution for SAP® applications: security content reference
@@ -33,7 +33,19 @@ For more information, see [Tutorial: Visualize and monitor your data](../monitor
3333

3434
## Built-in analytics rules
3535

36-
### Built-in SAP analytics rules for monitoring the SAP audit log
36+
### Risky configuration manipulation
37+
38+
To ensure the security of the SAP system, SAP has identified security-relevant parameters that need to be monitored for changes. With the TBD rule, the Microsoft Sentinel solution for SAP® applications tracks over 52 security-related parameters in the SAP system, and triggers an alert once these parameters are changed not according to the policy.
39+
40+
To understand parameter changes in the system, the Microsoft Sentinel solution for SAP® applications uses the parameter history table, which records changes made to both static and dynamic parameters in the system every hour.
41+
42+
These parameters can have different severities for production and non-production systems, as well as different recommended values for each parameter. When a change is made to a security-related parameter, Sentinel checks to see if the change is security-related and if the value is set according to the recommended values. If the change is suspected as outside the safe zone, the Microsoft Sentinel solution for SAP® applications creates an incident detailing the change, and identifies who made the change.
43+
44+
You can also add new configurations to create alerts for specific parameters and values.
45+
46+
Review the list of parameters that this rule monitors.
47+
48+
### Monitoring the SAP audit log
3749

3850
The SAP Audit log data is used across many of the analytics rules of the Microsoft Sentinel solution for SAP® applications. Some analytics rules look for specific events on the log, while others correlate indications from several logs to produce high fidelity alerts and incidents.
3951
In addition, there are two analytics rules which are designed to accommodate the entire set of standard SAP audit log events (183 different events), and any other custom events you may choose to log using the SAP audit log.
@@ -58,7 +70,7 @@ Learn more:
5870

5971
The following tables list the built-in [analytics rules](deploy-sap-security-content.md) that are included in the Microsoft Sentinel solution for SAP® applications, deployed from the Microsoft Sentinel Solutions marketplace.
6072

61-
### Built-in SAP analytics rules for initial access
73+
### Initial access
6274

6375
| Rule name | Description | Source action | Tactics |
6476
| --------- | --------- | --------- | --------- |
@@ -71,7 +83,7 @@ The following tables list the built-in [analytics rules](deploy-sap-security-con
7183
| **SAP - Informational - Lifecycle - SAP Notes were implemented in system** | Identifies SAP Note implementation in the system. | Implement an SAP Note using SNOTE/TCI. <br><br>**Data sources**: SAPcon - Change Requests | - |
7284

7385

74-
### Built-in SAP analytics rules for data exfiltration
86+
### Data exfiltration
7587

7688
| Rule name | Description | Source action | Tactics |
7789
| --------- | --------- | --------- | --------- |
@@ -91,7 +103,7 @@ The following tables list the built-in [analytics rules](deploy-sap-security-con
91103
| **SAP - (Preview) High Volume of Potentially Sensitive Data Exported** | Identifies export of a high volume of data via files in proximity to an execution of a sensitive transaction, a sensitive program, or direct access to sensitive table. | Export high volume of data via files. <br><br>**Data sources**: SAP Security Audit Log, [SAP - Sensitive Tables](#tables), [SAP - Sensitive Transactions](#transactions), [SAP - Sensitive Programs](#programs) | Exfiltration |
92104

93105

94-
### Built-in SAP analytics rules for persistency
106+
### Persistency
95107

96108
| Rule name | Description | Source action | Tactics |
97109
| --------- | --------- | --------- | --------- |
@@ -104,9 +116,7 @@ The following tables list the built-in [analytics rules](deploy-sap-security-con
104116
| **SAP - Execution of Obsolete/Insecure Program** |Identifies the execution of an obsolete or insecure ABAP program. <br><br> Maintain obsolete programs in the [SAP - Obsolete Programs](#programs) watchlist.<br><br> **Note**: Relevant for production systems only. | Run a program directly using SE38/SA38/SE80, or by using a background job. <br><br>**Data sources**: SAPcon - Audit Log | Discovery, Command and Control |
105117
| **SAP - Multiple Password Changes by User** | Identifies multiple password changes by user. | Change user password <br><br>**Data sources**: SAPcon - Audit Log | Credential Access |
106118

107-
108-
109-
### Built-in SAP analytics rules for attempts to bypass SAP security mechanisms
119+
### Attempts to bypass SAP security mechanisms
110120

111121
| Rule name | Description | Source action | Tactics |
112122
| --------- | --------- | --------- | --------- |
@@ -126,7 +136,7 @@ The following tables list the built-in [analytics rules](deploy-sap-security-con
126136
| **SAP - Dynamic ABAP Program** | Identifies the execution of dynamic ABAP programming. For example, when ABAP code was dynamically created, changed, or deleted. <br><br> Maintain excluded transaction codes in the [SAP - Transactions for ABAP Generations](#transactions) watchlist. | Create an ABAP Report that uses ABAP program generation commands, such as INSERT REPORT, and then run the report. <br><br>**Data sources**: SAPcon - Audit Log | Discovery, Command and Control, Impact |
127137

128138

129-
### Built-in SAP analytics rules for suspicious privileges operations
139+
### Suspicious privileges operations
130140

131141
| Rule name | Description | Source action | Tactics |
132142
| --------- | --------- | --------- | --------- |

0 commit comments

Comments
 (0)