OpenControls Logo

STIG Viewer

STIGViewer Support

The Juniper BGP router must be configured to enable the Generalized TTL Security Mechanism (GTSM).

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-217051JUNI-RT-000460SV-217051r855898_ruleCCI-002385low
Description
GTSM is designed to protect a router's IP-based control plane from DoS attacks. Many attacks focused on CPU load and line-card overload can be prevented by implementing GTSM on all Exterior Border Gateway Protocol speaking routers. GTSM is based on the fact that the vast majority of control plane peering is established between adjacent routers; that is, the Exterior Border Gateway Protocol peers are either between connecting interfaces or between loopback interfaces. Since TTL spoofing is considered nearly impossible, a mechanism based on an expected TTL value provides a simple and reasonably robust defense from infrastructure attacks based on forged control plane traffic.
STIGDate
Juniper Router RTR Security Technical Implementation Guide2024-12-05

Related Frameworks

1 mapping across 4 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (13) 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.1Intrusion Detection & Prevention Systems (IDS & IPS)
1.00
MON-01.3Inbound & Outbound Communications Traffic
1.00
MON-01.4System Generated Alerts
1.00
MON-01.8Security Event Monitoring
1.00
NET-01Network Security Controls (NSC)
1.00
NET-02Layered Network Defenses
1.00
SEA-01Secure Engineering Principles
1.00
SEA-02Alignment With Enterprise Architecture
1.00
CAP-01Capacity & Performance Management
0.50

+3 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (36) 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-10Concurrent Session Control
1.00
AC-17(9)Disconnect or Disable Access
1.00
AC-2(4)Automated Audit Actions
1.00
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
AU-3Content of Audit Records
1.00
AU-5Response to Audit Logging Process Failures
1.00
CM-11(2)Software Installation with Privileged Status
1.00

+26 more (top 10 by confidence shown)

CCI1 mapping
CCI-002385
1.00
NIST CSF 2.00 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.

DE.CM-01
1.00
PR.IR-01
1.00
PR.IR-04
0.50

Who does this work

12 NICE work roles and 9 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-217051r855898_chk)

Verify that a filter has been configured to only allow BGP packets with a TTL of 255 as shown in the example below. firewall { … … … filter GTSM_FILTER { term TTL_SECURITY { from { protocol tcp; ttl-except 255; port bgp; } then { syslog; discard; } } term ELSE_ACCEPT { then accept; } } } Verify that the filter is applied to all interfaces connecting to eBGP peers. interfaces { … … … ge-0/0/0 { unit 0 { family inet { filter { input-list [INBOUND_FILTER GTSM_FILTER]; } address x.x.x.x/30; } } } } Configure the router to send all BGP packets with a TTL of 255 as shown in the example below. If the router is not configured to use GTSM for all Exterior Border Gateway Protocol peering sessions, this is a finding.

Fix Text (F-18278r297022_fix)

Configure a filter to only accept bgp packets with a TTL of 255 as shown in the example below. [edit firewall] set filter GTSM_FILTER term TTL_SECURITY from protocol tcp port bgp ttl-except 255 set filter GTSM_FILTER term TTL_SECURITY then syslog discard set filter GTSM_FILTER term ELSE_ACCEPT then accept Apply the firewall filter to the inbound interface for all eBGP single-hop peer as shown in the example below. [edit interfaces ge-0/0/0 unit 0 family inet] set filter input-list INBOUND_FILTER set filter input-list GTSM_FILTER