Hello Kamran,
I have reviewed your Windows
agent.conf file and here are a couple that will help you with the setup:
There is a missing opening bracket in one of your configuration blocks. It currently looks like this:
localfile>
<location>System</location>
<log_format>eventchannel</log_format>
</localfile>
It should be updated to
<localfile> to ensure the file parses correctly.
I noticed that
whodata="yes" and
report_changes="yes" are enabled for big directories like
%WINDIR%\System32 and
%PROGRAMFILES%. Scanning these highly active directories could cause big CPU and RAM spikes.
You can use instead
realtime="yes" for large directories. And keep
whodata for highly sensitive folders that are rarely modified.
File Integrity Monitoring DocumentationRegarding your issue with managing multiple operating systems, you should avoid maintaining one massive configuration file. Instead, you can use our Centralized Configuration feature.
You can create distinct groups in your manager (e.g., `windows`, `linux`, `macos`) and assign the respective agents to them. The manager will then automatically push the correct configuration block to each specific group.
Centralized Configuration Documentation
Related to your rules question, keep in mind that Wazuh comes with a comprehensive set of built-in base rules out of the box that cover most standard use cases. However, if you need to build custom rules for your specific environment, we have a step-by-step guide on how to successfully create and test them.
Custom Rules GuideLet me know if you run into any issues or need further assistance with any of these processes!