-
Cisco Unified CallManager Security Guide, Release 5.0(2)
-
Index
-
Preface
-
Security Overview
-
Using Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS)
-
Configuring the Cisco CTL Client
-
Phone Security Overview
-
Configuring a Phone Security Profile
-
Using the Certificate Authority Proxy Function
-
Configuring Encrypted Phone Configuration Files
-
Configuring Digest Authentication for the SIP Phone
-
Phone Hardening
-
Configuring Voice Messaging Ports for Security
-
Configuring Authentication and Encryption for CTI, JTAPI, and TAPI
-
Configuring a Secure Survivable Remote Site Telephony (SRST) Reference
-
Configuring Encryption for Gateways and Trunks
-
Configuring a SIP Trunk Security Profile
-
Configuring Digest Authentication for the SIP Trunk
-
Troubleshooting
-
Table Of Contents
Configuring Encrypted Phone Configuration Files
Understanding Encryption of the Phone Configuration File
Symmetric Key Encryption with Phone Public Key
Encryption Configuration File Configuration Checklist
Enabling Phone Configuration File Encryption Enterprise Parameters
Configuring Manual Key Distribution
Manual Key Distribution Configuration Settings
Entering the Symmetric Key on the Phone
Using Symmetric Key Encryption with Phone Public Key
Verifying That the Phone Configuration File Is Encrypted
Disabling Encryption for the Phone Configuration Files
Where to Find More Information
Configuring Encrypted Phone Configuration Files
After you configure security-related settings, the phone configuration file contains sensitive configuration information, such as digest passwords and phone administrator passwords. To ensure privacy of the configuration file, you must configure the configuration files for encryption.
This chapter contains information on the following topics:
•
Understanding Encryption of the Phone Configuration File
•
•
•
•
•
•
•
•
•
Understanding Encryption of the Phone Configuration File
To encrypt the phone configuration file, you must enable an enterprise parameter in Cisco Unified CallManager Administration and perform additional tasks in Cisco Unified CallManager Administration. After you enable the parameter and restart required services in Cisco Unified CallManager Serviceability, the TFTP server deletes all clear text configuration files and then generates encrypted versions of the configuration files. If the phone supports encrypted phone configuration files and if you performed the necessary tasks for phone configuration file encryption, the phone requests an encrypted version of the configuration file.
Warning
Some phone models do not support encrypted phone configuration files, as described in the "Supported Phone Models" section. The phone model determines the method that the system uses to encrypt the configuration file; supported methods rely on Cisco Unified CallManager functionality and a firmware load that supports encrypted configuration files. If you downgrade the phone firmware load to a version that does not support encrypted configuration files, the TFTP server offers an unencrypted configuration file that provides minimal configuration settings, and the phone may not perform as expected.
To ensure that you maintain the privacy of the key information, Cisco strongly recommends that you perform the tasks that are associated with encrypted phone configuration files in a secure environment.
Cisco Unified CallManager supports the following methods:
•
The information in the "Manual Key Distribution" and "Symmetric Key Encryption with Phone Public Key" sections assumes that you configured the cluster for Secure Mode and that you enabled the TFTP Encrypted Configuration parameter in Cisco Unified CallManager Administration.
Manual Key Distribution
Tip
With manual key distribution, a 128- or 256-bit symmetric key, which gets entered into the Cisco Unified CallManager database, encrypts the phone configuration file after the phone resets. To determine the key size for your phone model, see the "Supported Phone Models" section.
To update the configuration file, the administrator can either manually enter the key into Cisco Unified CallManager Administration or prompt Cisco Unified CallManager Administration to generate the key. After the key exists in the database, the administrator or user must enter the key into the phone by accessing the user interface on the phone; the phone stores the key in flash as soon as you press the Accept softkey. Once the key is entered, the phone requests an encrypted configuration file after it is reset. After the required tasks occur, the symmetric key uses RC4 or AES 128 encryption algorithms to encrypt the configuration file. To determine which phones use the RC4 or AES 128 encryption algorithms, see the "Supported Phone Models" section.
When the phone contains the symmetric key, the phone requests the encrypted configuration file.The phone downloads the encrypted configuration file, which the TFTP server signs.
The Cisco Unified SIP IP Phone models 7960 and 7940 do not validate the signer of the configuration file.The phone decrypts the file contents by using the symmetric key that is stored in flash. If decryption fails, the configuration file does not get applied to the phone.
Tip
Symmetric Key Encryption with Phone Public Key
Tip
If the phone contains a manufacturing-installed certificate (MIC) or a locally significant certificate (LSC), the phone contains a public and private key pair. If you are using this method for the first time, the phone compares the MD5 hash of the phone certificate in the configuration file to the MD5 hash of the LSC or MIC. If the phone does not identify a problem, the phone requests an encrypted configuration file from the TFTP server after the phone resets. If the phone identifies a problem, for example, the hash does not match, the phone does not contain a certificate, or the MD5 value is blank, the phone attempts to initiate a session with CAPF unless the CAPF authentication mode equals By Authentication String (in which case, you must manually enter the string). CAPF extracts the phone public key from the LSC or MIC, generates a MD5 hash, and stores the values for the public key and certificate hash in the Cisco Unified CallManager database. After the public key gets stored in the database, the phone resets and requests a new configuration file.
After the public key exists in the database and the phone resets, the symmetric key encryption process begins once the database notifies TFTP that the public key exists for the phone. The TFTP server generates a 128-bit symmetric key, which encrypts the configuration file with the Advanced Encryption Standard (AES) 128 encryption algorithm. Then, the phone public key encrypts the symmetric key, which includes in the signed envelope header of the configuration file. The phone validates the file signing, and, if the signature is valid, the phone uses the private key from the LSC or MIC to decrypt the encrypted symmetric key. The symmetric key then decrypts the file contents.
Every time that you update the configuration file, the TFTP server automatically generates a new key to encrypt the file.
Tip
If the TFTP Encrypted Configuration enterprise parameter is enabled but the phone requests an unencrypted configuration file for some reason, the TFTP server offers an unencrypted file that contain minimal configuration settings.
Supported Phone Models
You can encrypt the phone configuration file for the following phone models:
•
The symmetric key uses the RC4 encryption algorithm and a key size of 256 bits.These SIP phone models do not support file signing.
•
The symmetric key uses the Advanced Encryption Standard (AES) 128 encryption algorithm and a key size of 128 bits. These SIP phones receive signed, encrypted configuration files, but ignore the signing information
•
The symmetric key uses the AES 128 encryption algorithm and a key size of 128 bits. These phones support file signing.
Encryption Configuration File Configuration Checklist
To encrypt the phone configuration file, you must perform the tasks in Table 7-1:
Table 7-1 Encryption Configuration File Configuration Checklist
Step 1
Verify that the Cluster Security Mode is configured for Secure Mode.
Step 2
In Cisco Unified CallManager Administration, enable the TFTP Encrypted Configuration enterprise parameter.
Enabling Phone Configuration File Encryption Enterprise Parameters
Step 3
Determine which phones support manual key distribution and which phones support symmetric key encryption with phone public key.
Step 4
If your phone supports manual key distribution, perform the manual key distribution tasks in Cisco Unified CallManager Administration.
•
Step 5
If your phone supports manual key distribution, enter the symmetric key on the phone; reset the phone.
Step 6
If your phone supports the method, symmetric key encryption with phone public key, verify that a manufacture-installed certificate (MIC) or locally significant certificate (LSC) exists in the phone.
•
•
Enabling Phone Configuration File Encryption Enterprise Parameters
Before you can encrypt phone configuration files, you must enable the TFTP Encrypted Configuration enterprise parameter in Cisco Unified CallManager Administration. The TFTP server queries the database when it builds the configuration file. If the enterprise parameter is enabled, the TFTP server builds an encrypted configuration file.
To access the enterprise parameter in Cisco Unified CallManager Administration, choose System > Enterprise Parameters.
For information on the enterprise parameter, including information on the default value, click the TFTP Encrypted Configuration link that displays in the Enterprise Parameters Configuration window.
Configuring Manual Key Distribution
To determine whether your phone supports manual key distribution, see the "Supported Phone Models" section.
To configure manual key distribution, perform the following procedure, which assumes that the phone exists in the Cisco Unified CallManager database, that a compatible firmware load exists on the TFTP server, and that you enabled the TFTP Encrypted Configuration enterprise parameter in Cisco Unified CallManager Administration:
Procedure
Step 1
Step 2
Step 3
Step 4
Additional Information
See the "Related Topics" section.
Manual Key Distribution Configuration Settings
Table 7-2 describes the manual distribution configuration settings in the Phone Configuration window. For related procedures, see the "Related Topics" section.
Entering the Symmetric Key on the Phone
For information on how to enter the symmetric key on the phone after you configure manual key distribution in Cisco Unified CallManager Administration, refer to the Cisco Unified IP Phone administration guide that supports your phone model and protocol.
Using Symmetric Key Encryption with Phone Public Key
To determine whether your phone supports the method, symmetric key encryption with phone public key, see the "Supported Phone Models" section. To use this method, perform the following tasks, which assume that the phone exists in the Cisco Unified CallManager database and that you enabled the TFTP Encrypted Configuration enterprise parameter in Cisco Unified CallManager Administration.
Procedure
Step 1
Step 2
Step 3
Additional Information
See the "Related Topics" section.
Verifying That the Phone Configuration File Is Encrypted
When the phone configuration file is encrypted, it uses the following format:
•
•
•
•
Disabling Encryption for the Phone Configuration Files
To disable encryption for the phone configuration files, you must update the TFTP Encrypted Configuration enterprise parameter in Cisco Unified CallManager Administration.
Warning
After you update the enterprise parameter, the keys for the phone remain in the Cisco Unified CallManager database.
If Cisco Unified IP Phone models 7911, 7941, 7961, 7970, and 7971 request an encrypted file (.enc.sgn file) when the encrypted configuration setting gets updated to false, the phone requests a unencrypted, signed file (.sgn file).
If Cisco Unified IP SIP Phone models 7940/7960/7905/7912 request an encrypted file when the encryption configuration setting gets updated to false, administrators must remove the symmetric key from the phone GUI so that the phone requests an unencrypted configuration file the next time that it is reset.
Tip
Where to Find More Information
Related Topics
•
•
•
•
•
•
•
•
•
•
Related Cisco documentation
•
•
