Collecting logs from Siemens SICAM SCC and sending them to Google Chronicle could be complex because of the unique combination of the log source and the desired destination. This post will show you how to forward log data from Siemens SICAM SCC to Google Chronicle by incorporating the NXLog log collection tool.
Siemens SICAM SCC or SICAM Station Control Center is a human-machine interface (HMI) for multiple power automation systems. Using various integrated communication drivers, SICAM SCC can communicate with SICAM PAS/PQS, SICAM RTUs, bay units, and protection devices that support IEC 61850/IEC 60870-5-104.
SICAM SCC system is scalable and offers efficient engineering for energy automation applications at utilities and industrial enterprises.
Siemens SICAM SCC produces a wide variety of logs concerning its operations. Some of those logs are available through Windows Event Log and network monitoring, but most exist as flat files.
Siemens SICAM SCC controls systems of significant financial and security importance. In mission-critical settings, the timely collection and processing of SICAM SCC logs is crucial to the reliability and security of the systems it controls. Even a brief interruption of normal operations could result in catastrophic consequences. However, the sheer diversity of log formats and data structures, and the noise that some of these logs contain, pose severe challenges to most logging software.
NXLog Enterprise Edition is a lightweight, modular log collection tool capable of tackling the most challenging cases log collection may pose. Its rich features allow it to read almost any log format and parse fields to produce structured data for further processing. It is the perfect tool for monitoring and collecting SICAM SCC logs.
- Collecting Siemens SICAM SCC logs from Windows Event Log
Many applications send their logs directly to Windows Event Log, the preferred logging facility on the Windows platform. Siemens SICAM SCC sends its diagnostic and security-related events, such as user authentication, the state of system components, record modifications, and information about various other services, to Windows Event Log. Logs can be read and collected using an Event ID related to SICAM SCC or by a given source name.
- Collecting Siemens SICAM SCC logs from file
File-based SICAM SCC logs include logs from:
Dynamic Alarm Filter Configuration trace log
Communication Connection trace log
Add-in trace log
Runtime Data Server trace log
Import/Export Wizard trace log
SICAM Global Wizard log, SICAM PAS Wizard log, SICAM IEC Wizard log
Import/Export Wizard log
- Siemens SICAM SCC Network Monitoring
NXLog can passively monitor network traffic and generate logs for most network protocols. This ability to log network communication from Siemens SICAM SCC, and integrated devices, can provide another valuable log source.
The easiest way to collect and normalize Siemens SICAM SCC logs is by deploying NXLog. With its unique capabilities, logs can be collected from literally any file in any format. Given the wide variation in format and structure of such log files, its versatility is ideal for these systems.
For more information on integrating NXLog with Siemens SICAM SCC, see the Siemens SICAM SCC integration guide.
The sources mentioned above and NXLog’s features play an important role in normalizing logs accepted by Google Chronicle.
Google Chronicle is a cloud-based service by Google for collecting and processing log data. It can accept both structured (UDM-formatted) and unstructured messages that can be searched and selected based on specific criteria, such as assets, domains, or IP addresses.
- Chronicle Partner Ingestion API
Sending logs via the Ingestion API is a direct forwarding method that is more flexible and allows Chronicle to immediately parse events as they are received. The API provides endpoints for both Unified Data Model (UDM) and unstructured log entries.
- Chronicle Forwarder Software
Sending logs via Chronicle Forwarder offers an easier initial configuration and built-in passive network capabilities. However, its disadvantage is that it requires intermediary software to be installed on the network and can only forward unstructured logs.
A central NXLog agent can act as an enhanced replacement for Chronicle Forwarder. It too can forward unstructured and UDM-formatted data, but it provides passive network monitoring as additional functionality.
For more information on configuring NXLog and sending logs to Google Chronicle, please visit the Google Chronicle integration section in the NXLog User Guide.