How sakkarose/wazuh-docker works
Main Components
• Docker Orchestration: At the heart of the design is Docker Compose (see single-node/docker-compose.yml) that bundles multiple containerized services.
• Wazuh Manager: The central security engine that processes logs and alerts.
• Wazuh Indexer: Responsible for indexing and searching through the logs (with its own configuration files found under single-node/config/wazuh_indexer and managed via separate certificate creation using the indexer-certs-creator).
• Wazuh Dashboard: Configurations under single-node/config/wazuh_dashboard point toward visualization (using OpenSearch Dashboards or Grafana as mentioned in the README).
• Wazuh Endpoint/Agent Provisioning: Configurations for Windows agents include setups for Sysmon, YARA, and active response scripts (located in single-node/config/wazuh_endpoint/windows).
• CI/CD Pipeline: The repository contains a well-populated .github directory with multiple workflows for building, scanning (using Trivy), and pushing Docker images as well as checks (filebeat and log-check scripts). This is an important part of the overall process, ensuring that deployments remain checked and secure.
Detail the Relationships/Interactions Between Components
• The Docker Compose environment will provide communication amongst the Wazuh Manager, Indexer, and Dashboard.
• The Manager collects and processes logs (including those forwarded from Windows agents) and interacts with the Indexer for storing/retrieving log data.
• The Dashboard accesses data from the Indexer to present insights and visualizations.
• The Windows agents (provisioned via provided scripts and configurations) securely communicate with the Manager for log collection and response actions.
• The indexer-certs-creator component ensures secure inter-service communication by generating necessary certificates before the Indexer comes online.
• The CI/CD pipeline (via GitHub Actions) automates the building, testing, and deployment processes, ensuring that changes in decoders, rules, and endpoint configurations propagate to the deployed containers.
Architectural Patterns and Design Principles
• Containerization & Microservices: The project adopts a containerized architecture (Docker), isolating responsibilities (manager, indexer, dashboard, cert creator) in separate containers.
• Modular Configuration: With directories separating decoders, rules, and agent provisioning scripts, the design supports easy updates and extensibility.
• Continuous Integration/Delivery: The GitHub workflows and scripts emphasize automation, continuous testing, and secure deployments.
Relevant Technologies, Frameworks, or Libraries
• Docker & Docker Compose for container orchestration.
• GitHub Actions for CI/CD (with specific workflows for pushing Docker images and running security scans with Trivy).
• Wazuh (as the core technology) for security monitoring.
• Supporting configurations for Windows agent tools (Sysmon, YARA) and custom scripts for active responses.
• OpenSearch Dashboards (or potential replacement with Grafana as discussed in the README) for visualization.