OpenControls Logo

STIG Viewer

STIGViewer Support

The Nokia perimeter router must be configured to filter ingress traffic at the external interface on an inbound direction.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-283906NOKI-RT-000950SV-283906r1203967_ruleCCI-001097medium
Description
Access control lists (ACLs) are used to separate data traffic into traffic that will be routed (permitted packets) and traffic that will not be routed (denied packets). Secure configuration of routers uses access lists for restricting access to services on the router and filtering traffic passing through the router. Inbound versus Outbound: Some operating systems' default access lists are applied to the outbound queue. The more secure solution is to apply the access list to the inbound queue for three reasons: - The router can protect itself before damage is inflicted. - The input port is still known and can be filtered on. - It is more efficient to filter packets before routing them.
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 (18) 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
CRY-01.1Alternate Physical Protection
1.00
CRY-03Transmission Confidentiality
1.00
CRY-04Transmission Integrity
1.00
CRY-05Encrypting Data At Rest
1.00
DCH-01Data Protection
1.00
IAC-21Least Privilege
1.00
MON-01Continuous Monitoring
1.00
MON-01.1Intrusion Detection & Prevention Systems (IDS & IPS)
1.00

+8 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

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

CM-6Configuration Settings
1.00
SC-24Fail in Known State
1.00
SC-47Alternate Communications Paths
1.00
SC-5Denial-of-service Protection
1.00
SC-7Boundary Protection
1.00
SC-7(11)Restrict Incoming Communications Traffic
1.00
SC-7(29)Separate Subnets to Isolate Functions
1.00
SC-7(5)Deny by Default — Allow by Exception
1.00
SI-4System Monitoring
1.00
SI-4(11)Analyze Communications Traffic Anomalies
1.00
NIST 800-1710 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.

3.13.1
1.00
3.13.2
1.00
3.13.5
1.00
CCI1 mapping
CCI-001097
1.00
NIST CSF 2.00 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.

DE.CM-01
1.00
PR.DS-01
1.00
PR.DS-02
1.00
PR.DS-10
1.00
PR.IR-01
1.00

Who does this work

15 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-283906r1203967_chk)

This requirement is not applicable for the DODIN Backbone. Review the router configuration to verify the ingress ACL is bound to the external interface in an inbound direction. To verify all interfaces have the ingress filter assigned, verify fields "Ingress Filter" and "Ingr IPv6 Flt" for all interfaces using the command below: - show router interface "TO-PE2" detail | match "Ingress Filter" Egress Filter : 10 Ingress Filter : 10 - show router interface "TO-PE2" detail | match "Ingr IPv6 Flt" Egr IPv6 Flt : 20 Ingr IPv6 Flt : 20 If the router is not configured to filter traffic entering the network at the external interface in an inbound direction, this is a finding.

Fix Text (F-88376r1203966_fix)

This requirement is not applicable for the DODIN Backbone. Configure an IPv4 filter using the example below: - configure filter ip-filter 10 create - config>filter>ip-filter# entry 10 create - config>filter>ip-filter>entry$ match src-ip 2.2.2.2/32 - config>filter>ip-filter>entry$ action forward - config>filter>ip-filter>entry$ exit all Configure an IPv6 filter using the example below: - configure filter ipv6-filter 20 create - config>filter>ipv6-filter# entry 10 create - config>filter>ipv6-filter>entry$ match src-ip 2001:acad:1234:200::2/128 - config>filter>ipv6-filter>entry$ action forward - config>filter>ipv6-filter>entry$ exit - config>filter>ipv6-filter# exit all Apply the IPv4 and IPv6 filters to the interface in an outbound direction using the configuration below: - configure router interface "TO-PE2" ingress filter ip 10 - configure router interface "TO-PE2" ingress filter ipv6 20