OpenControls Logo

STIG Viewer

STIGViewer Support

The Nokia perimeter router must be configured to deny network traffic by default and allow network traffic by exception.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-283913NOKI-RT-001030SV-283913r1203988_ruleCCI-001109high
Description
A deny-all, permit-by-exception network communications traffic policy ensures that only connections that are essential and approved are allowed. This requirement applies to both inbound and outbound network communications traffic. All inbound and outbound traffic must be denied by default. Firewalls and perimeter routers should only allow traffic through that is explicitly permitted. The initial defense for the internal network is to block any traffic at the perimeter that is attempting to make a connection to a host residing on the internal network. In addition, allowing unknown or undesirable outbound traffic by the firewall or router will establish a state that will permit the return of this undesirable traffic inbound. Satisfies: SRG-NET-000202-RTR-000001, SRG-NET-000019-RTR-000002
STIGDate
Nokia Service Router OS 25.x Router Security Technical Implementation Guide2026-06-15

Related Frameworks

2 mappings 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.

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

+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.

AC-3Access Enforcement
1.00
AC-4Information Flow Enforcement
1.00
AC-6(9)Log Use of Privileged Functions
1.00
AU-12Audit Record Generation
1.00
CM-7Least Functionality
1.00
SC-24Fail in Known State
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(5)Deny by Default — Allow by Exception
1.00
NIST 800-1710 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.

3.1.3
1.00
3.13.6
1.00
CCI2 mappings
CCI-001109
1.00
CCI-001414
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-283913r1203988_chk)

This requirement is not applicable for the DODIN Backbone. Review the router configuration to verify the access control list (ACL) or filter is configured to allow specific ports and protocols and deny all other traffic. 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 : 30 If the filter is not configured to allow specific ports and protocols and deny all other traffic, this is a finding. If the filter is not configured inbound on all external interfaces, this is a finding.

Fix Text (F-88383r1203987_fix)

Configure the Nokia router to enforce approved authorizations for controlling the flow of information between interconnected networks in accordance with applicable policy, as shown in the example below: Create an IPv4 filter: - configure filter ip-filter 30 create - config>filter>ip-filter$ entry 10 create - config>filter>ip-filter>entry$ match protocol "tcp" - 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 20 create - config>filter>ip-filter>entry$ match protocol "tcp" - config>filter>ip-filter>entry>match$ src-ip 10.12.1.9/32 - config>filter>ip-filter>entry>match$ dst-ip 10.12.1.10/30 - config>filter>ip-filter>entry>match$ dst-port 179 eq - 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 30 create - config>filter>ip-filter>entry$ match protocol "tcp" - config>filter>ip-filter>entry>match$ src-ip 10.12.1.9/32 - config>filter>ip-filter>entry>match$ dst-ip 10.12.1.10/32 - config>filter>ip-filter>entry>match$ src-port 179 eq - 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 "icmp" - config>filter>ip-filter>entry>match$ src-ip 10.12.1.9/32 - config>filter>ip-filter>entry>match$ dst-ip 10.12.1.10/32 - config>filter>ip-filter>entry>match$ icmp-type "echo-request" - 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 50 create - config>filter>ip-filter>entry$ match protocol "icmp" - config>filter>ip-filter>entry>match$ src-ip 10.12.1.9/32 - config>filter>ip-filter>entry>match$ dst-ip 10.12.1.10/32 - config>filter>ip-filter>entry>match$ icmp-type "echo-reply" - config>filter>ip-filter>entry$ action forward - config>filter>ip-filter>entry$ exit - config>filter>ip-filter$ entry 60 create - config>filter>ip-filter>entry$ match protocol "tcp" - config>filter>ip-filter>entry>match$ dst-ip 10.12.1.22/32 - config>filter>ip-filter>entry>match$ dst-port 80 eq - 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 30