Centralised infrastructure and security monitoring in a distributed IT environment
Distributed servers, network devices and services were monitored using different tools, while security event information remained scattered across individual systems. The project included building centralised infrastructure monitoring, implementing a SIEM platform, organising alerting and creating a single point for analysing service availability and security events.
- Client name Technology company with distributed IT infrastructure
- IT, SaaS and Technology Companies
Challenge
The environment included Linux and Windows servers, network devices and services operating across several infrastructure segments. Information about their status was distributed across different systems, and some problems were detected only through manual checks or after being reported by users.
At the same time, system logs and security events remained spread across multiple independent sources, making correlation and subsequent analysis more difficult.
Distributed monitoring
There was no single view showing the status of servers, network devices, services and key infrastructure parameters.
Scattered logs
Information required for security event analysis was distributed across multiple servers and devices.
Reactive problem detection
Some problems were identified only after they began affecting users or service availability.
Solution
The environment was organised around two complementary layers: operational infrastructure monitoring and centralised security monitoring.
Zabbix was used to monitor availability, performance and technical infrastructure parameters, while Wazuh was used to centralise and analyse security-related events.
Infrastructure monitoring
Servers, network devices, services and key environment parameters were brought under centralised monitoring and alerting.
Security monitoring
Events from servers and endpoints are centralised, making it possible to analyse authentication activity, changes and selected security anomalies.
Structured alerting
Alerts were aligned with the actual impact of problems to reduce noise and identify events requiring action more quickly.
The monitoring environment was designed to allow additional servers, devices and services to be added without creating separate monitoring mechanisms for every new component.
Result
After implementation, infrastructure status and key security events can be analysed centrally. The team gained a coherent view of the environment and the ability to detect some technical and security issues earlier.
Single perspective
The status of servers, networking, services and selected security events can be analysed from centralised platforms.
Faster diagnostics
Historical metrics, alerts and events make it easier to determine when a problem began and which parts of the environment were affected.
Better security visibility
Centralised event collection makes it easier to analyse unusual logins, system changes and other signals requiring verification.
Technologies and services used
Zabbix Wazuh Linux Windows Server
Two different challenges — monitoring and security
Infrastructure monitoring and security monitoring answer different questions.
Zabbix primarily helps determine whether infrastructure is operating correctly: whether a server responds, whether a filesystem is running out of space, how storage behaves, whether a service is available and whether its parameters differ from normal levels.
Wazuh, on the other hand, focuses on security-related events — user activity, system changes, security logs and signals that may require further analysis.
Knowing that a server is running does not mean that it is secure. At the same time, detecting a security event without understanding the state of the infrastructure can make it difficult to assess its actual impact.
Centralised infrastructure monitoring
Monitoring was designed as a common observability layer for different components of the environment.
Servers
Availability, CPU, RAM, filesystems, processes, system services and other parameters depending on the role of each individual machine.
Networking
Device availability, interfaces, link utilisation and other parameters used to assess the condition of the network layer.
Services
Monitoring of selected applications, endpoints, certificates and infrastructure services provides visibility beyond the operating system itself.
An alert should lead to action
Collecting thousands of metrics alone does not improve infrastructure availability. Monitoring becomes useful when it can identify a problem that actually requires action.
An important part of the project was therefore organising alerts, thresholds and dependencies between infrastructure components.
Good monitoring should not report everything. It should report what requires attention and provide the context needed to begin troubleshooting.
Centralising security events
In a distributed environment, analysing logs without a central system becomes increasingly difficult as the number of servers grows.
Implementing Wazuh made it possible to collect events from multiple systems in one place and create a common security monitoring layer.
Depending on the system, the analysed information can include:
- successful and failed authentication attempts,
- system events,
- changes to selected files and configurations,
- endpoint security alerts,
- selected vulnerability information,
- events from applications and infrastructure services.
Monitoring Linux and Windows in one environment
The infrastructure was not technologically homogeneous. Monitoring needed to cover Linux and Windows Server systems as well as infrastructure devices.
Instead of building separate environments for each technology, the central platforms were designed to collect information from different classes of systems and present it in a consistent way.
Linux
Monitoring of resources, services, logs, authentication and selected security-related elements of Linux systems.
Windows Server
Collection of Windows system parameters and events, including information relevant to availability and security.
Infrastructure devices
Monitoring of networking and other infrastructure components extends visibility to the layers on which servers and applications depend.
Historical data makes diagnosis easier
Centralised monitoring is useful not only for responding to current alerts. Historical metrics and events are often equally important when investigating problems.
It becomes possible to determine whether increased load occurred before a failure, whether an application problem correlated with a change in storage parameters, or whether an unusual security event appeared at the same time as other anomalies in the environment.
Without history, we can see only the current state. With historical data, we can reconstruct the sequence of events and understand much more quickly what actually happened.
An environment prepared for further growth
The monitoring architecture was designed so that additional servers, services and devices can be connected to the existing platforms instead of requiring separate tools.
This allows monitoring to grow together with the infrastructure while maintaining consistent rules for alerting, data collection and event analysis.
Zabbix and Wazuh serve different purposes, but together they provide a broader view of the technical condition and security of the environment.