Note: Wazuh v4.2.0 includes breaking changes in Active Response. Check out our documentation for updates on Blocking attacks with Active Response.
In this post, we will discuss how to blocking attacks using the active response feature in OSSEC. Active response allows OSSEC to run commands on an agent in response to certain triggers. In this example, we simulate an SSH Brute Force attack.
Detecting the attack
First of all, we need to know when to execute the response. We can use one of the following options:
- Rule ID: The response will be executed on any event with the defined ID.
- Rule group: The response will be executed on any event in the defined group.
- Level: The response will be executed on any event with this level or higher.
In our case, we want to prevent SSH brute force attacks so when the rule “5712 – SSHD brute force trying to get access to the system.” is triggered, it will execute the proper active response to block the IP of the attacker.
Defining the command
We know when the active response will be executed, now we have to define what it will do. You can create your own script to block an IP (or any other action) but OSSEC comes with a set of common scripts used in active response. These scripts are in
/var/ossec/active-response/bin/. We are going to use the
firewall-drop.sh script that should work with common Linux/Unix operating systems and it allows blocking of a malicious IP using the local firewall.
Define the command in the
ossec.conf of your OSSEC Manager:
<command> <name>firewall-drop</name> <executable>firewall-drop.sh</executable> <expect>srcip</expect> <timeout_allowed>yes</timeout_allowed> </command>
We set the command name (it will be used in the active response) and the path of the script to execute. If the script needs arguments it must be specified in the field expect. In our case, the script needs to know which IP to block. Remember that the decoders must extract that field in order to function. Finally, it is possible to set a defined timeout to unblock the IP.
Check out the documentation for detailed information about how to create a command.
Defining the active response
Now, we configure OSSEC to run the active response. The main fields are:
command: The command previously defined (firewall-drop).
location: Where the command should be executed. We want execute the command on the agent that reported the event. So, we use local.
rules_id: The command is executed if the rule 5712 is fired.
timeout: Block the IP for 1800 seconds on the firewall (iptables, ipfilter, etc).
Define the active response in the
ossec.conf of your OSSEC Manager:
<active-response> <command>firewall-drop</command> <location>local</location> <rules_id>5712</rules_id> <timeout>1800</timeout> </active-response>
Check out the documentation for more information about how to define an active response.
Restart OSSEC to apply changes.
Proof of concept
We are going to simulate an SSH attack, the attack will be executed from 10.0.0.6 to our agent running on 10.0.0.5.
First, we check if there is connectivity between the attacker and the agent:
[ec2-user@ip-10-0-0-6 ~]$ ping 10.0.0.5 PING 10.0.0.5 (10.0.0.5) 56(84) bytes of data. 64 bytes from 10.0.0.5: icmp_seq=1 ttl=64 time=0.602 ms 64 bytes from 10.0.0.5: icmp_seq=2 ttl=64 time=0.774 ms ^C
Now, we attempt to connect to the agent by SSH several times using an invalid user:
$ ssh 10.0.0.5 Permission denied (publickey). $ ssh 10.0.0.5 Permission denied (publickey). $ ssh 10.0.0.5 Permission denied (publickey). $ ssh 10.0.0.5 Permission denied (publickey). $ ssh 10.0.0.5 Permission denied (publickey). $ ssh 10.0.0.5 Permission denied (publickey). $ ssh 10.0.0.5 Permission denied (publickey). $ ssh 10.0.0.5 Permission denied (publickey).
After 8 attempts, we can see in the Manager how the rule is fired:
$ tail -f /var/ossec/logs/alerts/alerts.log ** Alert 1461258591.68247: mail – syslog,sshd,authentication_failures,pci_dss_11.4,pci_dss_10.2.4,pci_dss_10.2.5, 2016 Apr 21 17:09:51 (LinAgent) 10.0.0.5->/var/log/auth.log Rule: 5712 (level 10) -> ‘SSHD brute force trying to get access to the system.’ Src IP: 10.0.0.6 Apr 21 17:09:49 LinAgent sshd: Invalid user ec2-user from 10.0.0.6 Apr 21 17:09:46 LinAgent sshd: Invalid user ec2-user from 10.0.0.6 Apr 21 17:09:44 LinAgent sshd: Invalid user ec2-user from 10.0.0.6 Apr 21 17:09:44 LinAgent sshd: Invalid user ec2-user from 10.0.0.6 Apr 21 17:09:41 LinAgent sshd: Invalid user ec2-user from 10.0.0.6 Apr 21 17:09:41 LinAgent sshd: Invalid user ec2-user from 10.0.0.6 Apr 21 17:09:40 LinAgent sshd: Invalid user ec2-user from 10.0.0.6 Apr 21 17:09:38 LinAgent sshd: Invalid user ec2-user from 10.0.0.6
If we try to ping the agent from the attacker, we see that it is impossible:
[ec2-user@ip-10-0-0-6 ~]$ ping 10.0.0.5 PING 10.0.0.5 (10.0.0.5) 56(84) bytes of data. ^C --- 10.0.0.5 ping statistics --- 12 packets transmitted, 0 received, 100% packet loss, time 11000ms
Active response has blocked the IP so it is working properly.
Generating an alert when an active response is fired
Every agent has a log file where the active response activities are registered:
$ tail -f /var/ossec/logs/active-responses.log Thu Apr 21 17:09:51 UTC 2016 /var/ossec/active-response/bin/firewall-drop.sh add - 10.0.0.6 1461258591.68247 5712
The Manager does not realize if an active response was fired or not, so we should configure OSSEC to read
active-responses.log. In order to do it, we edit
/var/ossec/etc/shared/agent.conf in the Manager to centralize the configuration of all agents:
<agent_config> <localfile> <log_format>syslog</log_format> <location>/var/ossec/logs/active-responses.log</location> </localfile> </agent_config>
Likely the file
active-responses.log does not exist by default when OSSEC is installed, so it will not read it. You must create the file
/var/ossec/logs/ folder in each agent. Then, restart the Manager and all the agents to apply the changes.
Now, if you reproduce the previous proof of concept simulation, you will see the following alert in Manager:
** Alert 1461260681.76925: – ossec,active_response,pci_dss_11.4, 2016 Apr 21 17:44:41 (LinAgent) 10.0.0.5->/var/ossec/logs/active-responses.log Rule: 601 (level 3) -> ‘Host Blocked by firewall-drop.sh Active Response’ Src IP: 10.0.0.6 Thu Apr 21 17:09:51 UTC 2016 /var/ossec/active-response/bin/firewall-drop.sh add – 10.0.0.6 1461258591.68247 5712
This is possible because rule 601 is defined in
ossec_rules.xml. If you create your own script, you must add the proper rule.
We can also set a list of IP addresses that should never be blocked by the active response. In global section of
ossec.conf in the Manager, use the field
white_list. It allows IP address or netblock.
<ossec_config> <global> <jsonout_output>yes</jsonout_output> <email_notification>no</email_notification> <logall>yes</logall> <white_list>10.0.0.6</white_list> </global>
Increasing blocking time for repeated offenders
We set up a blocking time of 30 minutes for our active response, but in case you need to increase this blocking time for repeated offenders you can add the following configuration in the ossec.conf of each agent:
<active-response> <repeated_offenders>60,120,180</repeated_offenders> </active-response>
The first time that the active response is triggered, it will block for 30 minutes, the second time for 60 minutes, the third time for 120 minutes and finally the fourth time for 180 minutes.
Thanks to active response you can perform actions responding to several scenarios and restricting malicious activities and blocking attacks. Be aware any automated response has an implicit risk, so define your responses carefully.
If you have any questions about how to blocking attacks, join our Slack #community channel! Our team and other contributors will help you.