OpenControls Logo

STIG Viewer

STIGViewer Support

The FortiGate firewall must protect traffic log records from unauthorized access while in transit to the central audit server.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-234141FNFG-FW-000050SV-234141r835165_ruleCCI-000162medium
Description
Auditing and logging are key components of any security architecture. Logging the actions of specific events provides a means to investigate an attack, recognize resource utilization or capacity thresholds, or identify an improperly configured firewall. Thus, it is imperative that the collected log data be secured and access be restricted to authorized personnel. Methods of protection may include encryption or logical separation. This does not apply to traffic logs generated on behalf of the device itself (management). Some devices store traffic logs separately from the system logs.
STIGDate
Fortinet FortiGate Firewall Security Technical Implementation Guide2025-11-19

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (5) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CFG-02Secure Baseline Configurations
1.00
CRY-01Use of Cryptographic Controls
1.00
DCH-01Data Protection
1.00
IAC-21Least Privilege
1.00
MON-08Protection of Event Logs
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (54) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-10Concurrent Session Control
1.00
AC-17(1)Monitoring and Control
1.00
AC-17(10)Authenticate Remote Commands
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(10)Shared and Group Account Credential Change
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-3(4)Discretionary Access Control
1.00

+44 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.3.8
1.00
CCI1 mapping
CCI-000162
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

PR.DS-10
1.00

Who does this work

7 NICE work roles and 7 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-234141r835165_chk)

Log in to the FortiGate GUI with Super-Admin privileges. 1. Open a CLI console via SSH or from the GUI widget. 2. Run the following command: # show full-configuration log syslogd setting The output should include: set server {123.123.123.123} set mode reliable set enc-algorithm {medium-high | high} If the syslogd mode is not set to reliable, this is a finding. If the set enc-algorithm is not set to high or medium-high, this is a finding.

Fix Text (F-37291r835164_fix)

Log in to the FortiGate GUI with Super-Admin privilege. First, upload the CA certificate that issued the Syslog server certificate. 1. Click System. 2. Click Certificates. 3. Click Import, then CA Certificate. 4. Specify File, and click + Upload. 5. Choose the CA Certificate to upload from the local hard drive. 6. Click OK. Then, configure a TLS-enabled syslog connection: 1. Open a CLI console, via SSH or available from the GUI. 2. Run the following command: # config log syslogd setting # set status enable # set server {SYSLOG SERVER IP ADDRESS} # set mode reliable # set enc-algorithm {HIGH-MEDIUM | HIGH} # set certificate (Optional - Select local certificate if Syslog server is challenging client [FortiGate] for authentication) # end Note: The server IP address must be on the site's management network.