STIGViewer Support

The FortiGate device must enforce access restrictions associated with changes to the system components.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-234191FGFW-ND-000160SV-234191r961863_ruleCCI-000345medium
Description
Changes to the hardware or software components of the network device can have significant effects on the overall security of the network. Therefore, only qualified and authorized individuals should be allowed administrative access to the network device for implementing any changes or upgrades. This requirement applies to updates of the application files, configuration, ACLs, and policy filters.
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 (3) 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-01Configuration Management Program
1.00
CHG-04Access Restriction For Change
0.50
END-03.2Governing Access Restriction for Change
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (21) 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-2(3)Disable Accounts
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
AU-10Non-repudiation
1.00
AU-9Protection of Audit Information
1.00
CM-11(2)Software Installation with Privileged Status
1.00
CM-5Access Restrictions for Change
1.00
CM-5(1)Automated Access Enforcement and Audit Records
1.00

+11 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.4.5
1.00
CCI1 mapping
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (2) 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.

Who does this work

5 NICE work roles and 5 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-234191r961863_chk)

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

Fix Text (F-37341r628870_fix)

Log in to the FortiGate GUI with Super-Admin privilege. Set one admin profile with full System access. 1. Click System. 2. Click Admin Profiles. 3. Click +Create New (Admin Profile). 4. Assign a meaningful name to the Profile. 5. Set System Access Permissions to Read/Write. 6. Click OK to save this Profile. Then, 1. Click System. 2. Click Administrators. 3. Click on +Create New (Administrator). 4. Configure Administrator settings with unique Username, Type, and Password. 5. While assigning the Administrator Profile, use the Admin profile configured above with limited access to System settings. 6. Go to Restrict login to trusted hosts. 7. Add appropriate IP address in the field Trusted Host 1. 8. Click OK to save. Note: Do not assign this admin profile to any users other than designated administrator that can have full access to System Settings. To limit the System access to existing low-privilege administrators: 1. Click System. 2. Click Administrators. 3. Identify the admin role that has unauthorized access to System settings. 4. Select the admin role and hover over the profile assigned to the role. 5. Click Edit. 6. On System access permission, click None or Read only. 7. Go to Restrict login to trusted hosts. 8. Add appropriate IP address in the field Trusted Host 1. 9. Click OK to save. Repeat this process to define all the Administrators needed to meet privilege separation requirements for the organization.