STIGViewer Support

The Nokia router must be configured to log all packets that have been dropped.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-283898NOKI-RT-000870SV-283898r1203943_ruleCCI-000134low
Description
Auditing and logging are key components of any security architecture. Security personnel must know what is being done or attempted to be done, and by whom, to compile an accurate risk assessment. Auditing the actions on network devices provides a means to recreate an attack or identify a configuration mistake on the device.
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 (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.

MON-01Continuous Monitoring
1.00
MON-01.4System Generated Alerts
1.00
MON-03Content of Event Logs
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (64) 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-16Security and Privacy Attributes
1.00
AC-17(1)Monitoring and Control
1.00
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(3)Mandatory Access Control
1.00
AC-4Information Flow Enforcement
1.00

+54 more (top 10 by confidence shown)

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.3.1
1.00
3.3.2
1.00
CCI1 mapping
NIST CSF 2.00 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.

Who does this work

6 NICE work roles and 5 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-283898r1203943_chk)

Review the IP filter to verify all deny statements are logged. Use the commands below to verify the filter is logged and applied on the interface. - show filter ip 60 Entry : 10 Description : (Not Specified) Log Id : 101 Src. IP : 0.0.0.0/0 Src. Port : n/a Dest. IP : 0.0.0.0/0 Dest. Port : n/a Protocol : Undefined Dscp : Undefined ICMP Type : Undefined ICMP Code : Undefined Fragment : Off Src Route Opt : Off Sampling : Off Int. Sampling : On IP-Option : 0/0 Multiple Option: Off Tcp-flag : (Not Specified) Option-pres : Off Egress PBR : Disabled Primary Action : Drop Ing. Matches : 0 pkts Egr. Matches : 0 pkts - show router interface "TO-PE2" detail | match "Ingress Filter" Egress Filter : 10 Ingress Filter : 10 If packets being dropped are not logged and a filter is not applied, this is a finding.

Fix Text (F-88368r1203942_fix)

Configure an IP filter to log all deny statements using the example below: Create an IP filter: - configure filter ip-filter 60 create - config>filter>ip-filter$ entry 10 create - config>filter>ip-filter>entry$ action drop - config>filter>ip-filter>entry$ log 101 - config>filter>ip-filter>entry$ exit - config>filter>ip-filter$ exit all Apply the IP filter on the interface: - configure router interface "TO-PE2" ingress filter ip 10