Management traffic is not restricted to only the authorized management packets based on destination and source IP address.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-17754	NET1807	SV-19321r1_rule	ECNK-1	Medium

Description
The Out-of-Band Management (OOBM) network is an IP network used exclusively for the transport of OAM&P data from the network being managed to the OSS components located at the NOC. Its design provides connectivity to each managed network element enabling network management traffic to flow between the managed NEs and the NOC. This allows the use of paths separate from those used by the network being managed. Traffic from the managed network to the management network and vice-versa must be secured via IPSec encapsulation.

Description

The Out-of-Band Management (OOBM) network is an IP network used exclusively for the transport of OAM&P data from the network being managed to the OSS components located at the NOC. Its design provides connectivity to each managed network element enabling network management traffic to flow between the managed NEs and the NOC. This allows the use of paths separate from those used by the network being managed. Traffic from the managed network to the management network and vice-versa must be secured via IPSec encapsulation.

STIG	Date
Infrastructure L3 Switch Secure Technical Implementation Guide - Cisco	2013-10-08

Details

Check Text ( C-20302r1_chk )
Where IPSec technology is deployed to connect the OOBM gateway routers or firewall, the traffic entering the tunnels must be restricted to only the authorized management packets based on destination and source IP address from the address block used for the management network. Verify that all traffic from the managed network to the management network and vice-versa is secured via IPSec encapsulation. In the configuration examples, 10.2.2.0/24 is the management network at the NOC and 10.1.1.0/24 is the management address block used at the network being managed (i.e., the enclave). For Cisco router, the access-list referenced by the crypto map must have the source and destination addresses belonging to the management network address space at the enclave and NOC respectively. hostname OOBM-Gateway1 ! interface Serial1/0 ip address 19.16.1.1 255.255.255.0 description NIPRNet_Link crypto map myvpn interface Fastethernet 0/0 description Enclave_Management_LAN ip address 10.1.1.1 255.255.255.0 ! crypto isakmp policy 1 authentication pre-share lifetime 84600 crypto isakmp key ******* address 19.16.2.1 ! crypto ipsec transform-set toNOC esp-des esp-md5-hmac ! crypto map myvpn 10 ipsec-isakmp set peer 19.16.2.1 set transform-set toNOC match address 101 ! access-list 101 permit ip 10.1.1.0 0.0.0.255 10.2.2.0 0.0.0.255

Check Text ( C-20302r1_chk )

Where IPSec technology is deployed to connect the OOBM gateway routers or firewall, the traffic entering the tunnels must be restricted to only the authorized management packets based on destination and source IP address from the address block used for the management network. Verify that all traffic from the managed network to the management network and vice-versa is secured via IPSec encapsulation. In the configuration examples, 10.2.2.0/24 is the management network at the NOC and 10.1.1.0/24 is the management address block used at the network being managed (i.e., the enclave).

For Cisco router, the access-list referenced by the crypto map must have the source and destination addresses belonging to the management network address space at the enclave and NOC respectively.

hostname OOBM-Gateway1
!
interface Serial1/0
ip address 19.16.1.1 255.255.255.0
description NIPRNet_Link
crypto map myvpn
interface Fastethernet 0/0
description Enclave_Management_LAN
ip address 10.1.1.1 255.255.255.0
!
crypto isakmp policy 1
authentication pre-share
lifetime 84600
crypto isakmp key ******* address 19.16.2.1
!
crypto ipsec transform-set toNOC esp-des esp-md5-hmac
!
crypto map myvpn 10 ipsec-isakmp
set peer 19.16.2.1
set transform-set toNOC
match address 101
!
access-list 101 permit ip 10.1.1.0 0.0.0.255 10.2.2.0 0.0.0.255

Fix Text (F-17652r1_fix)
Where IPSec technology is deployed to connect the OOBM gateway routers or firewall, traffic entering the tunnels is restricted to only the authorized management packets based on destination and source IP address from the address block used for the management network.