{"id":30934,"date":"2024-05-27T10:06:49","date_gmt":"2024-05-27T08:06:49","guid":{"rendered":"https:\/\/inlab.fib.upc.edu\/news\/wazuh-an-open-source-platform-unifying-siem-and-xdr\/2024\/"},"modified":"2024-05-28T08:54:41","modified_gmt":"2024-05-28T06:54:41","slug":"wazuh-an-open-source-platform-unifying-siem-and-xdr","status":"publish","type":"post","link":"https:\/\/inlab.fib.upc.edu\/en\/blog\/wazuh-an-open-source-platform-unifying-siem-and-xdr","title":{"rendered":"Wazuh – An Open Source platform unifying SIEM and XDR"},"content":{"rendered":"\n

Open Source<\/em>, SIEM and XDR<\/strong><\/h2>\n\n

First, we will have to explain these concepts introduced in the title to understand the Wazuh framework; SIEM and XDR.<\/p>\n\n

SIEM (Security Information and Event Management<\/em>) is a technology that collects, analyzes and correlates data from different sources in real time to identify and respond to security threats. Sources can be logs<\/em> from systems, applications, network or end devices. It uses correlation and analysis techniques to identify patterns of malicious behavior and generate alerts when suspicious activity is detected. It also incorporates report generation functions, as well as graphical forms of visual representation.<\/p>\n\n

XDR (Extended Detection and Response<\/em>) goes further by extending its reach to a wider range of devices and\/or services (sources).<\/p>\n\n

In addition, it not only has a passive detection role, but also has the capability of automated active response, which allows action to be taken in the event that malicious behavior is detected.<\/p>\n\n

Wazuh therefore incorporates a whole range of features and functionalities that allow it to work as a SIEM and XDR. But first we will explore its architecture.<\/p>\n\n

Wazuh’s architecture<\/strong><\/h2>\n\n

The solution is based on deploying an agent on the monitored end devices (endpoints<\/em>) and three core components: the indexer, the server, and the dashboard<\/em>, which can be installed on one or several nodes, forming a cluster, thus improving performance, security and availability.<\/p>\n\n

These are all the necessary components for the operation of Wazuh.<\/p>\n\n

<\/div>\n\n
\"\"<\/a><\/figure>\n\n
<\/div>\n\n

The indexer <\/strong> is highly scalable and has a full-text search and parsing engine. Indexes and stores the alerts generated by the server in documents in JSON format. These documents are distributed in different containers called shards<\/em>, and by distributing these shards in different nodes we can ensure redundancy, improve the tolerance to hardware <\/em> errors as well as increase the query <\/em> capacity when we attach the nodes in a cluster.<\/p>\n\n

In addition to speed, scalability and resilience, Wazuh’s indexer also includes features such as data roll-ups, alerting, anomaly detection<\/em> and index lifecycle management<\/em>.<\/p>\n\n

<\/div>\n\n
\"\"<\/a><\/figure>\n\n
<\/div>\n\n

The server analyzes the data received from the agents and processes them through decoders and rules, using threat intelligence to detect known indicators of compromise (IOCs). A single server can analyze data from hundreds and thousands of agents and can scale horizontally in the form of a cluster. Additionally, through the server, it is possible to manage the agents remotely. The alerts use the MITRE ATT&CK framework and compliance <\/em> requirements such as GDPR.<\/p>\n\n

The server <\/strong> runs the following services: the analysis engine, the RESTful API, the agent registration service, the cluster daemon and Filebeat, which is used to send information to the indexer.<\/p>\n\n

<\/div>\n\n
\"\"<\/a><\/figure>\n\n
<\/div>\n\n

El dashboard<\/em><\/strong>\u00e9s la interf\u00edcie web perqu\u00e8 l\u2019usuari pugui visualitzar les dades recollides i l\u2019an\u00e0lisi dels esdeveniments i alertes de seguretat generades. It incorporates several functionalities that we will see later.<\/p>\n\n

<\/div>\n\n
\"\"<\/a><\/figure>\n\n
<\/div>\n\n

The agents <\/strong> are installed on end devices, such as desktop computers, servers, cloud instances or virtual machines. They allow the prevention, detection and response to threats, with the ability to operate in different operating systems.<\/p>\n\n

An interesting point of Wazuh is that the mentioned end devices are agent-based (requiring the installation of software<\/em>), but it also allows monitoring agent-less<\/em> devices (without agents) such as firewalls<\/em>, switches<\/em>, routers <\/em> or NIDS (Network Intrusion Detection System<\/em>).<\/p>\n\n

Therefore, the global structure of Wazuh and its components is as follows:<\/p>\n\n

<\/div>\n\n
\"\"<\/a><\/figure>\n\n
<\/div>\n\n

Functionalities and use cases of Wazuh<\/strong><\/h2>\n\n
<\/div>\n\n
    \n
  • SCA (Security Configuration Assessment):<\/strong>Wazuh monitors system and application configuration to ensure compliance with security standards and policies. Wazuh agents perform periodic scans to detect misconfigurations or security holes in end devices that could be exploited by malicious actors. These configuration checks can be configured to adapt them to the needs of the organization.<\/li>\n\n\n\n
  • Malware <\/em> detection:<\/strong>Wazuh detects malicious activity and generates indicators of compromise that occur on end devices as a result of malware <\/em> infections or cyberattacks.<\/li>\n\n\n\n
  • FIM (File Integrity Monitoring):<\/strong>Wazuh monitors the folder system, identifying changes in the content, permissions, ownership and attributes of the files to be monitored.<\/li>\n\n\n\n
  • Threat detection:<\/strong>Wazuh offers comprehensive visibility to end devices and monitored infrastructure. It has record retention, indexing and query capabilities that help investigate threats that may have evaded initial security controls.<\/li>\n\n\n\n
  • Log Data Analysis:<\/strong>Wazuh’s agents collect logs from the operating system and applications and securely send them to Wazuh’s server for rule-based analysis and mapping.<\/li>\n\n\n\n
  • Detection of vulnerabilities:<\/strong>Wazuh’s agents collect program inventory data and send this information to Wazuh’s server. The inventory data collected is correlated with continuously updated CVE databases to identify known vulnerable software.<\/li>\n\n\n\n
  • Incident Response:<\/strong>Wazuh has predefined active responses to perform various countermeasures against ongoing threats.<\/li>\n\n\n\n
  • Normative Compliance:<\/strong>Wazuh offers some of the security controls required for compliance with industry standards and regulations, such as GDPR, NIST, TSC and HIPAA, also achieved through SCA and FIM functions.<\/li>\n\n\n\n
  • The IT Hygiene:<\/strong>Wazuh builds an updated system inventory of all monitored end devices. This inventory helps organizations to optimize the visibility of assets and maintain good IT hygiene.<\/li>\n\n\n\n
  • Container Security:<\/strong>Wazuh provides security visibility to Docker hosts and containers, monitoring their behavior and detecting threats, vulnerabilities and anomalies.<\/li>\n\n\n\n
  • Protection of Work and Integration of third parties:<\/strong>Wazuh integrates with cloud platforms, collecting and aggregating security data. Alert on security risks and vulnerabilities discovered to ensure safety and compliance with regulatory standards. Wazuh monitors and protects the work crews in the workplace as well as in the local environment. It can integrate with cloud platforms such as AWS, Microsoft Azure, GCP, Microsoft 365 and GitHub to monitor services, virtual machines and the activities that occur on these platforms.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"

    Open Source, SIEM and XDR First, we will have to explain these concepts introduced in the title to understand the Wazuh framework; SIEM and XDR. SIEM (Security Information and Event Management) is a technology that collects, analyzes and correlates data from different sources in real time to identify and respond to security threats. Sources can […]<\/p>\n","protected":false},"author":1242,"featured_media":30901,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[572],"tags":[],"experteses":[],"class_list":["post-30934","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"acf":[],"_links":{"self":[{"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/posts\/30934","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/users\/1242"}],"replies":[{"embeddable":true,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/comments?post=30934"}],"version-history":[{"count":3,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/posts\/30934\/revisions"}],"predecessor-version":[{"id":30939,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/posts\/30934\/revisions\/30939"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/media\/30901"}],"wp:attachment":[{"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/media?parent=30934"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/categories?post=30934"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/tags?post=30934"},{"taxonomy":"experteses","embeddable":true,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/experteses?post=30934"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}