An IP-based VTC system implementing a single CODEC supporting conferences on multiple networks having different classification levels must be implemented in a manner such that configuration information for a network having a higher classification level is not disclosed to a network having a lower classification level.

From Video Services Policy STIG

Part of RTS-VTC 7120 [IP]

Associated with IA controls: EBCR-1

SV-55750r1_rule An IP-based VTC system implementing a single CODEC supporting conferences on multiple networks having different classification levels must be implemented in a manner such that configuration information for a network having a higher classification level is not disclosed to a network having a lower classification level.

Vulnerability discussion

Connecting the CODEC to a network while it is being reconfigured could lead to the disclosure of sensitive configuration information for a network having a higher classification level to a network having a lower classification level. Ideally, the CODEC will be disconnected from any network while it is being reconfigured. However, the requirement can be met by using a procedure that purges the configuration for the currently connected network, power cycling the CODEC as required (for a minimum of 60 seconds per another requirement) as the CODEC is switched to the next network, then reconfigures the CODEC for the next session.

Check content

Review the VTC system architecture documentation and observe system operation while transitioning between networks to verify one of the following: • The CODEC is switched to a disconnected/unused switch position while it is being purged/reconfigured . • The CODEC is purged while connected to one network, then power cycled as it is switched to the next network, then reconfigured for that network. • Alternately, if a manual switching procedure is used, ensure the CODEC is physically disconnected from any network while being reconfigured. If none of these procedures is being followed, this is a finding.

Fix text

Architect, implement, and configure the system such that the A/B, A/B/C, or A/B/C/D switch connects the CODEC to an unused switch position while it is being reconfigured during transition from one network to another. OR Architect, implement, and configure the system such that the CODEC configuration is purged before it is switched to the next network, then the CODEC is power cycled for the required time period as the A/B, A/B/C, or A/B/C/D switch connects the CODEC to the next network, then the CODEC is reconfigured for that network. OR If a manual switching procedure is used, physically disconnect the CODEC from any network while it is reconfigured for the next network.

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