The organization must manage Voice Video endpoint certificates by ensuring that authenticators have sufficient strength of mechanism for their intended use.

From Voice Video Policy Security Technical Implementation Guide

Part of SRG-POL-300454

Associated with: CCI-001544

VVSP-01-000101_rule The organization must manage Voice Video endpoint certificates by ensuring that authenticators have sufficient strength of mechanism for their intended use.

Vulnerability discussion

Individual authenticators for Voice Video endpoints are typically PKI certificates. In many cases, developers ship information system components with factory default authentication credentials to allow for initial installation and configuration. Default authentication credentials are often well known, are easily discoverable, and present a significant security risk. For Voice Video systems, the Voice Video endpoints must authenticate as a network device using 802.1X and register with a session manager. Managing the unique certificates for each Voice Video endpoint ensures communications are restricted to only known devices.

Check content

Review the Voice Video system security plan (SSP). Ensure the organization manages Voice Video endpoint certificates by ensuring that authenticators have sufficient strength of mechanism for their intended use. The acceptable authenticators must be documented in the Voice Video SSP. If the organization does not manages Voice Video endpoint certificates by ensuring that authenticators have sufficient strength of mechanism for their intended use, this is a finding. If the organization does not document a whitelist of acceptable authenticators in the Voice Video SSP, this is a finding.

Fix text

Develop and document in the Voice Video SSP a whitelist of acceptable authenticators for the Voice Video system. Document Voice Video endpoint certificates by ensuring that authenticators have sufficient strength of mechanism for their intended use.

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