# Experiment 6 – Security Event Monitoring Using Wazuh

Objective: Detect and monitor suspicious authentication activities on an Ubuntu server using Wazuh, analyze security alerts and configure detection rules.

## 1. What is Wazuh?

Wazuh is an open-source security monitoring platform used for threat detection, log analysis, vulnerability detection and security incident monitoring.

It helps identify suspicious activities such as repeated failed logins, unauthorized access attempts and malware-related events.

## 2. What are the main components of Wazuh?

- Wazuh Manager: Central component that analyzes security data and generates alerts.
- Wazuh Agent: Installed on monitored systems to collect logs and security events.
- Wazuh Indexer: Stores and indexes security alerts and events.
- Wazuh Dashboard: Provides a graphical interface to visualize and analyze security information.

## 3. What is a Wazuh Agent?

A Wazuh Agent is software installed on monitored endpoints such as Linux or Windows machines.

It collects system logs, authentication events and security information and forwards them to the Wazuh Manager.

## 4. What is the difference between Wazuh Manager and Agent?

- Manager: Receives and analyzes events, applies detection rules and generates alerts.
- Agent: Collects logs and security events from monitored machines and sends them to the manager.

## 5. What is a security event?

A security event is an activity that may affect the security of a system.

Examples:

- Failed login attempts.
- Unauthorized access.
- Suspicious file modifications.
- Unexpected privilege escalation.

## 6. What is log analysis in Wazuh?

Log analysis is the process of examining collected system logs to identify suspicious activities, errors and security threats.

Wazuh analyzes incoming logs using decoders and rules to identify potentially harmful events.

## 7. What are Decoders and Rules in Wazuh?

- Decoders: Extract and identify relevant fields from incoming log messages.
- Rules: Evaluate decoded events against predefined conditions to detect suspicious activities.

For example, a decoder extracts username and source IP from a failed login log, while a rule identifies repeated login failures.

## 8. What is a Wazuh alert?

An alert is a notification generated when an event matches a configured detection rule.

It contains information such as:

- Alert description.
- Severity level.
- Source host.
- Event timestamp.
- Related security information.

## 9. What are Wazuh alert severity levels?

Wazuh uses alert levels ranging from 0 to 15.

- Level 0: Ignored events.
- Levels 1–3: Informational or low priority.
- Levels 4–7: Low to medium severity.
- Levels 8–11: High severity.
- Levels 12–15: Critical or very high severity.

Higher levels generally indicate more serious security events.

## 10. What is brute-force detection?

Brute-force detection identifies repeated login attempts using different passwords to gain unauthorized access.

Wazuh can detect repeated authentication failures using log analysis and configured detection rules.

## 11. What is the difference between an event and an alert?

- Event: Any recorded activity occurring in a system.
- Alert: A security notification generated when an event matches a detection rule.

For example, a failed login is an event. Multiple suspicious failed logins may trigger an alert.

## 12. What is a Wazuh detection rule?

A detection rule defines conditions used to identify suspicious activities in collected logs.

Rules can detect repeated authentication failures, unauthorized access and other abnormal activities.

Custom rules can also be created to detect specific threats.

## 13. What is the purpose of Wazuh Dashboard?

The Wazuh Dashboard provides a graphical interface to monitor security alerts, investigate suspicious events, view affected hosts and analyze security activity.

## 14. What is the difference between Wazuh and traditional monitoring tools like Zabbix?

- Wazuh: Primarily focuses on security monitoring, threat detection and log analysis.
- Zabbix: Primarily focuses on infrastructure performance monitoring, such as CPU, RAM and network utilization.

Wazuh is security-focused, whereas Zabbix is infrastructure-focused.

## 15. How would you investigate repeated failed login attempts using Wazuh?

First, verify that the Wazuh Agent is connected to the Manager. Then generate or inspect authentication events and examine the resulting alerts.

I would check the affected host, source IP, event frequency and alert severity. If suspicious activity is confirmed, I would recommend blocking the source IP or securing the affected account.

## Last-minute revision

| Term                | Remember                             |
| ------------------- | ------------------------------------ |
| Wazuh               | Security monitoring platform         |
| Manager             | Analyzes events and generates alerts |
| Agent               | Collects endpoint logs               |
| Indexer             | Stores and indexes events            |
| Dashboard           | Visualizes security information      |
| Decoder             | Extracts fields from logs            |
| Rule                | Detects suspicious activity          |
| Alert               | Notification of detected activity    |
| Brute force         | Repeated password attempts           |
| Level 0–15          | Alert severity scale                 |
| Authentication logs | Login-related activities             |

Important for practical viva

Focus on:

1. Wazuh architecture and components.
2. Manager vs Agent.
3. Decoders vs Rules.
4. Event vs Alert.
5. Alert severity levels (0–15).
6. Brute-force detection.
7. Custom detection rules.
8. Wazuh vs Zabbix.

Based on Experiment 6 of your CS414 lab question bank.&#x20;

CS414_ITIMM_Lab_ESE.pdf
