STIGViewer Support

The Nokia Border Gateway Protocol (BGP) router must be configured to reject route advertisements from CE routers with an originating AS in the AS_PATH attribute that does not belong to that customer.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-283828NOKI-RT-000100SV-283828r1203733_ruleCCI-001368low
Description
Verifying the path a route has traversed will ensure the local AS is not used as a transit network for unauthorized traffic. To ensure the local AS does not carry any prefixes that do not belong to any customers, all Provider Edge (PE) routers must be configured to reject routes with an originating AS other than that belonging to the customer.
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
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.

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-283828r1203733_chk)

This requirement is not applicable for the DODIN Backbone. Review the router configuration to verify the router is configured to deny updates received from CE routers with an originating AS in the AS_PATH attribute that does not belong to that customer. Review the router policy as-path and policy statement, as shown in the example below: - show router policy as-path "accept-65560" as-path "accept-65560" expression "^65560$" - show router policy "Accept-routes" entry 10 from protocol bgp as-path "accept-65560" exit action accept exit exit default-action drop exit Review the import policy, as shown in the example below: - show router bgp neighbor 10.50.10.2 detail | match "Import Policy" Import Policy : Accept-routes If the router is not configured to reject updates from CE routers with an originating AS in the AS_PATH attribute that does not belong to that customer, this is a finding.

Fix Text (F-88298r1203732_fix)

Configure the router to reject updates from CE routers with an originating AS in the AS_PATH attribute that does not belong to that customer. Configure the as-path, as shown in the example below: - configure router policy-options - config>router>policy-options# begin - config>router>policy-options# as-path "accept-65560" - config>router>policy-options>as-path# expression "^65560$" - config>router>policy-options>as-path# - config>router>policy-options>as-path# exit Configure the policy statement, as shown in the example below: - config>router>policy-options# policy-statement "Accept-routes" - config>router>policy-options>policy-statement# entry 10 - config>router>policy-options>policy-statement>entry# from protocol bgp - config>router>policy-options>policy-statement>entry# from as-path "accept-65560" - config>router>policy-options>policy-statement>entry# action accept - config>router>policy-options>policy-statement>entry>action# exit - config>router>policy-options>policy-statement>entry# exit - config>router>policy-options>policy-statement# default-action drop - config>router>policy-options>policy-statement>default-action# exit - config>router>policy-options>policy-statement# exit - config>router>policy-options# commit - config>router>policy-options# exit all Apply the import policy, as shown in the example below: - configure router bgp group "eBGP-65560" import "Accept-routes"