Detections
Analytics

FNFG-FW-000015 - The FortiGate firewall must use organization-defined filtering rules that apply to the monitoring of remote access traffic for the traffic from the VPN access points.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

Remote access devices (such as those providing remote access to network devices and information systems) that lack automated capabilities increase risk and make remote user access management difficult at best.

Remote access is access to DoD non-public information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network.

Automated monitoring of remote access sessions allows organizations to detect cyberattacks and ensure ongoing compliance with remote access policies by auditing connection activities of remote access capabilities from a variety of information system components (e.g., servers, workstations, notebook computers, smart phones, and tablets).

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

This fix can be performed on the FortiGate GUI or on the CLI.
Log in to the FortiGate GUI with Super- or Firewall Policy-Admin privilege.

1. Click Policy and Objects.
2. Click IPv4 or IPv6 Policy.
3. Click +Create New to configure new ingress and egress SSL-VPN- or IPSec-VPN-related policies that meet the organization-defined filtering rules.
4. Configure Logging Options to log All Sessions (for most verbose logging).
5. Confirm each created Policy is Enabled.
6. Click OK.

or

1. Open a CLI console, via SSH or available from the GUI.
2. Run the following command:
 # config firewall policy
 # edit 0
 # set srcintf {vpn_interface}
 # set dstintf {interface_1}
 # set srcaddr {address_a}
 # set dstaddr {address_b}
 # set schedule {always}
 # set service {services required by site policy}
 # set action {accept}
 # set logtraffic enable
 # next
 # end
3. Create opposite (ingress or egress) policy as required.

The {} indicate the object is defined by the organization policy.

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_FN_FortiGate_Firewall_Y22M10_STIG.zip

Item Details

References: CAT|II, CCI|CCI-000067, Rule-ID|SV-234134r611402_rule, STIG-ID|FNFG-FW-000015, Vuln-ID|V-234134

Plugin: FortiGate

Control ID: 93c12a328de08ed68e35936e2ec9a870105a0d1f9a5963bc4ab7786337f107f8