Suricata, Pfsense and WAZUH
Suricata, Pfsense and WAZUH
Introduction:
In this task, I demonstrated how to set up Suricata in pfsense and push its logs to the Wazuh
dashboard. To accomplish this, I configured pfsense in my environment and performed the
installation and deployment of Wazuh.
Pfsense:
pfsense is an open-source firewall based on FreeBSD. It provides robust network security and
routing features, making it ideal for both small home networks and large enterprise environments.
pfsense offers a user-friendly web interface, advanced networking capabilities, and support for
add-on packages, making it a versatile choice for managing and securing network traffic.
Wazuh:
Wazuh is an open-source SIEM solution offering integrated security monitoring, threat detection,
and compliance management. It supports real-time data analysis across endpoints, servers,
networks, and clouds, enabling robust incident response and regulatory compliance. Wazuh's
scalability, user-friendly interface, and comprehensive documentation cater to diverse
organizational needs, from small businesses to large enterprises seeking heightened IT
infrastructure visibility and security.
Suricata:
Suricata is an open-source intrusion detection system (IDS) and intrusion prevention system (IPS)
that provides network security monitoring. It uses deep packet inspection, pattern matching, and
advanced logging to detect and mitigate threats in real-time. Suricata is highly scalable,
customizable, and integrates well with other security tools.
1. Wazuh:
2. Pfsense:
Deployed an agent on pfsense and ensured it sends logs to Wazuh for monitoring.
Deployment of Suricata:
Configure Suricata in IDS or IPS mode on the desired port to monitor and block traffic. For testing
purposes, I have configured Suricata as IDS on the LAN port and as IPS on the WAN port.
Set the time period for rule updates. How frequently do you want to update the rules.
Managing Rules:
You can view all the rules contained in each category. Additionally, you can enable or disable
rules according to your environment.
After ensuring logs are being saved in the file restart the agent (service wazuh-agent restart)
Alerts on wauzh: