- Are the logs analyzed on each agent?
- How often does the manager monitor the logs?
- How long are the logs stored on the server?
- How does this help me with regulatory compliance?
- What is the CPU usage like on the agents?
- From where can Wazuh get log messages?
- Can I send firewall, vpn, authentication logs to Wazuh?
- What information should Wazuh extract from my logs?
- Can I ignore events that are not important?
Are the logs analyzed on each agent?¶
No, the manager gets the logs from all the agents and then analyzes the messages.
How often does the manager monitor the logs?¶
The manager monitors logs in real time.
How long are the logs stored on the server?¶
Archived logs are not automatically deleted by default. However, you can choose when to manually or automatically (e.g., cron job) delete logs according to your own legal and regulatory requirements.
How does this help me with regulatory compliance?¶
Log analysis is a requirement for: PCI DSS Compliance, HIPAA Compliance, FISMA Compliance and SOX Compliance.
What is the CPU usage like on the agents?¶
The memory and CPU requirements of the Wazuh agent are insignificant since its primary duty is to forward events to the manager. However, on the Wazuh manager, CPU and memory consumption can increase rapidly depending on the events per second (EPS) that the manager has to analyze.
From where can Wazuh get log messages?¶
Wazuh can read log messages from text log files, Windows event logs and event channels, and via remote syslog. Logs are monitored in real time.
Can I send firewall, VPN, authentication logs to Wazuh?¶
Yes. Wazuh has the capability to receive and process logs from devices that send logs using the syslog protocol. You can create custom decoders and rules for your device-specific logs.
What information should Wazuh extract from my logs?¶
This depends on your needs. Once you know the format of your application logs and the typical events, you can create decoders and rules for them.