Collecting logs from Siemens SIMATIC PCS 7 and sending them to Graylog could be a complex task because of the unique combination of the log source and the desired destination. This post seeks to explain how to forward log data from SIMATIC PCS 7 to Graylog by incorporating the NXLog log collection tool.
Siemens SIMATIC PCS 7 is a distributed control system (DCS) solution that uses many Siemens hardware components supported and configured by PCS 7 software tools. Deployments usually consist of Engineering stations (ES), Operating stations (OS), and Automation stations (AS). The PCS 7 AS features the Siemens SIMATIC S7-400 series central processing unit, designed to automate plants requiring many I/O signals and control loops. SIMATIC PCS 7 is commonly used for automation tasks in various industrial sectors such as chemicals, petrochemicals, water treatment, pharmaceuticals, and power generation.
SCADA systems and Siemens have a couple of things in common: they employ a variety of network protocols to facilitate communication between various types of nodes (physical computers, CPUs, distributed I/Os, and field devices) and SCADA for storing data. Consequently, both solutions are firmly integrated within corporate networks where such nodes are typically deployed.
SIMATIC PCS 7 produces a wide variety of operational logs. Some are sent to Windows Event Log, but most are stored as flat files.
SIMATIC PCS 7 controls systems that are of significant financial and security importance. In mission-critical settings, the timely collection and processing of SIMATIC PCS 7 logs is crucial to the reliability and security of the systems it controls. 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. A brief interruption of normal operations could result in catastrophic consequences.
NXLog Enterprise Edition is a lightweight, modular log collection tool capable of tackling the most demanding cases log collection may pose. Its features enable it to parse, filter, process, aggregate, and output logs in any structured data format that a SIEM might require. Given its perfect balance of functionality and performance, it is the best choice for collecting and processing SIMATIC PCS 7 logs.
- Collecting SIMATIC PCS 7 logs from Windows Event Log
Many applications send their logs directly to Windows Event Log, the preferred logging facility on the Windows platform. SIMATIC PCS 7 sends its PC station, NET configuration, adapter operation-related information, and information about various other services to Windows Event Log.
- Collecting SIMATIC PCS 7 logs from file
File-based PCS7 logs include WinCC system diagnostics logs, SQL Server logs of WinCC, OS project logs, AS project logs, Multi-project logs, and Batch logs coming from Automation, Engineering, and Operator stations.
The easiest way to collect and normalize Siemens SIMATIC PCS 7 log data 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 SIMATIC PCS 7, see the Siemens SIMATIC PCS 7 integration guide.
The above mentioned log sources, and the features NXLog provides all play an important role when normalizing logs in order to be accepted by Graylog.
Graylog is a popular open source log collection tool that supports centralized log collection, data visualization, searching, and analysis. With its wide range of features, Graylog allows your security team to more effectively monitor the security of your IT infrastructure and to swiftly identify and act on security incidents.
To enable logs to be accepted by Graylog, from NXLog, you must first set up your appliance with the appropriate input source, in the Graylog web interface. This is done simply by navigating to system and then inputs. Here, you can establish if the input source is via UDP or TCP. However, if choosing to send logs over TLS (Transport Layer Security), you must configure your TLS certification file as well as your TLS private key file.
- Log sources
Setting up a generic log source in Graylog is important if you wish to send logs from a source that is not among Graylog’s list of predefined log sources. This can be achieved by sending logs to Graylog using GELF (Graylog Extended Log Format).
Forwarding logs to Graylog with NXlog is straightforward and can be accomplished by following simple configuration steps.