The FortiGate firewall must generate traffic log entries containing information to establish the network location where the events occurred.
Overview
Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-234137 | FNFG-FW-000030 | SV-234137r628776_rule | Medium |
Description |
---|
Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack.To compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know where events occurred, such as network element components, modules, device identifiers, node names, and functionality. Associating information about where the event occurred within the network provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured network element. |
STIG | Date |
---|---|
Fortinet FortiGate Firewall Security Technical Implementation Guide | 2021-01-29 |
Details
Check Text ( C-37322r611409_chk ) |
---|
Log in to the FortiGate GUI with Super-Admin privilege. 1. Click Log and Report. In addition to System log settings, verify that individual firewall policies are configured with most suitable Logging Options. 1. Click Policy and Objects. If the traffic log events do not contain source and destination IP addresses, or interfaces, this is a finding. |
Fix Text (F-37287r611410_fix) |
---|
This fix can be performed on the FortiGate GUI or on the CLI. Log in to the FortiGate GUI with Super-Admin privilege. 1. Click Log and Report. In addition to these log settings, configure individual firewall policies with the most suitable Logging Options. 1. Click Policy and Objects. or 1. Open a CLI console, via SSH or available from the GUI. The {} indicate the object is defined by the organization policy. |