Page History

In this section:

Reconfiguration Step Before Enabling FIPS-140-3 Mode

You must disable all trap targets with authPriv/authNoPriv securityLevel.

Example:

admin@sbc1% show oam snmp trapTarget EMS_-10.54.71.176
ipAddress 10.54.71.176;
port 162;
trapType v3;
targetUsername emstrapuser;
targetSecurityLevel authPriv;
state enabled;
admin@sbc1% set oam snmp trapTarget EMS_-10.54.71.176 state disabled
admin@sbc1% commit

Enable FIPS-140-3 mode

The

is compliant with the FIPS 140-3 level 1

for its cryptographic modules. It implements FIPS 140-3 Level 1 validated cryptographic hardware modules and software tool kits and operates this module in FIPS 140-3 approved mode for all cryptographic operations.

The following activities were made to achieve FIPS 140-3 certification:

• Self-Tests – The

  Spacevars
  0 product

  implements cryptographic algorithms using software firmware and hardware and the modules perform various self-tests (power-up self-test, conditional self-test, and critical function self-test) to verify their functionality and correctness. If any of the tests fail, the module goes into “Critical Error” state and it disables all access to cryptographic functions and Critical Security Parameters (CSPs). The management interfaces do not respond to any commands until the module is operational. The Crypto Officer must reboot the modules to clear the error and return to normal operational mode.

  Info
  title Note
  Self-tests are performed only when the system is running in FIPS 140-3 mode.

  The various self-tests are as follows:

  • Power-Up self-tests – The

    Spacevars
    0 product

    performs self-tests at power-up to verify the integrity of the firmware images and the correct operation of the FIPS-approved algorithm implementation in the modules
  • Conditional self-tests – The

    Spacevars
    0 product

    implements conditional self-tests such as Continuous Random Number Generator Tests (CRNGT), RSA Pair-wise Consistency Tests, Firmware Load Tests, and so on.
  • Critical function tests – The

    Spacevars
    0 product

    implements the SP 800-90A CTR_DRBG as it's random number generator. The SP 800-90A specification requires that certain critical functions are conditionally tested to ensure the security of the DRBG. Therefore, the critical function tests are implemented by the cryptographic modules.

• FIPS Finite State Model

• Info
  title Note
  The ability to change the FIPS

• 140-3 mode is reserved only for users having Administrator permissions; the Administrator is a role in the Spacevars 0 product that may be assigned to a Crypto Officer in a FIPS-compliant system.

  
  

• Install/upgrade Software Integrity Check – Software updates or patches to load onto the machine are automatically checked for integrity by validating

  Spacevars
  0 company

   provided signature file for the particular package. (Refer to the install/upgrade guide). A failure in validation causes the installation/upgrade to abort.

• TLS v1.1 and v1.2 support for EMA/PM and SIP/TLS- TLS v1.1 and v1.2 provide resistance to certain known attacks (e.g. the BEAST attack affecting TLS v1.0) against earlier TLS versions and offer additional cipher suites not supported with TLS v1.0.

  Info
  title Note
  Although TLS v1.0 and v1.2 are enabled by default, Spacevars 0 company  recommends disabling v1.0 (if possible) in favor of the more-secure TLS v1.2, if browser support (for EMA/PM) and SIP peer interoperability (for SIP/TLS) considerations permit.

  Include Page
  _EXTMS note for TLS 1.2 _EXTMS note for TLS 1.2

• Configuration database encryption key regeneration support – The System Administrator can cause the encryption keys used to protect sensitive information in the configuration database to regenerate.

• SSH key regeneration support – The System Administrator can regenerate the RSA keys used by the

  Spacevars
  0 product

  to authenticate itself for SFTP and for CLI and netconf over ssh at any time.

• Enabling FIPS-140-3 mode
  The FIPS compliant operating mode is a mode of system operation that is fully compliant with FIPS-140-3 at security level 1+. Putting the system in FIPS-140-3 operating mode requires enabling the fips-140-3 mode parameter as well as configuring other parameters. 
  

  Info
  title Note
  As per FIPS 140-3 standards, Critical Security Parameters (CSPs) are not transferrable from non-FIPS to FIPS mode. So, after enabling FIPS mode, the Operator must install new TLS certificates to set the EMA/PM as operational. Spacevars 0 company  recommends to back up the current encrypted parameters in plain text, if possible, as well as perform a full configuration backup immediately after this action successfully completes.

   

To enable Fips-140-3 mode

1. On the SBC main screen, go to Administration → Users and Application Management → Fips-140-3.
   The Fips-140-3 window opens.

2. In Admin, select the name of the SBC system.
   The Edit Fips-140-3 options open.
   

1. Image Added

   
   

2. Use the Mode option to enable Fips-140-3 mode.

FIPS Mode Security Restrictions

Beginning with SBC Core Release 10.1.6, the following restrictions are applied when you enable the FIPS-140-3 mode:

• The encryption algorithm 3descbc and null are not allowed in the IPSec Profile.
• The integrity hmacmd5 is not allowed in the IPSec Profile.
• The IKE Protection Profile dhGroup modp768, modp1024, and modp1536 are not allowed. You must set the dhGroup to modp2048 or higher.
• The encryption 3descbc is not allowed in the IKE Protection Profile.
• The integrity hmacmd5 is not allowed in the IKE Protection Profile.
• The ciphersuites rsa-with-null-sha, rsa-with-aes-128-cbc-sha, rsa-with-aes-128-cbc-sha-256, rsa-with-aes-256-cbc-sha, rsa-with-aes-256-cbc-sha-256, tls_rsa_with_aes_128_gcm_sha256, tls_rsa_with_aes_256_gcm_sha384, and rsa-with-3des-ede-cbc-sha are not allowed in the DTLS Profiles.
• The ciphersuites rsa-with-null-sha, rsa-with-aes-128-cbc-sha, rsa-with-aes-128-cbc-sha-256, rsa-with-aes-256-cbc-sha, rsa-with-aes-256-cbc-sha-256, tls_rsa_with_aes_128_gcm_sha256, tls_rsa_with_aes_256_gcm_sha384, and rsa-with-3des-ede-cbc-sha are not allowed in the TLS Profiles.
• Disable access to Platform Mode when DoD mode is enabled.
• Since 3DES is not allowed, any P12 certificate created with 3DES certpbe or keypbe is not supported. You must use the non-3DES certpbe and keypbe to import any P12 certificate to the SBC as a local certificate.
  For example, openssl3 pkcs12  -certpbe AES-256-CBC -keypbe AES-256-CBC -export -out cert.p12 -inkey cert.key -in cert.pem -passout pass:password.
• If the p12 certificates are already generated, run the following command to check the generated p12 certificates:
  $FIPS_OPEN_SSL_SH pkcs12 -nodes -in <p12-cert-file-path> -info -password pass:<password>  | grep -i pbe
  Note: Ensure that the output does not contain TripleDES.
• RSA for Key Transport is deprecated in:
  • SipOverTLS
    
  • dTLS ciphers 
    
  • EmaTlsProfile
    
  • rsyslogProfile 
    
  • ConfD keys

Reconfiguration Steps After Enabling FIPS-140-3 Mode

After enabling FIPS-140-3, you must reconfigure the keys (authKey/privKey) for all SNMP users (this applies to all SNMP users for authPriv/authNoPriv security level trap targets).

1. Use the following CLI commands to reconfigure the keys:

   Code Block
   admin@sbc1% set oam snmp users emstrapuser authKey Xd:aa:1f:09:75:6e:f6:da:NN:NN:NN:NN:NN:0d admin@sbc1% set oam snmp users emstrapuser privKey Xd:aa:1f:09:75:6e:f6:da:NN:NN:NN:NN:NN:0d admin@sbc1% commit

   
   

2. Enable the authPriv/authNoPriv trap targets:

   Code Block
   admin@sbc1% set oam snmp trapTarget <trap_target_IP> state enabled