Zum Inhalt

Upgrade Guides

Version-specific upgrade procedures for Wazuh SIEM components. Each guide is tailored to a specific Wazuh release version and includes version-specific considerations, known issues, and validated upgrade paths.

📚 About Versioned Upgrade Guides

Upgrade guides are versioned using mike to maintain documentation for multiple Wazuh releases. This allows you to:

  • Access upgrade procedures for your specific version
  • Review historical upgrade paths
  • Understand version-specific requirements and changes

Prüfprozess bei neuen Wazuh-Versionen

Wenn eine neue Wazuh-Version erscheint, MUSS folgender Prozess durchlaufen werden, bevor die Version für Kunden-Upgrades freigegeben wird:

Schritt 1: Offiziellen Upgrade Guide prüfen

  • Wazuh Release Notes lesen: https://documentation.wazuh.com/current/release-notes/
  • Offiziellen Upgrade Guide lesen: https://documentation.wazuh.com/current/upgrade-guide/
  • Breaking Changes identifizieren und dokumentieren
  • Deprecated Features notieren

Schritt 2: Interne Dokumentation aktualisieren

  • Neuen Ordner unter upgrade-guides/<version>/ erstellen
  • Version-spezifische Hinweise, Breaking Changes und bekannte Probleme dokumentieren
  • Runbook auf Kompatibilität prüfen (haben sich Befehle/Pfade geändert?)
  • Checkliste auf Vollständigkeit prüfen

Schritt 3: Freigabe

  • Review durch zweite Person
  • Pull Request mit Änderungen erstellen
  • Version als "freigegeben für Upgrades" markieren

WICHTIG: Kein Kunden-Upgrade durchführen, solange der interne Prüfprozess nicht abgeschlossen ist!

🎯 Available Upgrade Guides

Wazuh 4.x Series

Wazuh 4.12 Upgrade Guide

Latest stable release with enhanced detection capabilities and performance improvements.

Key Changes: - Improved SCA (Security Configuration Assessment) - Enhanced agent communication protocol - Dashboard UI improvements - Performance optimizations for large deployments

Upgrade Path: 4.10.x, 4.11.x → 4.12.0

Wazuh 4.11 Upgrade Guide (Coming Soon)

Previous stable release with focus on reliability.

Wazuh 4.10 Upgrade Guide (Coming Soon)

Long-term support release.

Version Selection Guide

From Version To Version Guide Complexity Downtime
4.11.x 4.12.x 4.12 Low ~30 min
4.10.x 4.12.x 4.12 Medium ~45 min
4.9.x 4.12.x 4.12 Medium ~45 min
4.8.x or older 4.12.x Contact Support High ~90 min

🚀 How to Use Upgrade Guides

1. Determine Your Current Version

# Check manager version
/var/ossec/bin/wazuh-control info | grep VERSION

# Check indexer version
curl -sk -u admin:admin https://127.0.0.1:9200/ | grep number

# Check dashboard version
dpkg -l | grep wazuh-dashboard

2. Select Target Version

  • Review release notes for target version
  • Check compatibility requirements
  • Verify your infrastructure meets prerequisites
  • Review known issues and breaking changes

3. Review Upgrade Path

  • Ensure your upgrade path is supported
  • Note any intermediate versions required
  • Plan for configuration migrations if needed

4. Follow Version-Specific Guide

  • Use the guide for your target version
  • Follow all version-specific prerequisites
  • Complete all validation steps
  • Document version numbers in metadata

📋 Version-Specific Considerations

Component Version Compatibility

Critical Rule: Manager version must be ≥ Agent version

✅ SUPPORTED:
   Manager 4.12.0 + Agent 4.11.0
   Manager 4.12.0 + Agent 4.12.0

❌ NOT SUPPORTED:
   Manager 4.11.0 + Agent 4.12.0

Upgrade Order for Central Components

Always upgrade in this order: 1. Wazuh Indexer first 2. Wazuh Manager second 3. Wazuh Dashboard third 4. Filebeat last

Agent Upgrade Strategy

Two approaches: - Rolling upgrade: Upgrade agents in phases (recommended for large deployments) - Batch upgrade: Upgrade all agents simultaneously (suitable for smaller environments)

🔍 Version-Specific Resources

Wazuh 4.12

Official Wazuh Documentation

📝 Version Metadata Requirements

When following an upgrade guide, always document:

current_version:
  indexer: "4.11.0"
  manager: "4.11.0"
  dashboard: "4.11.0"
  filebeat: "7.10.2"

target_version:
  indexer: "4.12.0"
  manager: "4.12.0"
  dashboard: "4.12.0"
  filebeat: "7.10.2"

upgrade_path: "4.11.0 -> 4.12.0"
guide_version: "4.12"

🔄 Using Mike for Version Management

This documentation uses mike for managing versioned content. See Deployment Guide for details.

Quick Reference

# Deploy a specific version
mike deploy 4.12 latest

# List all versions
mike list

# Set default version
mike set-default latest

# Delete a version
mike delete 4.11

🛡️ Pre-Upgrade Checklist

Before starting any upgrade:

  • Review target version release notes
  • Check compatibility matrix
  • Verify upgrade path is supported
  • Review version-specific known issues
  • Create backup/snapshot of current system
  • Document current versions
  • Schedule maintenance window
  • Get change approval
  • Notify stakeholders