The organization must implement static IP addresses for Voice Video core components in the dedicated Voice Video IP address space.

From Voice Video Policy Security Technical Implementation Guide

Associated with: CCI-001973

VVSP-01-000093_rule The organization must implement static IP addresses for Voice Video core components in the dedicated Voice Video IP address space.

Vulnerability discussion

Common device identifiers include, for example, media access control (MAC), Internet protocol (IP) addresses, device-unique identifiers, and phone numbers. Preventing reuse of identifiers implies preventing the assignment of previously used identifiers to different devices. For Voice Video systems, the importance of preventing reuse must also consider fire and emergency services (FES) requirements for life safety and Command and Control (C2) requirements mandating communications among top-level officials. Location (PS-ALI) and phone number (ANI) databases are often used with VoIP systems to identify the precise location of a Voice Video endpoint. When endpoints are reused, these databases must also be updated. Adversaries can use improperly maintained databases as a way of mobilizing security and emergency personnel to a faux site to weaken responses in another area.Assigning static IP addresses to the Voice Video core components permits tighter control using Access Control Lists (ACLs) on network infrastructure devices to help in the protection of these devices as a defense-in-depth.

Check content

Review each Voice Video system security plan (SSP). Ensure the organization implements static IP addresses for Voice Video core components in the dedicated Voice Video IP address space. If the organization does not implement static IP addresses for Voice Video core components in the dedicated Voice Video IP address space, this is a finding.

Fix text

Document in each Voice Video SSP the implementation of static IP addresses for Voice Video core components in the dedicated Voice Video IP address space.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.