STIGhubSTIGhub
STIGhub— A free STIG search and compliance tool·STIGs updated 1 hour ago
Powered by Pylon·Privacy·Terms·Feedback·© 2026 Beacon Cloud Solutions, Inc.
← Back to Nokia Service Router OS 25.x Router Security Technical Implementation Guide

V-283906

CAT II (Medium)

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

Rule ID

SV-283906r1203967_rule

STIG

Nokia Service Router OS 25.x Router Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-001097

Discussion

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.

Check Content

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

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