The Voice Video system design must maintain capability to initiate sessions when the enclave session manager is unavailable.

From Voice Video Policy Security Technical Implementation Guide

Part of SRG-POL-300611

Associated with: CCI-003072

VVSP-01-000146_rule The Voice Video system design must maintain capability to initiate sessions when the enclave session manager is unavailable.

Vulnerability discussion

The information security architecture at the individual information system level must be consistent with and complement the more global, organization-wide information security architecture that is integral to and developed as part of the enterprise architecture. The information security architecture includes an architectural description, the placement/allocation of security functionality (including security controls), security-related information for external interfaces, information being exchanged across the interfaces, and the protection mechanisms associated with each interface.In addition, the security architecture can include other important security-related information, for example, user roles and access privileges assigned to each role; unique security requirements; the types of information processed, stored, and transmitted by the information system; restoration priorities of information and information system services; and any other specific protection needs.Voice Video system services are critical to the effective operation of a business or office or in support or control of a DoD mission. We rely on these services being available in an emergency situation, such as a security breach or life safety event. The ability to place calls to emergency services must be maintained. While the DoD voice and data networks are designed to be extremely reliable, so that continuity of operations (COOP) is supported, there is the potential that Voice Video endpoints could lose availability to communicate with the enclave session manager or multifunction soft switch (MFSS). Natural disasters or damage to network connections or pathways do happen.

Check content

Review site documentation, network diagrams, and design information to confirm the Voice Video system design maintains capability to initiate sessions when the enclave session manager is unavailable. Verify all sites possessing a session manager or MFSS are capable of call/session establishment in the event these become unavailable to Voice Video endpoint signaling requests. At a minimum, Voice Video endpoints must be able to make local internal and local commercial network calls. If the Voice Video system design does not maintain capability to initiate sessions when the enclave session manager is unavailable, this is a finding. NOTE: The minimum capability for placement of precedence calls (line-side or to the DISN) is dependent on the DISN Voice Precedence requirements for the site and should be determined in conjunction with the local command authority. At minimum, the Voice Video system should maintain ROUTINE call placement capabilities.

Fix text

Implement and document the Voice Video system design maintaining capability to initiate sessions when the enclave session manager is unavailable. Any site possessing a session manager (or MFSS with session management portion) must be capable of call/session establishment in the event the session manager becomes unavailable to Voice Video endpoint signaling requests. At a minimum, Voice Video endpoints must be able to make local internal and local commercial network calls. NOTE: The minimum capability for placement of precedence calls (line-side or to the DISN) is dependent on the DISN Voice Precedence requirements for the site and should be determined in conjunction with the local command authority. At minimum, the Voice Video system should maintain ROUTINE call placement capabilities.

Pro Tips

Powered by sagemincer