OpenControls Logo

STIG Viewer

STIGViewer Support

The Nokia router must be configured to enforce approved authorizations for controlling the flow of information within the network based on organization-defined information flow control policies.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-283881NOKI-RT-000630SV-283881r1203892_ruleCCI-001368medium
Description
Information flow control regulates where information is allowed to travel within a network and between interconnected networks. The flow of all network traffic must be monitored and controlled so it does not introduce any unacceptable risk to the network infrastructure or data. Information flow control policies and enforcement mechanisms are commonly employed by organizations to control the flow of information between designated sources and destinations (e.g., networks, individuals, and devices) within information systems. Enforcement occurs, for example, in boundary protection devices (e.g., gateways, routers, guards, encrypted tunnels, and firewalls) that employ rule sets or establish configuration settings that restrict information system services, provide a packet filtering capability based on header information, or provide a message filtering capability based on message content (e.g., implementing key word searches or using document characteristics).
STIGDate
Nokia Service Router OS 25.x Router Security Technical Implementation Guide2026-06-15

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

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

AST-04Network Diagrams & Data Flow Diagrams (DFDs)
1.00
AST-04.2Control Applicability Boundary Graphical Representation
1.00
CFG-02Secure Baseline Configurations
1.00
CRY-01Use of Cryptographic Controls
1.00
DCH-01Data Protection
1.00
DCH-19Geographic Location of Data
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
IAC-21Least Privilege
1.00

+7 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (42) 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(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
AC-6(9)Log Use of Privileged Functions
1.00

+32 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.1.3
1.00
CCI1 mapping
CCI-001368
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (4) 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
ID.AM-03
1.00
PR.DS-10
1.00
PR.IR-01
1.00

Who does this work

18 NICE work roles and 10 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-283881r1203892_chk)

This requirement is not applicable for the DODIN Backbone. Review the router configuration to verify access control lists (ACLs) and filters are configured to allow or deny traffic for specific source and destination addresses as well as ports and protocols. Verify the IPv4 filter is applied on the interface using the command below: - show router interface "TO-PE2" detail | match "Ingress Filter" Egress Filter : none Ingress Filter : 20 If the router is not configured to enforce approved authorizations for controlling the flow of information within the network based on organization-defined information flow control policies, this is a finding.

Fix Text (F-88351r1203891_fix)

This requirement is not applicable for the DODIN Backbone. Configure a filter to allow or deny traffic for specific source and destination addresses as well as ports and protocols, as shown in the example below: Create a port list: - configure filter match-list port-list Filter-Server-Port-list create - config>filter>match-list>port-list$ port 515 - config>filter>match-list>port-list$ port 631 - config>filter>match-list>port-list$ port 9100 - config>filter>match-list>port-list$ exit Create an IPv4 filter: - configure filter ip-filter 20 create - config>filter>ip-filter$ entry 10 create - config>filter>ip-filter>entry$ match protocol "tcp" - config>filter>ip-filter>entry>match$ dst-ip 10.23.1.0/24 - config>filter>ip-filter>entry>match$ dst-port port-list "Filter-Server-Port-list" - config>filter>ip-filter>entry$ action forward - config>filter>ip-filter$ entry 20 create - config>filter>ip-filter>entry$ match protocol "tcp" - config>filter>ip-filter>entry>match$ dst-ip 10.23.2.0/24 - config>filter>ip-filter>entry>match$ dst-port port-list "Filter-Server-Port-list" - config>filter>ip-filter>entry>match$ exit - config>filter>ip-filter>entry$ action forward - config>filter>ip-filter$ entry 30 create - config>filter>ip-filter>entry$ match protocol "icmp" - config>filter>ip-filter>entry>match$ exit - config>filter>ip-filter>entry$ action forward - config>filter>ip-filter>entry$ exit - config>filter>ip-filter$ entry 40 create - config>filter>ip-filter>entry$ match protocol "ospf-igp" - config>filter>ip-filter>entry>match$ exit - config>filter>ip-filter>entry$ action forward - config>filter>ip-filter>entry$ exit - config>filter>ip-filter$ default-action drop - config>filter>ip-filter$ exit all Apply the IPv4 filter on the interface: - configure router interface "TO-PE2" ingress filter ip 20