Hello Vaijnath,
Thank you for using Wazuh!!!
Can you please check that the parameter
sca.remote_commands is set to "1" on the agent's local_internal_options.conf file? on Linux agents this can be located on /var/ossec/etc/local_internal_options.conf and on Windows agents this can be found on C:\Program Files(x86)\ossec-agent\local_internal_options.conf. After this is modified please restart the agent with the command "systemctl restart wazuh-agent" or "service wazuh-agent restart" (depending on your Linux distro) or using the Wazuh agent's GUI (ran as administrator).
You may also check that the new policy on the manager has the proper ownership with the command "ls -l
/var/ossec/etc/shared/default/log4j_check.yml" in case you placed the policy for the default group (All the agents by default belong to this group) or modify the path to match your desired group. The ownership must be set to "ossec:ossec".
Then you may force a SCA scan by restarting the Wazuh manager service with the command "systemctl restart wazuh-manager" or "service wazuh-manager restart". Please monitor your SCA events after this.
Please let me know.
Thank you.