OpenControls Logo

STIG Viewer

STIGViewer Support

The Nokia perimeter router must be configured to protect an enclave connected to an alternate gateway by using an inbound filter that only permits packets with destination addresses within the site's address space.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-283893NOKI-RT-000790SV-283893r1223374_ruleCCI-001414high
Description
Enclaves with alternate gateway connections must take additional steps to ensure there is no compromise on the enclave network or NIPRNet. Without verifying the destination address of traffic coming from the site's alternate gateway, the perimeter router could be routing transit data from the internet into the NIPRNet. This could also make the perimeter router vulnerable to a denial-of-service attack and provide a back door into the NIPRNet. The DoW enclave must ensure the ingress filter applied to external interfaces on a perimeter router connecting to an approved gateway is secure through filters permitting packets with a destination address belonging to the DoW enclave's address block.
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 (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.

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-5Denial-of-service Protection
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 (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-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-283893r1223374_chk)

This requirement is not applicable for the DODIN Backbone. Review the configuration of each router interface connecting to an alternate gateway. Verify IPv4 and IPv6 filters are applied on the interface using the command below: - show router interface "TO-PE2" detail | match "Ingress Filter" Egress Filter : none Ingress Filter : 10 - show router interface "TO-PE2" detail | match "Ingr IPv6 Flt" Egr IPv6 Flt : none Ingr IPv6 Flt : 80 If the ingress filter permits packets with addresses other than those specified, such as destination addresses of the site's NIPRNet address space or a destination address belonging to the address block assigned by the alternate gateway network service provider, this is a finding.

Fix Text (F-88363r1203927_fix)

This requirement is not applicable for the DODIN Backbone. Configure the ingress filter of the perimeter router connected to an alternate gateway to only permit packets with destination addresses of the site's NIPRNet address space or a destination address belonging to the address block assigned by the alternate gateway network service provider. Create an IPv4 filter using the example below: - configure filter ip-filter 10 - 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 "icmp" - config>filter>ip-filter>entry>match$ src-ip 10.12.1.16/32 - config>filter>ip-filter>entry>match$ dst-ip 10.12.2.17/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 30 create - config>filter>ip-filter>entry$ match protocol "icmp" - config>filter>ip-filter>entry>match$ src-ip 10.12.1.16/32 - config>filter>ip-filter>entry>match$ dst-ip 10.12.2.17/32 - config>filter>ip-filter>entry>match$ icmp-type "echo-reply" - 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 "tcp" - config>filter>ip-filter>entry>match$ dst-ip 10.12.2.17/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# entry 50 create - config>filter>ip-filter>entry$ match dst-ip 10.12.2.17/32 - config>filter>ip-filter>entry>match# dst-port 80 eq - 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 50 - 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 70 create - config>filter>ip-filter>entry# match protocol 51 - 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 Create an IPv6 filter using the example below: - configure filter ipv6-filter 80 create - config>filter>ipv6-filter# entry 10 create - config>filter>ipv6-filter>entry# match next-header "tcp" - config>filter>ipv6-filter>entry>match# tcp-established - config>filter>ipv6-filter>entry>match# exit - config>filter>ipv6-filter>entry# action forward - config>filter>ipv6-filter>entry# exit - config>filter>ipv6-filter# entry 20 create - config>filter>ipv6-filter>entry# match next-header "ipv6-icmp" - config>filter>ipv6-filter>entry>match# dst-ip 2001:acad:1234:50::2/128 - config>filter>ipv6-filter>entry>match# src-ip 2001:acad:1234:50::1/128 - config>filter>ipv6-filter>entry>match#icmp-type echo-request - config>filter>ipv6-filter>entry>match# exit - config>filter>ipv6-filter>entry# action forward - config>filter>ipv6-filter>entry# exit - config>filter>ipv6-filter# entry 30 create - config>filter>ipv6-filter>entry# match next-header "ipv6-icmp" - config>filter>ipv6-filter>entry>match# dst-ip 2001:acad:1234:50::2/128 - config>filter>ipv6-filter>entry>match# src-ip 2001:acad:1234:50::1/128 - config>filter>ipv6-filter>entry>match# icmp-type echo-reply - config>filter>ipv6-filter>entry>match# exit - config>filter>ipv6-filter>entry# action forward - config>filter>ipv6-filter>entry# exit - config>filter>ipv6-filter# entry 40 create - config>filter>ipv6-filter>entry# match next-header "tcp" - config>filter>ipv6-filter>entry>match# dst-ip 2001:acad:1234:50::2/128 - config>filter>ipv6-filter>entry>match# dst-port eq 80 - config>filter>ipv6-filter>entry>match# exit - config>filter>ipv6-filter>entry# action forward - config>filter>ipv6-filter>entry# exit - config>filter>ipv6-filter# entry 50 create - config>filter>ipv6-filter>entry# match next-header "tcp" - config>filter>ipv6-filter>entry>match# dst-ip 2001:acad:1234:50::10/128 - config>filter>ipv6-filter>entry>match# dst-port eq 80 - config>filter>ipv6-filter>entry>match# exit - config>filter>ipv6-filter>entry# action forward - config>filter>ipv6-filter>entry# exit - config>filter>ipv6-filter# entry 60 create - config>filter>ipv6-filter>entry# match next-header 50 - config>filter>ipv6-filter>entry>match# exit - config>filter>ipv6-filter>entry# action forward - config>filter>ipv6-filter>entry# exit - config>filter>ipv6-filter# entry 70 create - config>filter>ipv6-filter>entry# match next-header 51 - config>filter>ipv6-filter>entry>match# exit - config>filter>ipv6-filter>entry# action forward - config>filter>ipv6-filter>entry# exit - config>filter>ipv6-filter# default-action drop - config>filter>ipv6-filter# Apply IPv4 and IPv6 filters on the interface using the example below: - configure router interface "TO-PE2" ingress filter ip 10 - configure router interface "TO-PE2" ingress filter ipv6 80