Wazuh is an open cybersecurity platform combining SIEM and XDR capabilities. It enables centralized log collection and analysis, threat detection, file integrity monitoring, vulnerability identification, system configuration assessment, and automated response to selected incidents.

At SLogic Group, we design, deploy, and administer Wazuh environments intended to protect servers, workstations, virtual environments, containers, cloud services, and infrastructure devices. We prepare both small installations for individual organizations and distributed clusters supporting multiple locations and large numbers of data sources.

We integrate Wazuh with existing infrastructure, identity systems, firewalls, cloud services, virtualization platforms, helpdesk systems, and automation tools. We tailor detection rules, alerts, data retention, and response procedures to the organization’s actual risk profile.

An effective SIEM system should not merely collect logs. It must distinguish important events from noise, provide threat context, and enable administrators or security teams to respond quickly.

Open SIEM and XDR platform

Wazuh in business environments

Wazuh can protect on-premises infrastructure, data centers, branches, cloud environments, and remotely operating systems. Agents installed on endpoints send security data to the central platform, while devices that do not support an agent can forward events through Syslog, APIs, or other supported mechanisms.

The platform analyzes data in near real time using decoders, detection rules, vulnerability intelligence, and threat information. Results are indexed, stored, and displayed in dashboards designed for incident analysis, Threat Hunting, compliance monitoring, and security posture assessment.

SIEM

We centralize logs, analyze events, and correlate information from multiple systems and devices.

XDR

We extend threat detection using data from endpoints, servers, cloud services, containers, and network infrastructure.

Endpoint Security

We monitor operating systems, configuration, files, processes, software, and user activity.

Vulnerability Detection

We identify vulnerable packages and applications installed on protected endpoints.

Threat Hunting

We enable searches for anomalies, indicators of compromise, and suspicious event sequences.

Compliance

We support compliance monitoring for internal policies, security standards, and regulatory requirements.

Our Wazuh expertise

We can deploy a new platform from scratch, expand an existing environment, perform a migration, optimize performance, or take over ongoing administration.

  • analysis of security requirements and data sources,
  • design of Wazuh architecture,
  • selection of resources for the server, indexer, and dashboard,
  • installation of all-in-one, single-node, and multi-node environments,
  • deployment of Wazuh Server clusters,
  • deployment of Wazuh Indexer clusters,
  • configuration of multiple dashboard instances,
  • integration with load balancers,
  • installation of Windows, Linux, and macOS agents,
  • automation of agent deployment,
  • configuration of groups and centralized agent management,
  • collection of system and application logs,
  • Syslog integration,
  • integration with firewalls, routers, and switches,
  • monitoring of VMware, Hyper-V, and Proxmox environments,
  • monitoring of Docker and other container environments,
  • integration with AWS, Azure, and Google Cloud,
  • integration with Microsoft 365 and Microsoft Graph,
  • integration with GitHub and other SaaS services,
  • configuration of File Integrity Monitoring,
  • configuration of Security Configuration Assessment,
  • deployment of Vulnerability Detection,
  • monitoring of system inventory and IT hygiene,
  • malware and rootkit detection,
  • creation of custom decoders,
  • creation and tuning of detection rules,
  • mapping events to MITRE ATT&CK,
  • configuration of Active Response,
  • integration with IOC and CDB lists,
  • integration with external Threat Intelligence,
  • configuration of email alerts and webhooks,
  • integration with Microsoft Teams, Slack, and Telegram,
  • integration with helpdesk and ITSM systems,
  • integration with third-party SIEM and SOAR platforms,
  • creation of dashboards and visualizations,
  • configuration of RBAC, LDAP, and SSO,
  • configuration of retention and index policies,
  • backup of configuration and data,
  • platform and agent upgrades,
  • cluster performance optimization,
  • security audits of Wazuh environments,
  • preparation of technical documentation and operational procedures.
Wazuh Architecture

Agents and central platform components

Wazuh architecture is based on a multi-platform agent and three main central components: Wazuh Server, Wazuh Indexer, and Wazuh Dashboard. Endpoint data is sent to the server, analyzed, indexed, and made available to administrators through the web interface.

Individual components can operate on one server or be distributed across multiple nodes. In larger environments, we use clusters that provide scalability, load balancing, and fault tolerance.

Wazuh Agent

Collects events, system information, file changes, configuration, packages, and data required for security analysis.

Wazuh Server

Analyzes received data, applies decoders and rules, manages agents, and generates alerts.

Wazuh Indexer

Indexes and stores security data, enabling fast search and analysis.

Wazuh Dashboard

Provides an interface for event analysis, platform management, reporting, and data visualization.

Filebeat

Transfers alerts and selected data from Wazuh Server to the Wazuh Indexer cluster.

Wazuh API

Enables server, agent, and configuration management as well as integration with external systems.

Deployment models

All-in-One

All components operate on one server. This model is suitable for laboratories and small environments.

Single-Node

Server, Indexer, and Dashboard operate on separate systems, providing better performance and a clear separation of roles.

Multi-Node

Multiple Server and Indexer nodes form clusters intended for environments with high event volumes.

On-Premises Environment

All central components are maintained within infrastructure controlled by the organization.

Private Cloud

We deploy the platform on virtual machines or services operating in the selected cloud environment.

Hybrid Architecture

Agents and data sources operate in multiple locations while using one shared central platform.

Designing platform performance

  • we inventory the number of endpoints and Syslog sources,
  • we estimate the daily event volume,
  • we analyze the number of alerts per second,
  • we select the data retention period,
  • we define requirements for historical searches,
  • we select the number of server nodes,
  • we select the number of indexer nodes,
  • we design shards and replicas,
  • we choose high-performance storage for indexes,
  • we separate agent traffic from cluster communication,
  • we design load balancing,
  • we define CPU, RAM, and disk utilization thresholds,
  • we monitor Listener Engine and Analysis Engine performance,
  • we plan expansion before limits are reached.

The size of a SIEM environment depends on more than the number of agents. Event volume, enabled modules, logging level, and retention period are equally important.

Wazuh Agent

Endpoint protection and visibility

Wazuh Agent operates on the protected system and sends data to the central server through an authenticated and encrypted channel. The agent is available for popular operating systems and can be configured centrally.

The agent gives Wazuh access to information that cannot be collected through the network alone, including file changes, software inventory, running processes, system configuration, local logs, and security events.

Windows

We monitor Event Log, the registry, processes, services, files, software, accounts, and security events.

Linux

We analyze Syslog, journald, auditd, packages, configuration, processes, and changes in protected directories.

macOS

We collect system events, software information, and changes to important system components.

Central Configuration

We assign agents to groups and manage shared settings from the server.

Inventory

We collect information about hardware, systems, interfaces, packages, ports, and processes.

Active Response

The agent can execute a defined response after a specific threat is detected.

Agent deployment

  • manual installation on individual systems,
  • deployment through Active Directory and GPO,
  • distribution through Microsoft Intune,
  • deployment through Ansible,
  • automation through Puppet, Chef, and SCCM,
  • preparation of packages for management systems,
  • automatic agent registration,
  • assignment of agents to the correct groups,
  • agent version control,
  • centralized upgrades,
  • monitoring disconnected agents,
  • removing inactive and duplicate entries.

Agent groups and centralized management

Agents can be grouped according to operating system, location, function, criticality, or business owner. Each group can receive a separate configuration for modules, collected logs, monitored directories, and security policies.

Production Servers

We apply more detailed rules, additional log sources, and stricter alerting.

Workstations

We monitor logins, processes, software, configuration changes, and user activity.

Infrastructure Systems

We create profiles for domain controllers, DNS servers, backup systems, databases, and management platforms.

Log Data Analysis

Centralized security log analysis

Wazuh collects data from agents, log files, Windows Event Log, Syslog, network devices, cloud service APIs, and other sources. Data is decoded, compared with rules, and enriched with additional context.

Not every event needs to generate an alert. We configure rule levels, exceptions, dependencies, and data storage so that the platform directs the team’s attention toward genuinely important events.

System Logs

We analyze events from Windows, Linux, macOS, and other supported platforms.

Application Logs

We collect data from web servers, databases, business services, and custom applications.

Syslog

We receive events from firewalls, routers, switches, storage systems, and other devices.

Windows Event Log

We monitor logins, administrative events, policies, processes, and security activity.

Auditd

We analyze Linux audit events, system calls, and privileged operations.

Event Archives

Where required, we also retain events that did not generate an alert.

Decoders and rules

Decoders extract important fields from raw messages, while rules determine whether an event should be classified as an alert. We create custom extensions for systems and applications not covered by the standard rule set.

  • log format analysis,
  • creation of parent and child decoders,
  • extraction of users, IP addresses, and hostnames,
  • recognition of event codes,
  • creation of custom rules,
  • assignment of severity levels,
  • grouping of rules by technology,
  • correlation of recurring events,
  • detection of sequences within a defined time window,
  • creation of exceptions for legitimate activity,
  • mapping to MITRE ATT&CK,
  • testing rules before production deployment.

Enabling all available rules without tuning usually creates excessive alert volume. The system should be adapted to the actual infrastructure and accepted risk level.

File Integrity Monitoring

File integrity monitoring

File Integrity Monitoring detects the creation, deletion, and modification of selected files and directories. It can also track changes to ownership, permissions, size, and cryptographic hashes.

We use FIM to protect system configuration, application files, websites, scripts, keys, and other data whose unauthorized modification could indicate an attack or an administrative error.

Configuration Files

We detect changes to service, operating system, and application settings.

Web Directories

We monitor file replacement, webshell deployment, and changes to application code.

Windows Registry

We monitor important registry keys and changes that may affect system security.

Real-Time Monitoring

For selected paths, we detect changes without waiting for the next full scan.

Who-Data

On supported systems, we identify the user and process responsible for a change.

Content Comparison

For suitable files, we retain information that helps assess the scope of a modification.

Example areas covered by FIM

  • SSH configuration files,
  • system firewall configuration,
  • user and group files,
  • web application directories,
  • administrative scripts,
  • system service files,
  • cron jobs and Windows scheduled tasks,
  • keys and certificates,
  • database configuration files,
  • security policies,
  • critical application executables,
  • selected locations containing business data.

Reducing FIM noise

  • we exclude temporary files and caches,
  • we apply file extension filters,
  • we limit monitoring of directories generating frequent changes,
  • we use different scan intervals,
  • we create exceptions for legitimate updates,
  • we account for maintenance windows,
  • we raise alert severity for the most critical files,
  • we correlate file changes with logins and processes,
  • we separate system and application changes,
  • we regularly update the list of monitored paths.
Security Configuration Assessment

Configuration and hardening assessment

Security Configuration Assessment verifies whether systems meet defined security requirements. The agent performs checks covering services, files, system settings, policies, and application parameters.

Results show passed, failed, and not-applicable controls. This allows the organization to identify weak configurations and measure progress in hardening activities.

Linux Systems

We assess service configuration, permissions, password policies, logging, and kernel parameters.

Windows Systems

We assess security policies, services, registry settings, auditing, and domain configuration.

Custom Policies

We create checks aligned with internal standards and organizational requirements.

Benchmarks

We adapt assessments to selected hardening recommendations and best practices.

Reporting

We present compliance by host, group, system, and specific control.

Remediation

We prepare recommendations and a plan for correcting detected configuration gaps.

Example configuration checks

  • minimum password length and complexity,
  • account lockout after failed logins,
  • disabled unused services,
  • SSH configuration,
  • permissions on system files,
  • audit settings,
  • event logging configuration,
  • system firewall settings,
  • protection of privileged accounts,
  • availability of required security mechanisms,
  • protocol and encryption settings,
  • disabled default and unsafe functions.

A compliance score does not replace risk analysis. Not every recommendation has the same importance for every system or organization.

Vulnerability Detection

Identifying vulnerable software

Wazuh collects information about operating systems and installed packages, then compares it with known vulnerability data. This enables administrators to determine which endpoints require updates or additional protective measures.

The vulnerability view can include the CVE identifier, severity, affected package, version, status, and available references. Data can be filtered by host, operating system, criticality, and software.

Package Inventory

The agent collects information about the system and installed software.

CVE Information

The platform identifies known vulnerabilities associated with detected package versions.

Prioritization

We group vulnerabilities by severity, system, and the importance of the protected asset.

Vulnerability Status

We monitor the appearance, persistence, and removal of detected vulnerabilities.

Dashboards

We present the most common CVEs, the most exposed hosts, and vulnerable applications.

Patch Process Integration

We forward detected issues to maintenance teams and ticketing systems.

Vulnerability management

  • we identify critical vulnerabilities,
  • we consider the business importance of the host,
  • we analyze patch availability,
  • we assess service exposure,
  • we consider exploitability,
  • we group tasks by system and application,
  • we create tickets for administrators,
  • we monitor remediation deadlines,
  • we verify that vulnerabilities disappear after updates,
  • we document accepted exceptions,
  • we report overdue critical vulnerabilities,
  • we analyze risk-level trends.

A list of CVEs is not yet an action plan. Vulnerabilities must be prioritized according to system criticality, exposure, and actual exploitability.

Malware Detection

Detecting malicious changes and activity

Wazuh uses several mechanisms to detect potential malware, including log analysis, integrity monitoring, process inspection, integration with antivirus tools, and comparison against indicators of compromise.

Suspicious Files

We detect new or modified files in locations commonly abused by attackers.

Rootcheck

We inspect selected indicators of rootkits, hidden files, and unusual system components.

Processes and Ports

We analyze running processes, connections, and unusual listening services.

IOC

We compare file hashes, domains, and IP addresses against known threat indicators.

Antivirus Integration

We collect and analyze events from endpoint protection systems.

Active Response

After a confirmed event, we can execute a controlled response on the endpoint.

Example threat indicators

  • creation of a suspicious executable file,
  • modification of a system file,
  • execution of a process from a temporary directory,
  • connection to a domain present on an IOC list,
  • detection of a malicious file hash,
  • creation of an unusual scheduled task,
  • modification of an autostart mechanism,
  • disabling of a security tool,
  • attempt to hide a process or file,
  • unusual activity by a privileged account,
  • repeated failed command execution,
  • launch of a shell in an unexpected context.
MITRE ATT&CK

Classifying attacker behavior

Wazuh rules can be mapped to MITRE ATT&CK tactics and techniques. This gives the security team not only a description of an individual alert, but also context about the potential stage and method of attacker activity.

Initial Access

We analyze events that may indicate the first successful access to the environment.

Persistence

We detect mechanisms intended to maintain access after a restart or session change.

Privilege Escalation

We monitor attempts to gain higher privileges and the use of privileged accounts.

Defense Evasion

We detect disabled protections, cleared logs, and hidden activity.

Credential Access

We analyze events related to attempts to obtain passwords, tokens, and other credentials.

Command and Control

We monitor connections and behavior that may indicate communication with attacker infrastructure.

Using MITRE mapping

  • classification of alerts by tactic,
  • identification of frequently observed techniques,
  • analysis of detection coverage,
  • creation of Threat Hunting scenarios,
  • comparison of events with an incident timeline,
  • prioritization of detection development,
  • reporting for the security team,
  • support for purple-team exercises,
  • analysis of visibility gaps,
  • documentation of techniques during incident response.
Threat Hunting

Proactive threat hunting

Threat Hunting involves deliberately searching data for activity that has not been clearly identified by standard rules. Analysts can combine information about users, hosts, processes, IP addresses, and event timing.

Full-Text Search

We analyze large collections of alerts and events using filters and queries.

Timeline

We reconstruct the sequence of actions performed by a user or attacker across multiple systems.

IOC Search

We search historical data for specific IP addresses, domains, hashes, and filenames.

Anomalies

We look for unusual logins, processes, file changes, and administrative activity.

Host Correlation

We verify whether similar events appeared on multiple endpoints.

New Rules

Based on analysis results, we create additional detections and dashboards.

Example Threat Hunting scenarios

  • administrative logins outside normal working hours,
  • one account logging in from multiple locations,
  • command interpreter execution by an unusual process,
  • file changes following failed logins,
  • outbound connections to rare domains,
  • unusual use of built-in system tools,
  • creation of new privileged accounts,
  • disabled logging or endpoint protection,
  • repeated events across multiple hosts,
  • appearance of an IOC in historical data,
  • file changes without a corresponding update process,
  • unusual outbound connection activity.
Active Response

Automated incident response

Active Response enables a defined command to be executed after a specific alert occurs. It can operate locally on the endpoint or on a central component depending on the type of response and architecture.

We deploy automatic actions carefully. Every response should have a clearly defined scope, duration, rollback method, and procedure for handling incorrect execution.

Blocking an IP Address

After detecting an attack, we can temporarily add the source to the local system firewall.

Account Lockout

In controlled scenarios, we restrict access for an account showing suspicious activity.

Process Termination

We can terminate a known malicious process or launch an incident-response script.

Host Isolation

We integrate Wazuh with network or EDR solutions that can restrict endpoint communication.

External System Notification

We call a webhook, API, playbook, or incident-response workflow.

Temporary Response

After a defined period, we automatically remove a block when required by the procedure.

Safe automation principles

  • we limit responses to high-confidence alerts,
  • we test scripts outside production,
  • we create rollback mechanisms,
  • we define maximum blocking duration,
  • we protect administrative addresses and accounts from accidental blocking,
  • we log every automatic response,
  • we notify the security team,
  • we restrict the privileges of executed commands,
  • we verify endpoint status after the response,
  • we regularly review automation effectiveness,
  • we disable responses that generate false actions,
  • we document responsibility for approving new scenarios.

An incorrect alert should not automatically disconnect a critical service. The greater the impact of a response, the higher the required confidence level should be.

Cloud Security

Monitoring cloud services and environments

Wazuh can collect security data from popular cloud platforms and SaaS services. It enables centralized analysis of events from both on-premises infrastructure and cloud environments.

Amazon Web Services

We collect events from selected AWS services, audit logs, and information about resource activity.

Microsoft Azure

We analyze events from Azure and integrated Microsoft services.

Google Cloud

We centralize logs and security events originating from GCP.

Microsoft 365

We monitor logins, administrative activity, and other supported Microsoft 365 events.

GitHub

We analyze events related to organizations, repositories, users, and administrative changes.

Hybrid Environment

We combine cloud data with alerts generated on local servers and workstations.

Example cloud events

  • login from an unusual location,
  • creation of a new administrative account,
  • change to an access policy,
  • modification of a security group,
  • deletion of audit logging,
  • creation of an access key,
  • unusual API use,
  • resource configuration changes,
  • public exposure of data,
  • large numbers of failed logins,
  • operations performed by an inactive account,
  • changes to protection or retention settings.
Container Security

Protecting container environments

Wazuh can monitor Docker hosts, running containers, images, volumes, networks, and runtime events. We combine container-layer data with monitoring of the operating system and applications running inside containers.

Containers

We monitor container startup, shutdown, removal, and status changes.

Images

We analyze the creation, download, and removal of images used in the environment.

Privileged Mode

We detect containers launched with excessive access to the host system.

Shell Inside a Container

We analyze unusual shell sessions and administrative commands.

Volumes

We monitor changes and events related to persistent data and its attachment.

Host System

We monitor Docker Engine configuration, files, processes, and the security of the underlying system.

Containerized application monitoring

  • stdout and stderr logs,
  • application logs stored in volumes,
  • configuration file changes,
  • processes running inside containers,
  • unusual network connections,
  • image and tag changes,
  • launch of privileged containers,
  • mounting sensitive host directories,
  • container network rule changes,
  • orchestrator events,
  • package and image vulnerabilities,
  • unauthorized modifications to persistent data.
Network Device Monitoring

Firewalls, routers, switches, and infrastructure services

Devices that do not support an agent can forward events through Syslog or expose data through APIs. We create decoders and rules for the devices in use and configure secure log transmission.

Firewalls

We analyze blocked and permitted connections, VPN, IPS, malware, logins, and configuration changes.

Routers

We monitor administrator logins, routing changes, errors, and unusual activity.

Switches

We collect port, authentication, configuration-change, and security-violation events.

VPN

We analyze logins, disconnections, failed attempts, and unusual user locations.

DNS

We monitor queries, configuration changes, zone transfers, and suspicious domains.

Proxy and WAF

We analyze requests, blocks, scans, exploitation attempts, and unusual application traffic.

Example network detection scenarios

  • multiple failed VPN logins,
  • administrator login from a new IP address,
  • firewall configuration changes,
  • disabling of a security policy,
  • large numbers of blocked connections,
  • multi-port scanning,
  • connection to an address present on an IOC list,
  • unusual data transfer,
  • attack detected by IPS,
  • attempted application exploitation,
  • unauthorized DNS record changes,
  • loss of connectivity with a log source.
Identity Security

Monitoring authentication and user accounts

Identity-event analysis helps detect account compromise, privilege-escalation attempts, and misuse of administrative accounts. We combine logs from Windows, Linux, directory services, VPN systems, and applications.

Logins

We monitor successful and failed attempts, connection source, user, and login type.

Privileged Accounts

We increase alert severity for administrative accounts and high-risk actions.

Group Changes

We detect users being added to administrative groups and permission changes.

New Accounts

We alert on the creation of local, domain, and service accounts.

Brute Force

We correlate repeated failed attempts with a later successful login.

Unusual Activity

We analyze logins outside normal working hours and from new locations.

Active Directory and Windows Security

  • interactive and network logins,
  • account lockouts,
  • password changes,
  • password resets by administrators,
  • account creation and deletion,
  • changes to privileged groups,
  • domain policy changes,
  • audit configuration changes,
  • service and task execution,
  • clearing of event logs,
  • PowerShell and administrative tool usage,
  • Kerberos and NTLM logins,
  • domain controller events,
  • attempts to use disabled accounts.
Regulatory Compliance

Supporting compliance controls

Wazuh includes rules and dashboards related to selected standards and regulations. The platform can support evidence collection, violation detection, and reporting, but it does not replace the complete compliance management process.

PCI DSS

We support monitoring of events, integrity, access, and system configurations related to cardholder data environments.

GDPR

We help record security events and activities related to personal data protection.

NIST 800-53

We map selected detections and platform capabilities to security controls.

HIPAA

We provide visibility into events and changes relevant to the protection of medical data.

ISO 27001

We use Wazuh data to support monitoring, audits, incident management, and vulnerability management.

Internal Policies

We create custom rules, controls, and reports aligned with organizational requirements.

Wazuh as an ISMS support tool

  • central log collection,
  • security event monitoring,
  • detection of unauthorized changes,
  • vulnerability identification,
  • system configuration assessment,
  • monitoring of privileged accounts,
  • event and trend reporting,
  • support for incident analysis,
  • retention of audit data,
  • recording of administrative activity,
  • evidence of selected security controls,
  • preparation of data for audits.

A compliance dashboard presents technical information, but it does not by itself prove that an organization fully complies with a standard or regulation.

Wazuh Indexer

Indexing and storing security data

Wazuh Indexer is a full-text search and analytics engine. It stores alerts, agent status, statistics, vulnerability information, inventory, and other data used by the platform.

In larger environments, we deploy the indexer as a cluster. Data is divided into shards and distributed across nodes, while replicas improve fault tolerance and query performance.

Alert Indexes

Store events classified by rules as security alerts.

Archive Indexes

Can contain a broader range of events, including those that did not generate alerts.

Monitoring Indexes

Store information about agent connection status and availability.

Vulnerability Indexes

Contain detected vulnerability status and information about affected software.

Statistics Indexes

Store performance data and information about the number of events processed by the server.

Inventory Indexes

Contain hardware, system, and software information about protected endpoints.

Retention and index management

  • we define alert retention periods,
  • we separate current and archived data,
  • we create index lifecycle policies,
  • we control shard size,
  • we select the number of replicas,
  • we monitor storage utilization,
  • we define warning thresholds,
  • we create index snapshots,
  • we move older data to lower-cost storage,
  • we remove data according to retention policies,
  • we monitor cluster health,
  • we test data restoration.

Wazuh Indexer performance

  • we use high-performance SSD or NVMe storage,
  • we separate system storage from index storage,
  • we control JVM memory usage,
  • we monitor shard count,
  • we avoid excessively small and numerous indexes,
  • we analyze query times,
  • we monitor write queues,
  • we control replica status,
  • we balance shards across nodes,
  • we plan capacity with sufficient headroom,
  • we identify overloaded nodes,
  • we reduce unnecessary full-event indexing.
Wazuh Dashboard

Analysis, visualization, and platform management

Wazuh Dashboard provides a web interface for event analysis, Threat Hunting, vulnerability management, File Integrity Monitoring, SCA, compliance, and cloud and container monitoring.

From the panel, we also manage agents, rules, decoders, CDB lists, cluster status, users, roles, and selected central component settings.

Security Events

We review alerts by time, host, severity, rule, user, and source.

Threat Hunting

We create queries and filters for proactive threat searches.

Endpoint Security

We analyze FIM, configuration, malware, inventory, and endpoint vulnerabilities.

Cloud Security

We present events originating from cloud and SaaS services.

Custom Dashboards

We create views tailored to teams, customers, locations, and processes.

Reports

We prepare exports and reports for analysis, audits, and management.

Dashboards tailored to the audience

  • SOC dashboard,
  • systems administrator dashboard,
  • vulnerability dashboard,
  • identity and login dashboard,
  • firewall and network dashboard,
  • endpoint security dashboard,
  • compliance dashboard,
  • management dashboard,
  • customer-specific dashboard,
  • production environment dashboard,
  • cloud and Microsoft 365 dashboard,
  • Wazuh platform performance dashboard.
Role-Based Access Control

Roles, users, and access separation

A security platform contains information about the entire infrastructure, vulnerabilities, accounts, and incidents. Access to data and functions should therefore be restricted according to the user’s role and area of responsibility.

Platform Administrator

Manages components, users, rules, agents, and system settings.

SOC Analyst

Analyzes alerts and events without requiring full administrative privileges.

Auditor

Receives access only to dashboards, reports, and data required for an audit.

IT Team

Can view vulnerabilities and alerts related to assigned systems.

Customer or Department

We restrict visibility to specified agents, indexes, or resource groups.

SSO Integration

We integrate authentication with the organization’s central identity provider.

Access best practices

  • we separate administrative and analyst accounts,
  • we grant the minimum required permissions,
  • we integrate authentication with LDAP or SSO,
  • we require strong authentication,
  • we maintain an emergency account independent of the external IdP,
  • we restrict the panel to a management network or VPN,
  • we regularly review users and roles,
  • we disable unused accounts,
  • we log administrative activity,
  • we restrict API access,
  • we use separate credentials for integrations,
  • we monitor failed logins.
Alerts and Integrations

Routing events to the correct teams

Wazuh can send notifications and forward alerts to external systems. We configure integrations according to threat severity, technology, system owner, and the required escalation path.

Email

We send alerts containing the host, rule, severity, source, and key event information.

Microsoft Teams and Slack

We forward critical events to channels used by responsible teams.

Helpdesk and ITSM

We automatically create tickets and attach the data required to begin analysis.

Webhook

We send events to external APIs and automation platforms.

SOAR

We launch response playbooks and threat-enrichment workflows.

Threat Intelligence

We integrate analysis with reputation lists, IOC feeds, and external data sources.

Alert levels

  • informational events retained in the dashboard,
  • low-level alerts available for periodic review,
  • medium alerts forwarded to the system owner,
  • high alerts requiring rapid verification,
  • critical alerts routed to the security on-call team,
  • separate thresholds for critical servers,
  • escalation after missing acknowledgment,
  • different channels for business hours and on-call duty,
  • filters limiting recurring alerts,
  • aggregation of similar events,
  • suppression during planned maintenance,
  • automatic ticket closure after the problem is resolved.
Wazuh Platform Monitoring

Continuous supervision of security components

A SIEM platform also requires monitoring. We supervise component availability, agent status, server performance, indexer health, storage utilization, and the successful transfer of data.

Wazuh Server

We monitor processes, queues, and the number of received, decoded, and dropped events.

Wazuh Indexer

We monitor cluster status, shards, replication, queries, memory, and disk space.

Wazuh Dashboard

We verify interface availability, certificate status, authentication, and communication with the API and indexer.

Agents

We monitor Active, Disconnected, Pending, and Never Connected statuses.

Filebeat

We verify that alerts are transferred successfully to Wazuh Indexer.

Certificates

We monitor the expiry of certificates used by central components.

Example technical alerts

  • Wazuh Server node unavailable,
  • cluster quorum lost,
  • large numbers of disconnected agents,
  • no new alerts despite an active environment,
  • increasing number of dropped events,
  • analysis queue overload,
  • red or yellow indexer status,
  • unassigned shards,
  • insufficient free disk space,
  • excessive memory utilization,
  • Filebeat data transfer failure,
  • certificate expiry,
  • snapshot or backup failure,
  • failed administrative logins.
Backup and Recovery

Protecting platform configuration and data

Recovering Wazuh requires protection of server configuration, agent keys, certificates, custom decoders, rules, CDB lists, dashboard settings, and data stored in the indexer.

We select the backup scope according to retention and recovery-time requirements. Not every organization needs to retain the complete history of all events, but detection and access configuration should always be protected.

Server Configuration

We protect settings, rules, decoders, agent groups, and lists used by detections.

Certificates and Keys

We create secure copies of the material required to restore component communication.

Indexer Snapshots

We back up indexes containing alerts, vulnerabilities, and other required data.

Dashboard

We protect view configuration, objects, roles, and integrations.

Automated Backups

We create schedules and retention policies aligned with organizational requirements.

Recovery Tests

We verify that the environment can be rebuilt and agents can reconnect.

Recovery procedure

  • preparation of new servers,
  • installation of compatible component versions,
  • restoration of certificates and configuration,
  • restoration of the Wazuh Server cluster,
  • restoration of the Wazuh Indexer cluster,
  • restoration of index snapshots,
  • restoration of dashboards and roles,
  • API verification,
  • agent communication checks,
  • verification of incoming events,
  • testing of rules and alerting,
  • verification of external integrations,
  • documentation updates after recovery.
Updates and Development

Controlled Wazuh upgrades

An upgrade involves several interdependent components. Before making changes, we verify the supported upgrade path, agent compatibility, cluster status, backup availability, and system requirements.

  • we inventory component versions,
  • we analyze release information,
  • we verify compatibility of custom rules and decoders,
  • we back up configuration,
  • we create index snapshots,
  • we verify cluster health,
  • we upgrade nodes in stages,
  • we verify communication between components,
  • we test the dashboard and API,
  • we verify event flow,
  • we gradually upgrade agents,
  • we monitor performance after the change,
  • we test alerts and Active Response,
  • we document the completed upgrade.

Detection rule development

The security environment changes together with infrastructure and attacker techniques. We regularly review rule performance, add support for new sources, and adjust alert levels.

New Systems

We add decoders and rules for newly deployed applications, devices, and services.

False Positives

We analyze false alarms and create precise exceptions.

Missing Detections

Based on incidents and Threat Hunting, we close visibility gaps.

MITRE ATT&CK

We extend coverage of tactics and techniques relevant to the organization.

Threat Intelligence

We update IOC lists and reputation-source integrations.

Testing

We validate rules using sample logs and controlled scenarios.

Wazuh Migration

Moving and modernizing the environment

Migration may include changing the operating system, separating an all-in-one installation, building a cluster, moving indexes to new storage, or consolidating several independent environments.

New Infrastructure

We move components to servers with appropriate performance and capacity.

Component Separation

We transform an all-in-one installation into an architecture with separate roles.

Cluster Deployment

We add redundancy for the server, indexer, and dashboard.

Index Migration

We move historical data and adjust retention policies.

Consolidation

We combine agents and rules from several environments into one managed platform.

Minimized Downtime

We prepare a staged cutover and maintain continuity of event collection.

Migration process

  • we inventory agents and data sources,
  • we analyze index volume,
  • we review custom rules and integrations,
  • we design the target architecture,
  • we prepare certificates and DNS,
  • we install the target components,
  • we restore configuration,
  • we migrate indexes or required retained data,
  • we test agent communication,
  • we switch endpoint groups in stages,
  • we verify alerting,
  • we test dashboards and integrations,
  • we monitor the environment after cutover,
  • we update the documentation.

During a SIEM migration, visibility continuity is the top priority. The security team should not lose alerts precisely while infrastructure changes are taking place.

Wazuh Audit

Assessing architecture and detection effectiveness

A Wazuh audit covers both the technical condition of the platform and the quality of collected data and alerts. We verify whether critical systems are protected, whether rules work correctly, and whether the team receives information that enables an effective response.

Architecture

We assess component placement, clusters, redundancy, storage, and communication.

Agents

We verify deployment coverage, connection status, versions, and group configuration.

Log Sources

We verify that the platform receives data from critical systems and devices.

Rules

We analyze false positives, missing detections, severity levels, and MITRE mapping.

Security

We verify roles, certificates, access, updates, and protection of platform data.

Response Process

We assess escalations, alert handling, Active Response, and incident documentation.

Technical audit scope

  • component and agent versions,
  • Wazuh Server cluster status,
  • Wazuh Indexer cluster status,
  • CPU, RAM, and storage utilization,
  • shard and replica status,
  • event processing performance,
  • number of dropped events,
  • Filebeat communication status,
  • agent status,
  • certificate validity,
  • backups and snapshots,
  • retention policies,
  • roles and permissions,
  • API and panel security,
  • monitoring of the platform itself.

Detection audit scope

  • coverage of critical systems,
  • log completeness,
  • File Integrity Monitoring operation,
  • SCA scope,
  • Vulnerability Detection status,
  • decoder quality,
  • correctness of custom rules,
  • number of false positives,
  • recurring alerts,
  • missing dependencies and correlations,
  • MITRE ATT&CK mapping,
  • Active Response effectiveness,
  • external integrations,
  • escalation procedures,
  • alert response time.

Post-audit optimization

  • we upgrade components,
  • we organize agents and groups,
  • we add missing data sources,
  • we correct retention policies,
  • we optimize shard count,
  • we improve rules and decoders,
  • we reduce false positives,
  • we increase the severity of important alerts,
  • we add event correlation,
  • we rebuild dashboards,
  • we configure appropriate escalations,
  • we secure the panel and API,
  • we implement backups and recovery tests,
  • we complete the documentation.
Security Monitoring as a Service

Ongoing Wazuh maintenance and development

A SIEM platform requires regular administration. Systems, log formats, application versions, attacker techniques, and organizational requirements all change. Without continuous rule tuning and data-source verification, detection quality gradually declines.

Platform Monitoring

We supervise servers, indexers, dashboards, agents, queues, and capacity.

Alert Analysis

We review events at defined severity levels and identify required actions.

Rule Tuning

We reduce false alarms and develop detections for new threats.

Adding Systems

We deploy agents, new log sources, decoders, and dashboards.

Updates

We maintain supported versions of central components and agents.

Reporting

We prepare vulnerability, alert, compliance, and security posture reports.

Example maintenance scope

  • daily component health checks,
  • analysis of disconnected agents,
  • index capacity monitoring,
  • review of critical alerts,
  • false-positive tuning,
  • IOC list updates,
  • addition of new hosts,
  • creation of decoders for new applications,
  • rule updates,
  • integration health checks,
  • backup and snapshot monitoring,
  • system updates,
  • account and role review,
  • monthly reporting,
  • periodic recovery testing.
Documentation

Wazuh environment documentation

We document not only component installation, but also log sources, rules, alert ownership, and incident response procedures. This ensures that platform development does not depend solely on one person’s knowledge.

Architecture

We describe servers, component roles, clusters, networks, ports, and dependencies.

Data Sources

We create an inventory of agents, Syslog devices, cloud integrations, and applications.

Rules and Decoders

We document custom extensions, their purpose, and testing methods.

Alerting

We describe severity levels, recipients, channels, and escalation rules.

Emergency Procedures

We prepare instructions for restoring components, certificates, and indexes.

Incident Handling

We define the steps for verification, escalation, and event documentation.

Documentation elements

  • architecture diagram,
  • addressing and communication ports,
  • cluster node inventory,
  • agent group inventory,
  • naming standards,
  • Syslog and API sources,
  • custom rule inventory,
  • custom decoder inventory,
  • CDB and IOC list descriptions,
  • retention policy,
  • roles and users,
  • integrations and webhooks,
  • upgrade procedure,
  • backup and recovery procedure,
  • alert analysis instructions.
Flexible cooperation model

How can we support your Wazuh environment?

Design and Deployment

We design the architecture, install the platform, and connect selected endpoints and data sources.

Audit and Optimization

We analyze performance, security, monitoring coverage, and detection-rule quality.

Migration and Expansion

We move the environment, build clusters, and increase platform capacity.

Ongoing Administration

We maintain components, develop rules, add sources, and supervise alerts.

How do we begin working together?

  • We inventory the environment – we analyze endpoints, servers, devices, cloud services, and existing log sources.
  • We define the requirements – we determine detection scope, retention, event volume, and the expected response process.
  • We design the architecture – we select the number of Server, Indexer, and Dashboard nodes and the required resources.
  • We deploy the platform – we install components, certificates, clusters, and backup mechanisms.
  • We connect data sources – we deploy agents and configure Syslog, APIs, and cloud integrations.
  • We tune detections – we adjust rules, severity levels, exceptions, FIM, SCA, and Vulnerability Detection.
  • We configure response – we create alerts, escalations, tickets, and safe Active Response procedures.
  • We test the system – we simulate events, verify detection, and test the complete alerting path.
  • We provide documentation – we describe the architecture, rules, sources, and maintenance procedures.
  • We provide ongoing support – we update the platform and develop monitoring as the infrastructure evolves.

Wazuh technologies and features

Wazuh Agent

A multi-platform agent that collects logs, inventory, file changes, configuration, and endpoint security data.

Wazuh Server

The central component that analyzes data, manages agents, and generates alerts.

Wazuh Indexer

A scalable engine for indexing, storing, searching, and analyzing security data.

Wazuh Dashboard

An interface for alert analysis, Threat Hunting, agent management, reporting, and platform supervision.

File Integrity Monitoring

Monitoring the creation, deletion, and modification of files, directories, and the Windows registry.

Vulnerability Detection

Identification of known vulnerabilities in operating systems and installed software.

Security Configuration Assessment

Automated assessment of system settings against security policies and hardening recommendations.

Threat Hunting

Searching for anomalies, indicators of compromise, and suspicious activity in current and historical data.

MITRE ATT&CK

Mapping detections to tactics and techniques used by attackers.

Active Response

Automatic execution of controlled actions after specific threats are detected.

Cloud Security

Centralized analysis of events from AWS, Azure, Google Cloud, Microsoft 365, and SaaS services.

Compliance

Dashboards, rules, and reports supporting compliance monitoring and organizational audit processes.

Do you need a Wazuh deployment, audit, or expansion of your security environment?

We will analyze your infrastructure, design the right SIEM/XDR architecture, and prepare a platform that provides event visibility, threat detection, vulnerability monitoring, and an effective incident-response path.

Contact Us