In this section:

Related articles:


The SBC Core supports interfacing with the common certificate pool. The certificates used for HTTPS are exported from the database to the local disk space. The EMA TLS profile enables the selection of a certificate from the pool. The All Perspective allows importing of new certificates. EMA provides a tool to support certificate upload. The Certificate Upload tool is available under PKI object (System > Security > PKI). Once this action item is selected, an external window is directed to the Certificate Upload Servlet. Two types of files, p12 and pem, are supported.

The SBC also supports SHA-256 for certificate verification.


The SBC supports only one certificate in a local or remote certificate file. For example, a p12 certificate file can contain one local certificate and its privacy key.

The user may configure up to three client CA certifications (using separate 'set' commands) for an EMA TLS Profile.

PC Java Configuration supports TLS 1.0 only by default. When EmaTlsProfile v1_0 is disabled, the corresponding Java Configuration for TLS support must be enabled. See below example for Windows environment:

After configuring servercert and clientCACert in EmaTlsProfile, an appropriate value must be configured for clientAuthMethod in OAM > EMA to enable client SSL verification.

To enable TLS support in Windows:

  1. Click Start and enter "Java Control Panel" in the Search field.
  2. Launch the Java Control Panel program.
  3. From the Java Control Panel, select Advanced tab.
  4. Check the "Use TLS 1.1", "Use TLS 1.2", and "Use TLS 1.3" options under Advanced Security Settings section, and click Apply.
  5. Restart your browser for the changes to take effect.


The https interfaces of Embedded Management Application (EMA) and Platform Mode (PM) are vulnerable to the BEAST attack. Secure Sockets Layer (SSL) BEAST attack affects only Transport Layer Security (TLS) version 1.0, and not the later versions.  For further details, refer to the external link http://www.kb.cert.org/vuls/id/864643.

Generally, stream ciphers are not affected by the BEAST attack. However RC4 is the only stream cipher standardized for use with TLS 1.0, and its use is prohibited for TLS with the RFC7465 standards.

For the installation/upgrade process of SBC Core 6.0, the possible scenarios are as follows:

  • If the defaults for TLS 1.0, 1.1 and 1.2 are set, then TLS 1.0 is disabled in the default PM/EMA Tls profile.
  • If the defaults for TLS 1.0, 1.1 and 1.2 are not set, the user-provided configuration is preserved.

If the configuration of the EMA Tls Profile changes from the pre-6.0 defaults, the upgrade process does not attempts to apply the new defaults.

Enabling TLS 1.0 creates security risks, and is strongly advised against. To avoid security loopholes, upgrade to newer browser versions that supports TLS 1.1 and TLS 1.2. Disable TLS 1.0, and enable TLS 1.2 for protection against BEAST attacks.

To View Ema TLS Profile

On the SBC Core main screen, go to Configuration > System Provisioning > Security Configuration > Ema TLS Profile. The Ema TLS Profile window is displayed.

Figure 1: Security Configuration - Ema TLS Profile

To Edit Ema TLS Profile

To edit any of the Ema TLS Profile in the list, click the radio button next to the specific Ema TLS Profile name.

The Edit Selected Ema TLS Profile window is displayed below.

Figure 2: Security Configuration - Ema TLS Profile Edit Window

Make the required changes and click Save at the right hand bottom of the panel to save the changes made.

To Create Ema TLS Profile

To create a new Ema TLS Profile, click New Ema TLS Profile tab on the Ema TLS Profile List panel.

Figure 3: Security Configuration - Ema TLS Profile Fields

The Create New Ema TLS Profile window is displayed.

You can create only one Ema TLS Profile. Once the entry is created, the  button disappears from the panel.

Figure 4: Security Configuration - Ema TLS Profile Create Window

The following fields are displayed:

Table 1: Ema TLS Profile Parameters

ParameterDescription
 NameSpecifies the name of the EMA-TLS profile. 
Auth Client

If this field is set to true, the Ema-TLS client is forced to authenticate itself EMA-TLS. The options are:

  • false
  • true (default)
Server Cert NameSpecifies the name of the server certificate referred by this EMA-TLS profile. 
Ocsp Profile NameSpecifies the name of the OCSP profile referred by this TLS profile. 
V1_0

TLS protocol version 1.0.

  • disabled 
  • enabled (default)
V1_1

TLS protocol version 1.1.

  • disabled (default)
  • enabled
V1_2

TLS protocol version 1.2.

  • disabled (default)
  • enabled
V1_3

TLS protocol version 1.3.

  • disabled (default)
  • enabled

To Delete Ema TLS Profile

To delete any of the created Ema TLS Profile, click the radio button next to the specific Ema TLS Profile which you want to delete.

Click Delete at the end of the highlighted row. A delete confirmation message appears seeking your decision.

Click OK to remove the specific Ema TLS Profile from the list.