OpenControls Logo

STIG Viewer

STIGViewer Support

The Nokia router must be configured to assign appropriate user roles or access levels to authenticated users.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-283761NOKI-ND-000100SV-283761r1223367_ruleCCI-000213high
Description
Successful identification and authentication must not automatically give an entity full access to a network device or security domain. The lack of authorization-based access control could result in the immediate compromise of, and unauthorized access to, sensitive information. All DoW systems must be properly configured to incorporate access control methods that do not rely solely on authentication for authorized access. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset or set of resources. Information systems use access control policies and enforcement mechanisms to implement this requirement. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Some network devices are preconfigured with security groups. Other network devices enable operators to create custom security groups with custom permissions. For example, an information system security manager (ISSM) may require read-only access to audit the network device. Operators may create an audit security group, define permissions and access levels for members of the group, and then assign the ISSM's user persona to the audit security group. This is still considered privileged access, but the ISSM's security group is more restrictive than the network administrator's security group. Network devices that rely on Authentication, Authorization, and Accounting (AAA) brokers for authentication and authorization services may need to identify the available security groups or access levels available on the network devices and convey that information to the AAA operator. Once the AAA broker identifies the user persona on the centralized directory service, the user's security group memberships can be retrieved. The AAA operator may need to create a mapping that links target security groups from the directory service to the appropriate security groups or access levels on the network device. Once these mappings are configured, authorizations can happen dynamically based on each user's directory service group membership. Satisfies: SRG-APP-000033-NDM-000212, SRG-APP-000120-NDM-000237, SRG-APP-000121-NDM-000238, SRG-APP-000122-NDM-000239, SRG-APP-000123-NDM-000240, SRG-APP-000231-NDM-000271, SRG-APP-000329-NDM-000287, SRG-APP-000378-NDM-000302, SRG-APP-000380-NDM-000304, SRG-APP-000516-NDM-000335
STIGDate
Nokia Service Router OS 25.x Network Device Management Security Technical Implementation Guide2026-06-15

Related Frameworks

11 mappings across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (37) 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
CFG-02Secure Baseline Configurations
1.00
CHG-04.1Automated Access Enforcement / Auditing
1.00
CRY-01Use of Cryptographic Controls
1.00
CRY-01.1Alternate Physical Protection
1.00
CRY-05Encrypting Data At Rest
1.00
DCH-01Data Protection
1.00
END-01Endpoint Device Management (EDM)
1.00
END-04Malicious Code Protection (Anti-Malware)
1.00
END-06Endpoint File Integrity Monitoring (FIM)
1.00

+27 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (100) 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-16Security and Privacy Attributes
1.00
AC-17(1)Monitoring and Control
1.00
AC-17(10)Authenticate Remote Commands
1.00
AC-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-18(1)Authentication and Encryption
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(10)Shared and Group Account Credential Change
1.00
AC-2(11)Usage Conditions
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00

+90 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (7) 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.1.1
1.00
3.1.2
1.00
3.13.16
1.00
3.3.8
1.00
3.4.1
1.00
3.4.2
1.00
3.4.5
1.00
CCI11 mappings
CCI-000164
1.00
CCI-000213
1.00
CCI-000345
1.00
CCI-000366
1.00
CCI-001199
1.00
CCI-001493
1.00
CCI-001494
1.00
CCI-001495
1.00
CCI-001813
1.00
CCI-002169
1.00

+1 more (top 10 by weight shown)

NIST CSF 2.00 mappings

No source states a mapping between these directly.

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

DE.CM-09
1.00
PR.AA-05
1.00
PR.DS-01
1.00
PR.DS-10
1.00
PR.IR-01
1.00
PR.PS-01
1.00
ID.RA-07
0.50
PR.PSPlatform Security
0.50
PR.PS-05
0.50

Who does this work

19 NICE work roles and 9 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-283761r1223367_chk)

For local accounts, role-based access control is configured through the user profile. Verify the "profile" assigned to each user using the command below: - show system security user <user name> detail - show system security user "admin" detail | match profile profile : administrative In this example, user "admin" is configured with user profile "administrative". Verify the user-assigned profile matches the user roles and responsibilities: - show system security profile <profile name> - show system security profile "administrative" User Profile : administrative Def. Action : permit-all LI : no NETCONF RPC NETCONF Kill RPC Authorization : yes NETCONF Lock RPC Authorization : yes NETCONF Close-Session RPC Authorization : yes NETCONF Get RPC Authorization : yes NETCONF Get-Config RPC Authorization : yes NETCONF Get-Data RPC Authorization : yes NETCONF Edit-Config RPC Authorization : yes NETCONF Copy-Config RPC Authorization : yes NETCONF Delete-Config RPC Authorization : yes NETCONF Discard-Changes RPC Authorization : yes NETCONF Validate RPC Authorization : yes NETCONF Commit RPC Authorization : yes .... For external AAA servers, access levels are available per command. Nokia routers support TACACS+ and RADIUS authentication servers. If the Nokia router does not enforce the assigned privilege level for each administrator and authorizations for access to all commands relative to the privilege level, this is a finding.

Fix Text (F-88231r1203327_fix)

Administrative profiles exist by default. Other profiles should be created based on user roles and access levels. Create a new profile and add as many entries as needed: - configure system security profile <profile name> - default-action <deny-all or permit-all or none or read-only-all> - entry <entry id> - match <command string> - action < permit or deny or read-only or none> Apply the correct profile to each user: - configure system security user <user name> console member <profile name>