Dialogic 4000 SERIES Instrukcja Użytkownika Strona 61

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
  • Strona
    / 168
  • Spis treści
  • BOOKMARKI
  • Oceniono. / 5. Na podstawie oceny klientów
Przeglądanie stron 60
Data Security Overview
Page 61
CHAPTER 6
Data Security Overview
Since version 2.0, Diva SIPcontrol provides additional security options for transmitted and received data:
Secure HTTP: You can use Secure HTTP (HTTPS) to transmit data between the web-based configuration
interface of Diva SIPcontrol and your web browser.
TLS: The Transport Layer Security (TLS) protocol can be used to encrypt and authorize SIP messages.
Secure RTP
: The Secure Real-time Transport Protocol (SRTP) can be used for encrypting the data of the actual
conversation.
Note: The HTTPS and TLS protocols require digital identity Certificates
(e.g., public key certificates).
Secure HTTP
HTTP is a protocol that transmits data between the web-based configuration interface of Diva SIPcontrol and
your web browser. Even though the HTTP interface has access security (via a password), the transmitted data
is not entirely secure. The data is transmitted as clear text and thus it is possible for the transmission to be
intercepted and, in turn, for the data to be read.
HTTPS uses HTTP over an encrypted Secure Sockets Layer (SSL) or Transport Layer Security (TLS) connection
and with a different default port than HTTP.
For example, if a message containing a request to change a password was captured by a third party, the third
party could log on to the Diva SIPcontrol web interface and change the configuration. HTTPS encrypts and
authenticates HTTP data, and thus the data is no longer transmitted as clear text and is not easily readable.
HTTPS requires two actions by the user:
Both Diva SIPcontrol and the computer on which the web browser used to connect to Diva SIPcontrol via
HTTPS is running must be configured with the proper certificate.
When accessing the Diva SIPcontrol web interface, use
https://<IP-address-or-URL-of-Diva-Webserver>:10006/ instead of
http://<IP-address-or-URL-of-Diva-Webserver>:10005/.
TLS
SIP (Session Initiation Protocol) is a signaling protocol used for VoIP calls over the Internet. SIP messages contain
information such as call-party information, call media type, whether it is a secure call, and if so, what encryption
algorithm is used, etc. SIP can be carried by UDP, TCP, or TLS transports. Both UDP and TCP transport data in
clear text. As a result, UDP and TCP can easily be monitored by a third party. TLS, on the other hand, carries
SIP data in a secure way by encrypting the data and authenticating the transport connections. Authentication
helps to ensure that you are talking to the intended peer. For authentication purposes, you need to install
Certificates
, as described in Security Profiles, as described on page 44, and enable TLS as the transport protocol,
as described in Network Interfaces
on page 34.
Secure RTP
Once a Voice over IP (VoIP) call is established, voice data is transported in packets with the Real-time Transport
Protocol (RTP). The voice data can be easily extracted from RTP packets and replayed using commercially
available software. SRTP adds security by encrypting voice data and authenticating packets. Digital identity
certificates are not required, and the parameters are negotiated during call initiation time. SRTP mode is activated
typically in combination with TLS, but in some cases (e.g., testing, intranet connections only) it is useful to allow
SRTP also without TLS being activated.
For encryption and decryption of data, SRTP uses ciphers. The two parties involved in a conversation must be
"compatible" in the sense that each party understands the other party's cipher requirements and supports them.
Diva SIPcontrol supports the following ciphers: DH, ADH, AES (128-256 bits), 3DES (64 bits), DES (64 bits),
RC4 (64bytes), RC4 (256 bytes), MD5, SHA1.
Przeglądanie stron 60
1 2 ... 56 57 58 59 60 61 62 63 64 65 66 ... 167 168

Komentarze do niniejszej Instrukcji

Brak uwag