SolMan-SIEM integration lets SAP Solution Manager parse and filter SAP log events, then forward only structured alerts to SIEM platforms such as Splunk. This avoids ingesting raw logs, speeds deployment and reduces the rules needed to interpret SAP event data, giving centralized monitoring and cross-platform correlation.
Executive Summary
SAP Solution Manager detects Indicators of Compromise in SAP logs and manages the alerts. Because it collects data from one source for all SAP systems and enriches it, forwarding alerts to a SIEM is faster and cheaper than connecting every log directly. The most common method uses OS commands that write alerts to external files the SIEM ingests.
Key Takeaways
- Solution Manager monitors SAP logs in real time and triggers alerts for specific Indicators of Compromise (IOCs).
- Data collection uses existing RFC connections and Diagnostics Agents, which work in SAP and non-SAP systems.
- Direct SIEM monitoring needs every data source in every system connected separately, plus rules for every event.
- Solution Manager filters and enriches events first, so SIEM platforms avoid ingesting raw logs.
- The most common integration writes alerts to external files with OS commands.
- SolMan is most often used for application-level monitoring alongside an existing SIEM.
What does SAP Solution Manager monitor?
SAP Solution Manager monitors real-time event information in SAP logs to automatically detect and trigger alerts for specific Indicators of Compromise (IOCs). This includes events written to the security audit log, system log, gateway server log, change document log, HTTP log, transaction log, SAProuter log, Java security log and the HANA audit log. Alerts are managed in the Alert Inbox or the System Monitoring app of SAP Solution Manager and automatic email and SMS notifications are triggered for critical incidents. Alerts are integrated with Guided Procedures to support an end-to-end process for incident detection and response within Solution Manager.
Can Solution Manager act as a SIEM?
The data collection for event monitoring using Solution Manager is performed using existing RFC connections and Diagnostics Agents installed in managed systems. Since Diagnostics Agents can be installed in both SAP and non-SAP systems and components, Solution Manager can perform many of the functions of a Security Information and Event Management (SIEM) system. SolMan can monitor across the technology stack including database, operating system, and application layers, as well as network components such as routers, switches and firewalls. These areas are often monitored by organizations using existing SIEM platforms. Therefore, SolMan is more commonly used for application-level monitoring.
What are the drawbacks of monitoring SAP directly from a SIEM?
SIEM platforms support direct monitoring of SAP log files, tables and other data sources. However, there are several drawbacks with this approach. One of the drawbacks is that each data source within every target system must be connected separately to SIEM platforms. This increases deployment times and complexities. Once connected, rules and patterns must be defined in the platforms for every possible event. Also, since SIEM platforms are ingesting raw logs, the cost of monitoring and storing mammoth-sized logs for multiple SAP systems can be prohibitive, especially for large landscapes.
How does Solution Manager overcome these drawbacks?
SAP Solution Manager overcomes these drawbacks by parsing log files and tables and filtering events before forwarding alerts to SIEM platforms. This enables the platforms to avoid ingesting raw logs to monitor SAP event information. Since the event data forwarded to SIEM platforms is derived from a single source for all SAP systems in a landscape, deployment is also faster and less complex. Finally, Solution Manager structures and enriches the event data before it reaches SIEM platforms to reduce the need to develop rules and patterns to interpret SAP event information.
How does Solution Manager integrate with SIEM platforms?
Solution Manager can integrate with SIEM platforms through several ways. The most common is using OS commands that are called by SolMan to write event data to external files that are ingested by SIEM solutions. Alerts are written to external files as soon as they are triggered by SolMan. Alert fields can include the alert name, description, priority, date, time, SAP System ID, and other areas.
This process integrates alerts for IOCs and other security risks detected by SolMan for SAP applications with SIEM systems for centralized monitoring and cross-platform correlation. The example below is for Splunk Enterprise. Click on the images below to enlarge.
Frequently Asked Questions
How does SolMan send alerts to a SIEM?
The most common method uses OS commands called by SolMan to write event data to external files that the SIEM ingests as soon as alerts are triggered.
Why not connect SAP logs directly to the SIEM?
Each data source in every system must be connected separately, rules must be defined for every event, and storing raw logs can be prohibitively costly.
Which SAP logs does Solution Manager monitor?
The security audit, system, gateway server, change document, HTTP, transaction, SAProuter and Java security logs, plus the HANA audit log.
What fields can an alert include?
Alert name, description, priority, date, time and SAP System ID, among others.