Perimeter Router Security Technical Implementation Guide

The Perimeter Router Security Technical Implementation Guide (V8 R32) has 132 STIG checks. New to STIG checklists? Read What is a STIG checklist?, CKL vs CKLB, and STIG vs SCAP benchmark.

Find STIG checks

132STIG checks

Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.

Severity

Version

V8 · R32

CurrentPublished Fri Jan 25 2019

Traffic from the managed network is able to access the OOBM gateway router

Perimeter Router Security Technical Implementation Guide

Assessment Title

Rule Text

Traffic from the managed network is able to access the OOBM gateway router

Description

Discussion Text

If the gateway router is not a dedicated device for the OOBM network, several safeguards must be implemented for containment of management and production traffic boundaries. It is imperative that hosts from the managed network are not able to access the OOBM gateway router.

New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.

Objective

V-17817

Rule

SV-19071r2_rule

Severity

medium

Rule Version

NET0987

Documentable

false

IA Controls

NIST SP 800-53

Rev 5

Assessment Procedure

Check Text

Review the ACL or filters for the router’s receive path and verify that only traffic sourced from the management network is allowed to access the router. This would include both management and control plane traffic.

Implementation Procedure

Fix Text

Ensure that traffic from the managed network is not able to access the OOBM gateway router using either receive path or interface ingress ACLs.

STIG check 46 of 132 in the Perimeter Router STIG checklist

← Previous · V-17816The routes from the two IGP domains are redistributed to each other.Next · V-17818 →Traffic from the managed network will leak into the management network via the gateway router interface connected to the OOBM backbone.