Hi All,I need your help.
I am working with wazuh windows agents 3.0.0 ( on Windows 10) and wazuh-manager 2.2.1 ( on centos7)
The active-response firewalld-drop in Linux (centos7, service firewalld) and is working well.
The issue I have is with the active-response in windows is that the route-null.cmd shell does not block the offender IP.
I was trying to do by command line and based on the advise in this link:
https://www.beaming.co.uk/support/internet-and-connectivity/how-to-add-a-null-route-in-windows/route add X.X.X.X mask Y.Y.Y.Y Z.Z.Z.Z metric 1 -p
Where X.X.X.X and Y.Y.Y.Y is the IP range and subnet mask you wish to Null route and Z.Z.Z.Z is a spare unallocated IP address on your local network.
In my case for example, if you wish to Null route the IP address 128.9.55.101 and you have a spare unallocated IP address of 128.9.55.123 on your local area network then you would enter:
route add 128.9.55.101 mask 255.255.255.255 128.9.55.123 metric 1 -p
after that i still can ping the address 128.9.55.101
This IP address 128.9.55.101 does not get blocked .
I believe the issue is that "How to add a Null route in windows" itself doesn't works.
Do you have some similar reports to this?
When I try using /var/ossec/bin/agent_control -b 128.9.55.155 -f win_route-null0 -u 027
The win_route-null0 get launched in the agent , and I can see it in the active-response.log in that windows agent.
When I do: route print in that windows agent IP 128.9.55.155
I can see the route in the route table
Network Destination Netmask Gateway Interface Metric
128.9.55.101 255.255.255.255 128.9.55.123 128.9.55.155 51
after that i still can ping the address 128.9.55.101
This IP address 128.9.55.101 does not get blocked .
Some idea how deal with this issue?
Thanks and regards
Yollanda