Setup Log Triggers
Last updated
Was this helpful?
Last updated
Was this helpful?
appsec-open protects web servers from attacks. It is possible to trigger a logging event that includes information about the event that was detected or prevented.
Logs can be configured to reach a variety of destinations.
The default setup of appsec-open is already configured with a log trigger, and so, to view logs triggered by open-appsec event detection, no additional action is required.
The default Log Trigger object is configured to log the most interesting events:
Malicious events.
High severity (and above) suspicious events.
Most important identifying data from the request.
In the Quick Actions menu select New Trigger.
Configure a new name to the new trigger object:
Select the conditions in which logs are issued:
Detect/Prevent Events - Logs events caught by appsec-open engines in "Detect" mode or blocked by appsec-open engines in "Prevent" mode in addition to blocking.
Logging all web requests regardless of appsec-open configuration.
Logging all web requests has a substantial impact on resources and network bandwidth consumed by appsec-open.
Select the additional data you want to appear in the log sent upon event.
Additional logging for suspicious events from Severity "X" - Allows conditionally adding the Response Body and Response Code to logs according to the severity of the event reported.
Adding Request Body and Response Body to logs has the potential of substantially impacting the resources and network bandwidth consumed by CloudGuard AppSec, depending on the traffic. For this reason:
The response body is conditional to the severity of the suspicious event.
Either body content will not appear in the log if AppSec blocked the request prior to reading their values (for example, upon blocking a request based on its URL). In the case of response body, it will be logged only if the action is set to "Detect" and not "Prevent" as no response will ever arrive, if the request is blocked.
This configuration determines the destination of the logs sent from the AppSec agent, and multiple options can be selected.
The trigger destination can be:
Gateway/agent - Logging will be saved locally when possible in the folder /var/log/nano_agent.
Syslog service and/or CEF service - Log to an external Syslog/CEF service by adding:
A destination address
Port (Usually 514 in both cases)
Either selecting UDP (common for syslog) or TCP (common for CEF).
Browse to Cloud->Assets and edit the asset you wish to modify.
Go to each of the practices tabs and scroll to the bottom.
Click on the '+' icon next to Triggers and add your new Log Trigger object.
Host name - indicating the host name where the agent is installed
Application name - indicating the nano-service issuing the log.
Device Vendor - Check Point.
Device Product - indicating the nano-service issuing the log.
Event Name - This field will appear in the log structure but is not sent in the key-value pair system.
Severity
Events are sent to open-appsec AppSec cloud to be visible in the .
Cloud - appsec-open Cloud, to be viewed by the appsec-open Application .
Syslog protocol is defined by . The structure starts with a priority value in '<>' followed by a timestamp of the log. The agent will also send a value in the syslog header for:
Following the syslog header there are space delimited key value pairs in the structure of keyname='value'.The possible keys and description can be seen in the documentation page.
CEF protocol is explained . The protocol fields are '|' character delimited and the agent will send the value for:
Following the CEF protocol fields there are space delimited key value pairs in the structure of keyname=value.The possible keys and description can be seen in the documentation page.
