| V-73077 | | Access to the SDN management and orchestration systems must be authenticated using a FIPS-approved message authentication code algorithm. | The SDN controller receives network service requests from orchestration and management systems to deploy and configure network elements via the northb... |
| V-73083 | | Southbound API management plane traffic for provisioning and configuring virtual network elements within the SDN infrastructure must be authenticated using a FIPS-approved message authentication code algorithm. | Management and orchestration systems within the SDN framework instantiate, deploy, and configure virtual network elements. These systems also define t... |
| V-73085 | | Southbound API management plane traffic for provisioning and configuring virtual network elements within the SDN infrastructure must traverse an out-of-band path or be encrypted using a using a FIPS-validated cryptographic module. | Management and orchestration systems within the SDN framework instantiate, deploy, and configure network elements within the SDN infrastructure. These... |
| V-73087 | | Southbound API management plane traffic for configuring SDN parameters on physical network elements must be authenticated using DOD PKI certificate-based authentication. | Physical SDN-enabled switches are dependent on the SDN controller for their forwarding tables as well as their configuration and service parameters. T... |
| V-73089 | | Southbound API management plane traffic for configuring SDN parameters on physical network elements must be encrypted using a FIPS-validated cryptographic module. | Physical SDN-enabled switches are dependent on the SDN controller for their forwarding tables, as well as their configuration and service parameters. ... |
| V-73091 | | Physical SDN controllers and servers hosting SDN applications must reside within the management network with multiple paths that are secured by a firewall to inspect all ingress traffic. | Management and orchestration systems deploy and configure network devices such as switches and routers, both physical and virtual. SDN controllers are... |
| V-73097 | | SDN controllers must be deployed as clusters and on separate physical hosts to eliminate single point of failure. | SDN relies heavily on control messages between a controller and the forwarding devices for network convergence. The controller uses node and link stat... |
| V-73103 | | Servers hosting SDN controllers must have logging enabled. | It is critical for both network and security personnel to be aware of the state of the SDN infrastructure to maintain network stability. Associating l... |
| V-73105 | | Servers hosting SDN controllers must have an HIDS implemented to detect unauthorized changes. | The SDN controller is the backbone of the SDN infrastructure. If the server hosting the SDN controller is breached or if unauthorized changes are made... |
| V-73107 | | All Virtual Extensible Local Area Network (VXLAN) enabled switches must be configured with the appropriate VXLAN network identifier (VNI) to ensure VMs can send and receive all associated traffic for their Layer 2 domain. | VXLAN is a Layer 2 network that overlays a Layer 3 network; that is, it creates a Layer 2 adjacency across a routed IP fabric. Each Layer 2 overlay ne... |
| V-73109 | | Virtual Extensible Local Area Network (VXLAN) identifiers must be mapped to the appropriate VLAN identifiers. | VXLAN is a Layer 2 network that overlays a Layer 3 network; that is, it creates a Layer 2 adjacency across a routed IP fabric. Each Layer 2 overlay ne... |
| V-73111 | | The proper multicast group for each Virtual Extensible Local Area Network (VXLAN) identifier must be mapped to the appropriate virtual tunnel endpoint (VTEP) so the VTEP will join the associated multicast groups. | VXLAN is a Layer 2 network that overlays a Layer 3 network; that is, it creates a Layer 2 adjacency across a routed IP fabric. Each Layer 2 overlay ne... |
| V-73093 | | SDN-enabled routers and switches must provide link state information to the SDN controller to create new forwarding decisions for the network elements. | Southbound APIs such as OpenFlow provide the forwarding tables to network devices such as switches and routers. SDN controllers have an abstraction of... |
| V-73095 | | Quality of service (QoS) must be implemented on the underlying IP network to provide preferred treatment for traffic between the SDN controllers and SDN-enabled switches and hypervisors. | With the network topology abstraction, the SDN controllers are able to determine how traffic should flow through network devices based on application ... |
| V-73099 | | Physical devices hosting an SDN controller must be connected to two switches for high-availability. | SDN relies heavily on control messages between a controller and the forwarding devices for network convergence. The controller uses node and link stat... |
| V-73101 | | SDN-enabled routers and switches must rate limit the amount of unknown data plane packets that are punted to the SDN controller. | SDN-enabled forwarding devices are dependent on the SDN controller for their forwarding tables as well as their configuration and service parameters. ... |
| V-73113 | | The virtual tunnel endpoint (VTEP) must be dual-homed to two physical network nodes. | If uplink connectivity for the VTEP to the Virtual Extensible Local Area Network (VXLAN) transport network fails, traffic to and from the VM servers r... |
| V-73115 | | A secondary IP address must be specified for the virtual tunnel endpoint (VTEP) loopback interface when Virtual Extensible Local Area Network (VXLAN) enabled switches are deployed as a multi-chassis configuration. | A multi-chassis configuration (i.e., vPC domain, MLAG, MCLAG, etc.) can be used to attach a hypervisor host to a pair of VXLAN-enabled switches. For e... |
| V-73117 | | Two or more edge gateways must be deployed connecting the network virtualization platform (NVP) and the physical network. | An edge gateway is deployed to allow north-south traffic to flow between the virtualized network and the physical network, including destinations outs... |
| V-73119 | | Virtual edge gateways must be deployed across multiple hypervisor hosts. | An edge gateway is deployed to allow north-south traffic to flow between the virtualized network and the physical network, including destinations outs... |
| V-73121 | | The virtual edge gateways must be deployed with routing adjacencies established with two or more physical routers. | An edge gateway is deployed to allow north-south traffic to flow between the virtualized network and the physical network, including destinations outs... |
| V-73073 | | Southbound API control plane traffic between the SDN controller and SDN-enabled network elements must be mutually authenticated using a FIPS-approved message authentication code algorithm. | Southbound APIs such as OpenFlow provide the forwarding tables to network devices such as switches and routers, both physical and virtual (hypervisor-... |
| V-73075 | | Northbound API traffic received by the SDN controller must be authenticated using a FIPS-approved message authentication code algorithm. | The SDN controller determines how traffic should flow through physical and virtual network devices based on application profiles, network infrastructu... |
| V-73079 | | Southbound API control plane traffic must traverse an out-of-band path or be encrypted using a FIPS-validated cryptographic module. | Southbound APIs such as OpenFlow provide the forwarding tables to network devices such as switches and routers, both physical and virtual (hypervisor-... |
| V-73081 | | Northbound API traffic must traverse an out-of-band path or be encrypted using a FIPS-validated cryptographic module. | The SDN controller receives network service requests from orchestration and management systems to deploy and configure network elements via the northb... |
