Firewalls and web servers
Send firewall logs (via syslog to the monitoring probe) and web server logs (with the agent or via syslog) to the SIEM to detect attacks on administration, the VPN and your apps.
On this page
The SIEM reads firewall and web server logs and converts them to the common format: source, destination, user, action, URL, response code. With them it detects brute force against administration or the VPN, configuration changes, alerts from the firewall's IPS and antivirus, and attempts to exploit your web applications (Log4Shell, webshells, SQL injection, PHP remote code execution, among others).
ARGUNIS recognizes each vendor by the log format; you don't have to choose it. ARGUNIS only detects and recommends: it doesn't change your hosts' configuration.
Before you start
The SIEM enabled and Administer permission on Security (SIEM) to include the sources.
For firewalls: a monitoring probe that can reach them over the network.
For web servers with the agent: the ARGUNIS agent for Linux 3.9.0 or later.
Vendors and formats that are read
Vendor | What is read |
|---|---|
Fortinet FortiGate | Default format ( |
Palo Alto Networks (PAN-OS) | CSV: TRAFFIC, THREAT, SYSTEM, CONFIG and GLOBALPROTECT |
Cisco ASA and Firepower (FTD) |
|
Check Point | Log Exporter in syslog, CEF or LEEF format |
SonicWall | Default format: administration, SSL VPN, IPS, antivirus and traffic |
Sophos Firewall | The device's standard format: firewall, IPS, antivirus, web filter and events |
pfSense and OPNsense |
|
MikroTik RouterOS | Login via Winbox, SSH or web, VPN, configuration changes and rules with |
nginx, Apache, IIS and PHP | Access (Combined, Common and default IIS W3C) and errors (error.log and PHP-FPM) |
CEF or LEEF from other vendors that send it is also read.
Firewalls: send syslog to the probe
Step 1: prepare the probe and the host
Turn on syslog reception on the probe (UDP or TCP 514). See Receive syslog and traps on the probe.
The firewall must be a host monitored from that probe. On its page, click Configure and, under Logs and traps, check Receive syslog from this host.
Step 2: point the firewall's syslog to the probe
Use the probe's IP as the syslog server and port 514:
FortiGate: Log & Report → Log Settings → Send logs to syslog, or via CLI:
config log syslogd setting set status enable set server "<IP de la sonda>" set port 514 set format default endPalo Alto: Device → Server Profiles → Syslog (BSD format), then Objects → Log Forwarding for Traffic, Threat and URL, and Device → Log Settings for System, Config and GlobalProtect. Run a Commit.
Cisco ASA:
logging enable logging timestamp logging trap informational logging host <interfaz> <IP de la sonda>On FTD, from FMC: Devices → Platform Settings → Syslog.
Check Point: on the management server (expert mode):
cp_log_export add name argunis target-server <IP de la sonda> target-port 514 protocol udp format syslog cp_log_export restart name argunisSonicWall: Device → Log → Syslog → Add, Default format.
Sophos Firewall: System services → Log settings → Add, Device standard format, and check the modules you want to send.
pfSense: Status → System Logs → Settings → Remote Logging. OPNsense: System → Settings → Logging → Remote.
MikroTik:
/system logging action add name=argunis target=remote remote=<IP de la sonda> remote-port=514 bsd-syslog=yes /system logging add topics=info,!debug action=argunis /system logging add topics=critical action=argunis
Allowed traffic from a heavily used firewall can fill the SIEM's daily event quota. It's best to send denies, the security modules (IPS, antivirus, web filter) and system and VPN events.
Web servers
With the ARGUNIS agent (Linux)
Go to Settings → Monitoring → Agents, open the server's agent and click Configure plugins.
In Files, enter one path per line in Web logs to the SIEM, for example:
/var/log/nginx/access.log /var/log/nginx/error.log /var/log/apache2/access.log /var/log/php8.2-fpm.logClick Save and send.
Every line in those files goes to the SIEM while the SIEM is enabled. The paths must be inside the folders the agent is allowed to read (by default /var/log).
Via syslog to the probe
nginx:
access_log syslog:server=<IP de la sonda>:514,tag=nginx combined;Apache:
ErrorLog syslog:local1and rsyslog forwarding to the probe.IIS: a forwarder (for example NXLog) that sends the default W3C log to the probe.
Include the sources
Go to Security (SIEM) → Sources → SIEM sources.
Find the new sources: "host · syslog (probe …)" for a firewall and "agent · web logs" for a web server.
Click Sample to review a few lines, then Include.
What is detected
Web servers: Log4Shell, path traversal, webshells, SQL injection, XSS, PHP remote code execution (a heuristic that includes PHP2Shell), vulnerability scanners, bursts of 4xx and 5xx errors and bursts of PHP fatal errors. SigmaHQ rules for web servers and proxies also run.
Firewalls: brute force against administration and sign-in after it, administration from a new country, administrator accounts created or changed, configuration changes, brute force, spraying and sign-in on the VPN, critical IPS signatures, malware, bursts of blocks toward a host, port sweeps, firmware and high availability (HA) changes. SigmaHQ rules for FortiGate and firewalls also run.
If the attacked host has an open vulnerability or a firmware or language advisory for the same service (for example, FortiOS with a critical advisory and brute force against its VPN), the detection's severity goes up. High and critical detections open a case with a response playbook.
The PHP remote code execution rule is heuristic: it looks for known PHP exploitation patterns. For PHP2Shell there are no public request indicators yet; with the package's PHP advisories, a detection on a server with vulnerable PHP goes up in severity.