OpenControls Logo

STIG Viewer

STIGViewer Support

The FortiGate device must protect audit information from unauthorized deletion.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-234185FGFW-ND-000130SV-234185r960936_ruleCCI-000164medium
Description
Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity. If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veracity of audit data, the network device must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods, which will depend upon system architecture and design. Some commonly employed methods include: ensuring log files receive the proper file system permissions utilizing file system protections, restricting access, and backing up log data to ensure log data is retained. Network devices providing a user interface to audit data will leverage user permissions and roles identifying the user accessing the data, and the corresponding rights the user enjoys, to make access decisions regarding the deletion of audit data.
STIGDate
Fortinet FortiGate Firewall NDM 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 (51) 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(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(7)Role-based Access Control
1.00
AC-4Information Flow Enforcement
1.00
AC-6(10)Prohibit Non-privileged Users from Executing Privileged Functions
1.00

+41 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-000164
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-234185r960936_chk)

Log in to the FortiGate GUI with Super-Admin privilege. 1. Click System. 2. Click Administrators. 3. Click on each administrator who is not authorized to access Log and Report Settings and hover over the profile assigned to the role. 4. Click Edit. 5. Verify that the permission to Log and Report is set to None or Read. If any low-privileged administrator has Read/Write access to Log and Report, this is a finding.

Fix Text (F-37335r628866_fix)

Log in to the FortiGate GUI with Super-Admin privilege. To limit the Log and Report access to existing low-privileged administrators: 1. Click System. 2. Click Administrators. 3. Identify the admin role that has unauthorized access to Log and Report settings. 4. Select the admin role and hover over the profile assigned to the role. 5. Click Edit. 6. On Log and Report access permission, click None or Read. 7. Click OK to save. Repeat this process to define all the Administrators needed to meet privilege separation requirements for the organization.