SV-234160r611480_rule
V-234160
SRG-NET-000492-FW-000006
FNFG-FW-000160
CAT II
10
Log in to the FortiGate GUI with Super-Admin privilege.
1. Click Log and Report.
2. Click Log Settings.
3. Configure the Log Settings for Forward Traffic Log to ALL.
4. Click Apply.
In addition to these log settings, configure individual firewall policies with the most suitable Logging Options.
1. Click Policy and Objects.
2. Click IPv4 or IPv6 Policy.
3. For each policy, configure Logging Options for Log Allowed Traffic to log All Sessions (for most verbose logging).
4. Ensure the Enable this policy is toggled to right.
5. Configure the Implicit Deny Policy to Log Violation Traffic.
6. Click OK.
Log in to the FortiGate GUI with Super-Admin privilege.
1. Click Log and Report.
2. Click Log Settings.
3. Verify the Log Settings for Event Logging is configured to ALL.
In addition to System log settings, verify that individual firewall policies are configured with the most suitable Logging Options.
1. Click Policy and Objects.
2. Click IPv4 or IPv6 Policy.
3. Verify all Policy rules are configured with Logging Options set to Log All Sessions (for most verbose logging).
4. Verify the Implicit Deny Policy is configured to Log Violation Traffic.
If the Traffic Log setting is not configured to ALL, and the Implicit Deny Policies are not configured to LOG VIOLATION TRAFFIC, this is a finding.
V-234160
False
FNFG-FW-000160
Log in to the FortiGate GUI with Super-Admin privilege.
1. Click Log and Report.
2. Click Log Settings.
3. Verify the Log Settings for Event Logging is configured to ALL.
In addition to System log settings, verify that individual firewall policies are configured with the most suitable Logging Options.
1. Click Policy and Objects.
2. Click IPv4 or IPv6 Policy.
3. Verify all Policy rules are configured with Logging Options set to Log All Sessions (for most verbose logging).
4. Verify the Implicit Deny Policy is configured to Log Violation Traffic.
If the Traffic Log setting is not configured to ALL, and the Implicit Deny Policies are not configured to LOG VIOLATION TRAFFIC, this is a finding.
M
5258