+V17.2 Media
---+V17.2.1 Verify that the key for the Datagram Transport Layer Security (DTLS) certificate is managed and …
---+V17.2.2 Verify that the media server is configured to use and support approved Datagram Transport Layer …
---+V17.2.3 Verify that Secure Real-time Transport Protocol (SRTP) authentication is checked at the media …
---+V17.2.4 Verify that the media server is able to continue processing incoming media traffic when …
---+V17.2.5 Verify that the media server is able to continue processing incoming media traffic during a flood …
---+V17.2.6 Verify that the media server is not susceptible to the "ClientHello" Race Condition vulnerability …
---+V17.2.7 Verify that any audio or video recording mechanisms associated with the media server are able to …
---+V17.2.8 Verify that the Datagram Transport Layer Security (DTLS) certificate is checked against the Session …

V17.2 Media

These requirements only apply to systems that host their own WebRTC media servers, such as Selective Forwarding Units (SFUs), Multipoint Control Units (MCUs), recording servers, or gateway servers. Media servers handle and distribute media streams, making their security critical to protect communication between peers. Safeguarding media streams is paramount in WebRTC applications to prevent eavesdropping, tampering, and denial-of-service attacks that could compromise user privacy and communication quality.

In particular, it is necessary to implement protections against flood attacks such as rate limiting, validating timestamps, using synchronized clocks to match real-time intervals, and managing buffers to prevent overflow and maintain proper timing. If packets for a particular media session arrive too quickly, excess packets should be dropped. It is also important to protect the system from malformed packets by implementing input validation, safely handling integer overflows, preventing buffer overflows, and employing other robust error-handling techniques.

Systems that rely solely on peer-to-peer media communication between web browsers, without the involvement of intermediate media servers, are excluded from these specific media-related security requirements.

This section refers to the use of Datagram Transport Layer Security (DTLS) in the context of WebRTC. A requirement related to having a documented policy for the management of cryptographic keys can be found in the "Cryptography" chapter. Information on approved cryptographic methods can be found either in the Cryptography Appendix of the ASVS or in documents such as NIST SP 800‑52 Rev. 2 or BSI TR‑02102‑2 (Version 2025‑01).

1. Yleiskatsaus

Otsikko Standardi
V17.2.1 Verify that the key for the Datagram Transport Layer Security (DTLS) certificate is managed and …

Verify that the key for the Datagram Transport Layer Security (DTLS) certificate is managed and protected based on the documented policy for management of cryptographic keys.

V17.2.2 Verify that the media server is configured to use and support approved Datagram Transport Layer …

Verify that the media server is configured to use and support approved Datagram Transport Layer Security (DTLS) cipher suites and a secure protection profile for the DTLS Extension for establishing keys for the Secure Real-time Transport Protocol (DTLS-SRTP).

V17.2.3 Verify that Secure Real-time Transport Protocol (SRTP) authentication is checked at the media …

Verify that Secure Real-time Transport Protocol (SRTP) authentication is checked at the media server to prevent Real-time Transport Protocol (RTP) injection attacks from leading to either a Denial of Service condition or audio or video media insertion into media streams.

V17.2.4 Verify that the media server is able to continue processing incoming media traffic when …

Verify that the media server is able to continue processing incoming media traffic when encountering malformed Secure Real-time Transport Protocol (SRTP) packets.

V17.2.5 Verify that the media server is able to continue processing incoming media traffic during a flood …

Verify that the media server is able to continue processing incoming media traffic during a flood of Secure Real-time Transport Protocol (SRTP) packets from legitimate users.

V17.2.6 Verify that the media server is not susceptible to the "ClientHello" Race Condition vulnerability …

Verify that the media server is not susceptible to the "ClientHello" Race Condition vulnerability in Datagram Transport Layer Security (DTLS) by checking if the media server is publicly known to be vulnerable or by performing the race condition test.

V17.2.7 Verify that any audio or video recording mechanisms associated with the media server are able to …

Verify that any audio or video recording mechanisms associated with the media server are able to continue processing incoming media traffic during a flood of Secure Real-time Transport Protocol (SRTP) packets from legitimate users.

V17.2.8 Verify that the Datagram Transport Layer Security (DTLS) certificate is checked against the Session …

Verify that the Datagram Transport Layer Security (DTLS) certificate is checked against the Session Description Protocol (SDP) fingerprint attribute, terminating the media stream if the check fails, to ensure the authenticity of the media stream.

1.1 Viittaukset

1.2 Tunnistetut vaatimukset

1.3 Liittyvät säädökset

2. Tunnistetut vaatimukset

Vaatimukset
Lähde Vaatimus

3. Liittyvät säädökset

Säädökset
Lähde Sääntely
  • OWASP -

    EN: Publications of the OWASP Foundation, https://owasp.org/. OWASP® is a registered trademark of the OWASP Foundation, Inc.; GRCA is not affiliated with, nor endorsed by, the OWASP Foundation. Only the versions published by OWASP are authoritative.

    DE: Veröffentlichungen der OWASP Foundation, https://owasp.org/. OWASP® ist eine eingetragene Marke der OWASP Foundation, Inc.; GRCA steht in keiner Verbindung zur OWASP Foundation und wird von ihr nicht unterstützt. Maßgeblich sind allein die von OWASP veröffentlichten Fassungen.