OpenControls Logo

STIG Viewer

STIGViewer Support

The FortiGate device must off-load audit records on to a different system or media than the system being audited.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-234181FGFW-ND-000110SV-234181r961860_ruleCCI-001851medium
Description
Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Offloading is a common process in information systems with limited audit storage capacity.
STIGDate
Fortinet FortiGate Firewall NDM Security Technical Implementation Guide2025-11-19

Related Frameworks

1 mapping across 3 frameworks
SCF0 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.

MON-08.1Event Log Backup on Separate Physical Systems / Components
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (34) 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-17(1)Monitoring and Control
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-6(9)Log Use of Privileged Functions
1.00
AU-10Non-repudiation
1.00
AU-12Audit Record Generation
1.00
AU-12(1)System-wide and Time-correlated Audit Trail
1.00
AU-12(3)Changes by Authorized Individuals
1.00
AU-14(1)System Start-up
1.00

+24 more (top 10 by confidence shown)

CCI1 mapping
CCI-001851
1.00

Details

Check Text (C-234181r961860_chk)

Verify remote logging is configured. Via the GUI: Login via the FortiGate GUI with super-admin privileges. - Navigate to Log and Report. - Navigate to Log Settings. - Verify the Remote and Archiving settings. or Via the CLI: Open a CLI console via SSH or from the "CLI Console" button in the GUI. Run the following commands to verify which logging settings are enabled: # show full-configuration log fortianalyzer setting | grep -i 'status\|server' # show full-configuration log fortianalyzer2 setting | grep -i 'status\|server' # show full-configuration log fortianalyzer3 setting | grep -i 'status\|server' # show full-configuration log syslogd setting | grep -i 'status\|server' # show full-configuration log syslogd2 setting | grep -i 'status\|server' # show full-configuration log syslogd3 setting | grep -i 'status\|server' # show full-configuration log syslogd4 setting | grep -i 'status\|server' - The output should indicate enabled and an IP address. If the FortiGate is not logging to a fortianalyzer or syslog server, this is a finding.

Fix Text (F-37331r863253_fix)

Login via the GUI with super-admin privileges. 1. Click Log and Report. 2. Click Log Settings. To add a FortiAnalyzer: - In the Remote Logging and Archiving, enable logging to FortiAnalyzer and provide the IP address. To add a Syslog server: - In the Remote Logging and Archiving, enable Send logs to Syslog and provide the IP address. 3. Apply changes. or 1. Open a CLI console via SSH or from the "CLI Console" button in the GUI. 2. Configure a fortianalyzer or syslog server with the following commands: FortiAnalyzer: # config log fortianalyzer setting # set status enable # set server {IP Address} # set upload-option realtime # end Syslog: # config log syslogd setting # set status enable # set server {IP Address} # set mode reliable # end