The organization must document in the Voice Video registration policy the architecture used for registration, the supporting network services and protocols, boundary protection, and authorized registration servers (other than session managers) to register Voice Video endpoints.

From Voice Video Policy Security Technical Implementation Guide

Part of SRG-POL-300043

Associated with: CCI-002164

VVSP-01-000014_rule The organization must document in the Voice Video registration policy the architecture used for registration, the supporting network services and protocols, boundary protection, and authorized registration servers (other than session managers) to register Voice Video endpoints.

Vulnerability discussion

Authentication must not automatically give an entity access to an asset. Authorization procedures and controls must be implemented to ensure that each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Registration authenticates and authorizes Voice Video endpoints with the registration server, which is usually a function of the session manager.For most Voice Video systems (VoIP), registration is the process of centrally recording the user ID, endpoint MAC address, and service/policy profile with two-stage authentication prior to authorizing the establishment of the session and user service. The event of successful registration creates the session record immediately. Video conferencing systems register using a similar process with a gatekeeper. Without enforcing registration, an adversary could impersonate a legitimate device on the Voice Video network.Auto-registration is an automatic means of detecting and registering a Voice Video endpoint on the network with a session manager and then downloading its configuration to the instrument. Auto-registration allows unauthorized instruments to be added or moved without authorization, possibly allowing theft of services or other malicious attack. Configuring the boundary protection to deny registration (port 1719, etc.) is another layer of defense.

Check content

Review the Voice Video registration policy to confirm the policy includes the architecture used for registration, the supporting network services and protocols, boundary protection, and authorized registration servers (other than session managers) to register Voice Video endpoints. The policy must be detailed with drawings, diagrams, or tables making clear the process for registration by the organization. Limitations on enclaves must be clearly identified, with boundary protection deny-all filters for registration protocols and transfer protocols. The supporting network services, such as DHCP and DNS, are typically integrated with the registration process. All ports, protocols, and services used by the registration process must be allowable and documented. If the Voice Video registration policy does not include the architecture used for registration, the supporting network services and protocols, boundary protection, and authorized registration servers (other than session managers) to register Voice Video endpoints, this is a finding.

Fix text

Document the Voice Video registration policy to include the architecture used for registration, the supporting network services and protocols, boundary protection, and authorized registration servers (other than session managers) to register Voice Video endpoints. Include detailed drawings, diagrams, or tables that make clear the process for registration by the organization. Fully document enclave restrictions and limitations, with boundary protection network device deny-all filters for registration protocols and transfer protocols to adjacent LANs, WANs, and transports. Identify Voice Video registration traffic pathways, showing restrictions. The supporting network services, such as DHCP and DNS, are typically integrated with the registration process and must be documented. All ports, protocols, and services used by the registration process must be allowable and documented.

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.

Powered by sagemincer