advertisement
Cisco Unified Communications Manager
Security Guide
Release 8.6(1)
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA http://www.cisco.com
800 553-NETS (6387)
Text Part Number: OL-24964-01
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks . Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Cisco Unified Communications Manager Security Guide for Cisco Unified Communications Manager Business Edition 5000
Copyright © 2011 Cisco Systems, Inc. All rights reserved.
OL-24964-01
C O N T E N T S
Preface
xiii
Security Basics
Security Overview
1-1
1-2
1-5
1-5
1-6
1-7
1-7
1-8
1-9
1-9
Wideband Codecs and Encryption
1-9
Media Resources and Encryption
1-10
1-10
Phone Support and Encrypted Configuration Files
1-10
1-10
Cluster and Device Security Modes
1-11
Digest Authentication and Encryption
1-11
Packet Capturing and Encryption
1-12
1-12
Resetting the Devices, Restarting Services, or Rebooting
1-12
Configuring Media Encryption with Barge
1-13
1-14
1-14
1-14
1-15
1-16
Support for Certificates from External CAs
1-17
Authentication, Integrity, and Authorization Overview
1-17
1-18
1-18
Cisco Unified Communications Manager Security Guide iii
Contents
1-18
1-19
1-19
1-21
1-22
1-22
1-23
1-24
1-24
Configuration Checklist Overview
1-25
Where to Find More Information
1-29
Using Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS)
2-1
2-1
HTTPS for Cisco Unified IP Phone Services
2-2
2-3
2-3
Cisco Unified IP Phone Services Configuration Settings
2-3
Enterprise Parameter Configuration Settings
2-6
Using Internet Explorer 8 to Save the Certificate to the Trusted Folder
2-6
Copying the Certificate to File
2-7
2-8
Using Firefox 3.x to Save the Certificate to the Trusted Folder
2-8
Copying the Certificate to File
2-9
2-10
Using Safari 4.x to Save the Certificate to the Trusted Folder
2-10
Copying the Certificate to File
2-11
Where to Find More Information
2-12
Security by Default
3-1
3-1
3-2
3-2
3-2
3-2
3-3
3-3
3-3
Cisco Unified Communications Manager Security Guide iv OL-24964-01
OL-24964-01
Contents
Supported Cisco Unified IP Phones
3-4
3-4
Regenerating the CAPF Certificate
3-4
Regenerating a TVS Certificate
3-4
Regenerating a TFTP Certificate
3-5
Tomcat certificate regeneration
3-5
Backing Up the System after Regenerating the TFTP Certificate
3-5
Refresh Upgrade from Cisco Unified Communications Manager Release 7.x to Release 8.6 or later
3-6
Rolling Back the Cluster to a Pre-8.0 Release
3-7
Switching Back to Release 8.6 or later
3-8
Migrating IP Phones between Clusters with Cisco Unified Communications Manager 8.0 and ITL
3-8
3-9
Configuring the Cisco CTL Client
4-1
4-2
Important Installation Note for CTL Client 5.0 Plug-In
4-2
Important Installation Note for Windows 2000 Users
4-3
Configuration Tips for Cisco CTL Client Configuration
4-3
Cisco CTL Client Configuration Checklist
4-4
Activating the Cisco CTL Provider Service
4-5
Activating the Cisco CAPF Service
4-6
Configuring Ports for the TLS Connection
4-6
Installing the Cisco CTL Client
4-8
Upgrading the Cisco CTL Client and Migrating the Cisco CTL File
4-10
Configuring the Cisco CTL Client
4-10
4-13
4-15
Updating the Cisco Unified Communications Manager Security Mode
4-15
Cisco CTL Client Configuration Settings
4-15
Verifying the Cisco Unified Communications Manager Security Mode
4-17
Setting the Smart Card Service to Started and Automatic
4-18
Changing the Security Token Password (Etoken)
4-19
Deleting the CTL File on the Cisco Unified IP Phone
4-20
Determining the Cisco CTL Client Version
4-21
Verifying or Uninstalling the Cisco CTL Client
4-21
Cisco Unified Communications Manager Security Guide v
Contents
vi
Where to Find More Information
4-21
Certificate Configuration
5-1
Certificate Configuration Overview
5-1
5-1
Displaying Certificate Configuration
5-2
Security for Cisco Unified IP Phone and Cisco Voice-Messaging Ports
Phone Security Overview
6-1
Understanding How Security Works for Phones
6-1
6-2
6-3
Configure Security for Preferred Vendor SIP Phones
6-3
Configuring Preferred Vendor SIP Phone Security Profile with Per-device Certificates
6-4
Configuring Preferred Vendor SIP Phone Security Profile with Shared Certificates
6-4
Viewing Security Settings on the Phone
6-5
Phone Security Configuration Checklist
6-5
Where to Find More Information
6-6
Configuring a Phone Security Profile
7-1
Phone Security Profile Overview
7-1
Configuration Tips for Phone Security Profiles
7-2
Finding a Phone Security Profile
7-2
Configuring a Phone Security Profile
7-3
Phone Security Profile Configuration Settings
7-4
Applying a Phone Security Profile
7-10
Synchronizing a Phone Security Profile with Affected Phones
7-11
Deleting a Phone Security Profile
7-12
Finding Phones That Use Phone Security Profiles
7-12
Where to Find More Information
7-13
Configuring Secure and Nonsecure Indication Tones
8-1
8-1
8-1
Supported Devices
8-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
OL-24964-01
Important Information About Secure and Nonsecure Indication Tones
8-2
8-3
Configuring Encryption to Analog Endpoints
9-1
9-1
9-1
Using the Certificate Authority Proxy Function
10-1
Certificate Authority Proxy Function Overview
10-1
Cisco Unified IP Phone and CAPF Interaction
10-2
CAPF Interaction with IPv6 Addressing
10-3
CAPF System Interactions and Requirements
10-4
Configuring CAPF in Cisco Unified Serviceability
10-5
10-5
Activating the Certificate Authority Proxy Function Service
10-6
Updating CAPF Service Parameters
10-6
Using CAPF to Install, Upgrade, Troubleshoot, or Delete Certificates from the Phone
10-7
CAPF Settings in the Phone Configuration Window
10-8
Finding Phones on Basis of LSC Status or Authentication String
10-9
10-9
Entering the Authentication String on the Phone
10-10
Verifying the Authentication String on the Phone
10-11
Where to Find More Information
10-11
Configuring Encrypted Phone Configuration Files
11-1
Understanding Encryption of the Phone Configuration File
11-1
11-2
Symmetric Key Encryption with Phone Public Key
11-3
11-4
Configuration Tips for Encrypted Configuration Files
11-4
Encryption Configuration File Configuration Checklist
11-5
Enabling Phone Configuration File Encryption
11-6
Configuring Manual Key Distribution
11-6
Manual Key Distribution Configuration Settings
11-7
Entering the Symmetric Key on the Phone
11-7
Verifying That an LSC or MIC Certificate Is Installed
11-8
Cisco Unified Communications Manager Security Guide
Contents vii
Contents
Verifying That the Phone Configuration File Is Encrypted
11-9
Disabling Encryption for the Phone Configuration Files
11-9
Excluding Digest Credentials from Phone Configuration File Download
11-10
Where to Find More Information
11-10
Configuring Digest Authentication for the SIP Phone
12-1
SIP Phone Digest Authentication Configuration Checklist
12-1
Configuring Digest Authentication Service Parameters
12-2
Configuring Digest Credentials in the End User Configuration Window
12-3
End User Digest Credential Configuration Settings
12-3
Configuring the Digest User in the Phone Configuration Window
12-4
Where to Find More Information
12-4
Phone Hardening
13-1
13-1
13-1
Disabling the PC Voice VLAN Access Setting
13-2
Disabling the Setting Access Setting
13-2
13-2
13-2
Where to Find More Information
13-3
Configuring Secure Conference Resources
14-1
14-1
Conference Bridge Requirements
14-2
14-3
Maintaining a Secure Conference
14-3
Conference List for Ad Hoc Conferences
14-4
Meet-Me Conference with Minimum Security Level
14-5
Cisco Unified IP Phone Support
14-5
14-6
Secure Conference over Trunks and Gateways
14-6
14-6
14-6
14-7
14-7
Cisco Unified Communications Manager Security Guide viii OL-24964-01
OL-24964-01
Contents
Configuration Tips for Securing Conference Resources
14-8
Secure Conference Bridge Configuration Checklist
14-9
Configuring Secure Conference Bridge in Cisco Unified Communications Manager Administration
14-10
Configuring a Minimum Security Level for Meet-Me Conferences
14-11
Configuring Packet Capturing for a Secure Conference Bridge
14-12
Where to Find More Information
14-12
Configuring Voice-Messaging Ports for Security
15-1
Voice-Messaging Security Overview
15-1
Configuration Tips for Voice-Messaging Security
15-2
Secure Voice-Messaging Port Configuration Checklist
15-2
Applying a Security Profile to a Single Voice-Messaging Port
15-3
Applying the Security Profile in the Voice Mail Port Wizard
15-4
Where to Find More Information
15-5
Configuring Secure Call Monitoring and Recording
16-1
Secure Call Monitoring and Recording Overview
16-1
Configuring Secure Call Monitoring and Recording
16-2
Virtual Private Networks for Cisco Unified IP Phones
Configuring Virtual Private Networks
17-1
17-1
17-1
IOS configuration requirements
17-3
Configuring IOS for VPN client on IP phone
17-3
Sample IOS configuration summary
17-5
ASA configuration requirements
17-9
Configuring ASA for VPN client on IP phone
17-9
Sample ASA configuration summary
17-11
Configuring a VPN Gateway
18-1
Uploading VPN Concentrator Certificates
18-1
18-2
18-2
18-3
Cisco Unified Communications Manager Security Guide ix
Contents
Configuring a VPN Group
19-1
19-1
19-2
Configuring a VPN Profile
20-1
20-1
20-1
20-2
VPN Feature Configuration
21-1
21-1
VPN Feature Configuration Parameters
21-1
Security for Cisco CTI, JTAPI, and TAPI Applications
Configuring Authentication and Encryption for CTI, JTAPI, and TAPI
22-1
Understanding Authentication for CTI, JTAPI, and TAPI Applications
22-2
Understanding Encryption for CTI, JTAPI, and TAPI Applications
22-3
CAPF Overview for CTI, JTAPI, and TAPI Applications
22-4
CAPF System Interactions and Requirements for CTI, JTAPI, and TAPI Applications
22-5
Configuration Checklist for Securing CTI, JTAPI, and TAPI
22-5
Adding Application and End Users to the Security-Related Users Groups
22-7
Activating the Certificate Authority Proxy Function Service
22-8
Updating CAPF Service Parameters
22-8
Finding an Application User or End User CAPF Profile
22-9
Configuring the Application User or End User CAPF Profile
22-10
CAPF Settings in the Application User and End User CAPF Profile Windows
22-11
Deleting an Application User CAPF or End User CAPF Profile
22-12
Configuring JTAPI/TAPI Security-Related Service Parameters
22-13
Viewing the Certificate Operation Status for the Application or End User
22-14
Where to Find More Information
22-14
Security for SRST References, Trunks, and Gateways
Configuring a Secure Survivable Remote Site Telephony (SRST) Reference
23-1
Overview for Securing the SRST
23-1
Cisco Unified Communications Manager Security Guide x OL-24964-01
OL-24964-01
Contents
Configuration Tips for Securing the SRST
23-2
Secure SRST Configuration Checklist
23-2
Configuring Secure SRST References
23-3
Security Configuration Settings for SRST References
23-4
Deleting Security from the SRST Reference
23-5
If the SRST Certificate Is Deleted from the Gateway
23-5
Where to Find More Information
23-6
Configuring Encryption for Gateways and Trunks
24-1
Overview for Cisco IOS MGCP Gateway Encryption
24-1
Overview for H.323 Gateway and H.323/H.225/H.245 Trunk Encryption
24-2
Overview for SIP Trunk Encryption
24-3
Secure Gateway and Trunk Configuration Checklist
24-4
Considerations for Configuring IPSec in the Network Infrastructure
24-5
24-5
Configuring the SRTP Allowed Check Box
24-6
Where to Find More Information
24-6
Configuring the SIP Trunk Security Profile
25-1
SIP Trunk Security Profile Overview
25-1
Configuration Tips for SIP Trunk Security Profile
25-1
Finding a SIP Trunk Security Profile
25-2
Configuring the SIP Trunk Security Profile
25-3
SIP Trunk Security Profile Configuration Settings
25-3
Applying a SIP Trunk Security Profile
25-8
Synchronizing a SIP Trunk Security Profile with Affected SIP Trunks
25-9
Deleting a SIP Trunk Security Profile
25-9
Where to Find More Information
25-10
Configuring Digest Authentication for the SIP Trunk
26-1
SIP Trunk Digest Authentication Configuration Checklist
26-1
Configuring Digest Authentication Enterprise Parameters
26-2
Configuring the Digest Credentials in the Application User Configuration Window
26-2
Application User Digest Credential Configuration Settings
26-3
26-3
Cisco Unified Communications Manager Security Guide xi
Contents
26-4
SIP Realm Configuration Settings
26-5
26-5
Where to Find More Information
26-6
Configuring a Cisco Unified Mobility Advantage Server Security Profile
27-1
Cisco Unified Mobility Advantage Server Security Profile Overview
27-1
Finding a Cisco Unified Mobility Advantage Server Security Profile
27-2
Configuring a Cisco Unified Mobility Advantage Server Security Profile
27-2
Cisco Unified Mobility Advantage Server Security Profile Configuration Settings
27-3
Applying a Cisco Unified Mobility Advantage Server Security Profile
27-4
Deleting a Cisco Unified Mobility Advantage Server Security Profile
27-5
Where to Find More Information
27-5
Configuring FIPS 140-2 Mode
28-1
28-1
28-2
28-3
Checking the Status of FIPS 140-2 Mode
28-4
Rebooting a Server in FIPS 140-2 Mode
28-4
xii
Cisco Unified Communications Manager Security Guide
OL-24964-01
Preface
This preface describes the purpose, audience, organization, and conventions of this guide and provides information on how to obtain related documentation.
The preface covers these topics:
•
•
•
•
•
•
Related Documentation, page xvi
Obtaining Documentation, Obtaining Support, and Security Guidelines, page xvii
Purpose
Cisco Unified Communications Manager Security Guide helps system and phone administrators perform the following tasks:
•
•
•
•
•
•
•
Configure authentication.
Configure encryption.
Configure digest authentication.
Install server authentication certificate that is associated with HTTPS
Configure the Cisco CTL Client.
Configure security profiles.
•
•
•
•
Configure Certificate Authority Proxy Function (CAPF) to install, upgrade, or delete locally significant certificates on supported Cisco Unified IP Phone models.
Configure phone hardening.
Configure Survivable Remote Site Telephony (SRST) references for security.
Configure gateways and trunks for security.
Configure FIPS (Federal Information Processing Standard) 140-2 mode.
OL-24964-01
Cisco Unified Communications Manager Security Guide xiii
Preface
Audience
This guide provides a reference and procedural guide for system and phone administrators who plan to configure call security features for Cisco Unified Communications Manager.
Organization
Table 1 lists the major sections of this guide:
Table 1 Guide Overview
Chapter
Security Basics
Description
Chapter 1, “Security Overview”
Chapter 2, “Using Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS)”
Chapter 3, “Security by Default”
Provides an overview of security terminology, system requirements, interactions and restrictions, installation requirements, and a configuration checklist; describes the different types of authentication and encryption.
Provides an overview of HTTPS and describes how to install the server authentication certificate in the trusted folder.
Provides information about the Security by
Default feature, which provides automatic security features for Cisco Unified IP Phones.
Chapter 4, “Configuring the Cisco CTL Client”
Describes how to configure authentication by installing and configuring the Cisco CTL Client.
Chapter 5, “Certificate Configuration”
Describes how to manage certificates in the
Certificate Configuration window.
Security for Phones and Voice Mail Ports
Chapter 6, “Phone Security Overview”
Describes how Cisco Unified Communications
Manager and the phone use security; provides a list of tasks that you perform to configure security for the phone.
Chapter 7, “Configuring a Phone Security
Chapter 8, “Configuring Secure and Nonsecure
Chapter 9, “Configuring Encryption to Analog
Chapter 10, “Using the Certificate Authority
Describes how to configure the security profile and apply it to the phones in Cisco Unified
Communications Manager Administration.
Describes how to configure a phone to play a secure-indication tone.
Describes how to configure a secure SCCP connection to analog endpoints.
Provides an overview of Certificate Authority
Proxy Function and describes how to install, upgrade, delete, or troubleshoot locally significant certificates on supported phones.
xiv
Cisco Unified Communications Manager Security Guide
OL-24964-01
Preface
OL-24964-01
Table 1 Guide Overview (continued)
Chapter
Chapter 11, “Configuring Encrypted Phone
Chapter 12, “Configuring Digest Authentication for the SIP Phone”
Description
Describes how to configure encrypted phone configuration files in Cisco Unified
Communications Manager Administration.
Describes how to configure digest authentication on the phone that is running SIP in Cisco Unified
Communications Manager Administration.
Describes how to tighten the security on the phone by using Cisco Unified Communications Manager
Administration.
Chapter 14, “Configuring Secure Conference
Chapter 15, “Configuring Voice-Messaging Ports for Security”
Describes how to configure media encryption for secure conferences.
Describes how to configure security for voice mail ports in Cisco Unified Communications
Manager Administration.
Chapter 16, “Configuring Secure Call Monitoring and Recording”
Virtual Private Networks for Cisco IP Phones
Describes how to configure secure call monitoring and recording.
Chapter 17, “Configuring Virtual Private
Chapter 18, “Configuring a VPN Gateway”
Chapter 19, “Configuring a VPN Group”
Chapter 20, “Configuring a VPN Profile”
Describes how to configure a virtual private network (VPN).
Describes how to configure a VPN gateway.
Describes how to configure a VPN group.
Describes how to configure a VPN profile.
Describes how to configure a VPN feature.
Chapter 21, “VPN Feature Configuration”
Security for CTI, JTAPI, and TAPI
Chapter 22, “Configuring Authentication and
Encryption for CTI, JTAPI, and TAPI”
Describes how to configure the Application User
CAPF Profile and End User CAPF Profiles in
Cisco Unified Communications Manager
Administration.
Security for SRST References, Gateways, Trunks, and Cisco Unified Mobility Advantage Servers
Chapter 23, “Configuring a Secure Survivable
Remote Site Telephony (SRST) Reference”
Chapter 24, “Configuring Encryption for
Describes how to configure the SRST reference for security in Cisco Unified Communications
Manager Administration.
Describes how Cisco Unified Communications
Manager communicates with a secure gateway or trunk; describes IPSec recommendations and considerations.
Chapter 25, “Configuring the SIP Trunk Security
Describes how to configure and apply the SIP trunk security profile in Cisco Unified
Communications Manager Administration.
Chapter 26, “Configuring Digest Authentication for the SIP Trunk”
Describes how to configure digest authentication for the SIP trunk in Cisco Unified
Communications Manager Administration.
Cisco Unified Communications Manager Security Guide xv
Preface
Table 1 Guide Overview (continued)
Chapter
Chapter 27, “Configuring a Cisco Unified
Mobility Advantage Server Security Profile”
Chapter 28, “Configuring FIPS 140-2 Mode”
Description
Describes how to configure a Cisco Unified
Mobility Advantage server security profile in
Cisco Unified Communications Manager
Administration.
Describes how to configure FIPS (Federal
Information Processing Standard) 140-2 mode in
Cisco Unified Communications Manager
Administration.
Related Documentation
•
•
•
Each chapter contains a list of related documentation for the chapter topic.
Refer to the following documents for further information about related Cisco IP telephony applications and products:
•
Cisco Unified IP Phone Administration Guide for Cisco Unified Communications Manager
Media and Signaling Authentication and Encryption Feature for Cisco IOS MGCP Gateways
Cisco Unified Communications Manager Integration Guide for Cisco Unity
•
Cisco Unified Communications Manager Integration Guide for Cisco Unity Connection
Cisco Unified Survivable Remote Site Telephony (SRST) administration documentation that supports the SRST-enabled gateway
•
The firmware release notes that support your phone model
Conventions
Notes use the following conventions:
Note
Means reader take note. Notes contain helpful suggestions or references to material not covered in the publication.
Tips use the following conventions:
Tip
Means
the following are useful tips.
Cautions use the following conventions:
Caution
Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.
xvi
Cisco Unified Communications Manager Security Guide
OL-24964-01
Preface
Obtaining Documentation, Obtaining Support, and Security
Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly
What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Cisco Product Security Overview
This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately.
Further information regarding U.S. export regulations may be found at http://www.access.gpo.gov/bis/ear/ear_data.html
.
OL-24964-01
Cisco Unified Communications Manager Security Guide xvii
Preface xviii
Cisco Unified Communications Manager Security Guide
OL-24964-01
P
A R T I
Security Basics
OL-24964-01
C H A P T E R
1
Security Overview
Implementing security mechanisms in the Cisco Unified Communications Manager system prevents identity theft of the phones and the Cisco Unified Communications Manager server, data tampering, and call-signaling/media-stream tampering.
The Cisco IP telephony network establishes and maintains authenticated communication streams, digitally signs files before transferring the file to the phone, and encrypts media streams and call signaling between Cisco Unified IP Phones.
This chapter provides information on the following topics:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Interactions and Restrictions, page 1-7
Authentication, Integrity, and Authorization Overview, page 1-17
Encryption Overview, page 1-22
Running an NMAP Scan, page 1-24
Configuration Checklist Overview, page 1-25
Where to Find More Information, page 1-29
Cisco Unified Communications Manager Security Guide
1-1
Chapter 1 Security Overview
Terms and Acronyms
Terms and Acronyms
The definitions in
Table 1-1 apply when you configure authentication, encryption, and other security
features for your Cisco IP telephony network:
Table 1-1 Terminology
Term Definition
Access Control List (ACL) List that defines rights and permissions to access system functions and resources. See Method List.
Authentication
Authorization
Process that verifies the identity of the communicating entity.
Process that specifies whether an authenticated user, service, or application has the necessary permissions to perform a requested action; in
Cisco Unified Communications Manager, the security process that restricts certain trunk-side SIP requests to authorized users.
Authorization Header
Certificate
A SIP user agent response to a challenge.
A message that contains the certificate holder name, the public key, and the digital signature of the certificate authority that is issuing the certificate.
Certificate Authority (CA) Trusted entity that issues certificates: Cisco or a third-party entity.
Certificate Authority Proxy
Function (CAPF)
Process by which supported devices can request locally significant certificates by using Cisco Unified Communications Manager
Administration.
Certificate Trust List (CTL) A file, which is created with the CTL Client and signed by the Cisco Site
Administrator Security Token (security token), that contains a list of certificates for servers that the phone is to trust.
Challenge In digest authentication, a request to a SIP user agent to authenticate its identity.
Cisco Site Administrator
Security Token (security token; etoken)
Device Authentication
A portable hardware security module that contains a private key and an
X.509v3 certificate that the Cisco Certificate Authority signs; used for file authentication, it signs the CTL file.
Process that validates the identity of the device and ensures that the entity is what it claims to be before a connection is made.
Digest Authentication A form of device authentication where an MD5 hash of a shared password
(among other things) gets used to establish the identity of a SIP user agent
.
Digest User
Digital Signature
DSP
DSP Farm
User name that is included in an authorization request that phones that are running SIP or SIP trunks send.
Value that is generated by hashing the message and then encrypting the message with the private key of the signer; the recipient decrypts the message and the hash with the signer public key, produces another hash with the same hash function, then compares the two hashes to ensure that the messages match and the content is intact.
Digital signaling processor.
A network resource for IP telephony conferencing that is provided by
DSPs on a H.323 or MGCP gateway.
1-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 1 Security Overview
Terms and Acronyms
Table 1-1 Terminology (continued)
Term
Encryption
File Authentication
H.323
hash
Hypertext Transfer
Protocol over Secure
Sockets Layer (HTTPS)
Definition
Process of translating data into ciphertext, which ensures the confidentiality of the information and that only the intended recipient can read the data. Requires an encryption algorithm and encryption key.
Process that validates digitally signed files that the phone downloads.
The phone validates the signature to make sure that file tampering did not occur after the file creation.
An internet standard that defines a common set of codecs, call setup and negotiating procedures, and basic data transport methods.
A number, usually in hexadecimal, that is generated from a string of text by using a hash function, which creates a small digital “fingerprint” for the data.
An IETF-defined protocol that ensures (at a minimum) the identity of the HTTPS server; by using encryption, ensures the confidentiality of the information that is exchanged between the Tomcat server and the browser client.
Image Authentication Process whereby a phone validates the integrity and source of a binary image prior to loading it on the phone.
Process that ensures that data tampering did not occur between entities.
Integrity
IPSec
Locally Significant
Certificate (LSC)
Manufacture Installed
Certificate (MIC)
Transport that provides secure H.225, H.245, and RAS signaling channels for end-to-end security.
A digital X.509v3 certificate that CAPF issues; installed on the phone or JTAPI/TAPI/CTI application.
A digital X.509v3 certificate that is signed by the Cisco Certificate
Authority and installed in supported phones by Cisco Manufacturing; used as the authentication mechanism to CAPF when LSCs are installed in phones.
Man-in-the-Middle Attacks Process that allows an attacker to observe and modify the information flow between Cisco Unified Communications Manager and the phone.
Multipoint Control Unit
(MCU)
MD5
Media Encryption
A flexible system to connect multiple H.323 endpoints and allow multiple users to participate in IP-based video conferences.
A hash function that is used with encryption.
Process whereby the confidentiality of the media is protected with cryptographic procedures. Media encryption uses Secure Real-Time
Protocol (SRTP) as defined in IETF RFC 3711.
Message/Data Tampering Event when an attacker attempts to alter messages in transit, including ending a call prematurely.
Method List
Mixed Mode
Tool to restrict certain categories of messages that can come in on a SIP trunk during the authorization process; defines which SIP nonINVITE methods are allowed for a trunk-side application or device. Also method
ACL.
Cisco Unified Communications Manager security mode that you configure to allow devices with secure/nonsecure profiles and RTP/
SRTP media to connect to Cisco Unified Communications Manager.
OL-24964-01
Cisco Unified Communications Manager Security Guide
1-3
Chapter 1 Security Overview
Terms and Acronyms
Table 1-1
Term
Nonce
Nonsecure Mode
Nonsecure Call
Nonsecure Device
PKI
Public / Private key
Replay Attack
RTP
System Administrator
Security Token (SAST)
Simple Certificate
Enrollment Protocol
(SCEP)
Secure Call
SIP Realm
SRTP
SSL
Transport Layer Security
(TLS)
Trust List
Trust Store
X.509
Terminology (continued)
Signaling Authentication
Signaling Encryption
Definition
A unique, random number that the server generates for each digest authentication request; used to generate an MD5 hash.
Cisco Unified Communications Manager security mode that you configure to allow devices with nonsecure profiles and RTP media to connect to Cisco Unified Communications Manager.
Call in which at least one device is not authenticated or encrypted.
Device that uses UDP or TCP signaling and nonsecure media.
Public key infrastructure, which comprises the set of elements that is needed for public key encryption, including secure public key distribution, certificates, and certificate authorities.
Keys that are used in encryption. Public keys are widely available, but private keys are held by their respective owners. Asymmetrical encryption combines both types.
Event when an attacker captures information that identifies a phone or proxy server and replays information while pretending to be the actual device; for example, by impersonating the proxy server private key.
Real-Time Transport Protocol
In CTI/JTAPI/TAPI applications, a token that is used to sign the CTL file for CTL download.
A protocol that is used to communicate with a certificate authority that issues X.509 certificates.
Call in which all devices are authenticated, signaling is encrypted, and the media (voice stream) is encrypted.
TLS process that validates that no tampering occurred to signaling packets during transmission.
Process that uses cryptographic methods to protect the confidentiality of all signaling messages that are sent between the device and the Cisco
Unified Communications Manager server.
A string (name) that Cisco Unified Communications Manager uses to respond to a challenge.
Secure Real-Time Transport Protocol that secures voice conversation in the network and provides protection against replay attacks.
A cryptographic protocol that secures data communications such as e-mail on the Internet; equivalent to TLS, its successor.
A cryptographic protocol that secures data communications such as e-mail on the Internet; functionally equivalent to SSL.
Certificate list without digital signatures.
A repository of X.509 certificates that an application, such as Cisco
Unified Communications Manager, explicitly trusts.
An ITU-T cryptographic standard for importing PKI certificates, which includes certificate formats.
1-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 1 Security Overview
System Requirements
System Requirements
The following system requirements exist for authentication or encryption:
•
Cisco Unified Communications Manager Release 6.1 serves as the minimum requirement for the security features that this document describes.
•
•
The Administrator password can differ on every server in a cluster.
The username and password that are used at the Cisco CTL client (to log in to the Cisco Unified
Communications Manager server) must match the Cisco Unified Communications Manager
Administration username and password (the username and password that are used to log in to Cisco
Unified Communications Manager Administration).
•
•
LSCs exist in all phones to authenticate the TLS connection with Cisco Unified Communications
Manager. For Certificate Authority Proxy Function (CAPF) information, see
Interactions and Requirements” section on page 10-4
.
Before you configure voice mail ports for security, verify that you installed a version of Cisco Unity or Cisco Unity Connection system that supports this Cisco Unified Communications Manager release.
.
Features List
Cisco Unified Communications Manager system uses a multilayered approach to call security, from the transport layer to the application layer.
Transport layer security includes TLS and IPSec for signaling authentication and encryption to control and prevent access to the voice domain. SRTP adds media authentication and encryption to secure privacy and confidentiality for voice conversation and other media.
provides a summary of the authentication and encryption features that Cisco Unified
Communications Manager can implement during an SCCP call session, depending on the features that are supported and configured.
Table 1-2 SCCP Call Security Features
Security Feature Line Side
Transport/Connection/Integrity Secure TLS port
Device Authentication
Signaling
Authentication/Encryption
Media Encryption
Authorization
TLS certificate exchange w/Cisco Unified
Communications Manager and/or CAPF
TLS Mode: authenticated or encrypted
SRTP
Presence requests
Note: Supported features on a device vary by device type.
Trunk Side
IPSec associations
IPSec certificate exchange or preshared key
IPSec [authentication header, encryption (ESP), or both]
SRTP
Presence requests
provides a summary of the authentication and encryption features that Cisco Unified
Communications Manager can implement during a SIP call session, depending on the features that are supported and configured.
Cisco Unified Communications Manager Security Guide
OL-24964-01 1-5
Security Icons
Chapter 1 Security Overview
Table 1-3 SIP Call Security Features
Security Feature Line Side
Transport/Connection/Integrity Secure TLS port
Device Authentication
Digest Authentication
Signaling
Authentication/Encryption
Trunk Side
Secure TLS port
TLS certificate exchange w/Cisco Unified
Communications Manager and/or CAPF
Each SIP device uses unique digest user credentials.
IPSec certificate exchange or preshared key
SIP trunk user agents use unique digest credentials.
TLS Mode: authenticated or encrypted (except Cisco Unified
IP Phones 7940G/7960G).
TLS Mode: authenticated or encrypted mode
Media Encryption
Authorization
SRTP
Presence requests
SRTP
Presence requests
Method list
Note: Supported features on a device vary by device type.
Security Icons
Cisco Unified Communications Manager provides security status for a call, according to security levels that are configured for the Cisco Unified Communications Manager server(s) and devices that are participating in the call.
Phones that support security icons display the call security level.
•
•
The phone displays a shield icon for calls with a signaling security level of authenticated. A shield identifies a secured connection between Cisco IP devices, which means that the devices have authenticated or encrypted signaling.
The phone displays a lock icon for calls with encrypted media, which means that the devices are using encrypted signaling and encrypted media.
Note
Some phone models display only the lock icon.
The security status of a call can change for point-to-point, intracluster, intercluster, and multihop calls.
SCCP line, SIP line, and H.323 signaling support notification of call security status changes to participating endpoints. If a SIP trunk is involved in a call path, the call session status specifies nonsecure. Refer to
“Security Icons and Encryption” section on page 1-10
for restrictions that are associated with security icons.
1-6
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 1 Security Overview
Interactions and Restrictions
The audio and video portions of the call provide basis for the call security status. Consider the call secure only if both the audio and video portions are secure.
Table 1-4 describes the rules that determine whether
a security icon displays, and which icon appears.
Table 1-4 Security Icon Display Rules
Media and Device Types In the Call
Secure audio only
Secure audio with unsecure video
Secure audio with secure video
Authenticated device with nonsecure audio only
Authenticated device with nonsecure audio and video
Unauthenticated device with nonsecure audio only
Unauthenticated device with nonsecure audio and video
Shield
None
None
Phones That Display
Both Shield and Lock
Icons
Lock
Shield
Lock
Shield
Phones That Display Only the
Lock Icon
Lock
None
Lock
None
None
None
None
For conference and barge calls, the security icon displays the security status for the conference. See
“Secure Conference Icons” section on page 14-3
for more information.
Interactions and Restrictions
This section contains information on the following topics:
•
•
For information about interactions and restrictions that are associated with the secure conference feature,
refer to the “Configuring Secure Conference Resources” section on page 14-1
.
Interactions
This section describes how Cisco security features interact with Cisco Unified Communications
Manager applications.
Presence
To add presence group authorization for phones and trunks that are running SIP, configure presence groups to restrict presence requests to authorized users.
Note
Refer to the Cisco Unified Communications Manager Features and Services Guide for more information about configuring presence groups.
OL-24964-01
Cisco Unified Communications Manager Security Guide
1-7
Chapter 1 Security Overview
Interactions and Restrictions
To allow presence requests on SIP trunks, configure Cisco Unified Communications Manager to accept presence requests on the SIP trunk and, if required, configure Cisco Unified Communications Manager to accept and authenticate incoming presence requests from the remote device or application.
SIP Trunk
To use SIP-initiated transfer features and other advanced transfer-related features on SIP trunks, such as
Web Transfer and Click to Dial, configure Cisco Unified Communications Manager to accept incoming
Out of Dialog REFER requests.
To provide support for event reporting (such as MWI support) and to reduce per-call MTP allocations
(from a voice-messaging server, for example), configure Cisco Unified Communications Manager to accept Unsolicited Notification SIP requests.
To allow Cisco Unified Communications Manager to transfer an external call on a SIP trunk to an external device or party (in attended transfer, for example), configure Cisco Unified Communications
Manager to accept SIP requests with replaces header in REFERS and INVITES.
Extension Mobility
For extension mobility, the SIP digest credentials change when a user logs in and out because different credentials are configured for different end users.
CTI
Cisco Unified Communications Manager Assistant supports a secure connection to CTI (transport layer security connection) when you configure a CAPF profile (one for each Cisco Unified Communications
Manager Assistant node).
When multiple instances of a CTI/JTAPI/TAPI application are running, CTI TLS support requires you to configure a unique instanceID (IID) for every application instance to secure signaling and media communication streams between CTI Manager and JTAPI/TSP/CTI applications.
When the device security mode equals authenticated or encrypted, the Cisco Unity-CM TSP connects to
Cisco Unified Communications Manager through the Cisco Unified Communications Manager TLS port. When the security mode equals nonsecure, the Cisco Unity TSP connects to Cisco Unified
Communications Manager through the Cisco Unified Communications Manager port.
Restrictions
•
•
•
The following sections describe restrictions that apply to Cisco security features:
•
•
Authentication and Encryption, page 1-9
Barge and Encryption, page 1-9
•
Wideband Codecs and Encryption, page 1-9
Media Resources and Encryption, page 1-10
Phone Support and Encryption, page 1-10
Phone Support and Encrypted Configuration Files, page 1-10
•
•
•
•
Security Icons and Encryption, page 1-10
Cluster and Device Security Modes, page 1-11
Digest Authentication and Encryption, page 1-11
Packet Capturing and Encryption, page 1-12
1-8
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 1 Security Overview
Interactions and Restrictions
Authentication and Encryption
Consider the following restrictions before you install and configure authentication and encryption features:
•
Auto-registration does not work when you configure mixed mode.
•
•
You cannot implement signaling or media encryption without device authentication. To install device authentication, enable the Cisco CTL Provider service and install and configure the Cisco
CTL client.
Cisco does not support Network Address Translation (NAT) with Cisco Unified Communications
Manager if you configure mixed mode.
You can enable UDP in the firewall to allow media stream firewall traversal. Enabling UDP allows the media source on the trusted side of the firewall to open a bidirectional media flow through the firewall by sending the media packet through the firewall.
Tip
Hardware DSP resources cannot initiate this type of connection and, therefore, must exist outside the firewall.
Signaling encryption does not support NAT traversal. Instead of using NAT, consider using LAN extension VPNs.
Barge and Encryption
The following restrictions apply to barge and encryption:
•
•
Due to bandwidth requirements, Cisco Unified IP Phones 7940G and 7960G do not support barge from an encrypted device on an active encrypted call. The barge attempt will fail. A tone plays on the initiator phone to indicate that the barge failed.
Encrypted Cisco Unified IP Phones that are running release 8.2 or earlier can only barge an active call as authenticated or nonsecure participants.
•
•
If a caller barges a secure SCCP call, the system uses an internal tone-playing mechanism at the target device, and the status remains secure.
If a caller barges a secure SIP call, the system provides tone-on-hold, and Cisco Unified
Communications Manager classifies the call as nonsecure during the tone.
Note
Nonsecure or authenticated Cisco Unified IP Phones that are running release 8.3 or later can barge encrypted calls. The security icon indicates the security status for the conference. See
Conference Icons” section on page 14-3 for more information.
Wideband Codecs and Encryption
The following information applies for Cisco Unified IP Phones 7960G or 7940G that are configured for encryption and associated with a wideband codec region. This only applies to Cisco Unified IP Phones
7960G or 7940G that are configured for TLS/SRTP.
To establish an encrypted call, Cisco Unified Communications Manager ignores the wideband codec and chooses another supported codec from the codec list that the phone presents. If the other devices in the call are not configured for encryption, Cisco Unified Communications Manager may establish the authenticated/nonsecure call by using the wideband codec.
Cisco Unified Communications Manager Security Guide
OL-24964-01 1-9
Chapter 1 Security Overview
Interactions and Restrictions
Media Resources and Encryption
Cisco Unified Communications Manager supports authenticated and encrypted calls between secure
Cisco Unified IP Phones (SCCP or SIP), secure CTI devices/route points, secure Cisco MGCP IOS gateways, secure SIP trunks, secure H.323 gateways, secure conference bridges, and secure
H.323/H.245/H.225 trunks where no media resources are used. Cisco Unified Communications Manager does not provide media encryption in the following cases:
•
Calls that involve transcoders
•
•
Call that involve media termination points
Calls that involve music on hold (except for secure conference bridge calls)
Phone Support and Encryption
Some Cisco Unified IP Phones, such as Cisco Unified IP Phone 7912G, do not support encrypted calls.
Some phones support encryption but do not validate certificate signatures. Refer to the Cisco Unified IP
Phone administration guides for Cisco Unified IP Phones that support encryption and this version of
Cisco Unified Communications Manager for more information.
The followingCisco Unified IP Phones that are running SCCP support encryption: 7906G, 7911G,
7931G, 7940G, 7941G, 7941G-GE, 7942G, 7945G, 7960G, 7961G, 7961G-GE, 7962G, 7965G, 7970G,
7971G, 7971G-GE, and 7975G. The following Cisco Unified IP Phones that are running SIP support encryption: 7906G, 7911G, 7941G, 7941G-GE, 7942G, 7961G, 7961G-GE,7962G, 7965G, 7970G,
7971G, 7971G-GE, and 7975G.
Warning To obtain the full benefit of security features, Cisco recommends that you upgrade Cisco Unified IP
Phones to release 8.3, which supports the encryption features in this Cisco Unified Communications
Manager release. Encrypted phones that run earlier releases do not fully support these new features.
These phones can participate in secure conference and barge calls only as authenticated or nonsecure participants.
Cisco Unified IP Phones that are running release 8.3 with an earlier release of Cisco Unified
Communications Manager will display their connection security status, not the conference security status, during a conference or barge call, and do not support secure conference features like conference list.
Phone Support and Encrypted Configuration Files
Not all phones support encrypted configuration files. Some phones support encrypted configuration files but do not validate file signatures. Except for Cisco Unified IP Phones 7905G and 7912G, all phones that support encrypted configuration files require firmware that is compatible with Cisco Unified
Communications Manager Release 5.0 or later to receive full encrypted configuration files. Cisco
Unified IP Phones 7905G and 7912G use existing security mechanisms and do not require new firmware for this feature. Refer to
Supported Phone Models, page 11-4
, for phone support of encrypted configuration files.
Security Icons and Encryption
The following restrictions apply to security icons and encryption:
1-10
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 1 Security Overview
Interactions and Restrictions
•
•
•
The encryption lock icon may not display on the phone when you perform tasks such as transferring or putting a call on hold; the status changes from encrypted to nonsecure if the media streams that are associated with these tasks, such as MOH, are not encrypted.
Cisco Unified Communications Manager does not display the shield icon for calls that are transiting
H.323 trunks and SIP trunks.
For calls that involve the PSTN, the security icon shows the security status for only the IP domain portion of the call.
•
•
•
A SIP trunk will report encrypted or not-authenticated security status when using the TLS transport type. When SRTP is negotiated, the security status will get encrypted; otherwise it will remain not-authenticated. This will allow Cisco Unified Communications Manager call control to determine the overall security level of a call that involves a SIP trunk.
A SIP trunk will report authenticated status over the trunk if a party is authenticated during events such as a meet-me conference or a cbarge. (The SIP trunk will still be using TLS/SRTP.)
For Secure Monitoring and Recording, a SIP trunk will utilize the existing Call Info header mechanism for transmitting the security icon status over the SIP trunk, as currently used by the SIP line. This enables the SIP trunk peer to monitor the overall security status of a call.
If a call from an encrypted phone over a SIP trunk gets transferred back to an encrypted phone in its own cluster, the call does not get encrypted, and the lock icon does not display even though the encrypted phones exist in the same secure cluster.
•
Some phone models display only the lock icon, not the shield icon.
Refer to
“Secure Conference Icons” section on page 14-3
for security icon display with secure conference.
Cluster and Device Security Modes
Note
Device security mode configures the security capability for a Cisco Unified IP Phone or SIP trunk.
Cluster security mode configures the security capability for your standalone server or a cluster.
When the cluster security mode equals nonsecure, the device security mode equals nonsecure in the phone configuration file. In these circumstances, the phone makes nonsecure connections with the
SRST-enabled gateway and Cisco Unified Communications Manager, even if the device security mode specifies authenticated or encrypted. Security-related settings other than device security mode, such as the SRST Allowed check box, also get ignored. The security configuration does not get deleted in Cisco
Unified Communications Manager Administration, but security does not get provided.
The phone attempts a secure connection to the SRST-enabled gateway only when the cluster security mode equals secure, the device security mode in the phone configuration file is set to authenticated or encrypted, the SRST Allowed? check box is checked in the Trunk Configuration window, and a valid
SRST certificate exists in the phone configuration file.
Digest Authentication and Encryption
Cisco Unified Communications Manager defines a SIP call as having two or more separate call legs. For a standard, two-party call between two SIP devices, two separate call legs exist: one leg between the originating SIP user agent and Cisco Unified Communications Manager (the originating call leg) and the other leg between Cisco Unified Communications Manager and destination SIP user agent (the terminating call leg). Each call leg represents a separate dialog. Because digest authentication is a
OL-24964-01
Cisco Unified Communications Manager Security Guide
1-11
Chapter 1 Security Overview
Best Practices
point-to-point process, digest authentication on each call leg stays independent of the other call legs.
SRTP capabilities can change for each call leg, depending on the capabilities that are negotiated between the user agents.
Packet Capturing and Encryption
When SRTP encryption is implemented, third-party sniffing tools do not work. Authorized administrators with appropriate authentication can initiate packet capturing with a configuration change in Cisco Unified Communications Manager Administration (for devices that support packet capturing).
See the Troubleshooting Guide for Cisco Unified Communications Manager that supports this release for information about configuring packet capturing in Cisco Unified Communications Manager.
Best Practices
Cisco strongly recommends the following best practices:
•
Always perform installation and configuration tasks in a secure lab environment before you deploy to a wide-scale network.
•
Use IPSec for gateways and other application servers at remote locations.
Warning Failure to use IPSec in these instances results in session encryption keys getting transmitted in the clear.
•
•
To prevent toll fraud, configure conference enhancements that are described in the Cisco Unified
Communications Manager System Guide. Likewise, you can perform configuration tasks to restrict external transferring of calls. For information on how to perform this task, refer to the Cisco Unified
Communications Manager Features and Services Guide.
This section contains information on the following topics:
•
Resetting the Devices, Restarting Services, or Rebooting, page 1-12
Configuring Media Encryption with Barge, page 1-13
Resetting the Devices, Restarting Services, or Rebooting
•
•
•
This section describes when you need to reset the devices, to restart services in Cisco Unified
Serviceability, or to reboot the server/cluster.
Consider the following guidelines:
•
Reset a single device after you apply a different security profile in Cisco Unified Communications
Manager Administration.
•
•
Reset the devices if you perform phone-hardening tasks.
Reset the devices after you change the cluster security mode from mixed to nonsecure mode (or vice versa).
Restart all devices after you configure the Cisco CTL client or update the CTL file.
Reset the devices after you update CAPF enterprise parameters.
Restart the Cisco CTL Provider service after you update ports for the TLS connection.
1-12
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 1 Security Overview
Best Practices
•
•
•
•
Restart the Cisco CallManager service after you change the cluster security mode from mixed to nonsecure mode (or vice versa).
Restart the Cisco Certificate Authority Proxy Function service after you update associated CAPF service parameters.
Restart all Cisco CallManager and Cisco TFTP services in Cisco Unified Serviceability after you configure the Cisco CTL Client or update the CTL file. Perform this task on all servers that run these services in the cluster.
Restart all Cisco CallManager and Cisco TFTP services after you start or stop the CTL Provider service.
Reset dependent devices after you configure secure SRST references.
•
•
•
If you set the Smart Card service to Started and Automatic, reboot the PC where you installed the
Cisco CTL client.
Restart the Cisco IP Manager Assistant service, Cisco Web Dialer Web Service, and the Cisco
Extended Functions service after you configure the security-related service parameters that are associated with the Application User CAPF Profile.
To restart the Cisco CallManager service, refer to the Cisco Unified Serviceability Administration Guide.
To reset a single device after you update the phone configuration, see the
.
To reset all devices in a cluster, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
In Cisco Unified Communications Manager Administration, choose System > Cisco Unified CM.
The Find/List window displays.
Click Find.
A list of configured Cisco Unified Communications Manager servers displays.
Choose the Cisco Unified Communications Manager on which you want to reset devices.
Click Reset.
Perform
for each server in the cluster.
Configuring Media Encryption with Barge
Use the following information with the “Barge and Encryption” section on page 1-9
.
When you attempt to configure barge for Cisco Unified IP Phones 7960G and 7940G that are configured for encryption, the following message displays:
If you configure encryption for Cisco Unified IP Phone models 7960 and 7940, those encrypted devices cannot accept a barge request when they are participating in an encrypted call. When the call is encrypted, the barge attempt fails.
The message displays when you perform the following tasks in Cisco Unified Communications Manager
Administration:
•
In the Enterprise Parameter window, you update the Cluster Security Mode parameter.
OL-24964-01
Cisco Unified Communications Manager Security Guide
1-13
Installation
Chapter 1 Security Overview
•
In the Service Parameter window, you update the Builtin Bridge Enable parameter.
This message does not display in the Phone Configuration window when an encrypted security profile is configured for Cisco Unified IP Phones 7960G and 7940G and you choose On for the Built In Bridge setting (or the default setting equals On); however, the same restriction applies.
Tip
For changes to take effect, you must reset the dependent Cisco IP devices.
Installation
To obtain authentication support, you install a plug-in, the Cisco CTL client, from Cisco Unified
Communications Manager Administration. To install the Cisco CTL client, you must obtain at least two security tokens.
Media and signaling encryption capabilities automatically install when you install Cisco Unified
Communications Manager.
Cisco Unified Communications Manager automatically installs Secure Sockets Layer (SSL) for Cisco
Unified Communications Manager virtual directories.
Cisco Certificate Authority Proxy Function (CAPF) installs automatically as a part of Cisco Unified
Communications Manager Administration.
TLS and IPSec
Transport security handles the coding, packing, and sending of data. Cisco Unified Communications
Manager provides the following secure transport protocols:
•
Transport Layer Security (TLS) provides secure and reliable data transfer between two systems or devices, by using secure ports and certificate exchange. TLS secures and controls connections among Cisco Unified Communications Manager-controlled systems, devices, and processes to prevent access to the voice domain. Cisco Unified Communications Manager uses TLS to secure
SCCP calls to phones that are running SCCP and SIP calls to phones or trunks that are running SIP.
•
IP Security (IPSec) provides secure and reliable data transfer between Cisco Unified
Communications Manager and gateways. IPSec implements signaling authentication and encryption to Cisco IOS MGCP and H.323 gateways.
You can add secure RTP (SRTP) to TLS and IPSec transport services for the next level of security on devices that support SRTP. SRTP authenticates and encrypts the media stream (voice packets) to ensure that voice conversations that originate at or terminate to Cisco Unified IP Phones and either TDM or analog voice gateway ports are protected from eavesdroppers who may have gained access to the voice domain. SRTP adds protection against replay attacks.
Certificates
Certificates secure client and server identities. After root certificates are installed, certificates get added to the root trust stores to secure connections between users and hosts, including devices and application users.
1-14
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 1 Security Overview
Certificates
Administrators can view the fingerprint of server certificates, regenerate self-signed certificates, and delete trust certificates at the Cisco Unified Communications Operating System GUI.
Administrators can also regenerate and view self-signed certificates at the command line interface (CLI).
For information on updating the CallManager trust store and managing certificates, refer to the Cisco
Unified Communications Operating System Administration Guide that supports this Cisco Unified
Communications Manager release.
Note
Cisco Unified Communications Manager supports only PEM (.pem) and DER (.der) formatted certificates.
This section contains information on the following topics:
•
•
•
Phone Certificate Types, page 1-15
Server Certificate Types, page 1-16
Support for Certificates from External CAs, page 1-17
Phone Certificate Types
Cisco uses the following certificate types in phones:
•
•
Manufacture-installed certificate (MIC)—Cisco Manufacturing automatically installs this certificate in supported phone models. Manufacturer-installed certificates authenticate to
Cisco Certificate Authority Proxy Function (CAPF) for LSC installation. You cannot overwrite or delete the manufacture-installed certificate.
Locally significant certificate (LSC)—This certificate type installs on supported phones after you perform the necessary tasks that are associated with the Cisco Certificate Authority Proxy Function
(CAPF). See
Configuration Checklist Overview, page 1-25
, for configuration tasks. The LSC secures the connection between Cisco Unified Communications Manager and the phone after you configure the device security mode for authentication or encryption.
Tip
Cisco recommends that you use manufacturer-installed certificates (MICs) for LSC installation only.
Cisco supports LSCs to authenticate the TLS connection with Cisco Unified Communications Manager.
Because MIC root certificates can be compromised, customers who configure phones to use MICs for
TLS authentication or for any other purpose do so at their own risk. Cisco assumes no liability if MICs are compromised.
Cisco recommends upgrading Cisco Unified IP Phones 7906G, 7911G, 7931G (SCCP only), 7941G,
7941G-GE, 7942G, 7945G, 7961G, 7961G-GE, 7962G, 7965G, 7970G, 7971G, 7971G-GE, and 7975G to use LSCs for TLS connection to Cisco Unified Communications Manager and removing MIC root certificates from the CallManager trust store to avoid possible future compatibility issues. Be aware that some phone models that use MICs for TLS connection to Cisco Unified Communications Manager may not be able to register.
Administrators should remove the following MIC root certificates from the CallManager trust store:
CAP-RTP-001
CAP-RTP-002
Cisco_Manufacturing_CA
Cisco_Root_CA_2048
Cisco Unified Communications Manager Security Guide
OL-24964-01 1-15
Certificates
Chapter 1 Security Overview
MIC root certificates that stay in the CAPF trust store get used for certificate upgrades. For information on updating the CallManager trust store and managing certificates, refer to the Cisco Unified
Communications Operating System Administration Guide that supports this release.
Server Certificate Types
Cisco uses the following self-signed (own) certificate types in Cisco Unified Communications Manager servers:
•
HTTPS certificate (Tomcat)—A self-signed root certificate gets generated during the Cisco Unified
Communications Manager installation for the HTTPS server. Cisco Unity Connection uses this certificate for SMTP and IMAP services.
•
•
CallManager certificate—A self-signed root certificate automatically installs when you install Cisco
Unified Communications Manager on the Cisco Unified Communications Manager server.
CAPF certificate—The system copies this root certificate, which gets generated during Cisco
Unified Communications Manager installation, to your server or to all servers in the cluster after you complete the Cisco CTL client configuration.
•
•
IPSec certificate (ipsec_cert)—A self-signed root certificate gets generated during Cisco Unified
Communications Manager installation for IPSec connections with MGCP and H.323 gateways.
SRST-enabled gateway certificate—When you configure a secure SRST reference in Cisco Unified
Communications Manager Administration, Cisco Unified Communications Manager retrieves the
SRST-enabled gateway certificate from the gateway and stores it in the Cisco Unified
Communications Manager database. After you reset the devices, the certificate gets added to the phone configuration file. Because the certificate is stored in the database, you cannot manage this certificate with the certificate management tool.
•
•
•
Phone Certificates trust store (Phone-trust)—Cisco Unified Communications Manager uses this certificate type to support HTTPs access on phones. You can upload certificates to the Phone-trust store by using the Cisco Unified Communications Operating System GUI. These certificates are subsequently downloaded to the phones by means of the CTL file mechanism to support secure web access (HTTPS) from Cisco Unified IP Phones.
Cisco Unified Communications Manager imports the following certificate types to the CallManager trust store:
•
TVS certificate—These are self-signed certificates that support the Trust Verification Service
(TVS).
Phone-VPN-trust certificate—This category allows the system to import Cisco Unified IP Phone
VPN certificates. These certificates get stored in the Midlet trust store.
•
Cisco Unity server or Cisco Unity Connection certificate—Cisco Unity and Cisco Unity
Connection use this self-signed root certificate to sign the Cisco Unity SCCP and Cisco Unity
Connection SCCP device certificates. For Cisco Unity, the Cisco Unity Telephony Integration
Manager (UTIM) manages this certificate. For Cisco Unity Connection, Cisco Unity Connection
Administration manages this certificate.
Cisco Unity and Cisco Unity Connection SCCP device certificates—Cisco Unity and Cisco Unity
Connection SCCP devices use this signed certificate to establish a TLS connection with Cisco
Unified Communications Manager.
The certificate name represents a hash of the certificate subject name, which is based on the voice-mail server name. Every device (or port) gets issued a certificate that is rooted at the root certificate.
Cisco Unified Communications Manager Security Guide
1-16 OL-24964-01
Chapter 1 Security Overview
Authentication, Integrity, and Authorization Overview
•
SIP Proxy server certificate—A SIP user agent that connects via a SIP trunk authenticates to Cisco
Unified Communications Manager if the CallManager trust store contains the SIP user agent certificate and if the SIP user agent contains the Cisco Unified Communications Manager certificate in its trust store.
The following additional trust store exists:
•
Common Trust store for Tomcat and web applications—Tomcat-trust certificates get uploaded to the
Tomcat trust store from the corporate directory (Active Directory or Netscape Directory). After you upload the trusted certificate(s), you must restart the Cisco Tomcat and Cisco DirSync services.
Support for Certificates from External CAs
Cisco Unified Communications Manager supports integration with third-party certificate authorities
(CAs) by using a PKCS#10 certificate signing request (CSR) mechanism, which is accessible at the
Cisco Unified Communications Operating System Certificate Manager GUI. Customers who currently use third-party CAs should use the CSR mechanism to issue certificates for Cisco Unified
Communications Manager, CAPF, IPSec, and Tomcat.
Note
This release of Cisco Unified Communications Manager does not provide SCEP interface support.
Be sure to run the CTL client after you upload a third-party, CA-signed certificate to the platform to update the CTL file. After running the CTL client, restart the appropriate service(s) for the update; for example, restart Cisco CallManager and Cisco TFTP services when you update the Cisco Unified
Communications Manager certificate, restart CAPF when you update the CAPF certificate, and so on.
See
“Configuring the Cisco CTL Client” section on page 4-1
for the update procedure.
Note
After uploading the Cisco Unified Communications Manager or CAPF certificates, you might observe the phones reset automatically to update their ITL File. See
“Security by Default” section on page 3-1
.
For information on generating Certificate Signing Requests (CSRs) at the platform, refer to the Cisco
Unified Communications Operating System Administration Guide that supports this Cisco Unified
Communications Manager release.
Authentication, Integrity, and Authorization Overview
Integrity and authentication protect against the following threats:
•
•
TFTP file manipulation (integrity)
Modification of call-processing signaling between the phone and Cisco Unified Communications
Manager (authentication)
•
•
Man-in-the-middle attacks (authentication), as defined in
Phone and server identity theft (authentication)
Replay attack (digest authentication)
•
Authorization specifies what an authenticated user, service, or application can do. You can implement multiple authentication and authorization methods in a single session.
See the following sections for information on authentication, integrity, and authorization:
OL-24964-01
Cisco Unified Communications Manager Security Guide
1-17
Chapter 1 Security Overview
Authentication, Integrity, and Authorization Overview
•
•
•
•
•
•
Image Authentication, page 1-18
Device Authentication, page 1-18
File Authentication, page 1-18
Signaling Authentication, page 1-19
Digest Authentication, page 1-19
Image Authentication
This process prevents tampering with the binary image, the firmware load, prior to loading it on the phone. Tampering with the image causes the phone to fail the authentication process and reject the image. Image authentication occurs through signed binary files that automatically install when you install Cisco Unified Communications Manager. Likewise, firmware updates that you download from the web also provide signed binary images.
Device Authentication
This process validates the identity of the communicating device and ensures that the entity is who it claims to be. For a list of devices that are supported, see
“Supported Phone Models” section on page 6-3 .
Device authentication occurs between the Cisco Unified Communications Manager server and supported
Cisco Unified IP Phones, SIP trunks, or JTAPI/TAPI/CTI applications (when supported). An authenticated connection occurs between these entities only when each entity accepts the certificate of the other entity. Mutual authentication describes this process of mutual certificate exchange.
Device authentication relies on the creation of the Cisco CTL file (for authenticating Cisco Unified
Communications Manager server node and applications), as described in the
phones and JTAPI/TAPI/CTI applications), as described in the
“Using the Certificate Authority Proxy
Function” section on page 10-1 .
Tip
A SIP user agent that connects via a SIP trunk authenticates to Cisco Unified Communications Manager if the CallManager trust store contains the SIP user agent certificate and if the SIP user agent contains the Cisco Unified Communications Manager certificate in its trust store. For information on updating the
CallManager trust store, refer to the Cisco Unified Communications Operating System Administration
Guide that supports this Cisco Unified Communications Manager release.
File Authentication
This process validates digitally signed files that the phone downloads; for example, the configuration, ring list, locale, and CTL files. The phone validates the signature to verify that file tampering did not occur after the file creation. For a list of devices that are supported, see the
“Supported Phone Models” section on page 6-3
.
The TFTP server does not sign any files if you configure the cluster for nonsecure mode. If you configure the cluster for mixed mode, the TFTP server signs static files, such as ring list, localized, default.cnf.xml, and ring list wav files, in .sgn format. The TFTP server signs files in <device name>.cnf.xml format every time that the TFTP server verifies that a data change occurred for the file.
Cisco Unified Communications Manager Security Guide
1-18 OL-24964-01
Chapter 1 Security Overview
Authentication, Integrity, and Authorization Overview
The TFTP server writes the signed files to disk if caching is disabled. If the TFTP server verifies that a saved file has changed, the TFTP server re-signs the file. The new file on the disk overwrites the saved file that gets deleted. Before the phone can download the new file, the administrator must restart affected devices in Cisco Unified Communications Manager Administration.
After the phone receives the files from the TFTP server, the phone verifies the integrity of the files by validating the signature on the file. For the phone to establish an authenticated connection, ensure that the following criteria are met:
•
A certificate must exist in the phone.
•
•
The CTL file must exist on the phone, and the Cisco Unified Communications Manager entry and certificate must exist in the file.
You configured the device for authentication or encryption.
Note
File authentication relies on the creation of the Certificate Trust List (CTL) file, which the
“Configuring the Cisco CTL Client” section on page 4-1
describes.
Signaling Authentication
This process, also known as signaling integrity, uses the TLS protocol to validate that no tampering occurred to signaling packets during transmission.
Signaling authentication relies on the creation of the Certificate Trust List (CTL) file, which the
“Configuring the Cisco CTL Client” section on page 4-1 describes.
Digest Authentication
This process for SIP trunks and phones allows Cisco Unified Communications Manager to challenge the identity of a device that is connecting to Cisco Unified Communications Manager. When challenged, the device presents its digest credentials, similar to a username and password, to Cisco Unified
Communications Manager for verification. If the credentials that are presented match those that are configured in the database for that device, digest authentication succeeds, and Cisco Unified
Communications Manager processes the SIP request.
Note
Be aware that the cluster security mode has no effect on digest authentication.
Note
If you enable digest authentication for a device, the device requires a unique digest user ID and password to register.
You configure SIP digest credentials in the Cisco Unified Communications Manager database for a phone user or application user.
•
For applications, you specify digest credentials in the Applications User Configuration window.
•
For phones that are running SIP, you specify the digest authentication credentials in the End User window. To associate the credentials with the phone after you configure the user, you choose a
Digest User, the end user, in the Phone Configuration window. After you reset the phone, the
OL-24964-01
Cisco Unified Communications Manager Security Guide
1-19
Chapter 1 Security Overview
Authentication, Integrity, and Authorization Overview
credentials exist in the phone configuration file that the TFTP server offers to the phone. See
“Configuring Encrypted Phone Configuration Files”
to ensure digest credential do not get sent in the clear in TFTP downloads.
•
For challenges received on SIP trunks, you configure a SIP realm, which specifies the realm username (device or application user) and digest credentials.
When you enable digest authentication for an external phone or trunk that is running SIP and configure digest credentials, Cisco Unified Communications Manager calculates a credentials checksum that includes a hash of the username, password, and the realm. The system uses a nonce value, which is a random number, to calculate the MD5 hash. Cisco Unified Communications Manager encrypts the values and stores the username and the checksum in the database.
To initiate a challenge, Cisco Unified Communications Manager uses a SIP 401 (Unauthorized) message, which includes the nonce and the realm in the header. You configure the nonce validity time in the SIP device security profile for the phone or trunk. The nonce validity time specifies the number of minutes that a nonce value stays valid. When the time interval expires, Cisco Unified Communications
Manager rejects the external device and generates a new number.
Note
Cisco Unified Communications Manager acts as a user agent server (UAS) for SIP calls that are originated by line-side phones or devices that are reached through the SIP trunk, as a user agent client
(UAC) for SIP calls that it originates to the SIP trunk, or a back-to-back user agent (B2BUA) for line-to-line or trunk-to-trunk connections. In most environments, Cisco Unified Communications
Manager acts primarily as B2BUA connecting SCCP and SIP endpoints. (A SIP user agent represents a device or application that originates a SIP message.)
Tip
Digest authentication does not provide integrity or confidentiality. To ensure integrity and confidentiality for the device, configure the TLS protocol for the device, if the device supports TLS. If the device supports encryption, configure the device security mode as encrypted. If the device supports encrypted phone configuration files, configure encryption for the files.
Digest Authentication for Phones
When you enable digest authentication for a phone, Cisco Unified Communications Manager challenges all requests for phones that are running SIP except keepalive messages. Cisco Unified Communications
Manager does not respond to challenges from line-side phones.
After receiving a response, Cisco Unified Communications Manager validates the checksum for the username that is stored in the database against the credentials in the response header.
Phones that are running SIP exist in the Cisco Unified Communications Manager realm, which is defined in Cisco Unified Communications Manager Administration at installation. You configure the SIP Realm for challenges to phones with the service parameter SIP Station Realm. Each digest user can have one
information.
Tip
If you enable digest authentication for an end user but do not configure the digest credentials, the phone will fail registration. If the cluster mode is nonsecure and you enable digest authentication and configure digest credentials, the digest credentials get sent to the phone, and Cisco Unified Communications
Manager still initiates challenges.
1-20
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 1 Security Overview
Authentication, Integrity, and Authorization Overview
Digest Authentication for Trunks
When you enable digest authentication for a trunk, Cisco Unified Communications Manager challenges
SIP trunk requests from SIP devices and applications that connect through a SIP trunk. The system uses the Cluster ID enterprise parameter in the challenge message. SIP user agents that connect through the
SIP trunk respond with the unique digest credentials that you configured for the device or application in
Cisco Unified Communications Manager Administration.
When Cisco Unified Communications Manager initiates a SIP trunk request, a SIP user agent that connects through the SIP trunk can challenge the identity of Cisco Unified Communications Manager.
For these incoming challenges, you configure a SIP Realm to provide the requested credentials for the user. When Cisco Unified Communications Manager receives a SIP 401(Unauthorized) or SIP 407
(Proxy Authentication Required) message, Cisco Unified Communications Manager looks up the encrypted password for the realm that connects though the trunk and for the username that the challenge message specifies. Cisco Unified Communications Manager decrypts the password, calculates the digest, and presents it in the response message.
Tip
The realm represents the domain that connects through the SIP trunk, such as xyz.com, which helps to identify the source of the request.
To configure the SIP Realm, see
“Configuring Digest Authentication for the SIP Trunk” section on page 26-1
. You must configure a SIP Realm and username and password in Cisco Unified
Communications Manager for each SIP trunk user agent that can challenge Cisco Unified
Communications Manager. Each user agent can have one set of digest credentials per realm.
Authorization
Cisco Unified Communications Manager uses the authorization process to restrict certain categories of messages from phones that are running SIP, from SIP trunks, and from SIP application requests on SIP trunks.
•
•
For SIP INVITE messages and in-dialog messages, and for phones that are running SIP, Cisco
Unified Communications Manager provides authorization through calling search spaces and partitions.
For SIP SUBSCRIBE requests from phones, Cisco Unified Communications Manager provides authorization for user access to presence groups.
•
For SIP trunks, Cisco Unified Communications Manager provides authorization of presence subscriptions and certain non-INVITE SIP messages; for example, out-of-dial REFER, unsolicited notification, and any SIP request with the replaces header. You specify authorization in the SIP
Trunk Security Profile window when you check the allowed SIP requests in the window.
To enable authorization for SIP trunk applications, check the Enable Application Level Authorization and the Digest Authentication check box in the SIP Trunk Security Profile window; then, check the allowed SIP request check boxes in the Application User Configuration window.
If you enable both SIP trunk authorization and application level authorization, authorization occurs for the SIP trunk first and then for the SIP application user. For the trunk, Cisco Unified Communications
Manager downloads the trunk Access Control List (ACL) information and caches it. The ACL information gets applied to the incoming SIP request. If the ACL does not allow the SIP request, the call fails with a 403 Forbidden message.
OL-24964-01
Cisco Unified Communications Manager Security Guide
1-21
Chapter 1 Security Overview
Encryption Overview
If the ACL allows the SIP request, Cisco Unified Communications Manager checks whether digest authentication is enabled in the SIP Trunk Security Profile. If digest authentication is not enabled and application-level authorization is not enabled, Cisco Unified Communications Manager processes the request. If digest authentication is enabled, Cisco Unified Communications Manager verifies that the authentication header exists in the incoming request and then uses digest authentication to identify the source application. If the header does not exist, Cisco Unified Communications Manager challenges the device with a 401 message.
Before an application-level ACL gets applied, Cisco Unified Communications Manager authenticates the SIP trunk user agent through digest authentication. Therefore, you must enable digest authentication in the SIP Trunk Security Profile before application-level authorization can occur.
Encryption Overview
Tip
Encryption capability installs automatically when you install Cisco Unified Communications Manager on a server.
This section describes the types of encryption that Cisco Unified Communications Manager supports:
•
Signaling Encryption, page 1-22
•
•
Configuration File Encryption, page 1-24
Signaling Encryption
Signaling encryption ensures that all SIP and SCCP signaling messages that are sent between the device and the Cisco Unified Communications Manager server are encrypted.
Signaling encryption ensures that the information that pertains to the parties, DTMF digits that are entered by the parties, call status, media encryption keys, and so on, are protected against unintended or unauthorized access.
Cisco does not support Network Address Translation (NAT) with Cisco Unified Communications
Manager if you configure the cluster for mixed mode; NAT does not work with signaling encryption.
You can enable UDP ALG in the firewall to allow media stream firewall traversal. Enabling the UDP
ALG allows the media source on the trusted side of the firewall to open a bidirectional media flow through the firewall by sending the media packet through the firewall.
Tip
Hardware DSP resources cannot initiate this type of connection and, therefore, must exist outside the firewall.
Signaling encryption does not support NAT traversal. Instead of using NAT, consider using LAN extension VPNs.
SIP trunks support signaling encryption but do not support media encryption.
1-22
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 1 Security Overview
Encryption Overview
Media Encryption
Media encryption, which uses Secure Real-Time Protocol (SRTP), ensures that only the intended recipient can interpret the media streams between supported devices. Media encryption includes creating a media master key pair for the devices, delivering the keys to the devices, and securing the delivery of the keys while the keys are in transport. Cisco Unified Communications Manager supports SRTP primarily for IOS gateways and Cisco Unified Communications Manager H.323 trunks on gatekeeper-controlled and non-gatekeeper-controlled trunks as well as on SIP trunks.
Note
Cisco Unified Communications Manager handles media encryption keys differently for different devices and protocols. All phones that are running SCCP get their media encryption keys from Cisco Unified
Communications Manager, which secures the media encryption key downloads to phones with TLS encrypted signaling channels. Phones that are running SIP generate and store their own media encryption keys. Media encryption keys that are derived by Cisco Unified Communications Manager system securely get sent via encrypted signaling paths to gateways over IPSec-protected links for H.323 and
MGCP or encrypted TLS links for SCCP and SIP.
If the devices support SRTP, the system uses a SRTP connection. If at least one device does not support
SRTP, the system uses an RTP connection. SRTP-to-RTP fallback may occur for transfers from a secure device to a non-secure device, transcoding, music on hold, and so on.
For most security-supported devices, authentication and signaling encryption serve as the minimum requirements for media encryption; that is, if the devices do not support signaling encryption and authentication, media encryption cannot occur. Cisco IOS gateways and trunks support media encryption without authentication. For Cisco IOS gateways and trunks, you must configure IPSec when you enable the SRTP capability (media encryption).
Warning
Before you configure SRTP or signaling encryption for gateways and trunks, Cisco strongly recommends that you configure IPSec because Cisco IOS MGCP gateways, H.323 gateways, and
H.323/H.245/H.225 trunks rely on IPSec configuration to ensure that security-related information does not get sent in the clear. Cisco Unified Communications Manager does not verify that you configured
IPSec correctly. If you do not configure IPSec correctly, security-related information may get exposed.
SIP trunks rely on TLS to ensure that security-related information does not get sent in the clear.
The following example demonstrates media encryption for SCCP and MGCP calls.
1.
2.
Device A and Device B, which support media encryption and authentication, register with Cisco
Unified Communications Manager.
When Device A places a call to Device B, Cisco Unified Communications Manager requests two sets of media session master values from the key manager function.
3.
4.
5.
6.
Both devices receive the two sets: one set for the media stream, Device A—Device B, and the other set for the media stream, Device B—Device A.
Using the first set of master values, Device A derives the keys that encrypt and authenticate the media stream, Device A—Device B.
Using the second set of master values, Device A derives the keys that authenticate and decrypt the media stream, Device B—Device A.
Device B uses these sets in the inverse operational sequence.
OL-24964-01
Cisco Unified Communications Manager Security Guide
1-23
Chapter 1 Security Overview
Running an NMAP Scan
7.
After the devices receive the keys, the devices perform the required key derivation, and SRTP packet processing occurs.
Note
Phones that are running SIP and H.323 trunks/gateways generate their own cryptographic parameters and send them to Cisco Unified Communications Manager.
For media encryption with conference calls, refer to
“Configuring Secure Conference Resources” section on page 14-1 .
Configuration File Encryption
Cisco Unified Communications Manager pushes confidential data such as digest credentials and administrator passwords to phones in configuration file downloads from the TFTP server.
Cisco Unified Communications Manager uses reversible encryption to secure these credentials in the database. To secure this data during the download process, Cisco recommends that you configure encrypted configuration files for all Cisco Unified IP Phones that support this option (see
gets encrypted for download.
Note
In some circumstances, you may choose to download confidential data to phones in the clear; for example, to troubleshoot the phone or during auto-registration.
Cisco Unified Communications Manager encodes and stores encryption keys in the database. The TFTP server encrypts and decrypts configuration files by using symmetric encryption keys:
•
If the phone has PKI capabilities, Cisco Unified Communications Manager can use the phone public key to encrypt the phone configuration file.
•
If the phone does not have PKI capabilities, you must configure a unique symmetric key in Cisco
Unified Communications Manager and in the phone.
You enable encrypted configuration file settings in the Phone Security Profile window in Cisco Unified
Communications Manager Administration, which you then apply to a phone in the Phone Configuration window.
See
“Understanding Encryption of the Phone Configuration File” section on page 11-1
for more information.
Running an NMAP Scan
You can run a Network Mapper (NMAP) scan program on any Windows or Linux platform to perform vulnerability scans. NMAP represents a free and open source utility for network exploration or security auditing.
Note
NMAP DP scan can take up to 18 hours to complete.
Syntax nmap -n -vv -sU -p <port_range> <ccm_ip_address>
1-24
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 1 Security Overview
Configuration Checklist Overview
where:
-n: No DNS resolution. Tells NMAP to never do reverse DNS resolution on the active IP addresses that it finds. Because DNS can be slow even with the NMAP built-in parallel stub resolver, this option can slash scanning times.
-v: Increases the verbosity level, which causes NMAP to print more information about the scan in progress. The system shows open ports as they are found and provides completion time estimates when
NMAP estimates that a scan will take more than a few minutes. Use this option twice or more for even greater verbosity.
-sU: Specifies a UDP port scan.
-p: Specifies which ports to scan and overrides the default. Be aware that individual port numbers are acceptable, as are ranges that are separated by a hyphen (for example 1-1023).
ccm_ip_address: IP address of Cisco Unified Communications Manager
Configuration Checklist Overview
describes all the tasks that you must perform to implement authentication and encryption. Each chapter may also contain a checklist for the tasks that you must perform for the specified security feature
•
To implement authentication and encryption for a new install, refer to
.
•
To add a node to a secure cluster, refer to Installing Cisco Unified Communications Manager
Release 6.1(1), which describes how to add a node and how to configure security for the new node.
Table 1-5 Configuration Checklist for Authentication and Encryption
Configuration Steps
Step 1
Activate the Cisco CTL Provider service in Cisco Unified
Serviceability.
Be sure to activate the Cisco CTL Provider service on each
Cisco Unified Communications Manager server in the cluster.
Tip
If you activated this service prior to a Cisco Unified
Communications Manager upgrade, you do not need to activate the service again. The service automatically activates after the upgrade.
Related Procedures and Topics
Activating the Cisco CTL Provider Service, page 4-5
Step 2
Activate the Cisco Certificate Authority Proxy service in Cisco
Unified Serviceability to install, upgrade, troubleshoot, or delete locally significant certificates.
Activating the Certificate Authority Proxy
Activate the Cisco Certificate Authority Proxy service on the first node only.
Timesaver
Performing this task before you install and configure the Cisco CTL client ensures that you do not have to update the CTL file to use CAPF.
OL-24964-01
Cisco Unified Communications Manager Security Guide
1-25
Chapter 1 Security Overview
Configuration Checklist Overview
Table 1-5 Configuration Checklist for Authentication and Encryption (continued)
Configuration Steps
Step 3
If you do not want to use the default port settings, configure ports for the TLS connection.
Tip
If you configured these settings prior to a Cisco Unified
Communications Manager upgrade, the settings migrate automatically during the upgrade.
Related Procedures and Topics
Configuring Ports for the TLS Connection, page 4-6
Step 4
Step 5
Obtain at least two security tokens and the passwords, hostnames/IP addresses, and port numbers for the servers that you will configure for the Cisco CTL client.
Install the Cisco CTL client.
Tip
To update the Cisco CTL file after an upgrade to this
Cisco Unified Communications Manager release, you must install the plug-in that is available in this Cisco
Unified Communications Manager Administration release.
Configuring the Cisco CTL Client, page 4-10
•
•
•
•
Installing the Cisco CTL Client, page 4-8
Upgrading the Cisco CTL Client and
Migrating the Cisco CTL File, page 4-10
Step 6
.
Configure the Cisco CTL client.
Tip
•
If you created the Cisco CTL file prior to a Cisco
Unified Communications Manager upgrade, the
Cisco CTL file migrates automatically during the upgrade. To update the Cisco CTL file after an upgrade to this Cisco Unified Communications Manager release, you must install and configure the latest version of the
Cisco CTL client.
•
Configuring the Cisco CTL Client, page 4-10
Upgrading the Cisco CTL Client and
Migrating the Cisco CTL File, page 4-10
1-26
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 1 Security Overview
Configuration Checklist Overview
Table 1-5 Configuration Checklist for Authentication and Encryption (continued)
Configuration Steps
Step 7
Configure the phone security profiles. Perform the following tasks when you configure the profiles:
Related Procedures and Topics
Configuring a Phone Security Profile, page 7-3
•
Tip
Configure the device security mode.
The device security mode migrates automatically during the Cisco Unified Communications Manager upgrade. If you want to configure encryption for devices that only supported authentication in a prior release, you must choose a security profile for encryption in the Phone
Configuration window.
Configuration Tips for Phone Security
Configuring Encrypted Phone Configuration
Configuration Tips for Encrypted
Configuration Files, page 11-4
Step 8
Step 9
•
•
Configure CAPF settings (for some phones that are running
SCCP and SIP).
Additional CAPF settings display in the Phone
Configuration window.
If you plan to use digest authentication for phones that are running SIP, check the Enable Digest Authentication check box.
•
•
To enable encrypted configuration files (for some phones that are running SCCP and SIP), check the TFTP Encrypted
Confide check box.
To exclude digest credentials in configuration file downloads, check the TFTP Exclude Digest Credential in
Configuration File check box.
Apply the phone security profiles to the phones.
Configure CAPF to issue certificates to the phones.
Tip
If you performed certificate operations before the upgrade to this Cisco Unified Communications Manager release and CAPF ran on a subscriber server, you must copy the CAPF data to the publisher database server before you upgrade a cluster to this Cisco Unified
Communications Manager release.
•
Applying a Phone Security Profile, page 7-10
•
CAPF Configuration Checklist, page 10-5
Caution
The CAPF data on the Cisco Unified
Communications Manager subscriber server does not migrate to the Cisco Unified Communications
Manager database, and a loss of data occurs, if you do not copy the data to the database. If a loss of data occurs, the locally significant certificates that you issued with the CAPF utility remain in the phones, but the CAPF utility for this release must reissue the certificates, which are no longer valid.
OL-24964-01
Cisco Unified Communications Manager Security Guide
1-27
Chapter 1 Security Overview
Configuration Checklist Overview
Table 1-5 Configuration Checklist for Authentication and Encryption (continued)
Configuration Steps
Step 10
Verify that the locally significant certificates are installed on supported Cisco Unified IP Phones.
Step 11
Step 12
Related Procedures and Topics
•
•
Entering the Authentication String on the
Configure digest authentication for phones that are running SIP.
•
Configuring Digest Authentication for the SIP Phone, page 12-1
Perform phone-hardening tasks.
•
Tip
If you configured phone-hardening settings prior to a
Cisco Unified Communications Manager upgrade, the device configuration settings migrate automatically during the upgrade.
Step 13
Step 14
Step 15
Configure conference bridge resources for security.
Configure voice mail ports for security.
•
•
•
Configure security settings for SRST references.
Tip
If you configured secure SRST references in a previous
Cisco Unified Communications Manager release, the configuration automatically migrates during the Cisco
Unified Communications Manager upgrade.
•
Configuring Voice-Messaging Ports for
The applicable Cisco Unity or
Cisco Unity Connection integration guide for this Cisco Unified Communications
Manager release
Configuring a Secure Survivable Remote
Site Telephony (SRST) Reference, page 23-1
Step 16
Configure IPSec.
•
•
•
•
Configuring Encryption for Gateways and Trunks, page 24-1
Considerations for Configuring IPSec in the Network Infrastructure, page 24-5
Media and Signaling Authentication and
Encryption Feature for Cisco IOS MGCP
Gateways
Cisco Unified Communications
Operating System Administration Guide
1-28
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 1 Security Overview
Where to Find More Information
Table 1-5 Configuration Checklist for Authentication and Encryption (continued)
Configuration Steps
Step 17
Configure the SIP trunk security profile.
For trunk-level authorization, check the authorization check boxes for the allowed SIP requests.
Related Procedures and Topics
•
Configuring the SIP Trunk Security
If you plan to use digest authentication, check the Enable Digest
Authentication check box in the profile.
•
Configuring Digest Authentication
Enterprise Parameters, page 26-2
Step 18
Step 19
Step 20
Step 21
Step 22
If you want application-level authorization to occur after trunk-level authorization, check the Enable Application Level
Authorization check box.
You cannot check application-level authorization unless digest authentication is checked.
Apply the SIP trunk security profile to the trunk.
Configure digest authentication for the trunk.
•
•
Applying a SIP Trunk Security Profile, page 25-8
Configuring Digest Authentication for the SIP Trunk, page 26-1
If you checked the Enable Application Level Authorization check box in the SIP trunk security profile, configure the allowed SIP requests by checking the authorization check boxes in the Application User Configuration window.
Reset all phones.
•
•
Configuring the SIP Trunk Security
Resetting the Devices, Restarting Services, or
Reboot all servers.
Resetting the Devices, Restarting Services, or
Where to Find More Information
Related Cisco Documentation
Refer to the following documents for further information about related Cisco IP telephony applications and products:
•
•
•
•
•
Cisco Unified IP Phone Administration Guide for Cisco Unified Communications Manager
Cisco Unified Communications Operating System Administration Guide
Media and Signaling Authentication and Encryption Feature for Cisco IOS MGCP Gateways
Cisco Unified Communications Manager Integration Guide for Cisco Unity
•
Cisco Unified Communications Manager Integration Guide for Cisco Unity Connection
Cisco Unified Survivable Remote Site Telephony (SRST) administration documentation that supports the SRST-enabled gateway
•
•
•
•
Disaster Recovery System Administration Guide
Cisco Unified Communications Manager Bulk Administration Guide
Troubleshooting Guide for Cisco Unified Communications Manager
The firmware release notes that support your phone model
OL-24964-01
Cisco Unified Communications Manager Security Guide
1-29
Where to Find More Information
Chapter 1 Security Overview
1-30
Cisco Unified Communications Manager Security Guide
OL-24964-01
C H A P T E R
2
Using Hypertext Transfer Protocol over Secure
Sockets Layer (HTTPS)
This chapter contains information on the following topics:
•
•
HTTPS for Cisco Unified IP Phone Services, page 2-2
•
•
•
•
Using Internet Explorer 8 to Save the Certificate to the Trusted Folder, page 2-6
Using Firefox with HTTPS, page 2-8
Using Safari with HTTPS, page 2-10
Where to Find More Information, page 2-12
HTTPS Overview
HTTPS, or Hypertext Transfer Protocol over Secure Sockets Layer (SSL), secures communication between a browser and a web server for Microsoft Windows users. HTTPS uses certificates to ensure server identities and to secure the browser connection. HTTPS uses a public key to encrypt the data, including the user login and password, during transport over the Internet.
To enable HTTPS, you must download a certificate that identifies the server during the connection process. You can accept the server certificate for the current session only, or you can download the certificate to a trust folder (file) to secure the current session and future sessions with that server. The trust folder stores the certificates for all your trusted sites.
Cisco supports these browsers for connection to the Cisco Tomcat web server application in Cisco
Unified Communications Manager:
•
•
Microsoft Internet Explorer (IE) 7 when running on Microsoft Windows XP SP3
Microsoft Internet Explorer (IE) 8 when running on Microsoft Windows XP SP3 or Microsoft Vista
SP2
•
•
Firefox 3.x when running on Microsoft Windows XP SP3, Microsoft Vista SP2 or Apple MAC OS X
Safari 4.x when running on Apple MAC OS X
Cisco Unified Communications Manager Security Guide
2-1 OL-24964-01
HTTPS for Cisco Unified IP Phone Services
Chapter 2 Using Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS)
Note
When you install/upgrade Cisco Unified Communications Manager, an HTTPS self-signed certificate
(Tomcat) is generated. The self-signed certificate migrates automatically during upgrades to Cisco
Unified Communications Manager. A copy of this certificate is created in .DER and .PEM formats.
You can regenerate the self-signed certificate by using the Cisco Unified Communications Operating
System GUI. Refer to the Cisco Unified Communications Operating System Administration Guide for more information.
Table 2-1 shows the applications that use HTTPS with Cisco Tomcat in Cisco Unified Communications
Manager.
Table 2-1 Cisco Unified Communications Manager HTTPS Applications
Cisco Unified Communications
Manager HTTPS Application
ccmadmin ccmservice cmplatform cmuser ast
RTMTReports
PktCap art taps dna drf
SOAP
Web Application
Cisco Unified Communications Manager Administration
Cisco Unified Serviceability
Operating System administration pages
Cisco Personal Assistant
Real Time Monitoring Tool
Real Time Monitoring Tool reports archive
TAC troubleshooting tools that are used for packet capturing
Cisco Unified Communications Manager CDR Analysis and
Reporting
Cisco Unified Communications Manager Auto-Register Phone
Tool
Dialed Number Analyzer
Disaster Recovery System
Simple Object Access Protocol API for reading from and writing to the Cisco Unified Communications Manager database
Note
For security, all Web applications that are using SOAP require HTTPS. Cisco does not support HTTP for
SOAP applications. Existing applications that use
HTTP will fail; they cannot be converted to HTTPS by changing directories.
HTTPS for Cisco Unified IP Phone Services
Prior to Cisco Unified Communications Manager Release 8.0, Cisco Unified IP Phones and Cisco
Unified IP Phone Services did not support HTTPS communication and communicated using “clear text” over port 8080.
For Cisco Unified Communications Manager Release 8.0, Cisco Unified IP Phones and Cisco Unified
IP Phone Services support HTTPS, encryption, and secure identification of the server using port 8443.
2-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 2 Using Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS)
Supported Devices
The following Cisco Unified IP Phones support HTTPS:
•
7906
•
•
•
•
•
•
•
•
•
•
7911
7931
7941
7961
7970
7942
7945
7962
7965
7975
HTTPS for Cisco Unified IP Phone Services
Supported Features
The following features support HTTPS:
•
Cisco Extension Mobility (EM)
•
•
•
•
•
Cisco Extension Mobility Cross Cluster (EMCC)
Cisco Unified Communications Manager Manager Assistant (IPMA)
Cisco Unified IP Phone Services
Personal Directory
Change Credentials
Cisco Unified IP Phone Services Configuration Settings
To support HTTPS in Cisco Unified Communications Manager Release 8.0(1), the Phone Configuration
Settings include the secure URL parameters shown in
.
To configure the secure URL parameters, choose Device > Device Settings > Phone Services from
Cisco Unified Communications Manager Administration. For more information, see the “Cisco Unified
IP Phone Services Configuration” chapter in the Cisco Unified Communications Manager
Administration Guide.
OL-24964-01
Cisco Unified Communications Manager Security Guide
2-3
HTTPS for Cisco Unified IP Phone Services
Chapter 2 Using Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS)
Table 2-2 Phone Configuration Settings for Secure URLs
Field
Secure Authentication URL
Secure Directory URL
Secure Idle URL
Description
Enter the secure URL that the phone uses to validate requests that are made to the phone web server.
Note
If you do not provide a Secure
Authentication URL, the device uses the nonsecure URL. If you provide both a secure URL and a nonsecure URL, the device chooses the appropriate URL, based on its capabilities.
By default, this URL accesses a Cisco
Unified CM User Options window that was configured during installation.
Leave this field blank to accept the default setting.
Maximum length: 255
Enter the secure URL for the server from which the phone obtains directory information. This parameter specifies the URL that secured Cisco
Unified IP Phones use when you press the
Directory button.
Note
If you do not provide a Secure Directory
URL, the device uses the nonsecure URL.
If you provide both a secure URL and a nonsecure URL, the device chooses the appropriate URL, based on its capabilities.
Leave this field blank to accept the default setting.
Maximum length: 255
Enter the secure URL for the information that displays on the Cisco Unified IP Phone display when the phone is idle, as specified in Idle Timer field. For example, you can display a logo on the
LCD when the phone has not been used for 5 minutes.
Note
If you do not provide a Secure Idle URL, the device uses the nonsecure URL. If you provide both a secure URL and a nonsecure URL, the device chooses the appropriate URL, based on its capabilities.
To accept the default setting, leave this field blank.
Maximum length: 255
2-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 2 Using Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS)
HTTPS for Cisco Unified IP Phone Services
Table 2-2 Phone Configuration Settings for Secure URLs (continued)
Field
Secure Information URL
Secure Messages URL
Secure Services URL
Description
Enter the secure URL for the server location where the Cisco Unified IP Phone can find help text information. This information displays when the user presses the information (i) button or the question mark (?) button.
Note
If you do not provide a Secure
Information URL, the device uses the nonsecure URL. If you provide both a secure URL and a nonsecure URL, the device chooses the appropriate URL, based on its capabilities.
To accept the default setting, leave this field blank.
Maximum length: 255
Enter the secure URL for the messages server.
The Cisco Unified IP Phone contacts this URL when the user presses the Messages button.
Note
If you do not provide a Secure Messages
URL, the device uses the nonsecure URL.
If you provide both a secure URL and a nonsecure URL, the device chooses the appropriate URL, based on its capabilities.
To accept the default setting, leave this field blank.
Maximum length: 255
Enter the secure URL for Cisco Unified IP Phone services. The is the location that the secure Cisco
Unified IP Phone contacts when the user presses the Services button.
Note
If you do not provide a Secure Services
URL, the device uses the nonsecure URL.
If you provide both a secure URL and a nonsecure URL, the device chooses the appropriate URL, based on its capabilities.
To accept the default setting, leave this field blank.
Maximum length: 255
OL-24964-01
Cisco Unified Communications Manager Security Guide
2-5
Using Internet Explorer 8 to Save the Certificate to the Trusted Folder
Chapter 2 Using Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS)
Enterprise Parameter Configuration Settings
To support HTTPS, Cisco Unified Communications Manager Release 8.0(1) supports the following new
Enterprise Parameters:
•
Secured Authentication URL
•
•
•
•
•
Secured Directory URL
Secured Idle URL
Secured Information URL
Secured Messaged URL
Secured Services URL
Using Internet Explorer 8 to Save the Certificate to the Trusted
Folder
Be sure to import the Cisco Unified Communications Manager certificate to Internet Explorer 8 to secure access without having to reload the certificate every time that you restart the browser. If you continue to a website that has a certificate warning and the certificate is not in the trust store, Internet Explorer 8 remembers the certificate for the current session only.
After you download the server certificate, Internet Explorer 8 continues to display certificate errors for the website. You can ignore the security warnings when the Trusted Root Certificate Authority trust store for the browser contains the imported certificate.
The following procedure describes how to import the Cisco Unified Communications Manager certificate to the root certificate trust store for Internet Explorer 8.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Browse to application on the Tomcat server (for example, enter the hostname, localhost, or IP address for Cisco Unified Communications Manager Administration in the browser).
The browser displays a Certificate Error: Navigation Blocked message to indicate that this website is untrusted.
To access the server, click Continue to this website (not recommended).
The Cisco Unified Communications Manager Administration window displays, and the browser displays the address bar and Certificate Error status in red.
To import the server certificate, click the Certificate Error status box to display the status report. Click the View Certificates link in the report.
Verify the certificate details.
Select the General tab in the Certificate window and click Install Certificate.
The Certificate Import Wizard launches.
To start the Wizard, click Next.
The Certificate Store window displays.
Verify that the Automatic option, which allows the wizard to select the certificate store for this certificate type, is selected and click Next.
Cisco Unified Communications Manager Security Guide
2-6 OL-24964-01
Chapter 2 Using Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS)
Using Internet Explorer 8 to Save the Certificate to the Trusted Folder
Step 8
Step 9
Step 10
Step 11
Verify the setting and click Finish.
A security warning displays for the import operation.
To install the certificate, click Yes.
The Import Wizard displays “The import was successful.”
Click OK. The next time that you click the View certificates link, the Certification Path tab in the
Certificate window displays “This certificate is OK.”
To verify that the trust store contains the imported certificate, click Tools > Internet Options in the
Internet Explorer toolbar and select the Content tab. Click Certificates and select the Trusted Root
Certifications Authorities tab. Scroll to find the imported certificate in the list.
After importing the certificate, the browser continues to display the address bar and a Certificate Error status in red. The status persists even if you reenter the hostname, localhost, or IP address or refresh or relaunch the browser.
Additional Information
See the
“Related Topics” section on page 2-12 .
Copying the Certificate to File
Copying the certificate to a file and storing it locally allows you to restore the certificate whenever necessary.
Performing the following procedure copies the certificate by using a standard certificate storage format.
To copy the certificate contents to file, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Click the Certificate Error status box.
Click View Certificates.
Click the Details tab.
Click the Copy to File button.
The Certificate Export Wizard displays. Click Next.
The following list defines the file formats from which you can choose. Choose the file format that you want to use for the exported file; click Next.
•
DER encoded binary X.509 (.CER)—Uses DER to transfer information between entities.
•
•
Base-64 encoded X.509 (.CER)—Sends secure binary attachments over the internet; uses ASCII text format to prevent corruption of file.
Cryptographic Message Syntax Standard-PKCS #7 Certificates (.P7B)—Exports the certificate and all certificates in the certification path to the chosen PC.
Browse to the location to which you want to export the file copy and name the file. Click Save.
The file name and path display in the Certificate Export Wizard pane. Click Next.
Your file and settings display. Click Finish.
OL-24964-01
Cisco Unified Communications Manager Security Guide
2-7
Chapter 2 Using Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS)
Using Firefox with HTTPS
Step 10
When the successful export dialog box displays, click OK.
Additional Information
See the
“Related Topics” section on page 2-12
.
Using Firefox with HTTPS
The first time that you (or a user) accesses Cisco Unified Communications Manager Administration or other Cisco Unified Communications Manager SSL-enabled virtual directories (after the Cisco Unified
Communications Manager installation/upgrade) from a browser client, a Security Alert dialog box asks whether you trust the server.
When the dialog box displays, you must perform one of the following tasks:
•
By clicking I Understand The Risks, you choose to trust the certificate for the current web session only. If you trust the certificate for the current session only, the Security Alert dialog box displays each time that you access the application; that is, until you install the certificate in the trusted folder.
•
By clicking Get Me Out Of Here, you cancel the action. No authentication occurs, and you cannot access the web application. To access the web application, you must click I Understand The Risks.
The following sections tell you how to use HTTPS with the Safari browser:
•
•
Using Safari 4.x to Save the Certificate to the Trusted Folder, page 2-10
Copying the Certificate to File, page 2-11
Using Firefox 3.x to Save the Certificate to the Trusted Folder
Perform the following procedure to save the HTTPS certificate in the trusted folder in the browser client.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Access the Tomcat server (for example, enter the hostname, localhost, or IP address for Cisco Unified
Communications Manager Administration in the browser).
When the Security Alert dialog box displays, click I Understand The Risks.
Click Add Exception.
The Add Exception dialog box displays.
Click Get Certificate.
Check the Permanently store this exception check box.
Click Confirm Security Exception.
To view the details of the certificate by performing the following steps:
a.
From the Firefox browser, click Tools > Options.
The Options dialog box displays
b.
c.
Click Advanced.
Click View Certificates.
2-8
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 2 Using Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS) e.
f.
d.
g.
h.
The Certificate Manager dialog box displays.
Highlight the certificate that you want to view and click View.
The Certificate Viewer dialog box displays.
Click the Details tab.
In the Certificate Fields field, highlight the field that you want to view.
Details display in the Field Values field.
From the Certificate Viewer dialog box, click Close.
From the Certificate Manager dialog box, click OK.
Using Firefox with HTTPS
Copying the Certificate to File
Copying the certificate to a file and storing it locally allows you to restore the certificate whenever necessary.
Performing the following procedure copies the certificate by using a standard certificate storage format.
To copy the certificate contents to file, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
From the Firefox browser, click Tools > Options.
The Options dialog box displays.
If it is not already selected, click Advanced.
Click the Encryption tab and click View Certificates.
The Certificate Manager dialog box displays.
Click the Servers tab.
Highlight the certificate you want to copy and click Export.
The Save Certificate to File dialog box displays.
Browse to the location to which you want to copy the file.
From the Save as type drop-down list, choose the file type from the following options:
•
X.509 Certificate (PEM)—Uses PEM to transfer information between entities.
•
•
•
•
X.509 Certificate with chain (PEM)—Uses Privacy Enhanced Mail to verify the certificate chain and transfer information between entities.
X.509 Certificate (DER)—Uses DER to transfer information between entities.
X.509 Certificate (PKCS#7)—PKCS#7 is a standard for signing or encrypting data. Since the certificate is needed to verify signed data, it is possible to include it in the SignedData structure.
A .P7C-file is just a degenerated SignedData structure, without any data to sign.
X.509 Certificate with chain (PKCS#7)—Uses PKCS#7 to verify the certificate chain and transfer information between entities.
Click Save.
Click OK.
OL-24964-01
Cisco Unified Communications Manager Security Guide
2-9
Chapter 2 Using Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS)
Using Safari with HTTPS
Additional Information
See the
“Related Topics” section on page 2-12
.
Using Safari with HTTPS
The first time that you (or a user) accesses Cisco Unified Communications Manager Administration or other Cisco Unified Communications Manager SSL-enabled virtual directories (after the Cisco Unified
Communications Manager installation/upgrade) from a browser client, a Security Alert dialog box asks whether you trust the server.
When the dialog box displays, you must perform one of the following tasks:
•
•
•
By clicking Yes, you choose to trust the certificate for the current web session only. If you trust the certificate for the current session only, the Security Alert dialog box displays each time that you access the application; that is, until you install the certificate in the trusted folder.
By clicking Show Certificate > Install Certificate, you intend to perform certificate installation tasks, so you always trust the certificate. If you install the certificate in the trusted folder, the
Security Alert dialog box does not display each time that you access the web application.
By clicking No, you cancel the action. No authentication occurs, and you cannot access the web application. To access the web application, you must click Yes or install the certificate via the Show
Certificate > Install Certificate options.
Note
The address that you use to access Cisco Unified Communications Manager must match the name on the certificate, or a message will display by default. If you access the web application by using the localhost or IP address after you install the certificate in the trusted folder, a security alert indicates that the name of the security certificate does not match the name of the site that you are accessing.
The following sections tell you how to use HTTPS with Internet Explorer:
•
Using Firefox 3.x to Save the Certificate to the Trusted Folder, page 2-8
•
Copying the Certificate to File, page 2-7
Using Safari 4.x to Save the Certificate to the Trusted Folder
Perform the following procedure to save the HTTPS certificate in the trusted folder in the browser client.
Procedure
Step 1
Step 2
Access the Tomcat server (for example, enter the hostname, localhost, or IP address for Cisco Unified
Communications Manager Administration in the browser).
When the Security Alert dialog box displays, click Show Certificate.
You can click the Details tab to view the details of the certificate if you choose to verify the certificate data. To display a subset of settings, if available, choose one of the following options:
•
•
All—All options display in the Details pane.
Version 1 Fields Only—Version, Serial Number, Signature Algorithm, Issuer, Valid From, Valid To,
Subject, and the Public Key options display.
2-10
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 2 Using Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS)
Using Safari with HTTPS
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
•
•
Extensions Only—Subject Key Identifier, Key Usage, and the Enhanced Key Usage options display.
Critical Extensions Only—Critical Extensions, if any, display
Properties Only—Thumbprint algorithm and the thumbprint options display.
•
In the Certificate pane, click Install Certificate.
When the Certificate Import Wizard displays, click Next.
Click the Place all certificates in the following store radio button; click Browse.
Browse to Trusted Root Certification Authorities; select it and click OK.
Click Next.
Click Finish.
A Security Warning Box displays the certificate thumbprint for you.
To install the certificate, click Yes.
A message states that the import was successful. Click OK.
In the lower, right corner of the dialog box, click OK.
To trust the certificate, so you do not receive the dialog box again, click Yes.
Tip
You can verify the certificate was installed successfully by clicking the Certification Path tab in the Certificate pane.
Copying the Certificate to File
Copying the certificate to a file and storing it locally allows you to restore the certificate whenever necessary.
Performing the following procedure copies the certificate by using a standard certificate storage format.
To copy the certificate contents to file, perform the following procedure:
Procedure
Step 1
In the Security Alert dialog box, click Show Certificate.
Step 2
Step 3
Step 4
Step 5
Tip
In Safari, click the Certificate Error status box to display the Show Certificate option.
Click the Details tab.
Click the Copy to File button.
The Certificate Export Wizard displays. Click Next.
The following list defines the file formats from which you can choose. Choose the file format that you want to use for the exported file; click Next.
•
•
DER encoded binary X.509 (.CER)—Uses DER to transfer information between entities.
Base-64 encoded X.509 (.CER)—Sends secure binary attachments over the internet; uses ASCII text format to prevent corruption of file.
Cisco Unified Communications Manager Security Guide
OL-24964-01 2-11
Chapter 2 Using Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS)
Where to Find More Information
Step 6
Step 7
Step 8
Step 9
•
Cryptographic Message Syntax Standard-PKCS #7 Certificates (.P7B)—Exports the certificate and all certificates in the certification path to the chosen PC.
Browse to the location to which you want to export the file copy and name the file. Click Save.
The file name and path display in the Certificate Export Wizard pane. Click Next.
Your file and settings display. Click Finish.
When the successful export dialog box displays, click OK.
Additional Information
See the
“Related Topics” section on page 2-12
.
Where to Find More Information
Related Topics
Related Cisco Documentation
•
Cisco Unified Serviceability Administration Guide
•
Cisco Unified Communications Manager Administration Guide
•
Microsoft documentation that is available on HTTPS
2-12
Cisco Unified Communications Manager Security Guide
OL-24964-01
C H A P T E R
3
Security by Default
This section contains the following topics:
•
•
•
•
•
•
•
•
Trust Verification Service, page 3-2
Supported Cisco Unified IP Phones, page 3-4
Regenerating Certificates, page 3-4
Backing Up the System after Regenerating the TFTP Certificate, page 3-5
•
•
Rolling Back the Cluster to a Pre-8.0 Release, page 3-7
Migrating IP Phones between Clusters with Cisco Unified Communications Manager 8.0 and ITL
Overview
Security by Default provides the following automatic security features for Cisco Unified IP Phones:
•
Signing of the phone configuration files.
•
•
Support for phone configuration file encryption.
https with Tomcat and other Web services (Midlets)
For Cisco Unified Communications Manager Release 8.0, these security features are provided by default without running the CTL Client.
Note
Secure Signaling and Media will still require running the CTL Client and using the hardware eTokens.
Cisco Unified Communications Manager Security Guide
3-1 OL-24964-01
Chapter 3 Security by Default
Trust Verification Service
Trust Verification Service
Trust Verification Service (TVS) is the main component of Security by Default. TVS enables Cisco
Unified IP Phones to authenticate application servers, such as EM services, directory, and MIDlet, during HTTPS establishment.
TVS provides the following features:
•
•
•
Scalability—Cisco Unified IP Phone resources are not impacted by the number of certificates to trust.
Flexibility—Addition or removal of trust certificates are automatically reflected in the system.
Security by Default—Non-media and signaling security features are part of the default installation and do not require user intervention.
Note
Enabling secure signaling and media requires the CTL Client.
TVS Overview
The following basic concepts describe the Trust Verification Service:
•
TVS runs on the Cisco Unified Communications Manager server and authenticates certificates on behalf of the Cisco Unified IP Phone.
•
•
Instead of downloading all the trusted certificates, Cisco Unified IP Phone only need to trust TVS.
•
•
The TVS certificates and a few key certificates are bundled in a new file: the Initial Trust List file
(ITL).
The ITL file gets generated automatically without user intervention.
The ITL file gets downloaded by Cisco Unified IP Phones and trust flows from there.
Initial Trust List
Cisco Unified IP Phones need an Initial Trust List (ITL) to perform the following tasks:
•
Authenticate their configuration file signature.
•
•
Talk securely to CAPF, a pre-requisite to support configuration files encryption.
Trust TVS (which authenticates https certificates among other functions).
If the Cisco Unified IP Phone does not have an existing CTL file, it trusts the first ITL File automatically, like it does the CTL File. Subsequent ITL files must be either signed by the same TFTP private key or
TVS must be able to return the certificate corresponding to the signer.
If the Cisco Unified IP Phone has an existing CTL file, it uses the CTL file to authenticate the ITL file signature.
ITL Files
The ITL file contains the initial trust list. The ITL file has the same format as the CTL file and is basically a smaller, leaner version of the CTL file. The following attributes apply to the ITL file:
Cisco Unified Communications Manager Security Guide
3-2 OL-24964-01
Chapter 3 Security by Default
Autoregistration
•
•
•
Unlike the CTL File, the system builds the ITL file automatically when you install the cluster, and the ITL file gets updated automatically if the contents need to be changed.
The ITL File does not require eTokens. It uses a soft eToken (the TFTP private key).
The ITL File is downloaded by Cisco Unified IP Phones at boot up time or during reset, right after downloading the CTL File (if present).
Contents of the ITL File
The ITL File contains the following certificates:
•
The certificate of the TFTP server. This certificate allows to authenticate the ITL File signature and the phone configuration file signature.
•
•
All the TVS certificates in the cluster. These certificates allow phone to talk to TVS securely to request certificates authentication.
The CAPF certificate. This allows to support configuration file encryption. The CAPF certificate is not really required in the ITL File (TVS can authenticate it) but it simplifies the connection to CAPF.
Like the CTL File, the ITL File contains a record for each certificate. Each record contains:
•
A certificate.
•
•
Pre-extracted certificate fields for easy look up by the Cisco Unified IP Phone.
Certificate role (TFTP, CUCM, TFTP+CCM, CAPF, TVS, SAST)
The TFTP certificate is present in 2 ITL records with 2 different roles:
•
TFTP or TFTP+CCM role: to authenticate configuration file signature.
•
SAST role: to authenticate ITL file signature.
ITL and CTL File Interaction
The Cisco Unified IP Phone still relies on the CTL file to know the cluster security mode (nonsecure or mixed mode). The CTL File tracks the cluster security mode by including the Cisco Unified
Communications Manager certificate in the Cisco Unified Communications Manager record.
The ITL File also contains the cluster security mode indication.
Autoregistration
If the cluster is in nonsecure mode, the system supports autoregistration. The default configuration file will also be signed. Cisco Unified IP Phones that do not support Security by Default will be served a nonsigned default configuration file.
Note
In mixed mode, the system does not support autoregistration.
OL-24964-01
Cisco Unified Communications Manager Security Guide
3-3
Chapter 3 Security by Default
Supported Cisco Unified IP Phones
Supported Cisco Unified IP Phones
You can obtain a list of the Cisco Unified IP Phones that support security by default by using Cisco
Unified Reporting. To use Cisco Unified Reporting, follow this procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
From the Cisco Unified Reporting main window, click System Reports.
From the System Reports list, click Unified CM Phone Feature List.
Choose the appropriate feature from the Feature pull-down menu.
Click Submit.
For more information about using Cisco Unified Reporting, see the Cisco Unified Reporting
Administration Guide.
Regenerating Certificates
If you regenerate one of the Cisco Unified Communications Manager certificates, you must perform the steps in this section.
Regenerating the CAPF Certificate
To regenerate the CAPF certificate, perform the following steps:
Step 1
Step 2
Step 3
Step Additional Information
Regenerate the CAPF certificate.
See Chapter 6, “Security”, in the Cisco Unified Communications
Operating System Administration Guide.
If you have a CTL file then you must rerun the CTL client.
See Chapter 4, “Configuring the Cisco CTL Client”, in the Cisco
Unified Communications Operating System Administration
Guide.
Restart the CAPF service.
See the “Activating the Certificate Authority Proxy Function
Service” section, in the Cisco Unified Communications Manager
Security Guide.
Note
If the CAPF certificate is on the publisher, you might observe the phones restarting automatically to update their ITL file.
Regenerating a TVS Certificate
No manual steps are required to regenerate a TVS certificate.
3-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 3 Security by Default
Tomcat certificate regeneration
Note
If you plan to regenerate both TVS and TFTP certificates, regenerate the TVS certificate, wait for the possible phone restarts to complete, and then regenerate the TFTP certificate.
Regenerating a TFTP Certificate
To regenerate a TFTP certificate, follow these steps:
Note
If you plan to regenerate multiples certificates you must regenerate the TFTP certificate last. Wait for the possible phone restarts to complete before you regenerate the TFTP certificate. You might need to manually delete the ITL File from all Cisco Unified IP Phones, if you do not follow this procedure.
Step 1
Step 2
Step 3
Step 4
Step Additional Information
Regenerate the TFTP certificate.
See Chapter 6, “Security,” in the Cisco Unified Communications
Operating System Administration Guide.
If the TFTP service was activated, wait until all the phones have automatically restarted.
If your cluster is in mixed mode, run the CTL client.
If the cluster is part of an EMCC deployment, repeat the steps for bulk certificate provisioning.
See Chapter 4, “Configuring the CTL Client,” in the Cisco
Unified Communications Manager Security Guide.
See Chapter 6, “Security,” in the Cisco Unified Communications
Operating System Administration Guide.
Tomcat certificate regeneration
To regenerate the CAPF certificate, perform the following steps:
Step 1
Step 2
Step 3
Step Additional Information
Regenerate the Tomcat certificate. See Chapter 6, “Security”, in the Cisco Unified Communications
Operating System Administration Guide.
Restart the Tomcat service
If the cluster is part of an EMCC deployment, repeat the steps for bulk certificate provisioning.
See Chapter 6, “Security”, in the Cisco Unified Communications
Operating System Administration Guide.
See Chapter 6, “Security,” in the Cisco Unified Communications
Operating System Administration Guide.
Backing Up the System after Regenerating the TFTP Certificate
The trust anchor for the ITL File is a software entity: the TFTP private key. If the server crashes, the key gets lost, and phones will not be able to validate new ITL File.
OL-24964-01
Cisco Unified Communications Manager Security Guide
3-5
Chapter 3 Security by Default
Refresh Upgrade from Cisco Unified Communications Manager Release 7.x to Release 8.6 or later
In Cisco Unified Communications Manager Release 8.0, the TFTP certificate and private key both get backed up by the Disaster Recovery System. The system encrypts the backup package to keep the private key secret. If the server crashes, the previous certificates and keys will be restored.
Whenever the TFTP certificate gets regenerated, you must create a new system backup. For backup procedures, see the Disaster Recovery System Administration Guide.
Refresh Upgrade from Cisco Unified Communications Manager
Release 7.x to Release 8.6 or later
To upgrade your cluster from Release 7.x to Release 8.6 or later, follow this procedure:
Procedure
Step 1
Follow the normal procedure for upgrading a cluster. For more information, see Chapter 7, “Software
Upgrades,” in the Cisco Unified Communications Operating System Administration Guide.
Tip
Step 2
After you finish upgrading all nodes in the cluster to Cisco Unified Communications Manager Release
8.6 or later, you must also follow all the steps in this procedure to ensure that your Cisco Unified IP
Phones register with the system.
If you are running one of the following releases in mixed mode, you must run the CTL client:
Cisco Unified Communications Manager Release 7.1(2)
•
All regular releases of 7.1(2)
•
All ES releases of 712 prior to 007.001(002.32016.001)
Cisco Unified Communications Manager Release 7.1(3)
•
All regular releases of 713 prior to 007.001(003.21900.003) = 7.1(3a)su1a
•
All ES releases of 713 prior to 007.001(003.21005.001)
Note
For more information about running the CTL client, see Chapter 4, “Configuring the CTL
Client,” in the Cisco Unified Communications Manager Security Guide.
Step 3
Wait ten minutes for the Cisco Unified IP Phones to automatically restart and register with Cisco Unified
Communications Manager.
Back Up Your Cluster
Caution
You must back up your cluster using the Disaster Recovery System (DRS) to be able to recover the cluster.
Step 4
To backup your cluster using DRS, see the Disaster Recovery System Administration Guide.
3-6
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 3 Security by Default
Rolling Back the Cluster to a Pre-8.0 Release
Rolling Back the Cluster to a Pre-8.0 Release
Before you roll back a cluster to a pre-8.0 release of Cisco Unified Communications Manager, you must prepare the cluster for rollback using the Prepare Cluster for Rollback to pre-8.0 enterprise parameter.
To prepare the cluster for rollback, follow this procedure on each server in the cluster:
Procedure
Step 1
From Cisco Unified Communications Manager Administration, choose System > Enterprise
Parameters.
The Enterprise Parameters Configuration window displays.
Set the Prepare Cluster for Rollback to pre-8.0 enterprise parameter to True.
Step 2
Step 3
Step 4
Step 5
Note
Enable this parameter only if you are preparing to rollback your cluster to a pre-8.6 release of
Cisco Unified Communications Manager. Phone services that use https (for example, extension mobility) will not work while this parameter is enabled. However, users will be able to continue making and receiving basic phone calls while this parameter is enabled.
Wait ten minutes for the Cisco Unified IP Phones to automatically restart and register with Cisco Unified
Communications Manager.
Revert the Cluster to the Previous Release
Revert each server in the cluster to the previous release. For more information about reverting a cluster to a previous version, see Chapter 7, “Software Upgrades” in the Cisco Unified Communications
Operating System Administration Guide.
Wait until the cluster finishes switching to the previous version.
If you are running one of the following releases in mixed mode, you must run the CTL client:
Cisco Unified Communications Manager Release 7.1(2)
•
All regular releases of 7.1(2)
•
All ES releases of 712 prior to 007.001(002.32016.001)
Cisco Unified Communications Manager Release 7.1(3)
•
All regular releases of 713 prior to 007.001(003.21900.003) = 7.1(3a)su1a
•
All ES releases of 713 prior to 007.001(003.21005.001)
Note
For more information about running the CTL client, see Chapter 4, “Configuring the CTL
Client,” in the Cisco Unified Communications Manager Security Guide.
OL-24964-01
Cisco Unified Communications Manager Security Guide
3-7
Chapter 3 Security by Default
Migrating IP Phones between Clusters with Cisco Unified Communications Manager 8.0 and ITL Files
Switching Back to Release 8.6 or later
If you decide to switch back to the Release 8.6 or later release partition after you revert the cluster to
Release 7.x, follow the procedure in this section.
Procedure
Step 1
Step 2
Follow the procedure for switching the cluster back to the inactive partition. For more information, see the Cisco Unified Communications Operating System Administration Guide.
If you were running one of the following releases in mixed mode, you must run the CTL client:
Cisco Unified Communications Manager Release 7.1(2)
•
All regular releases of 7.1(2)
•
All ES releases of 712 prior to 007.001(002.32016.001)
Cisco Unified Communications Manager Release 7.1(3)
•
All regular releases of 713 prior to 007.001(003.21900.003) = 7.1(3a)su1a
•
All ES releases of 713 prior to 007.001(003.21005.001)
Note
For more information about running the CTL client, see Chapter 4, “Configuring the CTL
Client,” in the Cisco Unified Communications Manager Security Guide.
Step 3
Step 4
From Cisco Unified Communications Manager Administration, choose System > Enterprise
Parameters.
The Enterprise Parameters Configuration window displays.
Set the Prepare Cluster for Rollback to pre-8.6 enterprise parameter to False.
Wait ten minutes for the Cisco Unified IP Phones to automatically restart and register with Cisco Unified
Communications Manager.
Migrating IP Phones between Clusters with Cisco Unified
Communications Manager 8.0 and ITL Files
Cisco Unified Communications Manager 8.0(1) and later introduced the new Security By Default feature and the use of Initial Trust List (ITL) files. With this new feature, you must be careful when moving phones between different CiscoUnified CM clusters. If you don’t follow the proper steps it is possible to encounter a situation where thousands of phones must manually have their ITL files deleted.
Cisco Unified IP Phones that support the new ITL file must download this special file from their Cisco
Unified Communications Manager TFTP server. Once an ITL file is installed on a phone, all future configuration files and ITL file updates must be either signed by the TFTP Server certificate currently installed on the phone or signed by a TFTP certificate that can be validated by one of the cluster's TVS services. The certificates of TVS services within the cluster are listed in the ITL file.
3-8
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 3 Security by Default
Migrating IP Phones between Clusters with Cisco Unified Communications Manager 8.0 and ITL Files
With this new security functionality in mind here are the three problems that can occur when moving a phone from one cluster to another cluster.
1.
2.
The ITL file of the new cluster is not signed by the current ITL file signer, so the phone can not accept the new ITL file or config files.
The TVS servers listed in the existing ITL of the phone may not be reachable when the phones are moved to the new cluster.
3.
Even if the TVS servers are reachable for certificate verification, the old cluster servers may not have the new server's certificates.
If one or more of these three problems are encountered one possible solution is to delete the ITL file manually from all phones being moved between clusters. However, this is not a desirable solution since it requires massive effort as the number of phones increases.
The most preferred option is to make use of the Cisco Unified CM Enterprise Parameter "Prepare Cluster for Rollback to pre-8.0", see
Rolling Back the Cluster to a Pre-8.0 Release, page 3-7
. Once this parameter is set to True, the phones download a special ITL file that contains empty TVS and TFTP certificate sections.
When a phone has an empty ITL file it accepts any unsigned configuration file (for migrations to pre
CiscoUnified CM 8.x clusters), and also accepts any new ITL file (for migrations to different
CiscoUnified CM 8.x clusters).
The empty ITL file can be verified on the phone by checking Settings > Security > Trust List > ITL.
Empty entries appear where the old TVS and TFTP servers used to be.
The phones must have access to the old CiscoUnified CM servers only as long as it takes them to download the new empty ITL files.
If you plan to keep the old cluster online, disable the "Prepare Cluster for Rollback to pre-8.0" Enterprise
Parameter to restore Security By Default.
Bulk Certificate Export
If both the old and new clusters are online at the same time, you can use the Bulk Certificate migration method.
Remember that the Cisco Unified IP Phones verify every downloaded file against either the ITL file, or against a TVS server that exists in the ITL file. If the phone needs to move to a new cluster, the ITL file that the new cluster presents must be trusted by the old cluster TVS certificate store.
Note
The Bulk Certificate Export method only works if both clusters are online with network connectivity while the phones are being migrated.
To use the the Bulk Certificate Export method complete the following procedure:
Procedure
Step 1
Step 2
Step 3
From Cisco Unified Operating System Administration, choose Security > Bulk Certificate
Management.
Export certificates from new destination cluster (TFTP only) to a central SFTP server.
Consolidate certificates (TFTP only) on the SFTP server using the Bulk Certificate interface.
OL-24964-01
Cisco Unified Communications Manager Security Guide
3-9
Chapter 3 Security by Default
Migrating IP Phones between Clusters with Cisco Unified Communications Manager 8.0 and ITL Files
Step 4
Step 5
On the origination cluster use the Bulk Certificate function to import the TFTP certificates from the central SFTP server.
Use DHCP option 150, or some other method, to point the phones to the new destination cluster.
The phones download the new destination cluster ITL file and attempt to verify it against their existing
ITL file. The certificate is not in the existing ITL file so the phone requests the old TVS server to verify the signature of the new ITL file. The phone sends a TVS query to the old origination cluster on TCP port 2445 to make this request.
If the certificate export/consolidate/import process works correctly then the TVS returns success, and the phone replaces the ITL file in memory with the newly downloaded ITL file.
The phones can now download and verify the signed configuration files from the new cluster.
3-10
Cisco Unified Communications Manager Security Guide
OL-24964-01
OL-24964-01
C H A P T E R
4
Configuring the Cisco CTL Client
This chapter contains information on the following topics:
•
Cisco CTL Client Overview, page 4-2
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Configuration Tips for Cisco CTL Client Configuration, page 4-3
Important Installation Note for CTL Client 5.0 Plug-In, page 4-2
Important Installation Note for Windows 2000 Users, page 4-3
Configuration Tips for Cisco CTL Client Configuration, page 4-3
Cisco CTL Client Configuration Checklist, page 4-4
Activating the Cisco CTL Provider Service, page 4-5
Activating the Cisco CAPF Service, page 4-6
Configuring Ports for the TLS Connection, page 4-6
Installing the Cisco CTL Client, page 4-8
Upgrading the Cisco CTL Client and Migrating the Cisco CTL File, page 4-10
Configuring the Cisco CTL Client, page 4-10
Updating the CTL File, page 4-13
Deleting a CTL File Entry, page 4-15
Updating the Cisco Unified Communications Manager Security Mode, page 4-15
Cisco CTL Client Configuration Settings, page 4-15
Verifying the Cisco Unified Communications Manager Security Mode, page 4-17
Setting the Smart Card Service to Started and Automatic, page 4-18
Changing the Security Token Password (Etoken), page 4-19
Deleting the CTL File on the Cisco Unified IP Phone, page 4-20
Determining the Cisco CTL Client Version, page 4-21
Verifying or Uninstalling the Cisco CTL Client, page 4-21
Where to Find More Information, page 4-21
Cisco Unified Communications Manager Security Guide
4-1
Chapter 4 Configuring the Cisco CTL Client
Cisco CTL Client Overview
Cisco CTL Client Overview
Device, file, and signaling authentication rely on the creation of the Certificate Trust List (CTL) file, which is created when you install and configure the Cisco Certificate Trust List (CTL) Client on a single
Windows workstation or server that has a USB port.
Note
Supported Windows versions for Cisco CTL Client include Windows 2000, Windows XP, Windows
Vista, and Windows 7. Do not use Terminal Services to install the Cisco CTL Client. Cisco installs
Terminal Services, so Cisco Technical Assistance Center (TAC) can perform remote troubleshooting and configuration tasks.
The CTL file contains entries for the following servers or security tokens:
•
•
•
System Administrator Security Token (SAST)
Cisco CallManager and Cisco TFTP services that are running on the same server
Certificate Authority Proxy Function (CAPF)
•
•
TFTP server(s)
ASA firewall
The CTL file contains a server certificate, public key, serial number, signature, issuer name, subject name, server function, DNS name, and IP address for each server.
After you create the CTL file, you must restart the Cisco CallManager and Cisco TFTP services in Cisco
Unified Serviceability on all nodes that run these services. The next time that the phone initializes, it downloads the CTL file from the TFTP server. If the CTL file contains a TFTP server entry that has a self-signed certificate, the phone requests a signed configuration file in .sgn format. If no TFTP server contains a certificate, the phone requests an unsigned file.
After the Cisco CTL Client adds a server certificate to the CTL file, you can display the certificate in the
CTL Client GUI.
When you configure a firewall in the CTL file, you can secure a Cisco ASA Firewall as part of a secure
Cisco Unified Communications Manager system. The Cisco CTL Client displays the firewall certificate as a “CCM” certificate.
Cisco Unified Communications Manager Administration uses an etoken to authenticate the TLS connection between the Cisco CTL Client and Cisco CTL Provider.
Important Installation Note for CTL Client 5.0 Plug-In
If you are upgrading to the CTL Client 5.0 or 5.2 plug-in, you first need to remove eToken Run Time
Environment 3.00 by performing the following steps:
Procedure
Step 1
Step 2
Step 3
Download Windows Installer Cleanup Utility at the following URL: http://support.microsoft.com/kb/290301
Install the utility on your PC.
Run the utility.
Cisco Unified Communications Manager Security Guide
4-2 OL-24964-01
Chapter 4 Configuring the Cisco CTL Client
Step 4
Step 5
Find eToken rte3.0 in the list of programs and remove it.
Proceed with CTL Client installation.
Important Installation Note for Windows 2000 Users
Important Installation Note for Windows 2000 Users
If you are running Windows 2000 on your workstation or server, you must download Windows Installer
3.0 updates to correctly install CTL Client plug-ins. You can obtain Windows Installer 3.0 at the following URL: http://www.microsoft.com/downloads/details.aspx?familyid=5FBC5470-B259-4733-A914-A956122E
08E8&displaylang=en
Note
Windows 2000 comes with Windows Installer 2.0.
Windows Installer 3.0 requires validation. Follow the instructions to have your PC validated. Then, install Windows Installer 3.0, reboot your machine if necessary, and then proceed with CTL Client installation.
Configuration Tips for Cisco CTL Client Configuration
Consider the following information when you configure the Cisco CTL Client in Cisco Unified
Communications Manager:
•
The Cisco CTL Client limits the file size of a CTL file to 32 kilobytes because the phones cannot accept a larger CTL file. The following factors affect the size of a CTL file:
–
The number of nodes in the cluster
More nodes require more certificates in the CTL file.
–
The number of firewalls that are used for TLS Proxy
•
•
–
Firewalls with TLS Proxy feature, which are the same as nodes, therefore get included in the
CTL file.
Whether an external certificate authority (CA) signs the CAPF and CallManager certificates
Because certificates (CAPF/CallManager) that are signed by an external CA are significantly larger than default self-signed certificates, this can limit the maximum number of certificates that can fit into the CTL file.
These factors directly limit the maximum number of certificates that you can fit in a 32-kilobyte
CTL file, so they dictate the maximum number of nodes or firewalls that you can have in a secure
Cisco Unified Communications Manager deployment.
Ensure that the Cisco Unified Communications Manager node hostname or hostnames are resolvable on the remote PC where the Cisco CTL Client is installed, or the Cisco CTL Client will not function correctly.
You must activate the Cisco CTL Provider service. If you have a cluster environment, you must activate the Cisco CTL Provider service on all servers in the cluster.
OL-24964-01
Cisco Unified Communications Manager Security Guide
4-3
Chapter 4 Configuring the Cisco CTL Client
Cisco CTL Client Configuration Checklist
•
•
•
After you create or update the CTL file, you must restart the Cisco CallManager and Cisco TFTP services in Cisco Unified Serviceability on all Cisco Unified Communications Manager servers that run these services and on all TFTP servers in the cluster.
When the Cisco CTL Client contains entries for off-cluster servers, such as alternate or centralized
TFTP server, you must also run the Cisco CTL Provider service on these servers.
The alternate TFTP server section of the Cisco CTL Client GUI designates a Cisco TFTP server that exists in a different cluster. Use the Alternate TFTP Server Tab settings to configure alternate and centralized TFTP servers in the Cisco CTL Client.
Note
See “Cisco TFTP” in the Cisco Unified Communications Manager System Guide for information about configuring off-cluster (alternate and centralized) TFTP servers with TFTP service parameters.
•
For centralized TFTP configurations, all off-cluster TFTP servers that are operating in mixed mode must add the Master TFTP server or Master TFTP server IP address to the off-cluster CTL file. The master TFTP server serves configuration files from all alternate TFTP servers in the alternate file list that is configured for the master TFTP server. Clusters in a centralized TFTP configuration do not need to use the same security mode; each cluster can select its own mode.
Cisco CTL Client Configuration Checklist
Client for the first time. See
Unified Communications Manager.
Table 4-1 Cisco CTL Client Configuration Checklist
Configuration Steps
Step 1
Ensure that all the servers in the cluster are online and reachable from the PC on which the CTL Client will run. If a server is configured with a hostname, ping the hostname to verify reachability.
Step 2
Ensure that all of the hostnames of the cluster servers are defined in the DNS server that is configured on the publisher server.
Related Procedures and Topics
Step 3
Activate the Cisco CTL Provider service in Cisco Unified
Serviceability.
Activating the Cisco CTL Provider Service, page 4-5
Activate the Cisco CTL Provider service on each Cisco Unified
Communications Manager server in the cluster.
Tip
If you activated this service prior to a Cisco Unified
Communications Manager upgrade, you do not need to activate the service again. The service automatically activates after the upgrade.
4-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 4 Configuring the Cisco CTL Client
Activating the Cisco CTL Provider Service
Table 4-1 Cisco CTL Client Configuration Checklist (continued)
Configuration Steps
Step 4
Activate the Cisco Certificate Authority Proxy service in Cisco
Unified Serviceability.
Related Procedures and Topics
Activating the Certificate Authority Proxy
Tip
Activate the Cisco Certificate Authority Proxy service only on the first node in the cluster.
Step 5
Step 6
Step 7
Step 8
Timesaver
Performing this task before you install and configure the Cisco CTL Client ensures that you do not have to update the CTL file to use CAPF.
If you do not want to use the default settings, configure ports for the TLS connection.
Configuring Ports for the TLS Connection, page 4-6
Tip
If you configured these settings prior to a Cisco Unified
Communications Manager upgrade, the settings migrate automatically.
Obtain at least two security tokens and the passwords, hostnames/IP addresses, and port numbers for the servers that you will configure for the Cisco CTL Client.
Install the Cisco CTL Client.
Configuring the Cisco CTL Client, page 4-10
•
•
Configure the Cisco CTL Client.
•
Installing the Cisco CTL Client, page 4-8
Configuring the Cisco CTL Client, page 4-10
Activating the Cisco CTL Provider Service
After you configure the Cisco CTL Client, the Cisco CTL Provider service changes the security mode from nonsecure to mixed mode and transports the server certificates to the CTL file. The service then transports the CTL file to all Cisco Unified Communications Manager and Cisco TFTP servers.
If you activate this service and then upgrade Cisco Unified Communications Manager, Cisco Unified
Communications Manager automatically reactivates the service after the upgrade.
Tip
You must activate the Cisco CTL Provider service on all servers in the cluster.
To activate the service, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
In Cisco Unified Serviceability, choose Tools > Service Activation.
In the Servers drop-down list box, choose a server where you have activated the Cisco CallManager or
Cisco TFTP services.
Click the Cisco CTL Provider service radio button.
Click Save.
OL-24964-01
Cisco Unified Communications Manager Security Guide
4-5
Chapter 4 Configuring the Cisco CTL Client
Activating the Cisco CAPF Service
Tip
Perform this procedure on all servers in the cluster.
Note
You can enter a CTL port before you activate the Cisco CTL Provider service. If you want to change the default port number, see
“Configuring Ports for the TLS Connection” section on page 4-6
.
Step 5
Verify that the service runs on the servers. In Cisco Unified Serviceability, choose Tools > Control
Center - Feature Services to verify the state of the service.
Additional Information
See the
“Related Topics” section on page 4-21
.
Activating the Cisco CAPF Service
For information on activating this service, see the
“Activating the Certificate Authority Proxy Function
Service” section on page 10-6 .
Timesaver
Performing this task before you install and configure the Cisco CTL Client ensures that you do not have to update the CTL file to use CAPF.
Configuring Ports for the TLS Connection
You may have to configure a different TLS port number if the default port is currently being used or if you use a firewall and you cannot use the port within the firewall.
•
The Cisco CTL Provider default port for the TLS connection equals 2444. The Cisco CTL Provider port monitors requests from the Cisco CTL Client. This port processes Cisco CTL Client requests, such as retrieving the CTL file, setting the cluster security mode, and saving the CTL file to the
TFTP server.
Note
Cluster security mode configures the security capability for your standalone server or a cluster.
•
•
The Ethernet Phone Port monitors registration requests from the phone that is running SCCP. In nonsecure mode, the phone connects through port 2000. In mixed mode, the Cisco Unified
Communications Manager port for TLS connection equals the value for the Cisco Unified
Communications Manager port number added to (+) 443; therefore, the default TLS connection for
Cisco Unified Communications Manager equals 2443. Update this setting only if the port number is in use or if you use a firewall and you cannot use the port within the firewall.
The SIP Secure Port allows Cisco Unified Communications Manager to listen for SIP messages from phones that are running SIP. The default value equals 5061. If you change this port, you must restart the Cisco CallManager service in Cisco Unified Serviceability and reset the phones that are running
SIP.
Cisco Unified Communications Manager Security Guide
4-6 OL-24964-01
Chapter 4 Configuring the Cisco CTL Client
Configuring Ports for the TLS Connection
Tip
After you update the port(s), you must restart the Cisco CTL Provider service in Cisco Unified
Serviceability.
You must open the CTL ports to the data VLAN from where the CTL Client runs. Phones that are running
TLS for signaling back to Cisco Unified Communications Manager also use the ports that the CTL Client uses. Ensure that you open these ports to all VLANs where phones are configured for authenticated or encrypted status.
To change the default setting, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
Perform the following tasks, depending on the port that you want to change:
•
To change the Port Number parameter for the Cisco CTL Provider service, perform
•
To change the Ethernet Phone Port or SIP Phone Secure Port settings, perform
through
To change the Cisco CTL Provider port, choose System > Service Parameters in Cisco Unified
Communications Manager Administration.
In the Server drop-down list box, choose a server where the Cisco CTL Provider service runs.
In the Service drop-down list box, choose Cisco CTL Provider service.
Tip
For information on the service parameter, click the question mark or the link name.
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
To change the value for the Port Number parameter, enter the new port number in the Parameter Value field.
Click Save.
To change the Ethernet Phone Port or SIP Phone Secure Port settings, choose System >
Cisco Unified CM in Cisco Unified Communications Manager Administration.
Find a server where the Cisco CallManager service runs, as described in the Cisco Unified
Communications Manager Administration Guide; after the results display, click the Name link for the server.
After the Cisco Unified Communications Manager Configuration window displays, enter the new port numbers in the Ethernet Phone Port or SIP Phone Secure Port fields.
Reset the phones and restart the Cisco CallManager service in Cisco Unified Serviceability.
Click Save.
Additional Information
See the
“Related Topics” section on page 4-21 .
OL-24964-01
Cisco Unified Communications Manager Security Guide
4-7
Chapter 4 Configuring the Cisco CTL Client
Installing the Cisco CTL Client
Installing the Cisco CTL Client
You must use the client and update the CTL file when the following events occur:
•
The first time that you set the cluster security mode
•
•
•
The first time that you create the CTL file
After the Cisco Unified Communications Manager installation
•
•
•
•
•
•
After you restore a Cisco Unified Communications Manager server or Cisco Unified
Communications Manager data
After you change the IP address or hostname of the Cisco Unified Communications Manager server
After you add or remove a security token
After you add or remove a ASA firewall
After you add or remove a TFTP server
After you add or remove a Cisco Unified Communications Manager server
After you upload a third-party, CA-signed certificate to the platform
Tip
If the Smart Card service is not set to started and automatic on the server or workstation where you plan to install the client, the installation fails.
Windows XP, Windows 2000, and Windows Vista
To install the Cisco CTL Client for Windows XP, Windows 2000, and Windows Vista, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
From the Windows workstation or server where you plan to install the client, browse to Cisco Unified
Communications Manager Administration, as described in the Cisco Unified Communications Manager
Administration Guide.
In Cisco Unified Communications Manager Administration, choose Application > Plugins.
The Find and List Plugins window displays.
From the Plugin Type equals drop-down list box, choose Installation and click Find.
Locate the Cisco CTL Client.
To download the file, click Download on the left side of the window, directly opposite the
Cisco CTL Client plug-in name.
Click Save and save the file to a location that you will remember.
To begin the installation, double-click Cisco CTL Client (icon or executable depending on where you saved the file).
Step 8
Step 9
Note
You can also click Open from the Download Complete box.
The version of the Cisco CTL Client displays; click Next.
The installation wizard displays. Click Next.
Cisco Unified Communications Manager Security Guide
4-8 OL-24964-01
Chapter 4 Configuring the Cisco CTL Client
Installing the Cisco CTL Client
Step 10
Step 11
Step 12
Step 13
Accept the license agreement and click Next.
Choose a folder where you want to install the client. If you want to do so, click Browse to change the default location; after you choose the location, click Next.
To begin the installation, click Next.
After the installation completes, click Finish.
Windows 7
To install the Cisco CTL Client for Windows 7 32-bit and Windows 7 64-bit, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
From the Windows workstation or server where you plan to install the client, browse to Cisco Unified
Communications Manager Administration, as described in the Cisco Unified Communications Manager
Administration Guide.
In Cisco Unified Communications Manager Administration, choose Application > Plugins.
The Find and List Plugins window displays.
From the Plugin Type equals drop-down list box, choose Installation and click Find.
Locate the Cisco CTL Client (Windows 7) file.
To download the file, click Download on the left side of the window, directly opposite the
Cisco CTL Client plug-in name.
Click Save and save the file to a location that you will remember.
To begin the installation, double-click CiscoCTLClient_win7.exe (icon or executable depending on where you saved the file).
Note
You can also click Open from the Download Complete box.
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
The version of the Cisco CTL Client displays; click Next.
The installation wizard displays. Click Next.
Accept the license agreement and click Next.
Choose a folder where you want to install the client. If you want to do so, click Browse to change the default location; after you choose the location, click Next.
To begin the installation, click Next.
After the installation completes, click Finish.
Additional Information
See the
“Related Topics” section on page 4-21 .
OL-24964-01
Cisco Unified Communications Manager Security Guide
4-9
Chapter 4 Configuring the Cisco CTL Client
Upgrading the Cisco CTL Client and Migrating the Cisco CTL File
Upgrading the Cisco CTL Client and Migrating the Cisco CTL File
If you want to make changes to the CTL file after a Cisco Unified Communications Manager Release
5.x to 6.x upgrade, you must uninstall the Cisco CTL Client that you installed prior to the upgrade, install
, and regenerate the CTL file. If you did not remove or add any servers before the upgrade, you do not need to reconfigure the Cisco CTL Client after the upgrade. The Cisco Unified Communications
Manager upgrade automatically migrates the data in the CTL file.
When you upgrade from a Cisco Unified Communications Manager 4.x release to a 6.x release and security is enabled on the cluster, you must uninstall the Cisco CTL Client that you installed prior to the upgrade, install the latest Cisco CTL Client, and regenerate the CTL file. Follow this procedure to enable security on the upgraded cluster:
Procedure
Step 1
Step 2
Step 3
Step 4
Uninstall the existing Cisco CTL Client.
Install the new Cisco CTL Client as described in the
“Installing the Cisco CTL Client” section on page 4-8
Run the Cisco CTL Client by using at least one of the previously used USB keys, as described in
“Configuring the Cisco CTL Client” section on page 4-10
Restart the Cisco CallManager and Cisco TFTP services in Cisco Unified Serviceability on all Cisco
Unified Communications Manager servers that run these services and on all TFTP servers in the cluster.
Additional Information
See the
“Related Topics” section on page 4-21
.
Configuring the Cisco CTL Client
Tip
Configure the Cisco CTL Client during a scheduled maintenance window because you must restart the
Cisco CallManager services and Cisco TFTP services on all servers that run these services in the cluster.
The Cisco CTL Client performs the following tasks:
•
Sets the Cisco Unified Communications Manager cluster security mode.
Note
Cluster security mode configures the security capability for a standalone server or a cluster.
Tip
You cannot set the Cisco Unified Communications Manager cluster security parameter to mixed mode through the Enterprise Parameters Configuration window of Cisco Unified
Communications Manager Administration. You must configure the Cisco CTL Client to set the
.
4-10
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 4 Configuring the Cisco CTL Client
Configuring the Cisco CTL Client
OL-24964-01
•
Creates the Certificate Trust List (CTL), which is a file that contains certificate entries for security tokens, Cisco Unified Communications Manager, ASA firewall, and CAPF server.
The CTL file indicates the server(s) that support TLS for the phone connection. The client automatically detects the Cisco Unified Communications Manager, Cisco CAPF, and ASA firewall and adds certificate entries for these servers.
The security tokens that you insert during the configuration sign the CTL file.
Note
The Cisco CTL Client also provides Cisco Unified Communications Manager supercluster support: up to 16 call processing servers, 1 publisher, 2 TFTP servers, and up to 9 media resource servers.
Before You Begin
Tip
See “Upgrading the Cisco CTL Client and Migrating the Cisco CTL File” section on page 4-10
for more information about configuring the CTL file when you upgrade Cisco Unified Communications Manager.
Before you configure the Cisco CTL Client, verify that you activated the Cisco CTL Provider service and the Cisco Certificate Authority Proxy Function service in Cisco Unified Serviceability. Obtain at least two security tokens; the Cisco certificate authority issues these security tokens. The security tokens must come from Cisco. You will insert the tokens one at a time into the USB port on the server/workstation. If you do not have a USB port on the server, you may use a USB PCI card.
Obtain the following passwords, hostnames/IP addresses, and port numbers:
•
Administrative username and password for Cisco Unified Communications Manager
Tip
Ensure the administrative username is an application user, not an end user, and a member of a super user group with super user roles.
•
•
Security token administrative password
Administrative username and password for the ASA firewall
See
Table 4-2 on page 4-16 for a description of the preceding information.
Tip
Before you install the Cisco CTL Client, verify that you have network connectivity to the server. To ensure that you have network connectivity, issue a ping command, as described in the Cisco Unified
Communications Operating System Administration Guide. In a cluster configuration, verify you have network connectivity to all servers in the cluster.
If you installed multiple Cisco CTL Clients, Cisco Unified Communications Manager accepts CTL configuration information on only one client at a time, but you can perform configuration tasks on up to five Cisco CTL Clients simultaneously. While you perform configuration tasks on one client, Cisco
Unified Communications Manager automatically stores the information that you entered on the other clients.
After you complete the Cisco CTL Client configuration, the CTL Client performs the following tasks:
•
Writes the CTL file to the Cisco Unified Communications Manager server(s).
•
Writes CAPF capf.cer to all Cisco Unified Communications Manager subsequent nodes (not first node) in the cluster.
Cisco Unified Communications Manager Security Guide
4-11
Chapter 4 Configuring the Cisco CTL Client
Configuring the Cisco CTL Client
•
•
Writes CAPF certificate file in PEM format to all Cisco Unified Communications Manager subsequent nodes (not first node) in the cluster.
Writes the file to all configured TFTP servers.
Writes the file to all configured ASA firewalls.
•
•
Signs the CTL file with the private key of the security token that exists in the USB port at the time you create the CTL file.
To configure the client, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Obtain at least two security tokens that you purchased.
Perform one of the following tasks:
•
•
Double-click the Cisco CTL Client icon that exists on the desktop of the workstation/server where you installed it.
Choose Start > Programs > Cisco CTL Client.
Enter the configuration settings for the Cisco Unified Communications Manager server, as described in
Click Set Cisco Unified Communications Manager Cluster to Mixed Mode, as described in
Perform the following tasks, depending on what you want to accomplish:
•
To add a security token, see
•
To complete the Cisco CTL Client configuration, see
.
Caution
You need a minimum of two security tokens the first time that you configure the client. Do not insert the tokens until the application prompts you to do so. If you have two USB ports on the workstation or server, do not insert two security tokens at the same time.
Step 11
Step 12
Step 13
Step 14
Step 15
Step 16
Step 17
Step 6
Step 7
Step 8
Step 9
Step 10
When the application prompts you to do so, insert one security token in an available USB port on the workstation or server where you are currently configuring the Cisco CTL Client; click OK.
The security token information displays for the token that you inserted; click Add.
The detected certificate entries display in the pane.
To add other security token(s) to the certificate trust list, click Add Tokens.
If you have not already done so, remove the token that you inserted into the server or workstation. When the application prompts you to do so, insert the next token and click OK.
The security token information for the second token displays; click Add.
For all security tokens, repeat
.
The certificate entries display in the pane.
Enter the configuration settings, as described in
.
Click Next.
Enter the configuration settings, as described in
; click Next.
When you have added all security tokens and servers, click Finish.
4-12
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 4 Configuring the Cisco CTL Client
Updating the CTL File
Step 18
Step 19
Step 20
Step 21
Enter the username password for the security token, as described in
; click OK.
After the client creates the CTL file, a window displays the server, file location, and status of the CTL file on each server. Click Finish.
Reset all devices for your standalone server or cluster. See the “Resetting the Devices, Restarting
Services, or Rebooting” section on page 1-12
.
In Cisco Unified Serviceability, restart the Cisco CallManager and Cisco Tftp services.
Tip
Restart these services on all Cisco Unified Communications Manager servers that run these services and on all TFTP servers in the cluster.
Step 22
After you create the CTL file, you may remove the security token from the USB port. Store all security tokens in a safe place that you will remember.
Additional Information
See the
“Related Topics” section on page 4-21 .
Updating the CTL File
You must update the CTL file if the following scenarios occur:
•
If you add a new Cisco Unified Communications Manager server to the cluster
Note
To add a node to a secure cluster, refer to Installing Cisco Unified Communications Manager
Release 6.1(1), which describes how to add a node and how to configure security for the new node.
•
•
•
•
•
•
•
•
•
•
If you change the name or IP address of a Cisco Unified Communications Manager server
If you change the IP address or hostname for any configured TFTP servers
If you change the IP address or hostname for any configured ASA firewall
If you enabled the Cisco Certificate Authority Function service in Cisco Unified Serviceability
If you need to add or remove a security token
If you need to add or remove a TFTP server
If you need to add or remove a Cisco Unified Communications Manager server
If you need to add or remove an ASA firewall
If you restore a Cisco Unified Communications Manager server or Cisco Unified Communications
Manager data
After you upload a third-party, CA-signed certificate to the platform
OL-24964-01
Tip
Cisco strongly recommends that you update the file when minimal call-processing interruptions will occur.
To update the information that exists in CTL file, perform the following procedure:
Cisco Unified Communications Manager Security Guide
4-13
Chapter 4 Configuring the Cisco CTL Client
Updating the CTL File
Procedure
Step 1
Step 2
Step 3
Obtain one security token that you inserted to configure the latest CTL file.
Double-click the Cisco CTL Client icon that exists on the desktop of the workstation/server where you installed it.
Enter the configuration settings for the Cisco Unified Communications Manager server, as described in
Step 4
Tip
You make updates in this window for the Cisco Unified Communications Manager server.
To update the CTL file, click Update CTL File, as described in
; click Next.
Caution
For all CTL file updates, you must insert one security token that already exists in the CTL file into the
USB port. The client validates the signature of the CTL file through this token. You cannot add new tokens until the Cisco CTL Client validates the signature. If you have two USB ports on the workstation or server, do not insert both security tokens at the same time.
Step 5
Step 6
If you have not already inserted one security token in an available USB port on the workstation or server where you are currently updating the CTL file, insert one of the security tokens; click OK.
The security token information displays for the token that you inserted; click Next.
The detected certificate entries display in the pane.
Step 7
Step 8
Tip
You cannot update the Cisco Unified Communications Manager, Cisco TFTP, or ASA firewall entries from this pane. To update the Cisco Unified Communications Manager entry, click
Cancel and perform
through
To update existing Cisco CTL entries or to add or delete security tokens, consider the following information:
•
•
To delete a security token, see the
“Deleting a CTL File Entry” section on page 4-15
.
When you have finished updating the CTL file, restart the Cisco CallManager and Cisco TFTP services in Cisco Unified Serviceability.
Tip
Restart the TFTP and Cisco CallManager services on all nodes in the cluster that run these services.
Additional Information
See the
“Related Topics” section on page 4-21
.
4-14
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 4 Configuring the Cisco CTL Client
Deleting a CTL File Entry
Deleting a CTL File Entry
At any time, you can delete some CTL entries that display in the CTL Entries window of the Cisco CTL
Client. After you open the client and follow the prompts to display the CTL Entries window, highlight the item to delete and click Delete Selected to delete the entry.
You cannot delete servers that run Cisco Unified Communications Manager, Cisco TFTP, ASA firewall, or Cisco CAPF from the CTL file.
Two security token entries must exist in the CTL file at all times. You cannot delete all security tokens from the file.
Additional Information
See the
“Related Topics” section on page 4-21 .
Updating the Cisco Unified Communications Manager Security
Mode
You must use the Cisco CTL Client to configure the cluster security mode. You cannot change the Cisco
Unified Communications Manager security mode from the Enterprise Parameters Configuration window in Cisco Unified Communications Manager Administration.
Note
Cluster security mode configures the security capability for a standalone server or a cluster.
To change the cluster security mode after the initial configuration of the Cisco CTL Client, you must update the CTL file. Navigate to the Cluster Security Mode window, change the mode setting, and click
Next, then Finish, as described in the
“Updating the CTL File” section on page 4-13 and
If you change the cluster security mode from mixed to nonsecure mode, the CTL file still exists on the server(s), but the CTL file does not contain any certificates. Because no certificates exist in the CTL file, the phone requests an unsigned configuration file and registers as nonsecure with Cisco Unified
Communications Manager.
Cisco CTL Client Configuration Settings
You can set the cluster security mode to nonsecure or mixed mode, as described in
. Only mixed mode supports authentication, encrypted signaling, and encrypted media.
Note
Cluster security mode configures the security capability for a standalone server or a cluster.
Use
to configure the Cisco CTL Client for the first time, to update the CTL file, or to change the mode from mixed to nonsecure.
•
For configuration tips, see the
“Configuration Tips for Cisco CTL Client Configuration” section on page 4-3
.
•
For related information and procedures, see the “Related Topics” section on page 4-21
.
OL-24964-01
Cisco Unified Communications Manager Security Guide
4-15
Chapter 4 Configuring the Cisco CTL Client
Cisco CTL Client Configuration Settings
Table 4-2 Configuration Settings for CTL Client
Setting Description
Cisco Unified Communications Manager Server
Hostname or IP Address
Port
Username and Password
Enter the hostname or IP address for the first node.
Enter the CTL port number for the Cisco CTL Provider service that runs on this Cisco Unified Communications Manager server. The default port number equals 2444.
Enter the same application username and password that has superuser administrative privileges on the first node.
Security Mode
Set Cisco Unified
Communications Manager
Cluster to Mixed Mode
Set Cisco Unified
Communications Manager
Cluster to Non-Secure
Mode
Mixed mode allows authenticated, encrypted, and nonsecure Cisco
Unified IP Phones to register with Cisco Unified Communications
Manager. In this mode, Cisco Unified Communications Manager ensures that authenticated or encrypted devices use a secure port.
Note
Cisco Unified Communications Manager disables auto-registration if you configure mixed mode.
If you configure nonsecure mode, all devices register as unauthenticated, and Cisco Unified Communications Manager supports image authentication only.
When you choose this mode, the Cisco CTL Client removes the certificates for all entries that are listed in the CTL file, but the CTL file still exists in the directory that you specified. The phone requests unsigned configuration files and registers as nonsecure with Cisco
Unified Communications Manager.
Tip
To revert the phone to the default nonsecure mode, you must delete the CTL file from the phone and all Cisco Unified
Communications Manager servers.
Update CTL File
You can use auto-registration in this mode.
After you have created the CTL file, you must choose this option to make any changes to the CTL file. Choosing this option ensures that the Cisco
Unified Communications Manager security mode does not change.
CTL Entries
Add Tokens
Add TFTP Server
Click this button to add additional security token(s) to the certificate trust list.
If you have not already done so, remove the token that you initially inserted into the server or workstation. When the application prompts you to do so, insert the next token and click OK. When the security token information for the additional token displays, click Add. For all security tokens, repeat these tasks.
Click this button to add an Alternate TFTP server to the certificate trust list. For information on the settings, click the Help button after the
Alternate TFTP Server tab settings display. After you enter the settings, click Next.
4-16
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 4 Configuring the Cisco CTL Client
Verifying the Cisco Unified Communications Manager Security Mode
Table 4-2
Setting
Add Firewall
Configuration Settings for CTL Client (continued)
Description
Click this button to add an ASA firewall to the certificate trust list. For information on the settings, click the Help button after the Firewall tab settings display. After you enter the settings, click Next.
Alternate TFTP Server
Hostname or IP Address
Port
Username and Password
Enter the hostname or IP address for the TFTP server.
Alternate TFTP server designates a Cisco TFTP server that exists in a different cluster. If you use two different clusters for the alternate TFTP server configuration, both clusters must use the same cluster security mode, which means that you must install and configure the Cisco CTL
Client in both clusters. Likewise, both clusters must run the same version of Cisco Unified Communications Manager.
Ensure that the path in the TFTP service parameter, FileLocation, is the same for all servers in the cluster.
See “Configuration Tips for Cisco CTL Client Configuration” section on page 4-3
for more information.
Not required with this release of Cisco Unified Communications
Manager.
Not required with this release of Cisco Unified Communications
Manager.
Firewall
Hostname or IP Address
Port
Username and Password
Enter the hostname or IP address for the firewall.
Not configurable. The system uses the Cisco Unified Communications
Manager port; the default port number equals 2444.
Not configurable. The system uses the administrator name and password that you configured during Cisco Unified Communications Manager installation.
Security Token
User Password The first time that you configure the Cisco CTL client, enter Cisco123, the case-sensitive default password, to retrieve the private key of the certificate and ensure that the CTL file gets signed.
Verifying the Cisco Unified Communications Manager Security
Mode
To verify the cluster security mode, perform the following procedure:
Note
Cluster security mode configures the security capability for a standalone server or a cluster.
OL-24964-01
Cisco Unified Communications Manager Security Guide
4-17
Chapter 4 Configuring the Cisco CTL Client
Setting the Smart Card Service to Started and Automatic
Procedure
Step 1
Step 2
In Cisco Unified Communications Manager Administration, choose System > Enterprise Parameters.
Locate the Cluster Security Mode field. If the value in the field displays as 1, you correctly configured
Cisco Unified Communications Manager for mixed mode. (Click the field name for more information.)
Tip
You cannot configure this value in Cisco Unified Communications Manager Administration.
This value displays after you configure the Cisco CTL Client.
Additional Information
See the
“Related Topics” section on page 4-21
.
Setting the Smart Card Service to Started and Automatic
If the Cisco CTL Client installation detects that the Smart Card service is disabled, you must set the
Smart Card service to automatic and started on the server or workstation where you are installing the
Cisco CTL Client plug-in.
Tip
You cannot add the security tokens to the CTL file if the service is not set to started and automatic.
After you upgrade the operating system, apply service releases, upgrade Cisco Unified Communications
Manager, and so on, verify that the Smart Card service is started and automatic.
To set the service to started and automatic, perform the following procedure:
Procedure
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 1
On the server or workstation where you installed the Cisco CTL Client, choose Start > Programs >
Administrative Tools > Services or Start > Control Panel > Administrative Tools > Services.
From the Services window, right-click the Smart Card service and choose Properties.
In the Properties window, verify that the General tab displays.
From the Startup type drop-down list box, choose Automatic.
Click Apply.
In the Service Status area, click Start.
Click OK.
Reboot the server or workstation and verify that the service is running.
Additional Information
See the
“Related Topics” section on page 4-21
.
4-18
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 4 Configuring the Cisco CTL Client
Changing the Security Token Password (Etoken)
Changing the Security Token Password (Etoken)
This administrative password retrieves the private key of the certificate and ensures that the CTL file gets signed. Each security token comes with a default password. You can change the security token password at any time. If the Cisco CTL Client prompts you to change the password, you must change the password before you can proceed with the configuration.
To review pertinent information on setting passwords, click the Show Tips button. If you cannot set the password for any reason, review the tips that display.
Windows XP, Windows 2000, or Windows Vista
To change the security token password on a Windows XP, Windows 2000, or Windows Vista server or workstation, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Verify that you have installed the Cisco CTL Client on a Windows server or workstation.
If you have not already done so, insert the security token into the USB port on the Windows server or workstation where you installed the Cisco CTL Client.
Choose Start > Programs > etoken > Etoken Properties, right-click etoken, and choose Change
etoken password.
In the Current Password field, enter the password that you originally created for the token.
Enter a new password.
Enter the new password again to confirm it.
Click OK.
Windows 7
To change the security token password on a Windows 7 server or workstation, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Verify that you have installed the Cisco CTL Client on a Windows server or workstation.
If you have not already done so, insert the security token into the USB port on the Windows server or workstation where you installed the Cisco CTL Client.
Choose Start > Programs > Safenet > Safenet Authentication Client tools, right-click etoken, and choose Change etoken password.
In the Current Password field, enter the password that you originally created for the token.
Enter a new password.
Enter the new password again to confirm it.
Click OK.
OL-24964-01
Cisco Unified Communications Manager Security Guide
4-19
Chapter 4 Configuring the Cisco CTL Client
Deleting the CTL File on the Cisco Unified IP Phone
Additional Information
See the
“Related Topics” section on page 4-21
.
Deleting the CTL File on the Cisco Unified IP Phone
Caution
Cisco recommends that you perform this task in a secure lab environment, especially if you do not plan to delete the CTL file from the Cisco Unified Communications Manager server(s).
Delete the CTL file on the Cisco Unified IP Phone for the following cases:
•
You lose all security tokens that signed the CTL file.
•
•
The security tokens that signed the CTL file appear compromised.
You move a phone out of a secure environment; for example, to a storage area.
•
•
You move a phone to a nonsecure cluster or to another secure cluster in a different domain.
You move a phone from an area with an unknown security policy to a secure Cisco Unified
Communications Manager.
•
You change the alternate TFTP server address to a server that does not exist in the CTL file.
To delete the CTL file on the Cisco Unified IP Phone, perform the tasks in Table 4-3 .
Table 4-3 Deleting the CTL File on the Cisco Unified IP Phone
Cisco Unified IP Phone
Model
Cisco Unified IP Phones
7960G and 7940G
Cisco Unified IP Phone
7970G and equivalent
Tasks
Under the Security Configuration menu on the phone, press CTL file,
unlock or **#, and erase.
Perform one of the following methods:
•
•
Note
Unlock the Security Configuration menu, as described in Cisco
Unified IP Phone Administration Guide for Cisco Unified
Communications Manager. Under the CTL option, press the Erase softkey.
Under the Settings menu, press the Erase softkey.
Pressing the Erase softkey under the Settings menu deletes other information besides the CTL file. For additional information, refer to the Cisco Unified IP Phone Administration Guide for
Cisco Unified Communications Manager.
Additional Information
See the
“Related Topics” section on page 4-21
.
4-20
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 4 Configuring the Cisco CTL Client
Determining the Cisco CTL Client Version
Determining the Cisco CTL Client Version
To determine which version of the Cisco CTL Client you are using, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Perform one of the following tasks:
•
•
Double-click the Cisco CTL Client icon that exists on the desktop.
Choose Start > Programs > Cisco CTL Client.
In the Cisco CTL Client window, click the icon in the upper, left corner of the window.
Choose About Cisco CTL Client. The version of the client displays.
Additional Information
See the
“Related Topics” section on page 4-21 .
Verifying or Uninstalling the Cisco CTL Client
Uninstalling the Cisco CTL Client does not delete the CTL file. Likewise, the cluster security mode and the CTL file do not change when you uninstall the client. If you choose to do so, you can uninstall the
Cisco CTL Client, install the client on a different Windows workstation or server, and continue to use the same CTL file.
To verify that the Cisco CTL Client installed, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Choose Start > Control Panel > Add Remove Programs.
To verify that the client installed, locate Cisco CTL Client.
To uninstall the client, click Remove.
Additional Information
See the
“Related Topics” section on page 4-21 .
Where to Find More Information
Related Topics
•
•
•
Cisco CTL Client Overview, page 4-2
Cisco CTL Client Configuration Checklist, page 4-4
•
Activating the Cisco CTL Provider Service, page 4-5
OL-24964-01
Cisco Unified Communications Manager Security Guide
4-21
Chapter 4 Configuring the Cisco CTL Client
Where to Find More Information
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Activating the Cisco CAPF Service, page 4-6
Configuring Ports for the TLS Connection, page 4-6
Installing the Cisco CTL Client, page 4-8
Upgrading the Cisco CTL Client and Migrating the Cisco CTL File, page 4-10
Configuring the Cisco CTL Client, page 4-10
Updating the CTL File, page 4-13
Deleting a CTL File Entry, page 4-15
Updating the Cisco Unified Communications Manager Security Mode, page 4-15
Cisco CTL Client Configuration Settings, page 4-15
Verifying the Cisco Unified Communications Manager Security Mode, page 4-17
Setting the Smart Card Service to Started and Automatic, page 4-18
Deleting the CTL File on the Cisco Unified IP Phone, page 4-20
Determining the Cisco CTL Client Version, page 4-21
Verifying or Uninstalling the Cisco CTL Client, page 4-21
Using the Certificate Authority Proxy Function, page 10-1
Related Cisco Documentation
Cisco Unified IP Phone Administration Guide for Cisco Unified Communications Manager
Troubleshooting Guide for Cisco Unified Communications Manager
4-22
Cisco Unified Communications Manager Security Guide
OL-24964-01
Certificate Configuration
C H A P T E R
5
This chapter contains information on the following topics:
•
Certificate Configuration Overview, page 5-1
•
•
Finding a Certificate, page 5-1
Displaying Certificate Configuration, page 5-2
Certificate Configuration Overview
Use the Certificate Configuration window to view the certificates on your system. All fields on the
Certificate Configuration window are read-only, except Duration in Cache.
Finding a Certificate
To find a certificate, perform the following procedure:
Procedure
Step 1
Step 2
In Cisco Unified Communications Manager Administration, choose System > Security > Certificate.
The Find and List Certificates window displays. Records from an active (prior) query may also display in the window.
To find all records in the database, ensure the dialog box is empty; go to
To filter or search records
•
•
•
From the first drop-down list box, choose a search parameter.
From the second drop-down list box, choose a search pattern.
Specify the appropriate search text, if applicable.
Note
To add additional search criteria, click the + button. When you add criteria, the system searches for a record that matches all criteria that you specify. To remove criteria, click the – button to remove the last added criterion or click the Clear Filter button to remove all added search criteria.
Step 3
Click Find.
Cisco Unified Communications Manager Security Guide
OL-24964-01 5-1
Chapter 5 Certificate Configuration
Displaying Certificate Configuration
Step 4
All matching records display. You can change the number of items that display on each page by choosing a different value from the Rows per Page drop-down list box.
From the list of records that display, click the link for the record that you want to view.
Note
To reverse the sort order, click the up or down arrow, if available, in the list header.
The window displays the item that you choose.
Displaying Certificate Configuration
All fields on the Certificate Management window are read-only, except Duration in Cache.
Table 5-1 VPN Profile Configuration Settings
Field
Subject Name (read only)
Issuer Name (read only)
Serial Number (read only)
IPv4 Address (read only)
IPv6 Address (read only)
Duration in Cache
Selected Roles
Selected Services
Definition
Displays the subject name for the certificate.
Displays the issuer name for the certificate.
Displays the serial number (MAC address).
Displays the IPv4 address.
Displays the IPv6 address.
Enter the time, in hours, that the certificate can persist in the phone cache. A value of zero indicates that the certificate does not get cached. Leave blank to accept the system default value.
Maximum: 720 hours
Displays the roles currently associated with the certificate.
Displays the services currently associated with the certificate.
5-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
P
A R T
2
Security for Cisco Unified IP Phone and
Cisco Voice-Messaging Ports
Phone Security Overview
C H A P T E R
6
This chapter contains information on the following topics:
•
Understanding How Security Works for Phones, page 6-1
•
•
•
•
•
Supported Phone Models, page 6-3
Configure Security for Preferred Vendor SIP Phones, page 6-3
Viewing Security Settings on the Phone, page 6-5
Phone Security Configuration Checklist, page 6-5
Where to Find More Information, page 6-6
Understanding How Security Works for Phones
At installation, Cisco Unified Communications Manager boots up in nonsecure mode. When the phones boot up after the Cisco Unified Communications Manager installation, all devices register as nonsecure with Cisco Unified Communications Manager.
After you upgrade from Cisco Unified Communications Manager 4.0(1) or a later release, the phones boot up in the device security mode that you enabled prior to the upgrade; all devices register by using the chosen security mode.
The Cisco Unified Communications Manager installation creates a self-signed certificate on the Cisco
Unified Communications Manager and TFTP server. You may also choose to use a third-party,
CA-signed certificate for Cisco Unified Communications Manager instead of the self-signed certificate
.
After you configure authentication, Cisco Unified Communications Manager uses the certificate to authenticate with supported Cisco Unified IP Phones. After a certificate exists on the Cisco Unified
Communications Manager and TFTP server, Cisco Unified Communications Manager does not reissue the certificates during each Cisco Unified Communications Manager upgrade. You must create a new
CTL file with the new certificate entries.
Tip
For information on unsupported or nonsecure scenarios, see the
“Interactions and Restrictions” section on page 1-7
.
Cisco Unified Communications Manager maintains the authentication and encryption status at the device level. If all devices that are involved in the call register as secure, the call status registers as secure. If one device registers as nonsecure, the call registers as nonsecure, even if the phone of the caller or recipient registers as secure.
OL-24964-01
Cisco Unified Communications Manager Security Guide
6-1
Trusted Devices
Chapter 6 Phone Security Overview
Cisco Unified Communications Manager retains the authentication and encryption status of the device when a user uses Cisco Extension Mobility. Cisco Unified Communications Manager also retains the authentication and encryption status of the device when shared lines are configured.
Tip
When you configure a shared line for an encrypted Cisco Unified IP Phone, configure all devices that share the lines for encryption; that is, ensure that you set the device security mode for all devices to encrypted by applying a security profile that supports encryption.
Trusted Devices
Cisco Unified Communications Manager allows Security icons to be enabled by phone model on Cisco
Unified IP Phones. The Security icon indicates whether the call is secure and the connected device is trusted.
A Trusted Device represents a Cisco device or a third-party device that has passed Cisco security criteria for trusted connections. This includes, but is not limited to, signaling/media encryption, platform hardening, and assurance. If a device is trusted, a Security icon displays and a secure tone plays on supported devices. Also, the device may provide other features or indicators that are related to secure calls.
Cisco Unified Communications Manager determines whether a device is trusted when you add it to your system. The security icon displays for information purposes only, and the administrator cannot configure it directly.
Cisco Unified Communications Manager also indicates whether a gateway is trusted by displaying an icon and a message in Cisco Unified Communications Manager Administration.
This section describes the behavior of the security icon for trusted devices on both the Cisco Unified IP
Phones and in Cisco Unified Communications Manager Administration.
Cisco Unified Communications Manager Administration
The following windows in Cisco Unified Communications Manager Administration indicate whether a device is trusted:
Gateway Configuration
For each gateway type, the Gateway Configuration window (Device > Gateway) displays either Device
is trusted or Device is not trusted, along with a corresponding icon.
The system determines whether the device is trusted, based on the device type. You cannot configure whether the device is trusted.
Phone Configuration
For each phone device type, the Phone Configuration window (Device > Phone) displays either Device
is trusted or Device is not trusted, along with a corresponding icon.
The system determines whether the device is trusted, based on the device type. You cannot configure whether the device is trusted.
Cisco Unified IP Phones
The type of device that a user calls affects the security icon that displays on the phone. The system consider the following three criteria to determine whether the call is secure:
Cisco Unified Communications Manager Security Guide
6-2 OL-24964-01
Chapter 6 Phone Security Overview
Supported Phone Models
•
•
•
Are all devices on the call trusted?
Is the signaling secure (authenticated and encrypted)?
Is the media secure?
Before a supported Cisco Unified IP Phone displays the Lock Security icon, be aware that all three of these criteria must be met. For calls that involve a device that is not trusted, regardless of signaling and media security, the overall status of the call will stay unsecure, and the phone will not display the Lock icon. For example, if you include an untrusted device in a conference, the system considers its call leg, as well as the conference itself, to be unsecure.
Supported Phone Models
There are two categories of phone models which support security in Cisco Unified Communications
Manager: Secure Cisco phones and Secure Preferred Vendor phones. Secure Cisco phones are pre-installed with a Manufacture-Installed Certificate (MIC) and support automatic generation and exchange of Locally-Significant Certificates (LSC) using the Certificate Authority Proxy Function
(CAPF). Secure Cisco phones are capable of registering with Cisco Unified CM using the MIC without additional certificate management. For additional security, you can create and install an LSC on the phone using CAPF. The sections
“Viewing Security Settings on the Phone” section on page 6-5
and
“Phone Security Configuration Checklist” section on page 6-5
apply to these phone types.
Secure Preferred Vendor phones do not come pre-installed with a MIC, and do not support CAPF for generating LSCs. In order for Secure Preferred Vendor phones to connect to Cisco Unified CM, a certificate must be provided with the device, or generated by the device. The phone supplier must provide the details on how to acquire or generate a certificate for the phone. Once you obtain the certificate, you must upload the certificate to the Cisco Unified CM using the OS Administration
Certificate Management interface. The section
“Configure Security for Preferred Vendor SIP Phones” section on page 6-3 apply to these phone types.
For a list of security features that are supported on your phone, refer to the phone administration and user documentation that supports this Cisco Unified Communications Manager release or the firmware documentation that supports your firmware load.
You can also use Cisco Unified Reporting to list the phones that support a particular feature. For more information about using Cisco Unified Reporting, see the Cisco Unified Reporting Administration
Guide.
Configure Security for Preferred Vendor SIP Phones
Secure Preferred Vendor phones are phone types that are manufactured by 3rd-party vendors but are installed in the Cisco Unified database via a COP file. Cisco Unified Communications Manager provides security for a preferred vendor SIP phone. In order to support security, you must enable Security
Encryption or Security Authentication for the preferred vendor SIP phone in the COP file. These phone types appear in the drop-down list in the Add a New Phone window. While all preferred vendor phones support Digest Authorization, not all preferred vendor phones support TLS security. Security capabilities is based on the phone model. If the Phone Security Profile includes a “Device Security
Mode” field, then it supports TLS security.
If the preferred vendor phone supports TLS security, there are two modes that are possible: per-device certificate and shared certificate. The phone supplier must specify which mode is applicable for the phone as well as instructions on generating or acquiring a certificate for the phone.
OL-24964-01
Cisco Unified Communications Manager Security Guide
6-3
Chapter 6 Phone Security Overview
Configure Security for Preferred Vendor SIP Phones
Configuring Preferred Vendor SIP Phone Security Profile with Per-device
Certificates
To configure the preferred vendor SIP phone security profile with per-device certificates, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Upload the certificate for each phone using the OS Administration Certificate Management interface.
In the Cisco Unified Administration, choose System > Security > Phone Security Profile.
Configure a new Phone Security Profile for the device type of this phone and in the Device Security
Mode drop-down list box, choose Encrypted or Authenticated.
To configure the new SIP phone in the CCMAdmin interface, choose Device > Phone > Add New.
Select Phone type.
Fill in the required fields.
In the Device Security Profile drop-down list box, select the profile you just created.
Configuring Preferred Vendor SIP Phone Security Profile with Shared
Certificates
To configure the preferred vendor SIP phone security profile with shared certificates, perform the following procedure:
Procedure
Step 1
Using instructions from the phone vendor, generate a certificate with a Subject Alternate Name (SAN) string. The SAN must be of type DNS. Make a note of the SAN specified in this step. For example,
X509v3 extensions:
X509v3 Subject Alternative Name:
DNS:AscomGroup01.acme.com
Note
The SAN must be of type DNS or security will not be enabled.
Step 2
Step 3
Step 4
Upload the shared certificate using the OS Administration Certificate Management interface.
In the Cisco Unified Administration, choose System > Security > Phone Security Profile.
In the Name field, enter the name of the Subject Alt Name (SAN), which is the name on the certificate provided by the preferred vendor, or if there is no SAN enter the Certificate Name.
Note
Step 5
The name of the security profile must match the SAN in the certificate exactly or security will not be enabled.
In the Device Security Mode drop-down list box, choose Encrypted or Authenticated.
Cisco Unified Communications Manager Security Guide
6-4 OL-24964-01
Chapter 6 Phone Security Overview
Viewing Security Settings on the Phone
Step 6
Step 7
Step 8
Step 9
Step 10
In the Transport type drop-down list box, choose TLS.
To configure the new SIP phone in the CCMAdmin interface, choose Device > Phone > Add New.
Select Phone type.
Fill in the required fields
In the Device Security Profile drop-down list box, select the profile you just created.
Additional Information
Configuring a Phone Security Profile, page 7-1
Viewing Security Settings on the Phone
You can configure and view certain security-related settings on phones that support security; for example, you can view whether a phone has a locally significant certificate or manufacture-installed certificate installed. For additional information on the security menu and icons, refer to the Cisco
Unified IP Phone administration and user documentation that supports your phone model and this version of Cisco Unified Communications Manager.
When Cisco Unified Communications Manager classifies a call as authenticated or encrypted, an icon displays on the phone to indicate the call state. To determine when Cisco Unified Communications
Manager classifies the call as authenticated or encrypted, refer to the
“Security Icons” section on page 1-6
and the “Interactions and Restrictions” section on page 1-7
.
Phone Security Configuration Checklist
describes the tasks to configure security for supported phones.
Table 6-1 Phone Security Configuration Checklist
Configuration Steps
Step 1
If you have not already done so, configure the Cisco CTL Client and ensure that the Cisco Unified Communications Manager security mode equals Mixed Mode.
Related Procedures and Topics
Configuring the Cisco CTL Client, page 4-1
Step 2
Step 3
Step 4
Step 5
If the phone does not contain a locally significant certificate
(LSC) or manufacture-installed certificate (MIC), install a LSC by using the Certificate Authority Proxy Function (CAPF).
Using the Certificate Authority Proxy
Configure phone security profiles.
Apply a phone security profile to the phone.
If a phone that is running SIP supports digest authentication, configure the digest credentials in the End User Configuration window.
Configuring a Phone Security Profile, page 7-1
Applying a Phone Security Profile, page 7-10
•
Configuring Digest Credentials in the
End User Configuration Window, page 12-3
•
Configuration Settings, page 12-3
OL-24964-01
Cisco Unified Communications Manager Security Guide
6-5
Chapter 6 Phone Security Overview
Where to Find More Information
Table 6-1 Phone Security Configuration Checklist (continued)
Configuration Steps
Step 6
After you configure digest credentials, choose the Digest User from the Phone Configuration window.
Step 7
Step 8
Step 9
Related Procedures and Topics
Configuring the Digest User in the Phone
Configuration Window, page 12-4
On Cisco Unified IP Phone 7960G or 7940G (SIP only), enter the digest authentication username and password (digest credentials) that you configured in the End User Configuration window.
This document does not provide procedures on how to enter the digest authentication credentials on the phone. For information on how to perform this task, refer to the Cisco
Unified IP Phone administration guide that supports your phone model and this version of
Cisco Unified Communications Manager.
Encrypt the phone configuration file, if the phone supports this functionality.
Configuring Encrypted Phone Configuration
To harden the phone, disable phone settings.
Where to Find More Information
Related Topics
•
Interactions and Restrictions, page 1-7
•
Authentication, Integrity, and Authorization Overview, page 1-17
•
•
•
•
•
Encryption Overview, page 1-22
Configuration Checklist Overview, page 1-25
Using the Certificate Authority Proxy Function, page 10-1
Phone Security Configuration Checklist, page 6-5
•
•
Configuring a Phone Security Profile, page 7-1
Configuring Encrypted Phone Configuration Files, page 11-1
Related Cisco Documentation
•
Cisco Unified IP Phone Administration Guide for Cisco Unified Communications Manager
•
Troubleshooting Guide for Cisco Unified Communications Manager
6-6
Cisco Unified Communications Manager Security Guide
OL-24964-01
C H A P T E R
7
Configuring a Phone Security Profile
This chapter contains information on the following topics:
•
Phone Security Profile Overview, page 7-1
•
•
•
•
•
•
•
•
•
Configuration Tips for Phone Security Profiles, page 7-2
Finding a Phone Security Profile, page 7-2
Configuring a Phone Security Profile, page 7-3
Phone Security Profile Configuration Settings, page 7-4
Applying a Phone Security Profile, page 7-10
Synchronizing a Phone Security Profile with Affected Phones, page 7-11
Deleting a Phone Security Profile, page 7-12
Finding Phones That Use Phone Security Profiles, page 7-12
Where to Find More Information, page 7-13
Phone Security Profile Overview
Cisco Unified Communications Manager Administration groups security-related settings for a phone type and protocol into security profiles to allow you to assign a single security profile to multiple phones.
Security-related settings include device security mode, digest authentication, and some CAPF settings.
You apply the configured settings to a phone when you choose the security profile in the Phone
Configuration window.
Installing Cisco Unified Communications Manager provides a set of predefined, nonsecure security profiles for auto-registration. To enable security features for a phone, you must configure a new security profile for the device type and protocol and apply it to the phone.
Only the security features that the selected device and protocol support display in the security profile settings window.
Cisco Unified Communications Manager Security Guide
7-1 OL-24964-01
Chapter 7 Configuring a Phone Security Profile
Configuration Tips for Phone Security Profiles
Configuration Tips for Phone Security Profiles
Consider the following information when you configure phone security profiles in Cisco Unified
Communications Manager Administration:
•
When you configure phones, you must select a security profile in the Phone Configuration window.
If the device does not support security, apply the nonsecure profile.
•
•
•
You cannot delete or change predefined, nonsecure profiles.
You cannot delete a security profile that is currently assigned to a device.
•
If you change the settings in a security profile that is already assigned to a phone, the reconfigured settings apply to all phones that are assigned that profile.
You can rename security files that are assigned to devices. The phones that are assigned the old profile name and settings assume the new profile name and settings.
•
The CAPF settings in the Phone Security Profile, authentication mode and key size, also display in the Phone Configuration window. You must configure CAPF settings for certificate operations that involve manufacture-installed certificates (MICs) or locally significant certificates (LSCs). You can update these fields directly in the Phone Configuration window.
–
If you update the CAPF settings in the security profile, the settings get updated in the Phone
Configuration window.
–
–
If you update the CAPF settings in the Phone Configuration window and a matching profile is found, Cisco Unified Communications Manager applies the matching profile to the phone.
If you update the CAPF settings in the Phone Configuration window, and no matching profile is found, Cisco Unified Communications Manager creates a new profile and applies the new profile to the phone.
•
•
If you configured the device security mode prior to a Cisco Unified Communications Manager 5.0 or later upgrade, Cisco Unified Communications Manager creates a profile that is based on the model and protocol and applies the profile to the device.
Cisco recommends using manufacturer-installed certificates (MICs) for LSC installation only. Cisco supports LSCs to authenticate the TLS connection with Cisco Unified Communications Manager.
Because MIC root certificates can be compromised, customers who configure phones to use MICs for TLS authentication or for any other purpose do so at their own risk. Cisco assumes no liability if MICs are compromised.
Cisco recommends upgrading Cisco Unified IP Phone models 7906G, 7911G, 7931G (SCCP only),
7941G, 7941G,-GE, 7942G, 7945G, 7961G, 7961G-GE, 7962G, 7965G, 797G, 7971G, 7971G-GE, and 7975G to use LSCs for TLS connection to Cisco Unified Communications Manager and removing MIC root certificates from the CallManager trust store to avoid possible future compatibility issues. See
“Certificates” section on page 1-14
for more information.
Finding a Phone Security Profile
To find a phone security profile, perform the following procedure:
Procedure
Step 1
In Cisco Unified Communications Manager Administration, choose System > Security Profile > Phone
Security Profile.
Cisco Unified Communications Manager Security Guide
7-2 OL-24964-01
Chapter 7 Configuring a Phone Security Profile
Configuring a Phone Security Profile
Step 2
The Find and List Phone Security Profile window displays. Records from an active (prior) query may also display in the window.
To find all records in the database, ensure the dialog box is empty; go to
To filter or search records
•
•
•
From the first drop-down list box, choose a search parameter.
From the second drop-down list box, choose a search pattern.
Specify the appropriate search text, if applicable.
Step 3
Step 4
Note
To add additional search criteria, click the + button. When you add criteria, the system searches for a record that matches all criteria that you specify. To remove criteria, click the – button to remove the last added criterion or click the Clear Filter button to remove all added search criteria.
Click Find.
All matching records display. You can change the number of items that display on each page by choosing a different value from the Rows per Page drop-down list box.
From the list of records that display, click the link for the record that you want to view.
Note
To reverse the sort order, click the up or down arrow, if available, in the list header.
The window displays the item that you choose.
Additional Information
See the
“Related Topics” section on page 7-13 .
Configuring a Phone Security Profile
To add, update, or copy a security profile, perform the following procedure:
Procedure
Step 1
Step 2
In Cisco Unified Communications Manager Administration, choose System > Security Profile > Phone
Security Profile.
Perform one of the following tasks:
•
To add a new profile, click Add New in the Find window and continue with
•
To copy an existing security profile, locate the appropriate profile as described in
Security Profile” section on page 7-2 , click the Copy button next to the security profile that you
want to copy, and continue with Step 3
.
•
To update an existing profile, locate the appropriate security profile as described in
Security Profile” section on page 7-2
.
When you click Add New, the configuration window displays with the default settings for each field.
When you click Copy, the configuration window displays with the copied settings.
Cisco Unified Communications Manager Security Guide
OL-24964-01 7-3
Chapter 7 Configuring a Phone Security Profile
Phone Security Profile Configuration Settings
Step 3
Step 4
Enter the appropriate settings as described in
Table 7-1 for phones that are running SCCP or
for phones that are running SIP.
Click Save.
Next Steps
After you create the security profile, apply it to the phone, as described in the
Security Profile” section on page 7-10 .
If you configured digest authentication in the phone security profile for a phone that is running SIP, you must configure the digest credentials in the End User Configuration window. You then must associate the user with the phone by using the Digest User setting in the Phone Configuration window.
Additional Information
See the
“Related Topics” section on page 7-13
.
Phone Security Profile Configuration Settings
Table 7-1 describes the settings for the security profile for the phone that is running SCCP.
Table 7-2 describes the settings for the security profile the phone that is running SIP.
Only settings that the selected phone type and protocol support display.
•
For configuration tips, see the
“Configuration Tips for Phone Security Profiles” section on page 7-2
.
•
For related information and procedures, see the
“Related Topics” section on page 7-13 .
Table 7-1 Security Profile for Phone That is Running SCCP
Setting
Name
Description
Description
Enter a name for the security profile.
When you save the new profile, the name displays in the Device Security
Profile drop-down list box in the Phone Configuration window for the phone type and protocol.
Tip
Include the device model and protocol in the security profile name to help you find the correct profile when you are searching for or updating a profile.
Enter a description for the security profile. The description can include up to 50 characters in any language, but it cannot include double-quotes
("), percentage sign (%), ampersand (&), back-slash (\), or angle brackets
(<>).
7-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 7 Configuring a Phone Security Profile
Phone Security Profile Configuration Settings
Table 7-1 Security Profile for Phone That is Running SCCP (continued)
Setting
Device Security Mode
TFTP Encrypted Config
Description
From the drop-down list box, choose one of the following options:
•
•
Non Secure—No security features except image authentication exist for the phone. A TCP connection opens to Cisco Unified
Communications Manager.
Authenticated—Cisco Unified Communications Manager provides integrity and authentication for the phone. A TLS connection that uses NULL/SHA opens for signaling.
•
Encrypted—Cisco Unified Communications Manager provides integrity, authentication, and encryption for the phone. A TLS connection that uses AES128/SHA opens for signaling, and SRTP carries the media for all phone calls.
When this check box is checked, Cisco Unified Communications
Manager encrypts phone downloads from the TFTP server. Refer to
“Configuration File Encryption” section on page 1-24 , and
Encrypted Phone Configuration Files” procedure on page 11-1 , for more
information.
OL-24964-01
Cisco Unified Communications Manager Security Guide
7-5
Chapter 7 Configuring a Phone Security Profile
Phone Security Profile Configuration Settings
Table 7-1 Security Profile for Phone That is Running SCCP (continued)
Setting
Authentication Mode
Description
This field allows you to choose the authentication method that the phone uses during the CAPF certificate operation.
From the drop-down list box, choose one of the following options:
•
By Authentication String—Installs/upgrades, deletes, or troubleshoots a locally significant certificate only when the user enters the CAPF authentication string on the phone.
•
•
•
By Null String— Installs/upgrades, deletes, or troubleshoots a locally significant certificate without user intervention.
This option provides no security; Cisco strongly recommends that you choose this option only for closed, secure environments.
By Existing Certificate (Precedence to LSC)— Installs/upgrades, deletes, or troubleshoots a locally significant certificate if a manufacture-installed certificate (MIC) or locally significant certificate (LSC) exists in the phone. If a LSC exists in the phone, authentication occurs via the LSC, regardless whether a MIC exists in the phone. If a MIC and LSC exist in the phone, authentication occurs via the LSC. If a LSC does not exist in the phone, but a MIC does exist, authentication occurs via the MIC.
Before you choose this option, verify that a certificate exists in the phone. If you choose this option and no certificate exists in the phone, the operation fails.
At any time, the phone uses only one certificate to authenticate to
CAPF even though a MIC and LSC can exist in the phone at the same time. If the primary certificate, which takes precedence, becomes compromised for any reason, or, if you want to authenticate via the other certificate, you must update the authentication mode.
By Existing Certificate (Precedence to MIC)—Installs/upgrades, deletes, or troubleshoots a locally significant certificate if a LSC or
MIC exists in the phone. If a MIC exists in the phone, authentication occurs via the MIC, regardless whether a LSC exists in the phone. If a LSC exists in the phone, but a MIC does not exist, authentication occurs via the LSC.
Note
Before you choose this option, verify that a certificate exists in the phone. If you choose this option and no certificate exists in the phone, the operation fails.
The CAPF settings that are configured in the Phone Security
Profile window interact with the CAPF parameters that are configured in the Phone Configuration window (see
“Configuration Tips for Phone Security Profiles” section on page 7-2
, for more details). Refer to the Cisco Unified
Communications Manager Administration Guide for information about configuring these settings on the Phone Configuration window.
7-6
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 7 Configuring a Phone Security Profile
Table 7-1
Setting
Key Size
Phone Security Profile Configuration Settings
Security Profile for Phone That is Running SCCP (continued)
Description
For this setting that is used for CAPF, choose the key size for the certificate from the drop-down list box. The default setting equals 1024.
Other options include 512 and 2048.
If you choose a higher key size than the default setting, the phones take longer to generate the entropy that is required to generate the keys. Key generation, which is set at low priority, allows the phone to function while the action occurs. Depending on the phone model, you may notice that key generation takes up to 30 or more minutes to complete.
Note
The CAPF settings that are configured in the Phone Security
Profile window interact with the CAPF parameters that are configured in the Phone Configuration window (see
Communications Manager Administration Guide for configuring these settings on the Phone Configuration window.
Table 7-2
Setting
Name
Description
Security Profile for Phone That is Running SIP
Nonce Validity Time
Device Security Mode
Description
Enter a name for the security profile.
When you save the new profile, the name displays in the Device Security
Profile drop-down list box in the Phone Configuration window for the phone type and protocol.
Tip
Include the device model and protocol in the security profile name to help you find the correct profile when you are searching for or updating a profile.
Enter a description for the security profile.
Enter the number of minutes (in seconds) that the nonce value is valid.
The default value equals 600 (10 minutes). When the time expires, Cisco
Unified Communications Manager generates a new value.
Note
A nonce value, a random number that supports digest authentication, gets used to calculate the MD5 hash of the digest authentication password.
From the drop-down list box, choose one of the following options:
•
Non Secure—No security features except image authentication exist for the phone. A TCP connection opens to Cisco Unified
Communications Manager.
•
•
Authenticated—Cisco Unified Communications Manager provides integrity and authentication for the phone. A TLS connection that uses NULL/SHA opens for signaling.
Encrypted—Cisco Unified Communications Manager provides integrity, authentication, and encryption for the phone. A TLS connection that uses AES128/SHA opens for signaling, and SRTP carries the media for all phone calls on all SRTP-capable hops.
Cisco Unified Communications Manager Security Guide
OL-24964-01 7-7
Chapter 7 Configuring a Phone Security Profile
Phone Security Profile Configuration Settings
Table 7-2 Security Profile for Phone That is Running SIP (continued)
Setting
Transport Type
Enable Digest
Authentication
TFTP Encrypted Config
Description
When Device Security Mode is Non Secure, choose one of the following options from the drop-down list box (some options may not display):
•
•
TCP—Choose the Transmission Control Protocol to ensure that packets get received in the same order as the order in which they are sent. This protocol ensures that no packets get dropped, but the protocol does not provide any security.
UDP—Choose the User Datagram Protocol to ensure that packets are received quickly. This protocol, which can drop packets, does not ensure that packets are received in the order in which they are sent.
This protocol does not provide any security.
•
TCP + UDP—Choose this option if you want to use a combination of TCP and UDP. This option does not provide any security.
When Device Security Mode is Authenticated or Encrypted, TLS specifies the Transport Type. TLS provides signaling integrity, device authentication, and signaling encryption (encrypted mode only) for
SIP phones.
If Device Security Mode cannot be configured in the profile, the transport type specifies UDP.
If you check this check box, Cisco Unified Communications Manager challenges all SIP requests from the phone.
Digest authentication does not provide device authentication, integrity, or confidentiality. Choose a security mode of authenticated or encrypted to use these features.
Note
For more information on digest authentication, see
Authentication” section on page 1-19
and
Authentication for the SIP Phone” section on page 12-1
When this check box is checked, Cisco Unified Communications
Manager encrypts phone downloads from the TFTP server. This option exists for Cisco phones only.
Tip
Cisco recommends that you enable this option and configure a symmetric key to secure digest credentials and administrative passwords.
Exclude Digest Credentials in Configuration File
Refer to
“Configuration File Encryption” section on page 1-24 , and
“Configuring Encrypted Phone Configuration Files” section on page 11-1
, for more information.
When this check box is checked, Cisco Unified Communications
Manager omits digest credentials in phone downloads from the TFTP server. This option exists for Cisco Unified IP Phones 7905G, 7912G,
7940G, and 7960G (SIP only).
Refer to
“Configuration File Encryption” section on page 1-24 , and
“Configuring Encrypted Phone Configuration Files” section on page 11-1
, for more information.
7-8
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 7 Configuring a Phone Security Profile
Phone Security Profile Configuration Settings
Table 7-2 Security Profile for Phone That is Running SIP (continued)
Setting
Authentication Mode
Description
This field allows you to choose the authentication method that the phone uses during the CAPF certificate operation. This option exists for Cisco phones only.
From the drop-down list box, choose one of the following options:
•
By Authentication String—Installs/upgrades or troubleshoots a locally significant certificate only when the user enters the CAPF authentication string on the phone.
•
•
•
By Null String— Installs/upgrades or troubleshoots a locally significant certificate without user intervention.
This option provides no security; Cisco strongly recommends that you choose this option only for closed, secure environments.
By Existing Certificate (Precedence to LSC)— Installs/upgrades or troubleshoots a locally significant certificate if a manufacture-installed certificate (MIC) or locally significant certificate (LSC) exists in the phone. If a LSC exists in the phone, authentication occurs via the LSC, regardless whether a MIC exists in the phone. If a LSC does not exist in the phone, but a MIC does exist, authentication occurs via the MIC.
Before you choose this option, verify that a certificate exists in the phone. If you choose this option and no certificate exists in the phone, the operation fails.
At any time, the phone uses only one certificate to authenticate to
CAPF even though a MIC and LSC can exist in the phone at the same time. If the primary certificate, which takes precedence, becomes compromised for any reason, or, if you want to authenticate via the other certificate, you must update the authentication mode.
By Existing Certificate (Precedence to MIC)—Installs/upgrades or troubleshoots a locally significant certificate if a LSC or MIC exists in the phone. If a MIC exists in the phone, authentication occurs via the MIC, regardless whether a LSC exists in the phone. If a LSC exists in the phone, but a MIC does not exist, authentication occurs via the LSC.
Note
Before you choose this option, verify that a certificate exists in the phone. If you choose this option and no certificate exists in the phone, the operation fails.
The CAPF settings that are configured in the Phone Security
Profile window interact with the CAPF parameters that are configured in the Phone Configuration window (see
Communications Manager Administration Guide for information about configuring these settings in the Phone Configuration window.
OL-24964-01
Cisco Unified Communications Manager Security Guide
7-9
Chapter 7 Configuring a Phone Security Profile
Applying a Phone Security Profile
Table 7-2
Setting
Key Size
SIP Phone Port
Security Profile for Phone That is Running SIP (continued)
Description
For this setting that is used for CAPF, choose the key size for the certificate from the drop-down list box. The default setting equals 1024.
Other options include 512 and 2048.
If you choose a higher key size than the default setting, the phones take longer to generate the entropy that is required to generate the keys. Key generation, which is set at low priority, allows the phone to function while the action occurs. Depending on the phone model, you may notice that key generation takes up to 30 or more minutes to complete.
Note
The CAPF settings that are configured in the Phone Security
Profile window interact with the CAPF parameters that are configured in the Phone Configuration window (see
“Configuration Tips for Phone Security Profiles” section on page 7-2
for more details). Refer to the Cisco Unified
Communications Manager Administration Guide for information about configuring these settings in the Phone Configuration window.
This setting applies to phones that are running SIP that use UDP transport.
Enter the port number for Cisco Unified IP Phones (SIP only) that use
UDP to listen for SIP messages from Cisco Unified Communications
Manager. The default setting equals 5060.
Phones that use TCP or TLS ignore this setting.
Applying a Phone Security Profile
You apply a phone security profile to the phone in the Phone Configuration window.
Before You Begin
Before you apply a security profile that uses certificates for authentication of the phone, ensure that phone contains a locally significant certificate (LSC) or manufacture-installed certificate (MIC).
If the phone does not contain a certificate, perform the following steps:
1.
In the Phone Configuration window, apply a nonsecure profile.
2.
3.
In the Phone Configuration window, install a certificate by configuring the CAPF settings. For more
In the Phone Configuration window, apply a device security profile that is configured for authentication or encryption.
To apply a phone security profile to a device, perform the following procedure:
Procedure
Step 1
Step 2
Find the phone, as described in the Cisco Unified Communications Manager Administration Guide.
After the Phone Configuration window displays, locate the Device Security Profile.
Cisco Unified Communications Manager Security Guide
7-10 OL-24964-01
Chapter 7 Configuring a Phone Security Profile
Synchronizing a Phone Security Profile with Affected Phones
Step 3
Step 4
Step 5
From the Device Security Profile drop-down list box, choose the security profile that applies to the device. Only the phone security profiles that are configured for the phone type and protocol display.
Click Save.
To apply the changes to the applicable phone, click Apply Config.
Next Steps
If you configured digest authentication for phones that are running SIP, you must configure the digest credentials in the End User Configuration window. Then, you must configure the Digest User setting in the Phone Configuration window. For more information about configuring digest users and digest credentials, refer to the
“Configuring Digest Authentication for the SIP Phone” section on page 12-1
.
Additional Information
See the
“Related Topics” section on page 7-13 .
Synchronizing a Phone Security Profile with Affected Phones
To synchronize phones with a Phone Security Profile that has undergone configuration changes, perform the following procedure, which will apply any outstanding configuration settings in the least-intrusive manner possible. (For example, a reset/restart may not be required on some affected phones.)
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Choose System > Security Profile > Phone Security Profile.
The Find and List Phone Security Profiles window displays.
Choose the search criteria to use.
Click Find.
The window displays a list of phone security profiles that match the search criteria.
Click the phone security profile to which you want to synchronize applicable phones. The Phone
Security Profile Configuration window displays.
Make any additional configuration changes.
Click Save.
Click Apply Config.
The Apply Configuration Information dialog displays.
Click OK.
Additional Information
See the
“Related Topics” section on page 7-13 .
OL-24964-01
Cisco Unified Communications Manager Security Guide
7-11
Chapter 7 Configuring a Phone Security Profile
Deleting a Phone Security Profile
Deleting a Phone Security Profile
This section describes how to delete a phone security profile from the Cisco Unified Communications
Manager database.
Before You Begin
Before you can delete a security profile from Cisco Unified Communications Manager Administration, you must apply a different profile to the devices or delete all devices that use the profile. To find out which devices use the profile, choose Dependency Records from the Related Links drop-down list box in the Security Profile Configuration window and click Go.
If the dependency records feature is not enabled for the system, go to System > Enterprise Parameters and change the Enable Dependency Records setting to True. A message displays information about high
CPU consumption that relates to the dependency records feature. Save your change to activate dependency records. For more information about dependency records, refer to the Cisco Unified
Communications Manager System Guide.
Procedure
Step 1
Step 2
Step 3
Step 4
Find the security profile by using the procedure in the
“Finding a Phone Security Profile” section on page 7-2 .
To delete multiple security profiles, check the check boxes next to the appropriate check box in the Find and List window; then, click Delete Selected. You can delete all configurable records for this selection by clicking Select All and then clicking Delete Selected
To delete a single security profile, perform one of the following tasks:
•
In the Find and List window, check the check box next to the appropriate security profile; then, click
Delete Selected.
When prompted to confirm the delete operation, click OK to delete or Cancel to cancel the delete operation.
Additional Information
See the
“Related Topics” section on page 7-13
.
Finding Phones That Use Phone Security Profiles
To find the phones that use a specific security profile, perform the following procedure:
Step 1
Step 2
In Cisco Unified Communications Manager Administration, choose Device > Phone.
From the first drop-down list box, choose the search parameter Security Profile.
•
From the drop-down list box, choose a search pattern.
•
Specify the appropriate search text, if applicable.
7-12
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 7 Configuring a Phone Security Profile
Where to Find More Information
Step 3
Step 4
Note
To add additional search criteria, click the + button. When you add criteria, the system searches for a record that matches all criteria that you specify. To remove criteria, click the – button to remove the last added criterion or click the Clear Filter button to remove all added search criteria.
Click Find.
All matching records display. You can change the number of items that display on each page by choosing a different value from the Rows per Page drop-down list box.
From the list of records that display, click the link for the record that you want to view.
Note
To reverse the sort order, click the up or down arrow, if available, in the list header.
The window displays the item that you choose.
Additional Information
See the
“Related Topics” section on page 7-13 .
Where to Find More Information
Related Topics
•
Digest Authentication, page 1-19
•
Configuration File Encryption, page 1-24
•
•
•
•
Phone Security Profile Overview, page 7-1
Configuration Tips for Phone Security Profiles, page 7-2
Finding a Phone Security Profile, page 7-2
Configuring a Phone Security Profile, page 7-3
•
•
•
•
•
•
•
•
Phone Security Profile Configuration Settings, page 7-4
Applying a Phone Security Profile, page 7-10
Synchronizing a Phone Security Profile with Affected Phones, page 7-11
Deleting a Phone Security Profile, page 7-12
Finding Phones That Use Phone Security Profiles, page 7-12
Configuring Encrypted Phone Configuration Files, page 11-1
Configuring Digest Authentication for the SIP Phone, page 12-1
Related Cisco Documentation
Cisco Unified Communications Manager Administration Guide
Cisco Unified IP Phone Administration Guide for Cisco Unified Communications Manager
OL-24964-01
Cisco Unified Communications Manager Security Guide
7-13
Where to Find More Information
Chapter 7 Configuring a Phone Security Profile
7-14
Cisco Unified Communications Manager Security Guide
OL-24964-01
C H A P T E R
8
Configuring Secure and Nonsecure Indication
Tones
The system plays secure and nonsecure indication tones on a protected phone to indicate whether a call is encrypted.
This chapter contains information on the following topics:
•
•
•
•
Important Information About Secure and Nonsecure Indication Tones, page 8-2
Configuration Requirements, page 8-3
Overview
The secure indication tone plays on a protected phone when the overall status of the call specifies protected; that is, when the system determines that the call is encrypted. The tone denotes that the call is protected and that confidential information may be exchanged. The tone comprises three long beeps.
If the overall status of the call specifies protected, the tone begins to play on a protected phone as soon as the called party answers.
When the overall status of the call is not protected, the system plays nonsecure indication tone, which comprises six short beeps, on a protected phone.
Note
Only callers on protected phones can hear secure and nonsecure indication tones. Callers on phones that are not protected never hear these tones.
Protected Devices
Configuration designates a protected device in Cisco Unified Communications Manager. You can configure only supported Cisco Unified IP Phones and MGCP E1 PRI gateways as protected devices in
Cisco Unified Communications Manager.
Cisco Unified Communications Manager can also direct an MGCP IOS gateway to play secure and nonsecure indication tones when the system determines the protected status of a call.
Cisco Unified Communications Manager Security Guide
8-1 OL-24964-01
Chapter 8 Configuring Secure and Nonsecure Indication Tones
Supported Devices
You can make the following types of calls that can use the secure and nonsecure indication tones:
•
•
Intracluster IP-to-IP calls
Intercluster calls that the system determines are protected
•
IP-to-Time-Division-Multiplexing (TDM) calls through a protected MGCP E1 PRI gateway
To determine which Cisco Unified IP Phone models can be configured as protected devices, see the
“Supported Devices” section on page 8-2
.
Supported Devices
You can use Cisco Unified Reporting to determine which Cisco Unified IP Phone models support secure and nonsecure indication tones. From Cisco Unified Reporting, click Unified CM Phone Feature List.
For the Feature pull-down menu, choose Secure Tone. The system displays a list of products that support the feature.
For more information about using Cisco Unified Reporting, see the Cisco Unified Reporting
Administration Guide.
Important Information About Secure and Nonsecure Indication
Tones
This section provides information that pertains to the impact of using the secure indication tone feature:
•
Facts about protected devices
–
You can configure phones that are running SCCP or SIP as protected devices.
•
–
–
Protected devices can call nonprotected devices that are either encrypted or nonencrypted. In such cases, the call specifies nonprotected and the nonsecure indication tone will play.
When a protected phone calls another protected phone, but the media is not encrypted, the call does not drop. In this case, the system plays nonsecure indication tone to the phones on the call.
For video calls, the system plays secure and nonsecure indication tones on protected devices.
Note
For video calls, the user may first hear secure indication tone for the audio portion of the call and then nonsecure indication tone for overall nonsecure media.
•
•
A lock icon that displays on a Cisco Unified IP Phone indicates that the media is encrypted, but does not necessarily mean that the phone has been configured as a protected device. However, the lock icon must be present for a protected call to occur.
The following services and features are impacted:
–
–
Multiline supplementary services (such as call transfer, conference, and call waiting) are supported on protected phones. When the user invokes a supplementary service on a protected phone, the system plays secure or nonsecure indication tone to reflect the updated status of the call.
Cisco Extension Mobility and Join Across Line services are disabled on protected phones.
–
Shared-line configuration is not available on protected phones.
8-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 8 Configuring Secure and Nonsecure Indication Tones
Configuration Requirements
•
–
Hold/Resume and Call Forward All are supported for protected calls.
Facts about MGCP E1 PRI gateways
–
You must configure the MGCP gateway for SRTP encryption. Configure the gateway with this command: mgcp package-capability srtp-package.
–
–
The MGCP gateway must specify an Advanced IP Services or Advanced Enterprise Services image (for example, c3745-adventerprisek9-mz.124-6.T.bin).
Protected status gets exchanged with the MGCP E1 PRI gateway by using proprietary FacilityIE in the MGCP PRI Setup, Alert, and Connect messages.
–
–
Cisco Unified Communications Manager plays the secure indication tone only to the Cisco
Unified IP Phone. A PBX in the network plays the tone to the gateway end of the call.
If the media between the Cisco Unified IP Phone and the MGCP E1 PRI gateway is not encrypted, the call drops.
Note
For more information about encryption for MGCP gateways, refer to Media and Signaling
Authentication and Encryption Feature for Cisco IOS MGCP Gateways for the version of
Cisco IOS software that you are using.
Configuration Requirements
You must configure the following items for the secure tone to play:
•
In the Phone Configuration window, which you can navigate to by choosing Device > Phone in
Cisco Unified Communications Manager Administration, configure the following items:
–
From the Softkey Template drop-down list in the Device Information portion of the window, choose Standard Protected Phone.
Note
You must use a new softkey template without supplementary service softkeys for a protected phone.
•
–
–
For the Join Across Lines option (also in the Device Information portion of the window), choose Off.
Check the Protected Device check box (also in the Device Information portion of the window).
–
From the Device Security Profile drop-down list (in the Protocol Specific Information portion of the window), choose a secure phone profile that is already configured in the Phone Security
Profile Configuration window (System > Security Profile > Phone Security Profile).
Go to the Directory Number Configuration window that displays when you add a directory number from the Phone Configuration window. In the Multiple Call/Call Waiting Settings on Device
DeviceName area of the Directory Number Configuration window, set the following options to a value of 1:
–
Maximum Number of Calls
–
Busy Trigger
OL-24964-01
Cisco Unified Communications Manager Security Guide
8-3
Chapter 8 Configuring Secure and Nonsecure Indication Tones
Configuration Requirements
•
•
In Cisco Unified Communications Manager Administration, choose System > Service Parameters.
In the first Service Parameter Configuration window, choose your server and choose the Cisco
CallManager service. In the second Service Parameter Configuration window, locate the
Clusterwide Parameters (Feature - Secure Tone) area, and set the Play Secure Indication Tone option to True. (The default value specifies False.)
If you are configuring a protected MGCP E1 PRI gateway, choose Device > Gateway > Add New in Cisco Unified Communications Manager Administration and choose a supported gateway.
Choose MCGP as the protocol. When the Gateway Configuration window displays, specify the following configuration choices:
–
Set Global ISDN Switch Type to Euro.
–
After you complete the rest of the MGCP Gateway configuration, click Save; then, click the endpoint icon that appears to the right of subunit 0 in the window. The Enable Protected
Facility IE check box displays. Check this check box.
This configuration allows the system to pass protected status of the call between Cisco Unified
IP Phone endpoints and the protected PBX phones that connect to the MGCP gateway.
8-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
C H A P T E R
9
Configuring Encryption to Analog Endpoints
This feature enables you to create a secure SCCP connection for analog phones to a Cisco VG2xx
Gateway. The gateway uses Transport Layer Security (TLS) with Cisco Unified Communications
Manager for SCCP signaling communication and uses SRTP for voice communication. The existing
Cisco Unified Communications Manager TLS functionality, including certificate management, is used for secure SCCP communication.
This chapter contains the following sections:
•
•
Phone Security Profile, page 9-1
Certificate Management, page 9-1
Phone Security Profile
To establish an encrypted connection to analog phones, you must create a Phone Security Profile for analog phones with the Device Security Mode parameter set to Authenticated or Encrypted. To create a Phone Security Profile, navigate to System > Security Profile > Phone Security Profile in Cisco
Unified Communications Manager Administration.
For more information about creating a Phone Security Profile, see
Chapter 7, “Configuring a Phone
Security Profile” in the Cisco Unified Communications Manager Security Guide.
When you configure an analog phone attached to a Cisco VG2xx gateway, choose the secure analog profile you created for the Device Security Profile parameter. To configure the Device Security Profile parameter, navigate to Device > Phone in Cisco Unified Communications Manager Administration and scroll down to the Protocol Specific Information section for the phone you want to configure.
Certificate Management
For secure analog phones to function, you must import the same CA-signed certificate into Cisco Unified
Communications Manager that is being used by the Cisco VG2xx Gateway. For more information about importing certificates, see Chapter 6, “Security,” in the Cisco Unified Communications Operating
System Administration Guide.
Cisco Unified Communications Manager Security Guide
9-1 OL-24964-01
Certificate Management
Chapter 9 Configuring Encryption to Analog Endpoints
9-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
C H A P T E R
10
Using the Certificate Authority Proxy Function
This chapter provides information on the following topics:
•
Certificate Authority Proxy Function Overview, page 10-1
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Cisco Unified IP Phone and CAPF Interaction, page 10-2
CAPF Interaction with IPv6 Addressing, page 10-3
CAPF System Interactions and Requirements, page 10-4
Configuring CAPF in Cisco Unified Serviceability, page 10-5
CAPF Configuration Checklist, page 10-5
Activating the Certificate Authority Proxy Function Service, page 10-6
Updating CAPF Service Parameters, page 10-6
Using CAPF to Install, Upgrade, Troubleshoot, or Delete Certificates from the Phone, page 10-7
CAPF Settings in the Phone Configuration Window, page 10-8
Finding Phones on Basis of LSC Status or Authentication String, page 10-9
Generating a CAPF Report, page 10-9
Entering the Authentication String on the Phone, page 10-10
Verifying the Authentication String on the Phone, page 10-11
Where to Find More Information, page 10-11
Certificate Authority Proxy Function Overview
Certificate Authority Proxy Function (CAPF), which automatically installs with Cisco Unified
Communications Manager, performs the following tasks, depending on your configuration:
•
•
•
•
Authenticate via an existing Manufacturing Installed Certificate (MIC), Locally Significant
Certificate (LSC), randomly generated authentication string, or optional less secure “null” authentication.
Issues locally significant certificates to supported Cisco Unified IP Phones.
Upgrades existing locally significant certificates on the phones.
Retrieves phone certificates for viewing and troubleshooting.
Cisco Unified Communications Manager Security Guide
10-1 OL-24964-01
Chapter 10 Using the Certificate Authority Proxy Function
Cisco Unified IP Phone and CAPF Interaction
During installation, a certificate that is specific for CAPF gets generated. This CAPF certificate, which the Cisco CTL Client copies to all Cisco Unified Communications Manager servers in the cluster, uses the .0 extension. To verify that the CAPF certificate exists, display the CAPF certificate at the Cisco
Unified Communications Operating System GUI.
Cisco Unified IP Phone and CAPF Interaction
When the phone interacts with CAPF, the phone authenticates itself to CAPF by using an authentication string, existing MIC or LSC certificate, or “null,” generates its public key and private key pair, and then forwards its public key to the CAPF server in a signed message. The private key remains in the phone and never gets exposed externally. CAPF signs the phone certificate and then sends the certificate back to the phone in a signed message.
The following information applies when a communication or power failure occurs.
•
If a communication failure occurs while the certificate installation is taking place on the phone, the phone will attempt to obtain the certificate three more times in 30-second intervals. You cannot configure these values.
•
If a power failure occurs while the phone attempts a session with CAPF, the phone will use the authentication mode that is stored in flash; that is, if the phone cannot load the new configuration file from the TFTP server after the phone reboots. After the certificate operation completes, the system clears the value in flash.
Tip
Be aware that the phone user can abort the certificate operation or view the operation status on the phone.
Tip
Key generation, which is set at low priority, allows the phone to function while the action occurs. You may notice that key generation takes up to 30 or more minutes to complete.
Although the phone functions during certification generation, additional TLS traffic may cause minimal call-processing interruptions with the phone; for example, audio glitches may occur when the certificate is written to flash at the end of the installation.
If you choose a 2048-bit key for the certificate, establishing a connection among the phone, Cisco
Unified Communications Manager, and secure SRST-enabled gateway during phone boot-up and failover may take more than 60 seconds. Unless you want the highest possible security level, do not configure the 2048-bit key.
Consider the following information about how CAPF interacts with the Cisco Unified IP Phone 7960G and 7940G when the phone is reset by a user or by Cisco Unified Communications Manager.
Note
In the following examples, if the LSC does not already exist in the phone and if By Existing Certificate is chosen for the CAPF Authentication Mode, the CAPF certificate operation fails.
10-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 10 Using the Certificate Authority Proxy Function
CAPF Interaction with IPv6 Addressing
Example—Nonsecure Device Security Mode
In this example, the phone resets after you configure the Device Security Mode to Nonsecure and the
CAPF Authentication Mode to By Null String or By Existing Certificate (Precedence...). After the phone resets, it immediately registers with the primary Cisco Unified Communications Manager and receives the configuration file. The phone then automatically initiates a session with CAPF to download the LSC.
After the phone installs the LSC, configure the Device Security Mode to Authenticated or Encrypted.
Example—Authenticated/Encrypted Device Security Mode
In this example, the phone resets after you configure the Device Security Mode to Authenticated or
Encrypted and the CAPF Authentication Mode to By Null String or By Existing Certificate
(Precedence...). The phone does not register with the primary Cisco Unified Communications Manager until the CAPF session ends and the phone installs the LSC. After the session ends, the phone registers and immediately runs in authenticated or encrypted mode.
You cannot configure By Authentication String in this example because the phone does not automatically contact the CAPF server; the registration fails if the phone does not have a valid LSC.
CAPF Interaction with IPv6 Addressing
CAPF can issue and upgrade certificates to a phone that uses an IPv4, an IPv6, or both types of addresses.
To issue or upgrade certificates for phones that are running SCCP that use an IPv6 address, you must set the Enable IPv6 service parameter to True in Cisco Unified Communications Manager Administration.
When the phone connects to CAPF to get a certificate, CAPF uses the configuration from the Enable
IPv6 enterprise parameter to determine whether to issue or upgrade the certificate to the phone. If the enterprise parameter is set to False, CAPF ignores/rejects connections from phones that use IPv6 addresses, and the phone does not receive the certificate.
describes how a phone that has an IPv4, IPv6, or both types of addresses connects to CAPF.
Table 10-1 How IPv6 or IPv4 Phone Connects to CAPF
IP Mode of Phone
Dual-stack
IP Addresses on
Phone
IPv4 and IPv6 available
CAPF IP Address
IPv4, IPv6
Dual-stack
Dual-stack
Dual-stack
Dual-stack
Dual-stack
Dual-stack
IPv4
IPv6
IPv4
IPv4 and IPv6 available
IPv4 and IPv6 available
IPv4
IPv4, IPv6
IPv4, IPv6
IPv4
IPv6
IPv4
IPv6
How Phone Connects to CAPF
Phone uses an IPv6 address to connect to
CAPF; if the phone cannot connect via an IPv6 address, it attempts to connect by using an IPv4 address.
Phone uses an IPv4 address to connect to
CAPF.
Phone uses an IPv6 address to connect to
CAPF. If the attempt fails, the phone uses an IPv4 address to connect to CAPF.
Phone uses an IPv4 address to connect to
CAPF.
Phone uses and IPv6 address to connect to CAPF.
Phone uses an IPv4 address to connect to
CAPF.
Phone cannot connect to CAPF.
OL-24964-01
Cisco Unified Communications Manager Security Guide
10-3
Chapter 10 Using the Certificate Authority Proxy Function
CAPF System Interactions and Requirements
Table 10-1 How IPv6 or IPv4 Phone Connects to CAPF (continued)
IP Mode of Phone
Dual-stack
Dual-stack
IP Addresses on
Phone
IPv6
IPv6
IPv4
IPv6
IPv4
IPv4
IPv6
IPv6
IPv4
IPv6
IPv4
IPv4
IPv6
IPv6
CAPF IP Address
IPv4
IPv6
IPv4, IPv6
IPv4, IPv6
IPv4
IPv6
IPv6
IPv4
How Phone Connects to CAPF
Phone cannot connect to CAPF.
Phone uses an IPv6 address to connect to
CAPF.
Phone uses an IPv4 address to connect to
CAPF.
Phone uses an IPv6 address to connect to
CAPF.
Phone uses an IPv4 address to connect to
CAPF.
Phone cannot connect to CAPF.
Phone uses an IPv6 address to connect to
CAPF.
Phone cannot connect to CAPF.
CAPF System Interactions and Requirements
The following requirements exist for CAPF:
•
•
Before you use CAPF, ensure that you performed all necessary tasks to install and configure the
Cisco CTL Client. To use CAPF, you must activate the Cisco Certificate Authority Proxy Function service on the first node.
During a certificate upgrade or install operation, if By Authentication String is the CAPF authentication method for the phone, you must enter the same authentication string on the phone after the operation, or the operation will fail. If TFTP Encrypted Configuration enterprise parameter is enabled and you fail to enter the authentication string, the phone may fail and may not recover until the matching authentication string is entered on the phone.
•
•
Cisco strongly recommends that you use CAPF during a scheduled maintenance window because generating many certificates at the same time may cause call-processing interruptions.
All servers in the Cisco Unified Communications Manager cluster must use the same administrator username and password, so CAPF can authenticate to all servers in the cluster.
•
•
•
Ensure that the first node is functional and running during the entire certificate operation.
Ensure that the phone is functional during the entire certificate operation.
If a secure phone gets moved to another cluster, the Cisco Unified Communications Manager will not trust the LSC certificate that the phone sends because it was issued by another CAPF, whose certificate is not in the CTL file. To enable the secure phone to register, delete the existing CTL file by using the
“Deleting the CTL File on the Cisco Unified IP Phone” section on page 4-20
. You can then use the Install/Upgrade option to install a new LSC certificate with the new CAPF and reset the phone for the new CTL file (or use the MIC). Use the Delete option in the CAPF section on the
Phone Configuration window to delete the existing LSC before you move the phones.
10-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 10 Using the Certificate Authority Proxy Function
Configuring CAPF in Cisco Unified Serviceability
Tip
Cisco IP Telephony Backup and Restore System (BARS) backs up the CAPF data and reports because Cisco Unified Communications Manager stores the information in the Cisco Unified
Communications Manager database.
Configuring CAPF in Cisco Unified Serviceability
You perform the following tasks in Cisco Unified Serviceability:
•
•
Activate the Cisco Certificate Authority Proxy Function service.
Configure trace settings for CAPF.
Refer to the Cisco Unified Serviceability Administration Guides for more information.
CAPF Configuration Checklist
provides a list of tasks that you perform to install, upgrade, or troubleshoot locally significant certificates.
Table 10-2 CAPF Configuration Checklist
Configuration Steps
Step 1
Determine whether a locally significant certificate exists in the phone.
Related Procedures and Topics
•
Phone documentation that supports your phone model and this version of Cisco
Unified Communications Manager
Determine whether you need to copy CAPF data to the Cisco
Unified Communications Manager publisher database server.
Tip
If you used the CAPF utility with Cisco Unified
Communications Manager 4.0 and verified that the
CAPF data exists in the Cisco Unified Communications
Manager database, you can delete the CAPF utility that you used with Cisco Unified Communications Manager
4.0.
•
Data Migration Assistant User Guide that supports this version of Cisco Unified
Communications Manager
Step 2
Step 3
Verify that the Cisco Certificate Authority Proxy Function service is running.
Tip
This service must run during all CAPF operations. It must also run for the Cisco CTL Client to include the
CAPF certificate in the CTL file.
Verify that you performed all necessary tasks to install and configure the Cisco CTL Client. Ensure that the CAPF certificate exists in the Cisco CTL file.
Activating the Certificate Authority Proxy
Configuring the Cisco CTL Client, page 4-10
OL-24964-01
Cisco Unified Communications Manager Security Guide
10-5
Chapter 10 Using the Certificate Authority Proxy Function
Activating the Certificate Authority Proxy Function Service
Table 10-2
Configuration Steps
Step 4
Step 5
Step 6
CAPF Configuration Checklist (continued)
If necessary, update CAPF service parameters.
To install, upgrade, or troubleshoot locally significant certificates in the phone, use Cisco Unified Communications
Manager Administration.
If it is required for certificate operations, enter the authentication string on the phone.
Related Procedures and Topics
•
Updating CAPF Service Parameters, page 10-6
•
•
•
Using CAPF to Install, Upgrade,
Troubleshoot, or Delete Certificates from the Phone, page 10-7
Using CAPF to Install, Upgrade,
Troubleshoot, or Delete Certificates from the Phone, page 10-7
Configuration Window, page 10-8
•
Finding Phones on Basis of LSC Status or
Authentication String, page 10-9
Entering the Authentication String on the
Activating the Certificate Authority Proxy Function Service
Cisco Unified Communications Manager does not automatically activate the Certificate Authority Proxy
Function service in Cisco Unified Serviceability.
If you did not activate this service before you installed and configured the Cisco CTL Client, you must update the CTL file, as described in
“Updating the CTL File” section on page 4-13
. Activate this service only on the first node.
To activate the service, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
In Cisco Unified Serviceability, choose Tools > Service Activation.
From the Servers drop-down list box, choose the server on which you want to activate the Certificate
Authority Proxy Function service.
Check the Certificate Authority Proxy Function check box.
Click Save.
Additional Information
See the
“Related Topics” section on page 10-11 .
Updating CAPF Service Parameters
The CAPF Service Parameter window provides information on the number of years that the certificate is valid, the maximum number of times that the system retries to generate the key, the key size, and so on.
10-6
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 10 Using the Certificate Authority Proxy Function
Using CAPF to Install, Upgrade, Troubleshoot, or Delete Certificates from the Phone
For the CAPF service parameters to show Active status in Cisco Unified Communications Manager
Administration, you must activate the Certificate Authority Proxy Function service, as described in
“Activating the Certificate Authority Proxy Function Service” section on page 10-6 .
To update the CAPF service parameters, perform the following procedure:
Procedure
Step 1
Step 2
In Cisco Unified Communications Manager Administration, choose System > Service Parameters.
From the Server drop-down list box, choose the server.
Tip
Step 3
Step 4
You must choose the first node in the cluster.
From the Service drop-down list box, choose the Cisco Certificate Authority Proxy Function service.
Update the CAPF service parameters, as described in help that displays for the parameter.
Note
To display help for the CAPF service parameters, click the question mark or the parameter name links.
Step 5
For the changes to take effect, restart the Cisco Certificate Authority Proxy Function service.
Additional Information
See the
“Related Topics” section on page 10-11
.
Using CAPF to Install, Upgrade, Troubleshoot, or Delete
Certificates from the Phone
Use
as a reference when you use CAPF.
Perform the following procedure to use the Certificate Authority Proxy Function:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Find the phone, as described in the Cisco Unified Communications Manager Administration Guide.
After the search results display, locate the phone where you want to install, upgrade, delete, or troubleshoot the certificate and click the Device Name (Line) link for that phone.
Enter the configuration settings, as described in
Click Save.
Click Reset.
OL-24964-01
Additional Information
See the
“Related Topics” section on page 10-11
.
Cisco Unified Communications Manager Security Guide
10-7
Chapter 10 Using the Certificate Authority Proxy Function
CAPF Settings in the Phone Configuration Window
CAPF Settings in the Phone Configuration Window
Table 10-3 describes the CAPF settings in the Phone Configuration window in Cisco Unified
Communications Manager Administration.
•
For configuration tips, see the
“CAPF System Interactions and Requirements” section on page 10-4
.
•
For related information and procedures, see the
“Related Topics” section on page 10-11
.
Table 10-3 CAPF Configuration Settings
Setting
Certificate Operation
Authentication String
Generate String
Operation Completes by
Description
From the drop-down list box, choose one of the following options:
•
No Pending Operation—Displays when no certificate operation is occurring. (default setting)
•
•
Install/Upgrade—Installs a new or upgrades an existing locally significant certificate in the phone.
Delete—Deletes the locally significant certificate that exists in the phone.
•
Tip
Troubleshoot—Retrieves the locally significant certificate (LSC) or the manufacture-installed certificate (MIC), so you can view the certificate credentials in the CAPF trace file. If both certificate types exist in the phone, Cisco Unified Communications Manager creates two trace files, one for each certificate type.
By choosing the Troubleshoot option, you can verify that an LSC or MIC exists in the phone. The Delete and Troubleshoot options do not display if a certificate does not exist in the phone.
If you chose the By Authentication String option, this field applies.
Manually enter a string or generate a string by clicking the Generate
String button. Ensure that the string contains 4 to 10 digits.
To install, upgrade, or troubleshoot a locally significant certificate, the phone user or administrator must enter the authentication string on the
If you want CAPF to automatically generate an authentication string, click this button. The 4- to 10-digit authentication string displays in the
Authentication String field.
This field, which supports all certificate operation options, specifies the date and time by which you must complete the operation.
The values that display apply for the first node.
Operation Status This field displays the progress of the certificate operation; for example,
<operation type> pending, failed, or successful, where operating type equals the Install/Upgrade, Delete, or Troubleshoot certificate operation options. You cannot change the information that displays in this field.
10-8
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 10 Using the Certificate Authority Proxy Function
Finding Phones on Basis of LSC Status or Authentication String
Finding Phones on Basis of LSC Status or Authentication String
To find phones on the basis of certificate operation status or the authentication string, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
In Cisco Unified Communications Manager Administration, choose Device > Phone.
The Find and List window displays. Records from an active (prior) query may also display in the window.
From the first drop-down list box, choose one of the following options:
•
•
LSC Status—Choosing this option returns a list of phones that use CAPF to install, upgrade, delete, or troubleshoot locally significant certificates.
Authentication String—Choosing this option returns a list of phones with an authentication string that is specified in the Authentication String field.
From the second drop-down list box, choose a search pattern.
Specify the appropriate search text, if applicable.
Note
To add additional search criteria, click the + button. When you add criteria, the system searches for a record that matches all criteria that you specify. To remove criteria, click the – button to remove the last added criterion or click the Clear Filter button to remove all added search criteria.
Step 5
Step 6
Click Find.
All matching records display. You can change the number of items that display on each page by choosing a different value from the Rows per Page drop-down list box.
From the list of records that display, click the link for the record that you want to view.
Note
To reverse the sort order, click the up or down arrow, if available, in the list header.
The window displays the item that you choose.
Additional Information
See the
“Related Topics” section on page 10-11
.
Generating a CAPF Report
If you want to do so, you can generate a CAPF report to view the status of the certificate operation, the authentication string, security profile, authentication mode, and so on. The report includes information such as device name, device description, security profile, authentication string, authentication mode,
LSC status, and so on.
To generate a CAPF report, perform the following procedure:
OL-24964-01
Cisco Unified Communications Manager Security Guide
10-9
Chapter 10 Using the Certificate Authority Proxy Function
Entering the Authentication String on the Phone
Procedure
Step 1
Step 2
In Cisco Unified Communications Manager Administration, choose Device > Phone.
The Find/List window displays. Records from an active (prior) query may also display in the window.
To find all records in the database, ensure the dialog box is empty; go to
.
To filter or search records
•
From the first drop-down list box, choose a search parameter.
•
•
From the second drop-down list box, choose a search pattern.
Specify the appropriate search text, if applicable.
Note
To add additional search criteria, click the + button. When you add criteria, the system searches for a record that matches all criteria that you specify. To remove criteria, click the – button to remove the last added criterion or click the Clear Filter button to remove all added search criteria.
Step 3
Step 4
Step 5
Step 6
Click Find.
All matching records display. You can change the number of items that display on each page by choosing a different value from the Rows per Page drop-down list box.
In the Related Links drop-down list box, choose CAPF Report in File; then, click Go.
Save the file to a location that you will remember.
Use Microsoft Excel to open the .csv file.
Additional Information
See the
“Related Topics” section on page 10-11 .
Entering the Authentication String on the Phone
If you chose the By Authentication String mode and generated an authentication string, you must enter the authentication string on the phone to install the locally significant certificate.
Tip
The authentication string applies for one-time use only. Obtain the authentication string that displays in the Phone Configuration window or in the CAPF report.
Before You Begin
Before you enter the authentication string on the phone, verify that the following conditions are met:
•
•
•
•
The CAPF certificate exists in the CTL file.
The first node functions and runs. Ensure that the server runs for each certificate installation.
The device has registered.
10-10
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 10 Using the Certificate Authority Proxy Function
Verifying the Authentication String on the Phone
•
A signed image exists on the phone; refer to the Cisco Unified IP Phone administration documentation that supports your phone model.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Press the Settings button on the phone.
If the configuration is locked, press **# (asterisk, asterisk, pound sign) to unlock it.
Scroll down the Settings menu. Highlight “Security Configuration” and press the Select softkey.
Scroll down the Security Configuration menu. Highlight “LSC” and press the Update softkey.
When prompted for the authentication string, enter the string that the system provides and press the
Submit softkey.
The phone installs, updates, deletes, or fetches the certificate, depending on the current CAPF configuration.
You can monitor the progress of the certificate operation by viewing the messages that display on the phone. After you press Submit, the message “Pending” displays under the LSC option. The phone generates the public and private key pair and displays the information on the phone. When the phone successfully completes the process, the phone displays a successful message. If the phone displays a failure message, you entered the wrong authentication string or did not enable the phone for upgrade.
You can stop the process by choosing the Stop option at any time.
Additional Information
See the
“Related Topics” section on page 10-11
.
Verifying the Authentication String on the Phone
You can verify that the certificate is installed on the phone by choosing Settings > Model Information and viewing the LSC setting, which indicates Installed or Not Installed.
Additional Information
See the
“Related Topics” section on page 10-11
.
Where to Find More Information
Related Topics
•
Certificate Authority Proxy Function Overview, page 10-1
•
•
•
•
•
•
Cisco Unified IP Phone and CAPF Interaction, page 10-2
CAPF System Interactions and Requirements, page 10-4
Configuring CAPF in Cisco Unified Serviceability, page 10-5
CAPF Configuration Checklist, page 10-5
Activating the Certificate Authority Proxy Function Service, page 10-6
Updating CAPF Service Parameters, page 10-6
OL-24964-01
Cisco Unified Communications Manager Security Guide
10-11
Chapter 10 Using the Certificate Authority Proxy Function
Where to Find More Information
•
•
•
•
•
•
Using CAPF to Install, Upgrade, Troubleshoot, or Delete Certificates from the Phone, page 10-7
CAPF Settings in the Phone Configuration Window, page 10-8
Finding Phones on Basis of LSC Status or Authentication String, page 10-9
Generating a CAPF Report, page 10-9
Entering the Authentication String on the Phone, page 10-10
Verifying the Authentication String on the Phone, page 10-11
Related Cisco Documentation
Cisco Unified IP Phone Administration Guide for Cisco Unified Communications Manager
Cisco Unified Serviceability Administration Guide
10-12
Cisco Unified Communications Manager Security Guide
OL-24964-01
C H A P T E R
11
Configuring Encrypted Phone Configuration Files
After you configure security-related settings, the phone configuration file contains sensitive 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, page 11-1
Supported Phone Models, page 11-4
Configuration Tips for Encrypted Configuration Files, page 11-4
Encryption Configuration File Configuration Checklist, page 11-5
•
•
•
•
Enabling Phone Configuration File Encryption, page 11-6
Configuring Manual Key Distribution, page 11-6
Manual Key Distribution Configuration Settings, page 11-7
Entering the Symmetric Key on the Phone, page 11-7
•
•
•
Verifying That an LSC or MIC Certificate Is Installed, page 11-8
Verifying That the Phone Configuration File Is Encrypted, page 11-9
Disabling Encryption for the Phone Configuration Files, page 11-9
Where to Find More Information, page 11-10
Understanding Encryption of the Phone Configuration File
To secure digest credentials and secured passwords in phone downloads from Cisco Unified
Communications Manager, you must enable the TFTP Encrypted Config option in the Phone Security
Profile Configuration window and perform additional tasks in Cisco Unified Communications Manager
Administration.
After you enable the TFTP Encrypt Config option, configure the required parameters in Cisco Unified
Communications Manager Administration and the phone and restart required services in Cisco Unified
Serviceability, the TFTP server
1.
Deletes all clear text configuration files on disk
2.
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.
OL-24964-01
Cisco Unified Communications Manager Security Guide
11-1
Chapter 11 Configuring Encrypted Phone Configuration Files
Understanding Encryption of the Phone Configuration File
Warning If digest authentication is True for the phone that is running SIP when the TFTP encrypted configuration setting is False, digest credentials may get sent in the clear. See
“Disabling Encryption for the Phone Configuration Files” section on page 11-9 for more information.
Some phones do not support encrypted phone configuration files, as described in
to encrypt the configuration file. Supported methods rely on Cisco Unified Communications Manager 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 Communications Manager supports the following methods:
•
•
Symmetric Key Encryption with Phone Public Key
The information in the
“Symmetric Key Encryption with Phone Public
Key” sections assumes that you configured Mixed Mode and that you enabled the TFTP Encrypted
Config parameter in Cisco Unified Communications Manager Administration.
Manual Key Distribution
Tip
For a list of phones that support this method, see
“Supported Phone Models” section on page 11-4
.
With manual key distribution, a 128- or 256-bit symmetric key, which is stored in the Cisco Unified
Communications Manager database, encrypts the phone configuration file after the phone resets. To determine the key size for your phone model, see
“Supported Phone Models” section on page 11-4
.
To encrypt the configuration file, the administrator can either manually enter the key into or prompt
Cisco Unified Communications Manager to generate the key in the Phone Configuration window. 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.
After 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
“Supported Phone Models” section on page 11-4
.
When the phone contains the symmetric key, the phone always requests the encrypted configuration file.
Cisco Unified Communications Manager downloads the encrypted configuration file to the phone, which the TFTP server signs. Not all phone types validate the signer of the configuration file; see
Phone Models” section on page 11-4 for more information.
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
If the TFTP Encrypted Config setting gets disabled, administrators must remove the symmetric key from the phone GUI, so the phone requests an unencrypted configuration file the next time that it is reset.
11-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 11 Configuring Encrypted Phone Configuration Files
Understanding Encryption of the Phone Configuration File
Symmetric Key Encryption with Phone Public Key
Tip
For a list of phones that support this method, see
“Supported Phone Models” section on page 11-4 .
For more information about The Certificate Authority Proxy Function (CAPF), see
Authority Proxy Function Overview” section on page 10-1 . The Certificate Authority Proxy Function
(CAPF) authenticates Cisco Unified IP Phones to Cisco Unified Communications Manager and issues phone certificates (LSCs).
If the phone contains a manufacturing-installed certificate (MIC) or a locally significant certificate
(LSC), the phone contains a public and private key pair, which are used for PKI encryption.
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 Communications Manager 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 after 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 it 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
For phones that support this encryption method, the phone uses the encryption configuration flag in the configuration file to determine whether to request an encrypted or unencrypted file. If the TFTP
Encrypted Config setting is disabled, and Cisco Unified IP Phones that support this encryption method request an encrypted file (.enc.sgn file), Cisco Unified Communications Manager sends a ‘file not found error’ to the phone. The phone then requests an unencrypted, signed file (.sgn file).
If the TFTP Encrypted Config setting is enabled but the phone requests an unencrypted configuration file for some reason, the TFTP server offers an unencrypted file that contains minimal configuration settings. After the phone receives the minimum configuration, the phone can detect error conditions, such as key mismatch, and may start a session with CAPF to synchronize the phone public key with the
Cisco Unified Communications Manager database. If the error condition is resolved, the phone requests an encrypted configuration file the next time that it resets.
OL-24964-01
Cisco Unified Communications Manager Security Guide
11-3
Chapter 11 Configuring Encrypted Phone Configuration Files
Supported Phone Models
Supported Phone Models
You can encrypt the phone configuration file for the following Cisco Unified IP Phones:
Phone Model and Protocol
Cisco Unified IP Phone 7905G or 7912G (SIP only)
Cisco Unified IP Phone 7940G or 7960G (SIP only)
File signing support: No
Manual key distribution—
Encryption algorithm: Advanced Encryption
Standard (AES) 128
Key size: 128 bits
File signing support: These phones that are running SIP receive signed, encrypted configuration files but ignore the signing information.
Cisco Unified IP Phone 7970G, 7971G, or 7975G;
Cisco Unified IP Phone 7961G, 7962G, or 7965G;
Cisco Unified IP Phone 7941G, 7942G, or 7945G;
Cisco Unified IP Phone 7911G;
Cisco Unified IP Phone 7906G
Symmetric key encryption with phone public key
(PKI encryption)—
Encryption algorithm: AES 128
Key size: 128 bits
File signing support: Yes
Cisco Unified IP Phone 7971G-GE, 7961G-GE,
7941G-GE
Cisco Unified IP Phone 7931G (SCCP only)
Encryption Method
Manual key distribution—
Encryption algorithm: RC4
Key size: 256 bits
Configuration Tips for Encrypted Configuration Files
Cisco recommends that you enable the TFTP Encrypted Config flag to secure confidential data in phone downloads. For phones that do not have PKI capabilities, you must also configure a symmetric key in
Cisco Unified Communications Manager Administration and in the phone. If the symmetric key is missing from either the phone or Cisco Unified Communications Manager or if a mismatch occurs when the TFTP Encrypted Config flag is set, the phone cannot register.
Consider the following information when you configure encrypted configuration files in Cisco Unified
Communications Manager Administration:
•
•
Only phones that support encrypted configuration files display the TFTP Encrypted Config flag in the phone security profile. You cannot configure encrypted configuration files for Cisco Unified IP
Phones 7905G, 7912G, 7940G, and 7960G (SCCP only) because these phones do not receive confidential data in the configuration file download.
The default setting for TFTP Encrypted Config specifies False (not checked). If you apply the default, non-secure profile to the phone, digest credentials and secured passwords get sent in the clear.
11-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 11 Configuring Encrypted Phone Configuration Files
Encryption Configuration File Configuration Checklist
•
•
•
For Cisco Unified IP Phones that use public key encryption, Cisco Unified Communications
Manager does not require you to set the Device Security Mode to authenticated or encrypted to enable encrypted configuration files.
Cisco Unified Communications Manager uses the CAPF process for downloading its public key during registration.
You may choose to download unencrypted configuration files to phones if you know your environment is secure or to avoid manually configuring symmetric keys for phones that are not
PKI-enabled; however, Cisco does not recommend using this method.
For Cisco Unified IP Phones 7905G, 7912G, 7940G, and 7960G (SIP only), Cisco Unified
Communications Manager Administration provides a method of sending digest credentials to the phone that is easier, but less secure, than using an encrypted configuration file. This method, which uses the TFTP Exclude Digest Credential in Configuration File setting, is useful for initializing digest credentials because it does not require you to first configure a symmetric key and enter it on the phone.
With this method, you send the digest credentials to the phone in an unencrypted configuration file.
After the credentials are in the phone, Cisco recommends that you keep the TFTP file encryption setting disabled and enable the TFTP Exclude Digest Credential in Configuration File flag on the corresponding security profile window, which will exclude digest credentials from future downloads.
After digest credentials exist in these phones and an incoming file does not contain digest credentials, the existing credentials remain in place. The digest credentials remain intact until the phone is factory reset or new credentials (including blanks) are received.
If you change digest credentials for a phone or end user, temporarily disable the Exclude Digest
Credentials flag on the corresponding security profile window to download the new digest credentials to the phone.
Encryption Configuration File Configuration Checklist
Unified Communications Manager Administration.
Table 11-1 Encryption Configuration File Configuration Checklist
Configuration Steps
Step 1
Verify that the Cluster Security Mode is configured for Mixed
Mode.
Step 2
Note
Cluster security mode configures the security capability for your cluster or standalone server.
Check the TFTP Encrypted Config check box in the Phone
Security Profile. Be sure to apply the profile to the phone.
Related Procedures and Topics
Configuring the Cisco CTL Client, page 4-1
•
Configuration Tips for Encrypted
Configuration Files, page 11-4
•
•
Enabling Phone Configuration File
Applying a Phone Security Profile, page 7-10
OL-24964-01
Cisco Unified Communications Manager Security Guide
11-5
Chapter 11 Configuring Encrypted Phone Configuration Files
Enabling Phone Configuration File Encryption
Table 11-1 Encryption Configuration File Configuration Checklist (continued)
Configuration Steps
Step 3
Determine which phones support manual key distribution and which phones support symmetric key encryption with phone public key (PKI encryption).
Step 4
If your phone supports manual key distribution, perform the manual key distribution tasks.
Step 5
Step 6
Related Procedures and Topics
Supported Phone Models, page 11-4
If your phone supports manual key distribution, enter the symmetric key on the phone; reset the phone.
If your phone supports the method, symmetric key encryption with phone public key (PKI encryption), verify that a manufacture-installed certificate (MIC) or locally significant certificate (LSC) exists in the phone.
•
Configuration Tips for Encrypted
Configuration Files, page 11-4
•
•
•
Configuring Manual Key Distribution, page 11-6
Manual Key Distribution Configuration
Entering the Symmetric Key on the Phone, page 11-7
•
Verifying That an LSC or MIC Certificate
Using the Certificate Authority Proxy
Enabling Phone Configuration File Encryption
The TFTP server queries the database when it builds the configuration file. If the phone security profile that is applied to the phone has the TFTP encrypted configuration flag set, the TFTP server builds an encrypted configuration file.
To access the TFTP encryption flag, find the appropriate device security profile for the phone, as described in
“Finding a Phone Security Profile” section on page 7-2
. Check the TFTP Encrypted Config check box to enable configuration file encryption.
Additional Information
See the
“Related Topics” section on page 11-10
Configuring Manual Key Distribution
To determine whether your phone supports manual key distribution, see
“Supported Phone Models” section on page 11-4 .
The following procedure assumes that
•
•
•
The phone exists in the Cisco Unified Communications Manager database,
A compatible firmware load exists on the TFTP server, and
You enabled the TFTP Encrypted Config parameter in Cisco Unified Communications Manager
Administration.
Procedure
Step 1
Find the phone, as described in the Cisco Unified Communications Manager Administration Guide.
11-6
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 11 Configuring Encrypted Phone Configuration Files
Manual Key Distribution Configuration Settings
Step 2
Step 3
Step 4
After the Phone Configuration window displays, configure the manual key distribution settings that are
described in Table 11-2 . After you have configured the settings, you should not change the key.
Click Save.
Enter the symmetric key on the phone and then reset the phone. For information on how to perform these tasks, refer to the phone administration guide that supports your phone model.
Additional Information
See the
“Related Topics” section on page 11-10
.
Manual Key Distribution Configuration Settings
describes the manual distribution configuration settings in the Phone Configuration window.
•
•
For configuration tips, see the
.
“Configuration Tips for Encrypted Configuration Files” section on
For related information and procedures, see the “Related Topics” section on page 11-10
.
Table 11-2 Manual Key Distribution Configuration Settings
Setting
Symmetric Key
Description
Enter a string of hexadecimal characters that you want to use for the symmetric key. Valid characters include numerals, 0-9, and uppercase /lowercase characters, A-F (or a-f).
Make sure that you enter the correct bits for the key size; otherwise,
Cisco Unified Communications Manager rejects the value. Cisco Unified
Communications Manager supports the following key sizes:
Generate String
•
•
Cisco Unified IP Phones 7905G and 7912G (SIP only)—256 bits
Cisco Unified IP Phones 7940G and 7960G (SIP only)—128 bits
After the key is configured, you should not change it.
If you want Cisco Unified Communications Manager Administration to generate a hexadecimal string for you, click the Generate String button.
After the key is configured, you should not change it.
Revert to Database Value If you want to restore the value that exists in the database, click this button.
Entering the Symmetric Key on the Phone
Follow this procedure to enter the symmetric key on the phone after you configure manual key distribution in Cisco Unified Communications Manager Administration.
Procedure
Step 1
Press the Settings button on the phone.
OL-24964-01
Cisco Unified Communications Manager Security Guide
11-7
Chapter 11 Configuring Encrypted Phone Configuration Files
Verifying That an LSC or MIC Certificate Is Installed
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
If the configuration is locked, scroll down the Settings menu, highlight Unlock Phone and press the
Select softkey. Enter the phone password and press the Accept softkey.
The phone accepts the password.
Scroll down the Settings menu, highlight Security Configuration, and press the Select softkey.
In the Security Configuration menu, highlight the Set Cfg Encrypt Key option and press the Select softkey.
When prompted for the encryption key, enter the key (in hex). If you need to clear the key, enter 32 zero digits.
After you have finished entering the key, press the Accept softkey.
The phone accepts the encryption key.
Reset the phone.
After the phone resets, the phone requests encrypted configuration files.
Verifying That an LSC or MIC Certificate Is Installed
This procedure applies to Cisco Unified IP Phones that use PKI encryption. To determine whether your phone supports the method, symmetric key encryption with phone public key (PKI encryption), see the
“Supported Phone Models” section on page 11-4
.
The following procedure assumes that the phone exists in the Cisco Unified Communications Manager database and that you enabled the TFTP Encrypted Config parameter in Cisco Unified Communications
Manager Administration.
Procedure
Step 1
Verify that a manufacture-installed certificate (MIC) or a locally significant certificate (LSC) exists in the phone.
Step 2
Step 3
Step 4
Tip
By choosing the Troubleshooting option in the CAPF settings section of the Phone
Configuration window, you can verify that an LSC or MIC exists in the phone in Cisco Unified
Communications Manager Administration. The Delete and Troubleshoot options do not display if a certificate does not exist in the phone.
You can also verify that an LSC or MIC exists in the phone by checking the security configuration at the phone. Refer to the Cisco Unified IP Phone administration guides for Cisco
Unified IP Phones that support this version of Cisco Unified Communications Manager for more information.
If a certificate does not exist, install an LSC by using the CAPF functionality in the Phone Configuration window. For information on how to install a LSC, see the
“Using the Certificate Authority Proxy
Function” section on page 10-1 .
After you configure the CAPF settings, click Save.
In the Phone Configuration window, click Reset. The phone requests an encrypted configuration file from the TFTP server after the phone resets
11-8
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 11 Configuring Encrypted Phone Configuration Files
Additional Information
See the
“Related Topics” section on page 11-10
.
Verifying That the Phone Configuration File Is Encrypted
Verifying That the Phone Configuration File Is Encrypted
When the phone configuration file is encrypted, it uses the following format:
•
Cisco Unified IP Phones 7905G and 7912G (SIP only)—LD <MAC>.x
•
•
Cisco Unified IP Phones 7940G and 796G (SIP only)—SIP<MAC>.cnf.enc.sgn
Cisco Unified IP Phones 7911G, 7931G (SCCP only), 7941G, 7941G-GE, 7942G, 7945G, 7961G,
7961G-GE, 7962G,7965G, 7970G, 7971G, 7971G-GE, and 7975G—SEP<MAC>.cnf.xml.enc.sgn
To access the configuration file at the phone, refer to the Cisco Unified IP Phone administration guides for Cisco Unified IP Phones that support encryption and this Cisco Unified Communications Manager release for more information.
Disabling Encryption for the Phone Configuration Files
To disable encryption for the phone configuration files, you must uncheck the TFTP Encrypted Config check box in the phone security profile in Cisco Unified Communications Manager Administration and save your change.
Warning
If digest authentication is True for the phone that is running SIP when the TFTP encrypted configuration setting is False, digest credentials may get sent in the clear.
After you update the setting, the encryption keys for the phone remain in the Cisco Unified
Communications Manager database.
Cisco Unified IP Phones 7911G, 7931G (SCCP only), 7941G, 7941G-GE, 7942G, 7945G, 7961G,
7961G-GE, 7962G, 7965G, 7970G, 7971G, 7971G-GE, and 7975G request an encrypted file (.enc.sgn file) when the encrypted configuration setting gets updated to false, the phone requests an unencrypted, signed file (.sgn file).
If Cisco Unified IP Phones 7940G/7960G/7905G/7912G (SIP only) request an encrypted file when the encryption configuration setting gets updated to False, administrators must remove the symmetric key from the phone GUI so the phone requests an unencrypted configuration file the next time that it is reset.
Tip
For Cisco Unified IP Phones 7940G and 7960G (SIP only), enter a 32-byte 0 as the key value for the symmetric key at the phone GUI to disable encryption. For Cisco Unified IP Phones 7905G and 7912G
(SIP only), delete the symmetric key at the phone GUI to disable encryption. For information on how to perform these tasks, refer to the phone administration guide that supports your phone model.
OL-24964-01
Cisco Unified Communications Manager Security Guide
11-9
Chapter 11 Configuring Encrypted Phone Configuration Files
Excluding Digest Credentials from Phone Configuration File Download
Excluding Digest Credentials from Phone Configuration File
Download
To exclude digest credentials from the configuration file that is sent to phones after the initial configuration, check the TFTP Exclude Digest Credentials in Configuration File check box for the security profile that is applied to the phone. Only Cisco Unified IP Phones 7905G, 7912G, 7940G, and
7960G (SIP only) support this option.
You may need to uncheck this check box to update the configuration file for changes to digest credentials. See the
“Configuration Tips for Encrypted Configuration Files” section on page 11-4
for more information.
Additional Information
See the
“Related Topics” section on page 11-10 .
Where to Find More Information
Related Topics
•
Understanding Encryption of the Phone Configuration File, page 11-1
•
•
•
•
•
•
•
•
•
•
•
•
•
Supported Phone Models, page 11-4
Configuration Tips for Encrypted Configuration Files, page 11-4
Encryption Configuration File Configuration Checklist, page 11-5
Enabling Phone Configuration File Encryption, page 11-6
Configuring Manual Key Distribution, page 11-6
Manual Key Distribution Configuration Settings, page 11-7
Entering the Symmetric Key on the Phone, page 11-7
Verifying That an LSC or MIC Certificate Is Installed, page 11-8
Verifying That the Phone Configuration File Is Encrypted, page 11-9
Disabling Encryption for the Phone Configuration Files, page 11-9
Excluding Digest Credentials from Phone Configuration File Download, page 11-10
Using the Certificate Authority Proxy Function, page 10-1
Configuration Tips for Phone Security Profiles, page 7-2
Related Cisco documentation
•
Cisco Unified Communications Manager Bulk Administration Guide
•
Cisco Unified IP Phone administration guide for the phone model and protocol
11-10
Cisco Unified Communications Manager Security Guide
OL-24964-01
C H A P T E R
12
Configuring Digest Authentication for the SIP
Phone
When you enable digest authentication for a phone, Cisco Unified Communications Manager challenges all requests except keepalive messages for phones that are running SIP. Cisco Unified Communications
Manager uses the digest credentials for the end user, as configured in the End User Configuration window, to validate the credentials that the phone offers.
If the phone supports extension mobility, Cisco Unified Communications Manager uses the digest credentials for the extension mobility end user, as configured in the End User Configuration window, when the extension mobility user logs in.
For additional information on how digest authentication works for phones that are running SIP, see the
“Digest Authentication” section on page 1-19 .
For information about configuring digest authentication for non-Cisco phones that are running SIP, refer to Appendix C in the Cisco Unified Communications Manager Administration Guide.
This chapter contains information on the following topics:
•
•
•
•
•
•
SIP Phone Digest Authentication Configuration Checklist, page 12-1
Configuring Digest Authentication Service Parameters, page 12-2
Configuring Digest Credentials in the End User Configuration Window, page 12-3
End User Digest Credential Configuration Settings, page 12-3
Configuring the Digest User in the Phone Configuration Window, page 12-4
Where to Find More Information, page 12-4
SIP Phone Digest Authentication Configuration Checklist
describes the tasks to configure digest authentication for phones that are running SIP.
Table 12-1 SIP Phone Digest Authentication Configuration Checklist
Configuration Steps
Step 1
Configure the security profiles for phones that are running SIP; make sure that you check the Enable Digest Authentication check box.
Related Procedures and Topics
Configuring a Phone Security Profile, page 7-1
Cisco Unified Communications Manager Security Guide
12-1 OL-24964-01
Chapter 12 Configuring Digest Authentication for the SIP Phone
Configuring Digest Authentication Service Parameters
Table 12-1 SIP Phone Digest Authentication Configuration Checklist (continued)
Configuration Steps
Step 2
Step 3
Step 4
Step 5
Step 6
Apply a security profile to the phone that is running SIP.
Related Procedures and Topics
Configuring a Phone Security Profile, page 7-1
If you want to update the default setting, configure service parameters that are related to digest authentication; for example, configure the SIP Station Realm service parameter.
Configuring Digest Authentication Service
Configure the digest credentials in the End User Configuration window.
•
•
Configuring Digest Credentials in the
End User Configuration Window, page 12-3
Configuration Settings, page 12-3
Choose the Digest User in the Phone Configuration window.
Choosing a digest user for these phones that are running SIP ensures that the digest credentials get included in the phone configuration file: Cisco Unified IP Phones 7970G, 7971G,
7971G-GE,7975G, 7961G, 7961G-GE,7962G, 7965G, 7945G,
7941G, 7941G-GE, 7942G, 7945G, and 7911G.
On Cisco Unified IP Phones 7940G or 7960G (SIP only), enter the digest credentials that you configured in the End User
Configuration window.
Configuring the Digest User in the Phone
Configuration Window, page 12-4
For information on how to enter the authentication name and password on the phone, refer to the Cisco Unified IP Phone
Administrator Guide that supports this version of Cisco Unified Communications
Manager.
Configuring Digest Authentication Service Parameters
You configure the SIP Realm for challenges to phones with the service parameter SIP Station Realm. At installation, Cisco Unified Communications Manager provides a default setting, ccmsipline. For additional information on the parameter, click the question mark or the parameter name link that displays in the Service Parameter Configuration window.
To update digest authentication service parameters, for example, the SIP Realm Station parameter, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
In Cisco Unified Communications Manager Administration, choose System > Service Parameters.
From the Server drop-down list box, choose a node where you activated the Cisco CallManager service.
From the Service drop-down list box, choose the Cisco CallManager service. Verify that the word
“Active” displays next to the service name.
Update the SIP Realm Station parameter, as described in the help. To display help for the parameter, click the question mark or the parameter name link.
Click Save.
12-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 12 Configuring Digest Authentication for the SIP Phone
Configuring Digest Credentials in the End User Configuration Window
Additional Information
See the
“Related Topics” section on page 12-4 .
Configuring Digest Credentials in the End User Configuration
Window
The following procedure assumes that the end user exists in the Cisco Unified Communications Manager database. To configure digest credentials for the end user, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
Find the end user, as described in the Cisco Unified Communications Manager Administration Guide.
After the specific End User Configuration window displays, enter the appropriate settings, as described in
.
Click Save.
To configure digest credentials for additional end users, repeat the procedure.
Next Steps
After you configure digest credentials in the End User Configuration window, choose the digest user for the phone by accessing the Phone Configuration window.
After you choose the digest user, enter the digest authentication credentials that you get from the End
User Configuration window on the Cisco Unified IP Phone 7960G or 7940G (SIP only).
Additional Information
See the
“Related Topics” section on page 12-4 .
End User Digest Credential Configuration Settings
describes the settings for the digest credential settings in the End User Configuration window in Cisco Unified Communications Manager Administration. For related procedures, see the
“Configuring the Digest User in the Phone Configuration Window” section on page 12-4
.
Table 12-2 Digest Credentials
Setting
Digest Credentials
Description
Enter a string of alphanumeric characters.
Confirm Digest Credentials To confirm that you entered the digest credentials correctly, enter the credentials in this field.
OL-24964-01
Cisco Unified Communications Manager Security Guide
12-3
Chapter 12 Configuring Digest Authentication for the SIP Phone
Configuring the Digest User in the Phone Configuration Window
Configuring the Digest User in the Phone Configuration Window
To associate a digest user with a phone, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
Find the phone, as described in the Cisco Unified Communications Manager Administration Guide.
After the specific Phone Configuration window displays, locate the Digest User setting and choose the end user that you want to associate with the phone.
Click Save.
Click Reset.
After you associate the end user with the phone, save the configuration and reset the phone.
Additional Information
See the
“Related Topics” section on page 12-4
.
Where to Find More Information
Related Topics
•
Digest Authentication, page 1-19
•
Configuring a Phone Security Profile, page 7-1
•
•
•
•
•
SIP Phone Digest Authentication Configuration Checklist, page 12-1
Configuring Digest Authentication Service Parameters, page 12-2
Configuring Digest Credentials in the End User Configuration Window, page 12-3
End User Digest Credential Configuration Settings, page 12-3
Configuring the Digest User in the Phone Configuration Window, page 12-4
Related Cisco Documentation
Cisco SIP IP Phone Administrator Guide
12-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
C H A P T E R
13
Phone Hardening
To tighten security on the phone, you can perform phone hardening tasks in the Phone Configuration window in Cisco Unified Communications Manager Administration. This chapter contains information on the following topics:
•
Disabling Gratuitous ARP, page 13-1
•
•
•
•
•
•
Disabling Web Access, page 13-1
Disabling the PC Voice VLAN Access Setting, page 13-2
Disabling the Setting Access Setting, page 13-2
Disabling the PC Port Setting, page 13-2
Configuring Phone Hardening, page 13-2
Where to Find More Information, page 13-3
Disabling Gratuitous ARP
By default, Cisco Unified IP Phones accept Gratuitous ARP packets. Gratuitous ARP packets, which devices use, announce the presence of the device on the network. However, attackers can use these packets to spoof a valid network device; for example, an attacker could send out a packet that claims to be the default router. If you choose to do so, you can disable Gratuitous ARP in the Phone Configuration window.
Note
Disabling this functionality does not prevent the phone from identifying its default router.
Disabling Web Access
Disabling the web server functionality for the phone blocks access to the phone internal web pages, which provide statistics and configuration information. Features, such as Cisco Quality Report Tool, do not function properly without access to the phone web pages. Disabling the web server also affects any serviceability application, such as CiscoWorks, that relies on web access.
To determine whether the web services are disabled, the phone parses a parameter in the configuration file that indicates whether the services are disabled or enabled. If the web services are disabled, the phone does not open the HTTP port 80 for monitoring purposes and blocks access to the phone internal web pages.
OL-24964-01
Cisco Unified Communications Manager Security Guide
13-1
Chapter 13 Phone Hardening
Disabling the PC Voice VLAN Access Setting
Disabling the PC Voice VLAN Access Setting
By default,Cisco Unified IP Phones forward all packets that are received on the switch port (the one that faces the upstream switch) to the PC port. If you choose to disable the PC Voice VLAN Access setting in the Phone Configuration window, packets that are received from the PC port that use voice VLAN functionality will drop. Various Cisco Unified IP Phones use this functionality differently.
•
Cisco Unified IP Phones 7940G and 7960G drop any packets that are tagged with the voice VLAN, in or out of the PC port.
•
•
Cisco Unified IP Phone 7970G drops any packet that contains an 802.1Q tag on any VLAN, in or out of the PC port.
Cisco Unified IP Phone 7912G cannot perform this functionality.
Disabling the Setting Access Setting
By default, pressing the Settings button on a Cisco Unified IP Phone provides access to a variety of information, including phone configuration information. Disabling the Setting Access setting in the
Phone Configuration window prohibits access to all options that normally display when you press the
Settings button on the phone; for example, the Contrast, Ring Type, Network Configuration, Model
Information, and Status settings.
The preceding settings do not display on the phone if you disable the setting in Cisco Unified
Communications Manager Administration. If you disable this setting, the phone user cannot save the settings that are associated with the Volume button; for example, the user cannot save the volume.
Disabling this setting automatically saves the current Contrast, Ring Type, Network Configuration,
Model Information, Status, and Volume settings that exist on the phone. To change these phone settings, you must enable the Setting Access setting in Cisco Unified Communications Manager Administration.
Disabling the PC Port Setting
By default, Cisco Unified Communications Manager enables the PC port on all Cisco Unified IP Phones that have a PC port. If you choose to do so, you can disable the PC Port setting in the Phone
Configuration window. Disabling the PC port proves useful for lobby or conference room phones.
Configuring Phone Hardening
Caution
The following procedure disables functionality for the phone.
To disable functionality for the phone, perform the following procedure:
Procedure
Step 1
Step 2
In Cisco Unified Communications Manager Administration, choose Device > Phone.
Specify the criteria to find the phone and click Find or click Find to display a list of all phones.
13-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 13 Phone Hardening
Where to Find More Information
Step 3
Step 4
To open the Phone Configuration window for the device, click the device name.
Locate the following product-specific parameters:
•
PC Port
•
•
•
•
Settings Access
Gratuitous ARP
PC Voice VLAN Access
Web Access
Step 5
Step 6
Step 7
Tip
To review information on these settings, click the question mark that displays next to the parameters in the Phone Configuration window.
From the drop-down list box for each parameter that you want to disable, choose Disabled. To disable the speakerphone or speakerphone and headset, check the corresponding check boxes.
Click Save.
Click Reset.
Additional Information
See the
“Related Topics” section on page 13-3 .
Where to Find More Information
Related Topics
•
Disabling Gratuitous ARP, page 13-1
•
•
•
•
•
Disabling Web Access, page 13-1
Disabling the PC Voice VLAN Access Setting, page 13-2
Disabling the Setting Access Setting, page 13-2
Disabling the PC Port Setting, page 13-2
Configuring Phone Hardening, page 13-2
Related Cisco Documentation
Cisco Unified IP Phone Administration Guide for Cisco Unified Communications Manager
OL-24964-01
Cisco Unified Communications Manager Security Guide
13-3
Where to Find More Information
Chapter 13 Phone Hardening
13-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
C H A P T E R
14
Configuring Secure Conference Resources
This chapter contains information on the following topics:
•
Secure Conference Overview, page 14-1
•
•
•
•
•
•
•
•
•
•
•
Conference Bridge Requirements, page 14-2
Secure Conference Icons, page 14-3
Maintaining a Secure Conference, page 14-3
Cisco Unified IP Phone Support, page 14-5
Secure Conference over Trunks and Gateways, page 14-6
Interactions and Restrictions, page 14-6
Configuration Tips for Securing Conference Resources, page 14-8
Secure Conference Bridge Configuration Checklist, page 14-9
•
•
•
Configuring a Minimum Security Level for Meet-Me Conferences, page 14-11
Configuring Packet Capturing for a Secure Conference Bridge, page 14-12
Where to Find More Information, page 14-12
Secure Conference Overview
The Secure Conferencing feature provides authentication and encryption to secure a conference. A conference gets considered secure when all participating devices have encrypted signaling and media.
The secure conference feature supports SRTP encryption over a secure TLS or IPSec connection.
The system provides a security icon for the overall security status of the conference, which is determined by the lowest security level of the participating devices. For example, a secure conference that includes two encrypted connections and one authenticated connection has a conference security status of authenticated.
Cisco Unified Communications Manager Security Guide
14-1 OL-24964-01
Chapter 14 Configuring Secure Conference Resources
Conference Bridge Requirements
To configure secure ad hoc and meet-me conferences, you configure a secure conference bridge.
•
•
If a user initiates a conference call from a phone that is authenticated or encrypted, Cisco Unified
Communications Manager allocates the secure conference bridge
If a user initiates a call from a phone that is nonsecure, Cisco Unified Communications Manager allocates a nonsecure conference bridge.
When you configure conference bridge resources as nonsecure, the conference remains nonsecure, regardless of the security configuration for the phone.
Note
Cisco Unified Communications Manager allocates a conference bridge from the Media Resource Group
List (MRGL) for the phone that is initiating the conference. If a secure conference bridge is not available,
Cisco Unified Communications Manager assigns a nonsecure conference bridge, and the conference is nonsecure. Likewise, if a nonsecure conference bridge is not available, Cisco Unified Communications
Manager assigns a secure conference bridge, and the conference is nonsecure. If no conference bridge is available, the call will fail.
For meet-me conference calls, the phone that initiates the conference must also meet the minimum security requirement that is configured for the meet-me number. If no secure conference bridge is available or if the initiator security level does not meet the minimum, Cisco Unified Communications
Manager rejects the conference attempt. See
“Meet-Me Conference with Minimum Security Level” section on page 14-5 for more information
To secure conferences with barge, configure phones to use encrypted mode. After the Barge key is pressed and if the device is authenticated or encrypted, Cisco Unified Communications Manager establishes a secure connection between the barging party and the built-in bridge at the target device.
The system provides a conference security status for all connected parties in the barge call.
Note
Nonsecure or authenticated Cisco Unified IP Phones that are running release 8.3 or later can now barge encrypted calls.
Conference Bridge Requirements
A conference bridge can register as a secure media resource when you add a hardware conference bridge to your network and configure a secure conference bridge in Cisco Unified Communications Manager
Administration.
Note
Due to the performance impact to Cisco Unified Communications Manager processing, Cisco does not support secure conferencing on software conference bridge.
A Digital Signal Processor (DSP) farm, which provides conferencing on a H.323 or MGCP gateway, acts as the network resource for IP telephony conferencing. The conference bridge registers to Cisco Unified
Communications Manager as a secure SCCP client.
•
The conference bridge root certificate must exist in CallManager trust store, and the Cisco Unified
Communications Manager certificate must exist in the conference bridge trust store.
•
The secure conference bridge security setting must match the security setting in Cisco Unified
Communications Manager to register.
14-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 14 Configuring Secure Conference Resources
Secure Conference Icons
For more information about conferencing routers, refer to the IOS router documentation that is provided with your router.
Cisco Unified Communications Manager assigns conference resources to calls on a dynamic basis. The available conference resource and the enabled codec provide the maximum number of concurrent, secure conferences allowed per router. Because transmit and receive streams are individually keyed for each participating endpoint (so no rekeying is necessary when a participant leaves the conference), the total secure conference capacity for a DSP module equals one-half the nonsecure capacity that you can configure.
See “Understanding Conference Devices” in the Cisco Unified Communications Manager System Guide for more information.
Secure Conference Icons
Cisco Unified IP Phones display a conference security icon for the security level of the entire conference.
These icons match the status icons for a secure two-party call, as described in the user documentation for your phone.
The audio and video portions of the call provide the basis for the conference security level. The call gets considered secure only if both the audio and video portions are secure.
For ad hoc and meet-me secure conferences, the security icon for the conference displays next to the conference softkey in the phone window for conference participants. The icon that displays depends on the security level of the conference bridge and all participants:
•
•
A lock icon displays if the conference bridge is secure and all participants in the conference are encrypted.
A shield icon displays if the conference bridge is secure and all participants in the conference are authenticated. Some phone models do not display the shield icon.
•
When the conference bridge or any participant in the conference is nonsecure, the call state icon
(active, hold, and so on) displays, or, on some older phone models, no icon displays.
When an encrypted phone connects to a secure conference bridge, the media streaming between the device and the conference bridge gets encrypted; however, the icon for the conference can be encrypted, authenticated, or nonsecure depending on the security levels of the other participants. A nonsecure status indicates that one of the parties is not secure or cannot be verified.
When a user presses Barge, the icon that displays next to the Barge softkey provides the security level for the barge conference. If the barging device and the barged device support encryption, the system encrypts the media between the two devices, but the barge conference status can be nonsecure, authenticated, or encrypted, depending on the security levels of the connected parties.
Maintaining a Secure Conference
Conference status can change as participants enter and leave the conference. An encrypted conference can revert to a security level of authenticated or nonsecure if an authenticated or nonsecure participant connects to the call. Likewise, the status can upgrade if an authenticated or nonsecure participant drops off the call. A nonsecure participant that connects to a conference call renders the conference nonsecure.
Conference status can also change when participants chain conferences together, when the security status for a chained conference changes, when a held conference call is resumed on another device, when a conference call gets barged, or when a transferred conference call completes to another device.
OL-24964-01
Cisco Unified Communications Manager Security Guide
14-3
Chapter 14 Configuring Secure Conference Resources
Maintaining a Secure Conference
Note
The Advanced Ad Hoc Conference Enabled service parameter determines whether ad hoc conferences can be linked together by using features such as conference, join, direct transfer, and transfer.
Cisco Unified Communications Manager provides these options to maintain a secure conference:
•
•
Conference List for Ad Hoc Conferences, page 14-4
Meet-Me Conference with Minimum Security Level, page 14-5
Conference List for Ad Hoc Conferences
A conference list displays on participating phones when the ConfList softkey is pressed during a conference call. The conference list provides the conference status as well as the security status for each participant to identify participants that are not encrypted.
Conference list displays these security icons: nonsecure, authenticated, encrypted, held. The conference initiator can use the conference list to eject participants with a low security status.
Note
The Advanced Ad Hoc Conference Enabled service parameter determines whether conference participants other than the conference initiator can eject conference participants.
As participants join the conference, they get added to the top of the conference list. To remove nonsecure participants from a secure conference with the ConfList and RmLstC softkeys, refer to the user documentation for your phone.
The following sections describe secure ad hoc conference interactions with other features.
Secure Ad Hoc Conference and Conference Chaining
When an ad hoc conference is chained to another ad hoc conference, the chained conference displays in the list as member “Conference” with its own security status. Cisco Unified Communications Manager includes the security level for the chained conference to determine the overall conference security status.
Secure Ad hoc Conference and cBarge
When a user presses the cBarge softkey to join an active conference, Cisco Unified Communications
Manager creates an ad hoc conference and allocates a conference bridge according to the security level and MRGL of the barged device. The cbarge member names display in the conference list.
Secure Ad Hoc Conference and Barge
If a participant in a secure ad hoc conference gets barged, the barge call security status shows in the conference list next to the barge target. The security icon for the barge target may show authenticated when, in fact, the media is encrypted between the barge target and the conference bridge, because the barge caller has an authenticated connection.
If the barge target is secure but in an unsecured ad hoc conference, if the ad hoc conference status later changes to secure, the barge caller icon will update as well.
Secure Ad Hoc Conference and Join
Authenticated or encrypted phone users can use the Join softkey at a Cisco Unified IP Phone (only phones that are running SCCP) to create or join a secure ad hoc conference. If a user presses Join to add a participant with an unknown security status to an existing conference, Cisco Unified Communications
14-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 14 Configuring Secure Conference Resources
Cisco Unified IP Phone Support
Manager downgrades the conference status to unknown. A participant who adds a new member with Join becomes the conference initiator and can eject the new member or any other participant from the conference list (if the Advanced Ad Hoc Conference Enabled setting is True).
Secure Ad Hoc Conference and Hold/Resume
When a conference initiator puts the conference call on hold to add a participant, the conference status remains unknown (nonsecure) until the added participant answers the call. After the new participant answers, conference status updates in the conference list.
If a caller on a shared line resumes a held conference call at another phone, the conference list updates when the caller presses Resume.
Meet-Me Conference with Minimum Security Level
As administrator, you can specify a minimum security level for a conference when you configure a meet-me pattern or number as nonsecure, authenticated, or encrypted. Participants must meet the minimum security requirement, or the system blocks the participant and drops the call. This action applies to meet-me conference call transfers, resumed meet-me conference calls on shared lines, and chained Meet-Me conferences.
The phone that initiates the meet-me conference must meet the minimum security level, or the system rejects the attempt. When the minimum security level specifies authenticated or encrypted and a secure conference bridge is not available, the call fails.
If you specify nonsecure as the minimum level for the conference bridge, the conference bridge accepts all calls, and the conference status is nonsecure. See
“Configuring a Minimum Security Level for
Meet-Me Conferences” section on page 14-11
to secure a Meet-Me conference.
The following sections describe secure meet-me conference interactions with other features.
Meet-Me Conference and Ad Hoc Conference
To add a meet-me conference to an ad hoc conference or add an ad hoc conference to a meet-me conference, the ad hoc conference must meet the minimum security level for the meet-me conference, or the call is dropped. The conference icon can change when the conference gets added.
Meet-Me Conference and Barge
Unless a barge caller meets the minimum security requirement when the caller barges a meet-me conference participant, the security level of the barged device downgrades, and both the barge caller and the barged call get dropped.
Meet-Me Conference and Hold/Resume
A phone on a shared line cannot resume a meet-me conference unless the phone meets the minimum security level. If a phone does not meet the minimum security level, all phones on the shared line get blocked when the user presses Resume.
Cisco Unified IP Phone Support
These Cisco Unified IP Phones support secure conference and secure conference icons:
•
Cisco Unified IP Phones 7940G and 7960G (SCCP only, authenticated secure conference only)
•
Cisco Unified IP Phones 7906G, 7911G, and 7931G (SCCP only)
OL-24964-01
Cisco Unified Communications Manager Security Guide
14-5
CTI Support
Chapter 14 Configuring Secure Conference Resources
•
Cisco Unified IP Phones 7941G, 7941G-GE, 7942G, 7945G, 7961G,7961G-GE, 7962G, 7965G,
7970G, 7971G, 7971G-GE, and 7975G
Warning
To obtain the full benefit of secure conference features, Cisco recommends upgrading Cisco Unified
IP Phones to release 8.3, which supports the encryption features in this release. Encrypted phones that run earlier releases do not fully support these new features. These phones can only participate in secure conference as authenticated or nonsecure participants.
Cisco Unified IP Phones that are running release 8.3 with an earlier release of Cisco Unified
Communications Manager will display their connection security status, not the conference security status, during a conference call, and do not support secure conference features like conference list.
See
“Restrictions” section on page 14-7 for more restrictions that apply to Cisco Unified IP Phones.
For additional information about secure conference calls and security icons, refer to your phone user guide and the Cisco Unified IP Phone Administration Guide for Cisco Unified Communications
Manager that supports this Cisco Unified Communications Manager release.
CTI Support
Cisco Unified Communications Manager supports secure conference over licensed CTI devices. Refer to the Cisco Unified Communications Manager JTAPI Developers Guide and Cisco Unified
Communications Manager TAPI Developers Guide for this release for more information.
Secure Conference over Trunks and Gateways
Cisco Unified Communications Manager supports secure conference over intracluster trunks (ICTs),
H.323 trunks/gateways, and MGCP gateways; however, encrypted phones that are running release 8.2 or earlier will revert to RTP for ICT and H.323 calls, and the media does not get encrypted.
If a conference involves a SIP trunk, the secure conference status is nonsecure. In addition, SIP trunk signaling does not support secure conference notifications to off-cluster participants.
CDR Data
CDR data provides the security status of each call leg from the phone endpoint to the conference bridge as well as the security status of the conference itself. The two values use two different fields inside the
CDR database.
CDR data provides termination cause code 58 (Bearer capability not presently available) when a meet-me conference rejects a join attempt that does not meet the minimum security level requirement.
See the CDR Analysis and Reporting Administration Guide for more information.
Interactions and Restrictions
This section contains information on the following topics:
•
14-6
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 14 Configuring Secure Conference Resources
Interactions and Restrictions
•
Interactions
This section describes Cisco Unified Communications Manager interactions with the secure conference feature.
•
To keep a conference secure, if a participant in a secure ad hoc conference puts a call on hold or parks the call, the system does not play MOH, even if the Suppress MOH to Conference Bridge service parameter is set to False. The secure conference status does not change.
•
•
In intercluster environments, if an off-cluster conference participant presses hold in a secure ad hoc conference, the media stream to the device stops, MOH plays, and the media status changes to unknown. If the off-cluster participant resumes a held call with MOH, the conference status may upgrade.
A secure MeetMe call across an intercluster trunk (ICT) will clear if the remote user invokes a phone feature such a hold/resume, which changes the media status to unknown.
•
•
•
•
•
•
•
•
Annunciator tones or announcements for Cisco Unified Communications Manager Multilevel
Precedence and Preemption that play on a participant phone during a secure ad hoc conference change the conference status to nonsecure.
If a caller barges a secure SCCP phone call, the system uses an internal tone-playing mechanism at the target device, and the conference status remains secure.
If a caller barges a secure SIP phone call, the system provides tone-on-hold, and the conference status remains nonsecure during the tone.
If a conference is secure and RSVP is enabled, the conference remains secure.
For conference calls that involve the PSTN, the security conference icon shows the security status for only the IP domain portion of the call.
The Maximum Call Duration Timer service parameter also controls the maximum conference duration.
Conference bridge supports packet capture. During a packet capture session, the phone displays a nonsecure status for the conference, even if the media stream is encrypted.
The media security policy that is configured for your system may alter secure conference behavior; for example, an endpoint will use media security according to the system media security policy, even when participating in a conference call with endpoints that do no support media security.
Restrictions
This section describes Cisco Unified Communications Manager restrictions with secure conferencing feature.
•
Encrypted Cisco Unified IP Phones that are running release 8.2 or earlier can only participate in a secure conference as authenticated or nonsecure participants.
•
•
Cisco Unified IP Phones that are running release 8.3 with an earlier release of Cisco Unified
Communications Manager will display their connection security status, not the conference security status, during a conference call and do not support secure conference features like conference list.
Cisco Unified IP Phones 7905G and 7911G do not support conference list.
OL-24964-01
Cisco Unified Communications Manager Security Guide
14-7
Chapter 14 Configuring Secure Conference Resources
Configuration Tips for Securing Conference Resources
•
•
•
•
•
Due to bandwidth requirements, Cisco Unified IP Phones 7940G and 7960G do not support barge from an encrypted device on an active encrypted call. The barge attempt will fail.
Cisco Unified IP Phone 7931G does not support conference chaining.
Phones that are calling over SIP trunks get treated as nonsecure phones, regardless of their device security status.
If a secure phone attempts to join a secure meet-me conference over a SIP trunk, the call gets dropped.
Because SIP trunks do not support providing the “device not authorized” message to a phone that is running SIP, the phone does not update with this message. In addition, 7960G phones that are running
SIP do not support the “device not authorized” message.
In intercluster environments, the conference list does not display for off-cluster participants; however, the security status for the connection displays next to the Conference softkey as long as the connection between the clusters supports it. For example, for H.323 ICT connections, the authentication icon does not display (the system treats the authenticated connection as nonsecure), but the encryption icon displays for an encrypted connection.
Off-cluster participants can create their own conference that connects to another cluster across the cluster boundary. The system treats the connected conferences as a basic, two-party call.
Configuration Tips for Securing Conference Resources
Consider the following information before you configure secure conference bridge resources:
•
•
•
Use localization if you want the phone to display custom text for secure conference messages. Refer to the Cisco Unified Communications Manager Locale Installer documentation for more information.
The conference or built-in bridge must support encryption to secure conference calls.
•
To enable secure conference bridge registration, set the cluster security mode to mixed mode.
Ensure the phone that initiates a conference is authenticated or encrypted to procure a secure conference bridge.
•
•
•
•
•
To maintain conference integrity on shared lines, do not configure devices that share a line with different security modes; for example, do not configure an encrypted phone to share a line with an authenticated or nonsecure phone.
Do not use SIP trunks as ICTs when you want to share conference security status between clusters.
If you set the cluster security mode to mixed mode, the security mode that is configured for the DSP farm (nonsecure or encrypted) must match the conference bridge security mode in Cisco Unified
Communications Manager Administration, or the conference bridge cannot register. The conference bridge registers as encrypted when both security modes specify encrypted; the conference bridge registers as nonsecure when both security modes specify nonsecure.
If you set the cluster security mode to mixed mode, if the security profile you applied to the conference bridge is encrypted, but the conference bridge security level is nonsecure, Cisco Unified
Communications Manager rejects conference bridge registration.
If you set the cluster security mode to nonsecure mode, configure the security mode at the DSP farm as nonsecure, so the conference bridge can register. The conference bridge registers as nonsecure even if the setting in Cisco Unified Communications Manager Administration specifies encrypted.
14-8
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 14 Configuring Secure Conference Resources
Secure Conference Bridge Configuration Checklist
•
•
•
•
During registration, the conference bridge must pass authentication. To pass authentication, the DSP farm must contain the Cisco Unified Communications Manager certificate, and Cisco Unified
Communications Manager must contain certificates for the DSP farm system and the DSP connection. To ensure the conference bridge passes authentication, the X509 certification name must contain the conference bridge name.
If conference bridge certificates expire or change for any reason, use the certificate management feature in Cisco Unified Communications Operating System Administration to update the certificates in the trusted store. The TLS authentication fails when certificates do not match, and conference bridge does not work because it cannot register to Cisco Unified Communications
Manager.
The secure conference bridge registers to Cisco Unified Communications Manager through TLS connection at port 2443; a nonsecure conference bridge registers to Cisco Unified Communications
Manager through TCP connection at port 2000.
Changing the device security mode for the conference bridge requires a reset of Cisco Unified
Communications Manager devices and a restart of the Cisco CallManager service.
Secure Conference Bridge Configuration Checklist
Use
as a reference to add secure conferencing to your network.
Table 14-1 Configuration Checklist for Configuring Secure Conference Bridge
Configuration Steps
Step 1
Verify that you installed and configured the Cisco CTL Client for Mixed Mode.
Step 2
Related Procedures and Topics
Configuring the Cisco CTL Client, page 4-1
Verify that you configured the DSP farm security settings for
Cisco Unified Communications Manager connection, including adding the Cisco Unified Communications Manager certificate to the trust store. Set the DSP farm security level to encrypted.
Refer to the documentation for your conference bridge.
Step 3
Tip
The DSP farm establishes the TLS port connection to
Cisco Unified Communications Manager on port 2443.
Verify the DSP farm certificate is in the CallManager trust store.
•
To add the certificate, use the certificate management function in the Cisco Unified Communications Operating System to copy the DSP certificate to the trusted store in Cisco Unified
Communications Manager.
•
When you have finished copying the certificate, restart the
Cisco CallManager service on the server.
Tip
Be sure to copy the certificate to each server in the cluster and restart the Cisco CallManager service on each server in the cluster.
Cisco Unified Communications Manager
Administration Guide
Cisco Unified Serviceability
Administration Guide
OL-24964-01
Cisco Unified Communications Manager Security Guide
14-9
Chapter 14 Configuring Secure Conference Resources
Configuring Secure Conference Bridge in Cisco Unified Communications Manager Administration
Table 14-1 Configuration Checklist for Configuring Secure Conference Bridge (continued)
Configuration Steps
Step 4
In Cisco Unified Communications Manager Administration, configure Cisco IOS Enhanced Conference Bridge as the conference bridge type and select Encrypted Conference Bridge for device security mode.
Tip
Related Procedures and Topics
•
•
Configuration Tips for Securing
Conference Resources, page 14-8
Configuring Secure Conference Bridge in
Cisco Unified Communications Manager
When you upgrade to this release, Cisco Unified
Communications Manager automatically assigns a nonsecure conference bridge security profile to Cisco
IOS Enhanced Conference Bridge configurations.
Step 5
Configure a minimum security level for Meet-Me Conferences.
Tip
When you upgrade to this release, Cisco Unified
Communications Manager automatically assigns a minimum security level of nonsecure to all Meet Me patterns.
Configuring a Minimum Security Level for
Meet-Me Conferences, page 14-11
Step 6
(Optional) Configure packet capturing for the secure conference bridge.
Configuring Packet Capturing for a Secure
Tip
Set packet capture mode to batch mode and capture tier to SRTP.
Troubleshooting Guide for Cisco Unified
Communications Manager
Configuring Secure Conference Bridge in Cisco Unified
Communications Manager Administration
To configure a secure conference bridge in Cisco Unified Communications Manager Administration, perform the following procedure. After you configure encryption for the conference bridge, you must reset Cisco Unified Communications Manager devices and restart the Cisco CallManager service.
Before You Begin
Ensure that you installed certificates in Cisco Unified Communications Manager and in the DSP farm to secure the connection between the devices.
Procedure
Step 1
Step 2
Step 3
Choose Media Resources> Conference Bridge.
In the Find and List Conference Bridges window, verify that a Cisco IOS Enhanced Conference Bridge is installed and go to
If the device does not exist in the database, click Add New; go to
In the Conference Bridge Configuration window, select Cisco IOS Enhanced Conference Bridge in the Conference Bridge Type drop-down list box. Configure the Conference Bridge Name, Description,
Device Pool, Common Device Configuration, and Location settings as described in the Cisco Unified
Communications Manager Administration Guide.
14-10
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 14 Configuring Secure Conference Resources
Configuring a Minimum Security Level for Meet-Me Conferences
Step 4
Step 5
Step 6
In the Device Security Mode field, select Encrypted Conference Bridge.
Click Save.
Click Reset.
Next Steps
To perform additional conference bridge configuration tasks, you can jump to the Meet-Me
Number/Pattern Configuration window or the Service Parameter Configuration window by selecting the option from the Related Links drop-down list box and clicking Go.
Additional Information
See the
“Related Topics” section on page 14-12
.
Configuring a Minimum Security Level for Meet-Me
Conferences
To configure a minimum security level for Meet-Me conferences, perform the following procedure.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Choose Call Routing> Meet-Me Number/Pattern.
In the Find and List Conference Bridges window, verify that the Meet-Me number/pattern is configured and go to
.
If the Meet-Me number/pattern is not configured, click Add New; go to
In the Meet-Me Number Configuration window, enter a Meet-Me number or range in the Directory
Number or Pattern field. Configure the Description and Partition settings as described in the Cisco
Unified Communications Manager Administration Guide.
In the Minimum Security Level field, select Non Secure, Authenticated, or Encrypted.
Click Save.
Next Steps
If you have not yet installed a secure conference bridge, install and configure a secure conference bridge, as described in
“Configuring Secure Conference Bridge in Cisco Unified Communications Manager
Administration” section on page 14-10
.
Additional Information
See the
“Related Topics” section on page 14-12
.
OL-24964-01
Cisco Unified Communications Manager Security Guide
14-11
Chapter 14 Configuring Secure Conference Resources
Configuring Packet Capturing for a Secure Conference Bridge
Configuring Packet Capturing for a Secure Conference Bridge
To configure packet capturing for a secure conference bridge, enable packet capturing in the Service
Parameter Configuration window; then, set the packet capture mode to batch mode and capture tier to
SRTP for the phone, gateway, or trunk in the device configuration window. Refer to the Troubleshooting
Guide for Cisco Unified Communications Manager for more information.
During a packet capture session, the phone displays a nonsecure status for the conference, even if the media stream is encrypted.
Where to Find More Information
•
•
•
•
•
•
Related Topics
•
Interactions and Restrictions, page 1-7
•
•
•
Configuration Checklist Overview, page 1-25
Secure Conference Overview, page 14-1
Conference Bridge Requirements
Secure Conference Icons, page 14-3
•
•
Maintaining a Secure Conference, page 14-3
Cisco Unified IP Phone Support, page 14-5
Secure Conference over Trunks and Gateways, page 14-6
•
•
•
•
•
Interactions and Restrictions, page 14-6
Configuration Tips for Securing Conference Resources, page 14-8
Secure Conference Bridge Configuration Checklist, page 14-9
Configuring a Minimum Security Level for Meet-Me Conferences, page 14-11
Configuring Packet Capturing for a Secure Conference Bridge, page 14-12
Related Cisco Documentation
•
Conference Bridges, Cisco Unified Communications Manager System Guide
•
Cisco DSP Resources for Transcoding, Conferencing, and MTP, Cisco Unified Communications
Manager System Guide
•
•
•
•
Conference Bridge Configuration, Cisco Unified Communications Manager Administration Guide
Meet-Me Number/Pattern Configuration, Cisco Unified Communications Manager Administration
Guide
Cisco Unified Communications Operating System Administration Guide
Troubleshooting Guide for Cisco Unified Communications Manager
14-12
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 14 Configuring Secure Conference Resources
Where to Find More Information
•
•
•
CDR Analysis and Reporting Administration Guide
Cisco Unified IP Phone Administration Guide for Cisco Unified Communications Manager
Cisco IP Phone User Documentation and release notes for this release of Cisco Unified
Communications Manager and your Cisco Unified IP Phone
OL-24964-01
Cisco Unified Communications Manager Security Guide
14-13
Where to Find More Information
Chapter 14 Configuring Secure Conference Resources
14-14
Cisco Unified Communications Manager Security Guide
OL-24964-01
C H A P T E R
15
Configuring Voice-Messaging Ports for Security
This chapter contains information on the following topics:
•
Voice-Messaging Security Overview, page 15-1
•
•
•
•
•
Configuration Tips for Voice-Messaging Security, page 15-2
Secure Voice-Messaging Port Configuration Checklist, page 15-2
Applying a Security Profile to a Single Voice-Messaging Port, page 15-3
Applying the Security Profile in the Voice Mail Port Wizard, page 15-4
Where to Find More Information, page 15-5
Voice-Messaging Security Overview
To configure security for Cisco Unified Communications Manager voice-messaging ports and
Cisco Unity devices that are running SCCP or Cisco Unity Connection devices that are running SCCP, you choose a secure device security mode for the port. If you choose an authenticated voice mail port, a
TLS connection opens, which authenticates the devices by using a mutual certificate exchange (each device accepts the certificate of the other device). If you choose encrypted voice mail port, the system first authenticates the devices and then sends encrypted voice streams between the devices.
•
For Cisco Unity or Cisco Unity Connection 1.2 or earlier, the Cisco Unity Unified CM TSP connects to Cisco Unified Communications Manager through the TLS port when the device security mode equals authenticated or encrypted. When the device security mode equals nonsecure, the Cisco
Unity Unified CM TSP connects to Cisco Unified Communications Manager through the SCCP port.
•
Cisco Unity Connection 2.0 or later connects to Cisco Unified Communications Manager through the TLS port. When the device security mode equals nonsecure, Cisco Unity Connection connects to Cisco Unified Communications Manager through the SCCP port.
Note
In this chapter, the use of the term “server” refers to a Cisco Unified Communications Manager server.
The use of the phrase “voice-mail server” refers to a Cisco Unity server or to a Cisco Unity Connection server.
Cisco Unified Communications Manager Security Guide
15-1 OL-24964-01
Chapter 15 Configuring Voice-Messaging Ports for Security
Configuration Tips for Voice-Messaging Security
Configuration Tips for Voice-Messaging Security
Consider the following information before you configure security:
•
You must run Cisco Unity 4.0(5) or later with this version of Cisco Unified Communications
Manager.
•
•
You must run Cisco Unity Connection 1.2 or later with this version of Cisco Unified
Communications Manager.
For Cisco Unity, you must perform security tasks by using the Cisco Unity Telephony Integration
Manager (UTIM); for Cisco Unity Connection, you must perform security tasks by using
Cisco Unity Connection Administration. For information on how to perform these tasks, refer to the applicable Cisco Unified Communications Manager integration guide for Cisco Unity or for
Cisco Unity Connection.
•
•
•
•
In addition to the procedures that are described in this chapter, you must use the certificate management feature in Cisco Unified Communications Operating System to save the Cisco Unity certificate to the trusted store. For more information on this task, refer to the Cisco Unified
Communications Operating System Administration Guide.
After you copy the certificate, you must restart the Cisco CallManager service on each Cisco
Unified Communications Manager server in the cluster.
If Cisco Unity certificates expire or change for any reason, use the certificate management feature in the Cisco Unified Communications Operating System Administration Guide to update the certificates in the trusted store. The TLS authentication fails when certificates do not match, and voice messaging does not work because it cannot register to Cisco Unified Communications
Manager.
When configuring voice-mail server ports, you must select a device security mode.
The setting that you specify in the Cisco Unity Telephony Integration Manager (UTIM) or in
Cisco Unity Connection Administration must match the voice-messaging port device security mode that is configured in Cisco Unified Communications Manager Administration. In Cisco Unity
Connection Administration, you apply the device security mode to the voice-messaging port in the
Voice Mail Port Configuration window (or in the Voice Mail Port Wizard).
Tip
If the device security mode settings do not match, the voice-mail server ports fail to register with
Cisco Unified Communications Manager, and the voice-mail server cannot accept calls on those ports.
•
•
Changing the security profile for the port requires a reset of Cisco Unified Communications
Manager devices and a restart of the voice-mail server software. If you apply a security profile in
Cisco Unified Communications Manager Administration that uses a different device security mode than the previous profile, you must change the setting on the voice-mail server.
You cannot change the Device Security Mode for existing voice-mail servers through the Voice Mail
Port Wizard. If you add ports to an existing voice-mail server, the device security mode that is currently configured for the profile automatically applies to the new ports.
Secure Voice-Messaging Port Configuration Checklist
Use
Table 15-1 as a reference when you configure security for voice-messaging ports.
15-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 15 Configuring Voice-Messaging Ports for Security
Applying a Security Profile to a Single Voice-Messaging Port
Table 15-1 Configuration Checklist for Securing Voice-Messaging Ports
Configuration Steps
Step 1
Verify that you installed and configured the Cisco CTL Client for Mixed Mode.
Step 2
Step 3
Related Procedures and Topics
Configuring the Cisco CTL Client, page 4-1
Verify that you configured the phones for authentication or encryption.
Phone Security Overview, page 6-1
Use the certificate management feature in Cisco Unified
Communications Operating System Administration to copy the
Cisco Unity certificate to the trusted store on the Cisco Unified
Communications Manager server; then restart the
Cisco CallManager service.
•
Configuring a Phone Security Profile, page 7-1
•
Configuration Tips for Voice-Messaging
Cisco Unified Communications
Operating System Administration Guide
Tip
Activate the Cisco CTL Provider service on each Cisco
Unified Communications Manager server in the cluster; then restart the Cisco CallManager service on all servers.
•
Cisco Unified Serviceability
Administration Guide
Step 4
Step 5
Step 6
In Cisco Unified Communications Manager Administration, configure the device security mode for the voice-messaging ports.
•
•
Applying a Security Profile to a Single
Voice-Messaging Port, page 15-3
Applying the Security Profile in the Voice
Perform security-related configuration tasks for Cisco Unity or
Cisco Unity Connection voice-messaging ports; for example, configure Cisco Unity to point to the Cisco TFTP server.
Cisco Unified Communications Manager
Integration Guide for Cisco Unity or for
Cisco Unity Connection
Reset the devices in Cisco Unified Communications Manager
Administration and restart the Cisco Unity software.
•
•
Cisco Unified Communications Manager
Integration Guide for Cisco Unity or for
Cisco Unity Connection
Applying a Security Profile to a Single
Voice-Messaging Port, page 15-3
Applying a Security Profile to a Single Voice-Messaging Port
To apply a security profile to a single voice-messaging port, perform the following procedure.
This procedure assumes that you added the device to the database and installed a certificate in the phone, if a certificate does not already exist. After you apply a security profile for the first time or if you change the security profile, you must reset the device.
Before you apply a security profile, review the following sections:
•
Voice-Messaging Security Overview, page 15-1
•
•
Configuration Tips for Voice-Messaging Security, page 15-2
Secure Voice-Messaging Port Configuration Checklist, page 15-2
OL-24964-01
Cisco Unified Communications Manager Security Guide
15-3
Chapter 15 Configuring Voice-Messaging Ports for Security
Applying the Security Profile in the Voice Mail Port Wizard
Procedure
Step 1
Step 2
Step 3
Step 4
Find the voice-messaging port, as described in the Cisco Unified Communications Manager
Administration Guide.
After the configuration window for the port displays, locate the Device Security Mode setting. From the drop-down list box, choose the security mode that you want to apply to the port. The database predefines these options. The default value specifies Not Selected.
Click Save.
Click Reset.
Additional Information
See the
“Related Topics” section on page 15-5
.
Applying the Security Profile in the Voice Mail Port Wizard
To change the security setting for an existing voice-mail server, see the
“Applying a Security Profile to a Single Voice-Messaging Port” section on page 15-3 .
Before you apply a security profile, review the following sections:
•
Voice-Messaging Security Overview, page 15-1
•
•
Configuration Tips for Voice-Messaging Security, page 15-2
Secure Voice-Messaging Port Configuration Checklist, page 15-2
To apply the Device Security Mode setting in the Voice Mail Port Wizard for a new voice-mail server, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Cisco Unified Communications Manager Administration, choose Voice Mail > Voice Mail Port
Wizard.
Enter the name of the voice-mail server; click Next.
Choose the number of ports that you want to add; click Next.
In the Device Information window, choose a Device Security Mode from the drop-down list box. The database predefines these options. The default value specifies Not Selected.
Configure the other device settings, as described in the Cisco Unified Communications Manager
Administration Guide. Click Next.
Continue the configuration process, as described in the Cisco Unified Communications Manager
Administration Guide. When the Summary window displays, click Finish.
Additional Information
See the
“Related Topics” section on page 15-5
.
15-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 15 Configuring Voice-Messaging Ports for Security
Where to Find More Information
Where to Find More Information
Related Topics
•
•
Interactions and Restrictions, page 1-7
•
•
•
•
Configuration Checklist Overview, page 1-25
Voice-Messaging Security Overview, page 15-1
Configuration Tips for Voice-Messaging Security, page 15-2
•
•
Applying a Security Profile to a Single Voice-Messaging Port, page 15-3
Applying the Security Profile in the Voice Mail Port Wizard, page 15-4
Related Cisco Documentation
•
Cisco Unified Communications Manager Integration Guide for Cisco Unity or Cisco Unity
Connection for this Cisco Unified Communications Manager release
•
Cisco Unified Communications Operating System Administration Guide
OL-24964-01
Cisco Unified Communications Manager Security Guide
15-5
Where to Find More Information
Chapter 15 Configuring Voice-Messaging Ports for Security
15-6
Cisco Unified Communications Manager Security Guide
OL-24964-01
C H A P T E R
16
Configuring Secure Call Monitoring and
Recording
This chapter contains information on the following topics:
•
•
Secure Call Monitoring and Recording Overview, page 16-1
Configuring Secure Call Monitoring and Recording, page 16-2
Secure Call Monitoring and Recording Overview
Secure calls can be monitored and recorded, as described in this section:
•
•
A supervisor can establish a secured monitoring session for a secured or a non-secured call.
The call security of the original call is never impacted or downgraded as a result of a call monitoring request.
•
•
The monitoring call is allowed to proceed only when it can be established and maintained at the same security level as the device capability of the agent.
The original call between the agent and customer must have different crypto keys than that of monitoring call. In a monitoring session, the system encrypts the mixed voices of the agent and customer with the new key first before sending to the supervisor.
Note
The system does not support secure recording on authenticated phones.
Cisco Unified Communications Manager Security Guide
16-1 OL-24964-01
Chapter 16 Configuring Secure Call Monitoring and Recording
Configuring Secure Call Monitoring and Recording
Configuring Secure Call Monitoring and Recording
To configure Secure Call Monitoring and Recording, use the following procedure:
Table 16-1 Configuring Secure Call Monitoring and Recording
Step 1
Step 2
Step 3
Step
Provision secure capability on agent and supervisor phones.
Create a secure SIP trunk with the following configuration:
•
Set the Device Security Mode to Encrypted.
Notes
See the
Phone Security Configuration Checklist, page 6-5
in the
Cisco Unified Communications Manager Security Guide.
For more information, see the
“Configuring the SIP Trunk Security
Profile” chapter in the Cisco Unified Communications Manager
Security Guide.
•
•
Check the Transmit Security
Status check box.
Check the Allow SRTP check box.
•
Configure the TLS SIP trunk to the recorder.
Configure monitoring and recording, in the same way you would for non-secure monitoring and recording:
•
•
Configure a built-in bridge for the agent phone.
Configure the Call Recording option (enable Automatic
Application) using the DN page on the agent phone.
For more information and detailed procedures, see the
“Monitoring and Recording” chapter in the Cisco Unified
Communications Manager Features and Services Guide.
•
•
•
Create a route pattern for the recorder.
Add a call recording profile to the DN.
Provision monitoring and recording tones as needed.
16-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
P
A R T
3
Virtual Private Networks for Cisco Unified
IP Phones
C H A P T E R
17
Configuring Virtual Private Networks
Note
The VPN menu and its options are not available in the U.S. export unrestricted version of Cisco Unified
Communications Manager.
The Cisco VPN Client for Cisco Unified IP Phones adds another option for customers attempting to solve the remote telecommuter problem by complementing other Cisco remote telecommuting offerings.
•
•
Easy to Deploy—All settings configured via CUCM administration.
Easy to Use—After configuring the phone within the Enterprise, the user can take it home and plug it into their broadband router for instant connectivity, without any difficult menus to configure.
•
•
Easy to Manage—Phone can receive firmware updates and configuration changes remotely.
Secure—VPN tunnel only applies to voice and Cisco Unified IP Phone services. A PC connected to the PC port is responsible for authenticating and establishing it own tunnel with VPN client software.
Supported Devices
You can use Cisco Unified Reporting to determine which Cisco Unified IP Phones support the VPN client. From Cisco Unified Reporting, click Unified CM Phone Feature List. For the Feature, choose
Virtual Private Network Client from the pull-down menu. The system displays a list of products that support the feature.
For more information about using Cisco Unified Reporting, see the Cisco Unified Reporting
Administration Guide.
Configuring the VPN Feature
To configure the VPN feature for supported Cisco Unified IP Phones, follow the steps in the following table.
Cisco Unified Communications Manager Security Guide
17-1 OL-24964-01
Chapter 17 Configuring Virtual Private Networks
Configuring the VPN Feature
Table 17-1 VPN Configuration Checklist
Configuration Steps
Step 1
Set up the VPN concentrators for each VPN Gateway.
Notes and Related Procedures
For configuration information, refer to the documentation for the
VPN concentrator; such the following:
•
Note
SSL VPN Client (SVC) on ASA with ASDM Configuration
Example
http://www.cisco.com/en/US/products/ps6120/products_conf iguration_example09186a008071c428.shtml
The ASA software must be version 8.0.4 or later, and the
“AnyConnect Cisco VPN Phone” license must be installed.
Step 2
Note
To avoid long delays when the user upgrades the firmware or configuration information on a remote phone, Cisco recommends that you set up the VPN concentrator close in the network to the TFTP or Cisco Unified
Communications Manager server. If this is not feasible in your network, you can set up an alternate TPTP or load server that is next to the VPN concentrator.
•
Note
SSL VPN Client (WebVPN) on IOS with SDM Configuration
Example
http://www.cisco.com/en/US/products/ps6496/products_conf iguration_example09186a008072aa61.shtml
The IOS software must be versions 15.1(2)T or later.
Feature Set/License:" Universal (Data & Security & UC)" for the 2900 models and “Advanced Security” for the 2800 models with SSL VPN licenses activated.
Note
To avoid long delays when the user upgrades the firmware or configuration information on a remote phone, Cisco recommends that you set up the VPN concentrator close in the network to the TFTP or Cisco Unified
Communications Manager server. If this is not feasible in your network, you can set up an alternate TPTP or load server that is next to the VPN concentrator.
Chapter 18, “Configuring a VPN Gateway”
Step 3
Step 4
Step 5
Upload the VPN concentrator certificates.
Configure the VPN Gateways.
Create a VPN Group using the
VPN Gateways.
Configure the VPN Profile
Chapter 18, “Configuring a VPN Gateway”
Chapter 19, “Configuring a VPN Group”
Chapter 20, “Configuring a VPN Profile”
17-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 17 Configuring Virtual Private Networks
IOS configuration requirements
Table 17-1 VPN Configuration Checklist
Configuration Steps
Step 6
Step 7
Step 8
Add the VPN Group and VPN
Profile to a Common Phone
Profile.
Notes and Related Procedures
In Cisco Unified Communications Manager Administration, choose Device > Device Settings > Common Phone Profile. For more information, see the “Common Phone Profile Configuration” chapter in the Cisco Unified Communications Manager
Administration Guide.
Upgrade the firmware for Cisco
Unified IP Phones to a version that supports VPN.
Note
If you do not associate a VPN Profile with the Common
Phone Profile, VPN uses the default settings defined in the
VPN Feature Configuration window.
To run the Cisco VPN client, a supported Cisco Unified IP Phone must be running firmware release 9.0(2) or higher. For more information about upgrading firmware, see the Cisco Unified IP
Phone Administration Guide for Cisco Unified Communications
Manager for your Cisco Unified IP Phone model.
Using a supported Cisco Unified
IP Phone, establish a VPN connection.
Note
Before you can upgrade to firmware release 9.0(2), supported Cisco Unified IP Phones must be running firmware release 8.4(4) or later.
For more information about configuring a Cisco Unified IP Phone and establishing a VPN connection, see the Cisco Unified IP
Phone Administration Guide for Cisco Unified Communications
Manager for your Cisco Unified IP Phone model.
IOS configuration requirements
Before you create an ISO configuration for VPN client on IP phone, complete the following steps:
Step 1
Step 2
Install IOS Software version 15.1(2)T or later
Feature Set/License: Universal (Data & Security & UC) for IOS ISR-G2
Feature Set/License: Advanced Security for IOS ISR
Activate the SSL VPN License
Configuring IOS for VPN client on IP phone
Perform the following steps to configure IOS for VPN client on IP phone.
Step 1
Configure IOS locally.
a.
Configure the Network Interface
Example: router(config)# interface GigabitEthernet0/0 router(config-if)# description "outside interface" router(config-if)# ip address 10.1.1.1 255.255.255.0
OL-24964-01
Cisco Unified Communications Manager Security Guide
17-3
Chapter 17 Configuring Virtual Private Networks
Configuring IOS for VPN client on IP phone
Step 2 b.
b.
router(config-if)# duplex auto router(config-if)# speed auto router(config-if)# no shutdown router#show ip interface brief (shows interfaces summary)
Configure static and default routes.
router(config)# ip route <dest_ip> < mask> < gateway_ip>
Example: router(config)# ip route 10.10.10.0 255.255.255.0 192.168.1.1
Generate and register the necessary certificates for Cisco Unified Communications Manager and IOS.
The following certificates need to be imported from the Cisco Unified Communications Manager.
•
•
•
CallManager - Authenticating the Cisco UCM during TLS handshake (Only required for mixed-mode clusters)
Cisco_Manufacturing_CA - Authenticating IP phones with a Manufacturer Installed Certificate
(MIC).
CAPF - Authenticating IP phones with an LSC.
To import these Cisco Unified Communications Manager certificates
a.
From the Cisco Unified Communications Manager OS Administration web page.
Choose Security > Certificate Management. (Note: This location may change based on the UCM version)
c.
d.
Find the certificates Cisco_Manufacturing_CA and CAPF. Download the .pem file and save as .txt file
Create trustpoint on the IOS
e.
•
•
Example: hostname(config)# crypto pki trustpoint trustpoint_name hostname(config-ca-trustpoint)# enrollment terminal hostname(config)# crypto pki authenticate trustpoint
When prompted for base 64 encoded CA Certificate, copy-paste the text in the downloaded
.pem file along with the BEGIN and END lines. Repeat the procedure for the other certificates
You should generate the following IOS self-signed certificates and register them with Cisco Unified
Communications Manager, or replace with a certificate that you import from a CA.
Generate a self-signed certificate.
Example:
Router> enable
Router# configure terminal
Router(config)# crypto key generate rsa general-keys label <name> <exportable
-optional>
Router(config)# crypto pki trustpoint <name>
Router(ca-trustpoint)# enrollment selfsigned
Router(ca-trustpoint)# rsakeypair <name> 1024 1024
Router(ca-trustpoint)#authorization username subjectname commonname
Router(ca-trustpoint)# crypto pki enroll <name>
Router(ca-trustpoint)# end
Generate a self-signed certificate with Host-id check enabled on the VPN profile in Cisco Unified
Communications Manager.
Example:
Router> enable
Router# configure terminal
17-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 17 Configuring Virtual Private Networks
Sample IOS configuration summary
Step 3
Step 4
•
Router(config)# crypto key generate rsa general-keys label <name> <exportable
-optional>
Router(config)# crypto pki trustpoint <name>
Router(ca-trustpoint)# enrollment selfsigned
Router(config-ca-trustpoint)# fqdn <full domain name>
Router(config-ca-trustpoint)# subject-name CN=<full domain name>, CN=<IP>
Router(ca-trustpoint)#authorization username subjectname commonname
Router(ca-trustpoint)# crypto pki enroll <name>
Router(ca-trustpoint)# end
Register the generated certificate with Cisco Unified Communications Manager.
Example:
Router(config)#
crypto pki export <name> pem terminal
Copy the text from the terminal and save it as a .pem file and upload it to the Managing
Certificate part of the CUCM.
Install Anyconnect on IOS.
Download anyconnect package from cisco.com and install to flash
Example: router(config)#webvpn install svc flash:/webvpn/anyconnect-win-2.3.2016-k9.pkg
Configure the VPN feature. You can use the Sample IOS configuration summary bellow to guide you with the configuration.
Note
To use the phone with both certificate and password authentication, create a user with the phone MAC address. Username matching is case sensitive. For example: username CP-7975G-SEP001AE2BC16CB password k1kLGQIoxyCO4ti9 encrypted
Sample IOS configuration summary
You can use the following sample IOS configuration for VPN client on IP phone as a general guideline to creating your own configurations. The configuration entries can change over time.
Current configuration: 4648 bytes
!
! Last configuration change at 13:48:28 CDT Fri Mar 19 2010 by test
!
version 15.2
service timestamps debug datetime localtime show-timezone service timestamps log datetime localtime show-timezone no service password-encryption
!
! hostname of the IOS hostname vpnios
!
boot-start-marker
! Specifying the image to be used by IOS – boot image boot system flash c2800nm-advsecurityk9-mz.152-1.4.T
boot-end-marker
!
!
logging buffered 21474836
!
OL-24964-01
Cisco Unified Communications Manager Security Guide
17-5
Sample IOS configuration summary
aaa new-model
!
!
aaa authentication login default local
aaa authentication login webvpn local
aaa authorization exec default local
!
aaa session-id common
!
clock timezone CST -6
clock summer-time CDT recurring
!
crypto pki token default removal timeout 0
!
! Define trustpoints
crypto pki trustpoint iosrcdnvpn-cert
enrollment selfsigned
serial-number
subject-name cn=iosrcdnvpn-cert
revocation-check none
rsakeypair iosrcdnvpn-key 1024
!
crypto pki trustpoint CiscoMfgCert
enrollment terminal
revocation-check none
authorization username subjectname commonname
!
crypto pki trustpoint CiscoRootCA
enrollment terminal
revocation-check crl
authorization username subjectname commonname
!
!
! Certificates
crypto pki certificate chain iosrcdnvpn-cert
certificate self-signed 04
crypto pki certificate chain CiscoMfgCert
certificate ca 6A6967B3000000000003
crypto pki certificate chain CiscoRootCA
certificate ca 5FF87B282B54DC8D42A315B568C9ADFF
crypto pki certificate chain test
certificate ca 00
dot11 syslog
ip source-route
!
!
ip cef
!
!
!
ip domain name nw048b.cisco.com
no ipv6 cef
!
multilink bundle-name authenticated
!
!
voice-card 0
!
!
!
license udi pid CISCO2821 sn FTX1344AH76
archive
log config
Chapter 17 Configuring Virtual Private Networks
Cisco Unified Communications Manager Security Guide
17-6 OL-24964-01
Chapter 17 Configuring Virtual Private Networks
Sample IOS configuration summary
hidekeys
username admin privilege 15 password 0 vpnios
username test privilege 15 password 0 adgjm
username usr+ privilege 15 password 0 adgjm
username usr# privilege 15 password 0 adgjm
username test2 privilege 15 password 0 adg+jm
username CP-7962G-SEP001B0CDB38FE privilege 15 password 0 adgjm
!
redundancy
!
!
!--- Configure interface. Generally one interface to internal network and one outside
interface GigabitEthernet0/0
description "outside interface"
ip address 10.89.79.140 255.255.255.240
duplex auto
speed auto
!
interface GigabitEthernet0/1
description "Inside Interface"
ip address dhcp
duplex auto
speed auto
!
!--- Define IP local address pool
ip local pool webvpn-pool 10.8.40.200 10.8.40.225
ip default-gateway 10.89.79.129
ip forward-protocol nd
ip http server
ip http authentication local
ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
!
!
!--- Define static IP routes ip route 0.0.0.0 0.0.0.0 10.89.79.129
ip route 10.89.0.0 255.255.0.0 10.8.40.1
!
no logging trap
access-list 23 permit 10.10.10.0 0.0.0.7
!
control-plane
!
line con 0
exec-timeout 15 0
line aux 0
! telnet access
line vty 0 4
exec-timeout 30 0
privilege level 15
password vpnios
transport input telnet
line vty 5 15
access-class 23 in
privilege level 15
transport input all
!
exception data-corruption buffer truncate
scheduler allocate 20000 1000
!
! webvpn gateway configuration
webvpn gateway VPN_RCDN_IOS
hostname vpnios
Cisco Unified Communications Manager Security Guide
OL-24964-01 17-7
Chapter 17 Configuring Virtual Private Networks
Sample IOS configuration summary
ip address 10.89.79.140 port 443
! ssl configuration
ssl encryption aes128-sha1
ssl trustpoint iosrcdnvpn-cert
inservice
!
! webvpn context for User and Password authentication
webvpn context UserPasswordContext
title "User-Password authentication"
ssl authenticate verify all
!
!
policy group UserPasswordGroup
functions svc-enabled
hide-url-bar
timeout idle 3600
svc address-pool "webvpn-pool"
svc default-domain "nw048b.cisco.com"
svc split include 10.89.75.0 255.255.255.0
svc dns-server primary 64.101.128.56
svc dtls
default-group-policy UserPasswordGroup
gateway VPN_RCDN_IOS domain UserPasswordVPN
inservice
!
!
! webvpn context for Certificate (username pre-filled) and Password authentication
webvpn context CertPasswordContext
title "certificate plus password"
ssl authenticate verify all
!
!
policy group CertPasswordGroup
functions svc-enabled
hide-url-bar
timeout idle 3600
svc address-pool "webvpn-pool"
svc default-domain "nw048b.cisco.com"
svc dns-server primary 64.101.128.56
svc dtls
default-group-policy CertPasswordGroup
gateway VPN_RCDN_IOS domain CertPasswordVPN
authentication certificate aaa
username-prefill
ca trustpoint CiscoMfgCert
inservice
!
!
! webvpn context for certificate only authentication
webvpn context CertOnlyContext
title "Certificate only authentication"
ssl authenticate verify all
!
!
policy group CertOnlyGroup
functions svc-enabled
hide-url-bar
timeout idle 3600
svc address-pool "webvpn-pool"
svc default-domain "nw048b.cisco.com"
svc dns-server primary 64.101.128.56
svc dtls
default-group-policy CertOnlyGroup
gateway VPN_RCDN_IOS domain CertOnlyVPN
Cisco Unified Communications Manager Security Guide
17-8 OL-24964-01
Chapter 17 Configuring Virtual Private Networks
ASA configuration requirements
authentication certificate
ca trustpoint CiscoMfgCert
inservice
!
end
ASA configuration requirements
Before you create an ASA configuration for VPN client on IP phone, complete the following steps:
Step 1
Step 2
Step 3
Install ASA software (version 8.0.4 or later) and compatible ASDM
Install a compatible anyconnect package
Activate License
a.
Show features of the current license.
show activation-key detail b.
For a new license with additional SSL VPN sessions and Linksys phone enabled, visit http://www.cisco.com/go/license . Select “Any Connect Cisco VPN phone” license to support the
VPN feature.
Configuring ASA for VPN client on IP phone
Perform the following steps to configure ASA for VPN client on IP phone.
Step 1
Step 2
Local configuration
a.
Configure network interface.
Example:
b.
c.
router(config)# interface GigabitEthernet0/0 router(config-if)# description "outside interface" router(config-if)# ip address 10.1.1.1 255.255.255.0 router(config-if)# duplex auto router(config-if)# speed auto router(config-if)# no shutdown router#show ip interface brief (shows interfaces summary)
Configure static routes and default routes.
router(config)# ip route <dest_ip> <mask> <gateway_ip>
Example: router(config)# ip route 10.10.10.0 255.255.255.0 192.168.1.1
Configure the DNS.
Example: hostname(config)# dns domain-lookup inside hostname(config)# dns server-group DefaultDNS hostname(config-dns-server-group)# name-server 10.1.1.5 192.168.1.67 209.165.201.6
Generate and register the necessary certificates for Cisco Unified Communications Manager and IOS.
The following certificates need to be imported from the Cisco Unified Communications Manager.
OL-24964-01
Cisco Unified Communications Manager Security Guide
17-9
Chapter 17 Configuring Virtual Private Networks
Configuring ASA for VPN client on IP phone
•
•
•
CallManager - Authenticating the Cisco UCM during TLS handshake (Only required for mixed-mode clusters)
Cisco_Manufacturing_CA - Authenticating IP phones with a Manufacturer Installed Certificate
(MIC).
CAPF - Authenticating IP phones with an LSC.
To import these Cisco Unified Communications Manager certificates
From the Cisco Unified Communications Manager OS Administration web page.
a.
b.
c.
Choose Security > Certificate Management. (Note: This location may change based on the UCM version)
Find the certificates Cisco_Manufacturing_CA and CAPF. Download the .pem file and save as .txt file
d.
e.
•
•
•
Create trustpoint on the IOS
Example: hostname(config)# crypto pki trustpoint trustpoint_name hostname(config-ca-trustpoint)# enrollment terminal hostname(config)# crypto pki authenticate trustpoint
When prompted for base 64 encoded CA Certificate, copy-paste the text in the downloaded
.pem file along with the BEGIN and END lines. Repeat the procedure for the other certificates
You should generate the following IOS self-signed certificates and register them with Cisco Unified
Communications Manager, or replace with a certificate that you import from a CA.
Generate a self-signed certificate.
Example:
Router> enable
Router# configure terminal
Router(config)# crypto key generate rsa general-keys label <name> <exportable
-optional>
Router(config)# crypto pki trustpoint <name>
Router(ca-trustpoint)# enrollment selfsigned
Router(ca-trustpoint)# rsakeypair <name> 1024 1024
Router(ca-trustpoint)#authorization username subjectname commonname
Router(ca-trustpoint)# crypto pki enroll <name>
Router(ca-trustpoint)# end
Generate a self-signed certificate with Host-id check enabled on the VPN profile in Cisco Unified
Communications Manager.
Example:
Router> enable
Router# configure terminal
Router(config)# crypto key generate rsa general-keys label <name> <exportable
-optional>
Router(config)# crypto pki trustpoint <name>
Router(ca-trustpoint)# enrollment selfsigned
Router(config-ca-trustpoint)# fqdn <full domain name>
Router(config-ca-trustpoint)# subject-name CN=<full domain name>, CN=<IP>
Router(ca-trustpoint)#authorization username subjectname commonname
Router(ca-trustpoint)# crypto pki enroll <name>
Router(ca-trustpoint)# end
Register the generated certificate with Cisco Unified Communications Manager.
Example:
Router(config)#
crypto pki export <name> pem terminal
17-10
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 17 Configuring Virtual Private Networks
Sample ASA configuration summary
Step 3
Copy the text from the terminal and save it as a .pem file and upload it to the Managing
Certificate part of the CUCM.
Configure the VPN feature. You can use the Sample IOS configuration summary bellow to guide you with the configuration.
Note
To use the phone with both certificate and password authentication, create a user with the phone MAC address. Username matching is case sensitive. For example: username CP-7975G-SEP001AE2BC16CB password k1kLGQIoxyCO4ti9 encrypted username CP-7975G-SEP001AE2BC16CB attributes vpn-group-policy GroupPhoneWebvpn service-type remote-access
Sample ASA configuration summary
You can use the following sample ASA configuration for VPN client on IP phone as a general guideline to creating your own configurations. The configuration entries can change over time.
ciscoasa(config)# show running-config
: Saved
:
!--- ASA version
ASA Version 8.2(1)
!
!--- Basic local config on ASA hostname ciscoasa domain-name nw048b.cisco.com
enable password 8Ry2YjIyt7RRXU24 encrypted passwd 2KFQnbNIdI.2KYOU encrypted names dns-guard
!--- Configure interface. Generally one interface to internal network and one outside
!--- Ethernet0/0 is outside interface with security level 0
!
interface Ethernet0/0
nameif outside
security-level 0
ip address 10.89.79.135 255.255.255.0
!--- Ethernet0/1 is inside interface with security level 100
!
interface Ethernet0/1
nameif inside
security-level 100
ip address dhcp
!
interface Ethernet0/2
shutdown
no nameif
no security-level
no ip address
!
interface Ethernet0/3
shutdown
OL-24964-01
Cisco Unified Communications Manager Security Guide
17-11
Chapter 17 Configuring Virtual Private Networks
Sample ASA configuration summary
no nameif
security-level 100
no ip address
!
interface Management0/0
shutdown
nameif management
security-level 100
no ip address
management-only
!
!--- Boot image of ASA boot system disk0:/asa821-k8.bin
ftp mode passive
!--- Clock settings clock timezone CST -6 clock summer-time CDT recurring
!--- DNS configuration dns domain-lookup outside dns server-group DefaultDNS
name-server 64.101.128.56
domain-name nw048b.cisco.com
!--- Enable interface on the same security level so that they can communicate to each other same-security-traffic permit inter-interface
!--- Enable communication between hosts connected to same interface same-security-traffic permit intra-interface pager lines 24
!--- Logging options logging enable logging timestamp logging console debugging no logging message 710005 mtu outside 1500 mtu inside 1500 mtu management 1500
!--- Define IP local address pool ip local pool Webvpn_POOL 10.8.40.150-10.8.40.170 mask 255.255.255.192
no failover icmp unreachable rate-limit 1 burst-size 1 icmp permit any inside
!--- ASDM image asdm image disk0:/asdm-623.bin
no asdm history enable arp timeout 14400
!--- Static routing route outside 0.0.0.0 0.0.0.0 10.89.79.129 1 route inside 10.89.0.0 255.255.0.0 10.8.40.1 1 route inside 0.0.0.0 0.0.0.0 10.8.40.1 tunneled timeout xlate 3:00:00 timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02 timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00 timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00 timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
Cisco Unified Communications Manager Security Guide
17-12 OL-24964-01
Chapter 17 Configuring Virtual Private Networks
Sample ASA configuration summary
timeout tcp-proxy-reassembly 0:01:00 dynamic-access-policy-record DfltAccessPolicy http server enable http 192.168.1.0 255.255.255.0 inside http redirect outside 80 no snmp-server location no snmp-server contact snmp-server enable traps snmp authentication linkup linkdown coldstart crypto ipsec security-association lifetime seconds 28800 crypto ipsec security-association lifetime kilobytes 4608000
!--- ASA certs
!--- trustpoints and certificates crypto ca trustpoint ASA_VPN_Cert
enrollment self
keypair ASA_VPN_Cert_key
crl configure crypto ca trustpoint CiscoMfgCert
enrollment terminal
crl configure crypto ca trustpoint UCM_CAPF_Cert
enrollment terminal
no client-types
crl configure crypto ca certificate chain ASA_VPN_Cert
certificate 02d5054b
quit crypto ca certificate chain CiscoMfgCert
certificate ca 6a6967b3000000000003
quit crypto ca certificate chain UCM_CAPF_Cert
certificate ca 6a6967b3000000000003
quit telnet timeout 5 ssh scopy enable ssh timeout 5 console timeout 0
!--- configure client to send packets with broadcast flag set dhcp-client broadcast-flag
!--- specifies use of mac-addr for client identifier to outside interface dhcp-client client-id interface outside
!
tls-proxy maximum-session 200
!
threat-detection basic-threat threat-detection statistics access-list no threat-detection statistics tcp-intercept
!--- configure ssl ssl encryption aes128-sha1 ssl trust-point ASA_VPN_Cert ssl certificate-authentication interface outside port 443
!--- VPN config
!--- Configure webvpn webvpn
enable outside
default-idle-timeout 3600
svc image disk0:/anyconnect-win-2.1.0148-k9.pkg 1
svc enable
OL-24964-01
Cisco Unified Communications Manager Security Guide
17-13
Chapter 17 Configuring Virtual Private Networks
Sample ASA configuration summary
!--- Group-policy group-policy GroupPhoneWebvpn internal group-policy GroupPhoneWebvpn attributes
banner none
vpn-simultaneous-logins 10
vpn-idle-timeout none
vpn-session-timeout none
vpn-tunnel-protocol IPSec svc webvpn
default-domain value nw048b.cisco.com
address-pools value Webvpn_POOL
webvpn
svc dtls enable
svc keep-installer installed
svc keepalive 120
svc rekey time 4
svc rekey method new-tunnel
svc dpd-interval client none
svc dpd-interval gateway 300
svc compression deflate
svc ask none default webvpn
!--- Configure user attributes username test password S.eA5Qq5kwJqZ3QK encrypted username test attributes
vpn-group-policy GroupPhoneWebvpn
service-type remote-access
!—Configure username with Phone MAC address for certificate+password method username CP-7975G-SEP001AE2BC16CB password k1kLGQIoxyCO4ti9 encrypted username CP-7975G-SEP001AE2BC16CB attributes
vpn-group-policy GroupPhoneWebvpn
service-type remote-access
!--- Configure tunnel group for username-password authentication tunnel-group VPNphone type remote-access tunnel-group VPNphone general-attributes
address-pool Webvpn_POOL
default-group-policy GroupPhoneWebvpn tunnel-group VPNphone webvpn-attributes
group-url https://10.89.79.135/VPNphone enable
!--- Configure tunnel group with certificate only authentication tunnel-group CertOnlyTunnelGroup type remote-access tunnel-group CertOnlyTunnelGroup general-attributes
default-group-policy GroupPhoneWebvpn tunnel-group CertOnlyTunnelGroup webvpn-attributes
authentication certificate
group-url https://10.89.79.135/CertOnly enable
!--- Configure tunnel group with certificate + password authentication tunnel-group CertPassTunnelGroup type remote-access tunnel-group CertPassTunnelGroup general-attributes
authorization-server-group LOCAL
default-group-policy GroupPhoneWebvpn
username-from-certificate CN tunnel-group CertPassTunnelGroup webvpn-attributes
authentication aaa certificate
pre-fill-username ssl-client
group-url https://10.89.79.135/CertPass enable
!
class-map inspection_default
match default-inspection-traffic
!
Cisco Unified Communications Manager Security Guide
17-14 OL-24964-01
Chapter 17 Configuring Virtual Private Networks
!
policy-map type inspect dns preset_dns_map
parameters
message-length maximum 512 policy-map global_policy
class inspection_default
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect esmtp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect xdmcp
inspect sip
inspect netbios
inspect tftp
!
service-policy global_policy global prompt hostname context
Cryptochecksum:cd28d46a4f627ed0fbc82ba7d2fee98e
: end
Sample ASA configuration summary
OL-24964-01
Cisco Unified Communications Manager Security Guide
17-15
Sample ASA configuration summary
Chapter 17 Configuring Virtual Private Networks
17-16
Cisco Unified Communications Manager Security Guide
OL-24964-01
C H A P T E R
18
Configuring a VPN Gateway
Note
The VPN menu and its options are not available in the U.S. export unrestricted version of Cisco Unified
Communications Manager.
To configure a VPN gateway, you must first upload the VPN concentrator certificates and then configure the VPN gateway.
This chapter contains the following sections:
•
Uploading VPN Concentrator Certificates, page 18-1
•
Configuring the VPN Gateway, page 18-2
Uploading VPN Concentrator Certificates
Cisco recommends that you generate a certificate on the ASA when you set it up to support the VPN feature. Download the generated certificate to your PC or workstation and then upload it to Cisco Unified
Communications Manager using the procedure in this section. Cisco Unified Communications Manager saves the certificate in the Phone-VPN-trust list.
The ASA will send this certificate during the SSL handshake and the Cisco Unified IP Phone compares it against the values stored in the Phone-VPN-trust list.
The Cisco Unified IP Phone sends its Manufacturer Installed Certificate (MIC) by default, or if you configure the CAPF service, the Cisco Unified IP Phone sends its Locally Significant Certificate (LSC).
If you want to use device level certificate authentication, then they you need to install the root MIC or
CAPF certificate in the ASA, so that the Cisco Unified IP Phones are trusted.
You upload certificates to Cisco Unified Communications Manager using the Cisco Unified
Communications Operating System. Follow this procedure to upload VPN concentrator certificates:
Procedure
Step 1
Step 2
From Cisco Unified Communications Operating System Administration, choose Security > Certificate
Management.
The Certificate List window displays.
Click Upload Certificate.
The Upload Certificate popup window displays.
OL-24964-01
Cisco Unified Communications Manager Security Guide
18-1
Chapter 18 Configuring a VPN Gateway
Configuring the VPN Gateway
Step 3
Step 4
Step 5
Step 6
From the Certificate Name pull-down menu, choose Phone-VPN-trust.
Click Browse to choose the file you want to upload.
Click Upload File.
Choose another file to upload or click Close.
For more information about certificate management, see Chapter 6, “Security,” in the Cisco Unified
Communications Operating System Administration Guide.
Configuring the VPN Gateway
This section includes the following topics:
•
Finding a VPN Gateway, page 18-2
•
Configuring a VPN Gateway, page 18-3
Finding a VPN Gateway
To find a VPN gateway, perform the following procedure:
Procedure
Step 1
Step 2
In Cisco Unified Communications Manager Administration, choose Advanced Features > VPN > VPN
Gateway.
The Find and List VPN Gateways window displays. Records from an active (prior) query may also display in the window.
To find all records in the database, ensure the dialog box is empty; go to
.
To filter or search records
•
•
•
From the first drop-down list box, choose a search parameter.
From the second drop-down list box, choose a search pattern.
Specify the appropriate search text, if applicable.
Note
To add additional search criteria, click the + button. When you add criteria, the system searches for a record that matches all criteria that you specify. To remove criteria, click the – button to remove the last added criterion or click the Clear Filter button to remove all added search criteria.
Step 3
Step 4
Click Find.
All matching records display. You can change the number of items that display on each page by choosing a different value from the Rows per Page drop-down list box.
From the list of records that display, click the link for the record that you want to view.
18-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 18 Configuring a VPN Gateway
Configuring the VPN Gateway
Note
To reverse the sort order, click the up or down arrow, if available, in the list header.
The window displays the item that you choose.
Configuring a VPN Gateway
To add, update, or copy a VPN Gateway, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
In Cisco Unified Communications Manager Administration, choose Advanced Features > VPN > VPN
Gateway.
Perform one of the following tasks:
•
•
To add a new profile, click Add New in the Find window and continue with
To copy an existing VPN gateway, locate the appropriate profile as described in “Finding a VPN
, click the Copy button next to the VPN gateway that you want to copy, and continue with
•
To update an existing profile, locate the appropriate VPN gateway as described in
and continue with
When you click Add New, the configuration window displays with the default settings for each field.
When you click Copy, the configuration window displays with the copied settings.
Enter the appropriate settings as described in
Click Save.
Table 18-1 VPN Gateway Configuration Settings
Field
VPN Gateway Name
VPN Gateway Description
Description
Enter the name of the VPN gateway.
Enter a description of the VPN gateway.
OL-24964-01
Cisco Unified Communications Manager Security Guide
18-3
Chapter 18 Configuring a VPN Gateway
Configuring the VPN Gateway
Table 18-1 VPN Gateway Configuration Settings
Field
VPN Gateway URL
VPN Certificates for this Gateway
Description
Enter the URL for the main VPN concentrator in the gateway.
Note
You must configure the VPN concentrator with a group-URL and use this URL as the gateway URL.
For configuration information, refer to the documentation for the VPN concentrator; such the following:
•
SSL VPN Client (SVC) on ASA with ASDM
Configuration Example
http://www.cisco.com/en/US/products/ps612
0/products_configuration_example09186a00
8071c428.shtml
Use the up and down arrow keys to assign certificates to the gateway. If you do not assign a certificate for the gateway, the VPN client will fail to connect to that concentrator.
Note
You can assign up to 10 certificates to a
VPN Gateway, and you must assign at least one certificate to each gateway. Only certificates that are associated with the
Phone-VPN-trust role display in the available VPN certificates list.
18-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
Configuring a VPN Group
C H A P T E R
19
Note
The VPN menu and its options are not available in the U.S. export unrestricted version of Cisco Unified
Communications Manager.
This chapter provides instructions for creating a VPN group. After you create a VPN group, you can add one of the VPN gateways you just configured to it.
This chapter includes the following sections:
•
Finding a VPN Group, page 19-1
•
Configuring a VPN Group, page 19-2
Finding a VPN Group
To find a VPN group, perform the following procedure:
Procedure
Step 1
Step 2
In Cisco Unified Communications Manager Administration, choose Advanced Features > VPN > VPN
Group.
The Find and List VPN Groups window displays. Records from an active (prior) query may also display in the window.
To find all records in the database, ensure the dialog box is empty; go to
To filter or search records
•
From the first drop-down list box, choose a search parameter.
•
•
From the second drop-down list box, choose a search pattern.
Specify the appropriate search text, if applicable.
Note
To add additional search criteria, click the + button. When you add criteria, the system searches for a record that matches all criteria that you specify. To remove criteria, click the – button to remove the last added criterion or click the Clear Filter button to remove all added search criteria.
Step 3
Click Find.
Cisco Unified Communications Manager Security Guide
OL-24964-01 19-1
Chapter 19 Configuring a VPN Group
Configuring a VPN Group
Step 4
All matching records display. You can change the number of items that display on each page by choosing a different value from the Rows per Page drop-down list box.
From the list of records that display, click the link for the record that you want to view.
Note
To reverse the sort order, click the up or down arrow, if available, in the list header.
The window displays the item that you choose.
Configuring a VPN Group
To add, update, or copy a VPN group, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
In Cisco Unified Communications Manager Administration, choose Advanced Features > VPN > VPN
Group.
Perform one of the following tasks:
•
To add a new profile, click Add New in the Find window and continue with
.
•
•
To copy an existing VPN group, locate the appropriate profile as described in
Group” section on page 19-1 , click the Copy button next to the VPN group that you want to copy,
and continue with
To update an existing profile, locate the appropriate VPN group as described in
Group” section on page 19-2 and continue with Step 3
.
When you click Add New, the configuration window displays with the default settings for each field.
When you click Copy, the configuration window displays with the copied settings.
Enter the appropriate settings as described in
.
Click Save.
Table 19-1 VPN Group Configuration Settings
Field
VPN Group Name
VPN Group Description
Definition
Enter the name of the VPN group.
Enter a description of the VPN group.
19-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 19 Configuring a VPN Group
Configuring a VPN Group
Table 19-1 VPN Group Configuration Settings
Field
All Available VPN Gateways
VPN Gateways in this VPN Group
Definition
Scroll to see all available VPN gateways.
Use the up and down arrow buttons to move available VPN gateways into and out of this VPN group.
If the VPN client encounters a critical error and cannot connect to a particular VPN gateway, it will attempt to move to the next VPN gateway in the list.
Note
You can add up to a maximum of three
VPN gateways to a VPN group. Also, the total number of certificates in the VPN group cannot exceed 10.
OL-24964-01
Cisco Unified Communications Manager Security Guide
19-3
Configuring a VPN Group
Chapter 19 Configuring a VPN Group
19-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
Configuring a VPN Profile
C H A P T E R
20
Note
The VPN menu and its options are not available in the U.S. export unrestricted version of Cisco Unified
Communications Manager.
This chapter contains information on the following topics:
•
•
•
VPN Profile Overview, page 20-1
Finding a VPN Profile, page 20-1
Configuring a VPN Profile, page 20-2
VPN Profile Overview
Use the VPN Profile window to create a profile that you assign to the Cisco Unified IP Phone by using the Common Phone Profile Configuration window.
Finding a VPN Profile
To find a VPN profile, perform the following procedure:
Procedure
Step 1
Step 2
In Cisco Unified Communications Manager Administration, choose Advanced Features > VPN > VPN
Profile.
The Find and List VPN Profiles window displays. Records from an active (prior) query may also display in the window.
To find all records in the database, ensure the dialog box is empty; go to
To filter or search records
•
From the first drop-down list box, choose a search parameter.
•
•
From the second drop-down list box, choose a search pattern.
Specify the appropriate search text, if applicable.
OL-24964-01
Cisco Unified Communications Manager Security Guide
20-1
Chapter 20 Configuring a VPN Profile
Configuring a VPN Profile
Step 3
Step 4
Note
To add additional search criteria, click the + button. When you add criteria, the system searches for a record that matches all criteria that you specify. To remove criteria, click the – button to remove the last added criterion or click the Clear Filter button to remove all added search criteria.
Click Find.
All matching records display. You can change the number of items that display on each page by choosing a different value from the Rows per Page drop-down list box.
From the list of records that display, click the link for the record that you want to view.
Note
To reverse the sort order, click the up or down arrow, if available, in the list header.
The window displays the item that you choose.
Configuring a VPN Profile
To add, update, or copy a VPN profile, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
In Cisco Unified Communications Manager Administration, choose Advanced Features > VPN > VPN
Profile.
Perform one of the following tasks:
•
To add a new profile, click Add New in the Find window and continue with
.
•
•
To copy an existing profile, locate the appropriate profile as described in
.
To update an existing profile, locate the appropriate VPN profile as described in
Profile” section on page 20-1 and continue with
When you click Add New, the configuration window displays with the default settings for each field.
When you click Copy, the configuration window displays with the copied settings.
Enter the appropriate settings as described in
.
Click Save.
Table 20-1
Field
Name
Description
VPN Profile Configuration Settings
Definition
Enter a name for the VPN profile.
Enter a description for the VPN profile.
20-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 20 Configuring a VPN Profile
Configuring a VPN Profile
Table 20-1 VPN Profile Configuration Settings (continued)
Field Definition
Enable Auto Network Detection When you check this check box, the VPN client can only run when it detects that it is out of the corporate network.
MTU
Fail to Connect
Enable Host ID Check
Default: Disabled.
Enter the size, in bytes, for the Maximum Transmission Unit (MTU).
Default: 1290 bytes.
This field specifies the amount of time to wait for log-in or connect operations to complete while the system creates the VPN tunnel.
Default: 30 seconds
When you check this check box, the gateway certificate subjectAltName or CN must match the URL to which the VPN client is connected.
Default: Enabled
Client Authentication Method From the drop-down list, choose the client authentication method:
•
•
User and password
Password only
Enable Password Persistence
•
Certificate (LSC or MIC)
When you check this check box, a user password gets saved in the phone until either a failed log-in attempt occurs, a user manually clears the password, or the phone resets or loses power.
OL-24964-01
Cisco Unified Communications Manager Security Guide
20-3
Configuring a VPN Profile
Chapter 20 Configuring a VPN Profile
20-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
C H A P T E R
21
VPN Feature Configuration
Note
The VPN menu and its options are not available in the U.S. export unrestricted version of Cisco Unified
Communications Manager.
This chapter describes the VPN feature configuration parameters and includes the following section:
•
•
VPN Feature Configuration Parameters, page 21-1
Overview
The VPN Feature Configuration window contains the common configuration settings for the VPN feature that the system uses when you do not associate a VPN Profile with a Common Phone Profile. If you define a VPN Profile as part of configuring a Common Phone Profile, the VPN Profile settings take precedence over the VPN Feature Configuration settings.
VPN Feature Configuration Parameters
To edit the VPN feature configuration parameters, follow this procedure:
Step 1
Step 2
Step 3
In Cisco Unified Communications Manager Administration, choose Advanced Features > VPN > VPN
Feature Configuration.
The VPN Feature Configuration Window Displays.
Accept the suggested values or enter a new value, as described in
Click Save.
Cisco Unified Communications Manager Security Guide
21-1 OL-24964-01
Chapter 21 VPN Feature Configuration
VPN Feature Configuration Parameters
Table 21-1
MTU
Keep Alive
Fail to Connect
VPN Feature Configuration Parameters
Field
Enable Auto Network Detect
Client Authentication Method
Enable Password Persistence
Enable Host ID Check
Default
When True, the VPN client can only run when it detects that it is out of the corporate network.
Default: False
This field specifies the maximum transmission unit:
Default: 1290 bytes
Minimum: 256 bytes
Maximum: 1406 bytes
This field specifies the rate at which the system sends the keep-alive message.
Note
If it is non-zero and less than the value specified in Cisco Unified
Communications Manager, the keep-alive setting in the VPN concentrator overwrites this setting.
Default: 60 seconds
Minimum: 0
Maximum: 120 seconds
This field specifies the amount of time to wait for log-in or connect operations to complete while the system creates the VPN tunnel.
Default: 30 seconds
Minimum: 0
Maximum: 600 seconds
From the drop-down list, choose the client authentication method:
•
User and password
•
•
Password only
Certificate (LSC or MIC)
Default: User And Password
When True, a user password gets saved in the phone until either a failed log-in attempt occurs, a user manually clears the password, or the phone resets or loses power.
Default: False
When True, the gateway certificate subjectAltName or CN must match the URL to which the VPN client is connected.
Default: True
21-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 21 VPN Feature Configuration
VPN Feature Configuration Parameters
OL-24964-01
Cisco Unified Communications Manager Security Guide
21-3
VPN Feature Configuration Parameters
Chapter 21 VPN Feature Configuration
21-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
P
A R T
4
Security for Cisco CTI, JTAPI, and TAPI
Applications
OL-24964-01
C H A P T E R
22
Configuring Authentication and Encryption for
CTI, JTAPI, and TAPI
This chapter provides a brief overview of how to secure the CTI, JTAPI, and TAPI applications. It also describes the tasks that you must perform in Cisco Unified Communications Manager Administration to configure authentication and encryption for CTI/TAPI/JTAPI applications.
This document does not describe how to install the Cisco JTAPI or TSP plug-ins that are available in
Cisco Unified Communications Manager Administration, nor does it describe how to configure the security parameters during the installation. Likewise, this document does not describe how to configure restrictions for CTI-controlled devices or lines.
This chapter provides information on the following topics:
•
•
•
•
•
•
•
•
Understanding Authentication for CTI, JTAPI, and TAPI Applications, page 22-2
Understanding Encryption for CTI, JTAPI, and TAPI Applications, page 22-3
CAPF Overview for CTI, JTAPI, and TAPI Applications, page 22-4
CAPF System Interactions and Requirements for CTI, JTAPI, and TAPI Applications, page 22-5
Configuration Checklist for Securing CTI, JTAPI, and TAPI, page 22-5
Adding Application and End Users to the Security-Related Users Groups, page 22-7
Activating the Certificate Authority Proxy Function Service, page 22-8
Updating CAPF Service Parameters, page 22-8
•
•
•
•
•
•
•
Finding an Application User or End User CAPF Profile, page 22-9
Configuring the Application User or End User CAPF Profile, page 22-10
CAPF Settings in the Application User and End User CAPF Profile Windows, page 22-11
Deleting an Application User CAPF or End User CAPF Profile, page 22-12
Configuring JTAPI/TAPI Security-Related Service Parameters, page 22-13
Viewing the Certificate Operation Status for the Application or End User, page 22-14
Where to Find More Information, page 22-14
Cisco Unified Communications Manager Security Guide
22-1
Understanding Authentication for CTI, JTAPI, and TAPI Applications
Chapter 22 Configuring Authentication and Encryption for CTI, JTAPI, and TAPI
Understanding Authentication for CTI, JTAPI, and TAPI
Applications
Cisco Unified Communications Manager allows you to secure the signaling connections and media streams between CTIManager and CTI/JTAPI/TAPI applications.
Tip
The following information assumes that you configured security settings during the Cisco JTAPI/TSP plug-in installation. It also assumes that the Cluster Security Mode equals Mixed Mode, as configured in the Cisco CTL Client. If these settings are not configured when you perform the tasks that are described in this chapter, CTIManager and the application connect via a nonsecure port, port 2748.
CTIManager and the application verify the identity of the other party through a mutually authenticated
TLS handshake (certificate exchange). When a TLS connection occurs, CTIManager and the application exchange QBE messages via the TLS port, port 2749.
To authenticate with the application, CTIManager uses the Cisco Unified Communications Manager certificate — either the self-signed certificate that installs automatically on the Cisco Unified
Communications Manager server during installation or a third-party, CA-signed certificate that you uploaded to the platform. After you install the Cisco CTL Client and generate the CTL file, this certificate gets added automatically to the CTL file. Before the application attempts to connect to
CTIManager, the application downloads the CTL file from the TFTP server.
The first time that the JTAPI/TSP client downloads the CTL file from the TFTP server, the JTAPI/TSP client trusts the CTL file. Because the JTAPI/TSP client does not validate the CTL file, Cisco strongly recommends that the download occur in a secure environment. The JTAPI/TSP client verifies subsequent downloads of the CTL file; for example, after you update the CTL file, the JTAPI/TSP client uses the security tokens in the CTL file to authenticate the digital signature of the new CTL file it downloads. Contents of the file include the Cisco Unified Communications Manager certificates and
CAPF server certificate.
If the CTL file appears compromised, the JTAPI/TSP client does not replace the downloaded CTL file; the client logs an error and attempts to establish a TLS connection by using an older certificate in the existing CTL file. The connection may not succeed if the CTL file has changed or is compromised. If the CTL file download fails and more than one TFTP server exists, you can configure another TFTP server to download the file, as described in the
“Configuring the Cisco CTL Client” section on page 4-1
.
The JTAPI/TAPI client does not connect to any port under the following circumstances:
•
•
The client cannot download the CTL file for some reason; for example, no CTL file exists.
The client does not have an existing CTL file.
•
You configured the application user as a secure CTI user.
To authenticate with CTIManager, the application uses a certificate that the Certificate Authority Proxy
Function (CAPF) issues. To use TLS for every connection between the application and CTIManager, each instance that runs on the application PC must have a unique certificate. One certificate does not cover all instances. To ensure that the certificate installs on the node where Cisco IP Manager Assistant service is running, you configure a unique Instance ID for each Application User or End User CAPF
Profile in Cisco Unified Communications Manager Administration, as described in
Tip
If you uninstall the application from one PC and install it on another PC, you must install a new certificate for each instance on the new PC.
22-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 22 Configuring Authentication and Encryption for CTI, JTAPI, and TAPI
Understanding Encryption for CTI, JTAPI, and TAPI Applications
You must also add the application users or the end users to the Standard CTI Secure Connection user group in Cisco Unified Communications Manager Administration to enable TLS for the application.
After you add the user to this group and install the certificate, the application ensures that the user connects via the TLS port.
Understanding Encryption for CTI, JTAPI, and TAPI Applications
Tip
Authentication serves as the minimum requirement for encryption; that is, you cannot use encryption if you have not configured authentication.
Cisco Unified Communications Manager Assistant, Cisco QRT, and Cisco Web Dialer do not support encryption. CTI clients that connect to the CTIManager service may support encryption if the client sends voice packets.
To secure the media streams between the application and CTIManager, add the application users or the end users to the Standard CTI Allow Reception of SRTP Key Material user group in Cisco Unified
Communications Manager Administration. If these users also exist in the Standard CTI Secure
Connection user group and if the cluster security mode equals Mixed Mode, CTIManager establishes a
TLS connection with the application and provides the key materials to the application in a media event
Note
Cluster security mode configures the security capability for your standalone server or cluster.
Although applications do not record or store the SRTP key materials, the application uses the key materials to encrypt its RTP stream and decrypt the SRTP stream from CTIManager.
If the application connects to the nonsecure port, port 2748, for any reason, CTIManager does not send the keying material. If CTI/JTAPI/TAPI cannot monitor or control a device or directory number because you configured restrictions, CTIManager does not send the keying material.
Tip
For an application to receive SRTP session keys, the application or end user must exist in three groups:
Standard CTI Enabled, Standard CTI Secure Connection, and Standard CTI Allow Reception of SRTP
Key Material.
Although Cisco Unified Communications Manager can facilitate secure calls to and from CTI ports and route points, you must configure the application to support secure calls because the application handles the media parameters.
CTI ports/route points register through dynamic or static registration. If the port/route point uses dynamic registration, the media parameters get specified for each call; for static registration, media parameters get specified during registration and cannot change per call. When CTI ports/route points register to CTIManager through a TLS connection, the device registers securely, and the media gets encrypted via SRTP if the application uses a valid encryption algorithm in the device registration request and if the other party is secure.
When the CTI application begins to monitor a call that is already established, the application does not receive any RTP events. For the established call, the CTI application provides a DeviceSnapshot event, which defines whether the media for the call is secure or nonsecure; this event provides no keying material.
OL-24964-01
Cisco Unified Communications Manager Security Guide
22-3
Chapter 22 Configuring Authentication and Encryption for CTI, JTAPI, and TAPI
CAPF Overview for CTI, JTAPI, and TAPI Applications
CAPF Overview for CTI, JTAPI, and TAPI Applications
Certificate Authority Proxy Function (CAPF), which automatically installs with Cisco Unified
Communications Manager, performs the following tasks for CTI/TAPI/TAPI applications, depending on your configuration:
•
Authenticates to the JTAPI/TSP client via an authentication string.
•
•
Issues locally significant certificates (LSC) to CTI/JTAPI/TAPI application users or end users.
Upgrades existing locally significant certificates.
•
Retrieves certificates for viewing and troubleshooting.
When the JTAPI/TSP client interacts with CAPF, the client authenticates to CAPF by using an authentication string; the client then generates its public key and private key pair and forwards its public key to the CAPF server in a signed message. The private key remains in the client and never gets exposed externally. CAPF signs the certificate and then sends the certificate back to the client in a signed message.
You issue certificates to application users or end users by configuring the settings in the Application
User CAPF Profile Configuration window or End User CAPF Profile Configuration window, respectively. The following information describes the differences between the CAPF profiles that Cisco
Unified Communications Manager supports:
•
Application User CAPF Profile—This profile allows you to issue locally significant certificates to secure application users so that a TLS connection opens between the CTIManager service and the application.
•
One Application User CAPF Profile corresponds to a single instance of the service or application on a server. If you activate multiple web services or applications on the same server, you must configure two Application User CAPF Profiles, one for each service on the server.
If you activate a service or application on two servers in the cluster, you must configure two
Application User CAPF Profiles, one for each server.
End User CAPF Profile—This profile allows you to issue locally significant certificates to CTI clients so that the CTI client communicates with the CTIManager service via a TLS connection.
Tip
The JTAPI client stores the LSC in Java Key Store format in the path that you configure in the JTAPI
Preferences window. The TSP client stores the LSC in an encrypted format in the default directory or in the path that you configure.
The following information applies when a communication or power failure occurs.
•
If a communication failure occurs while the certificate installation is taking place, the JTAPI client attempts to obtain the certificate three more times in 30-second intervals. You cannot configure this value.
For the TSP client, you can configure the retry attempts and the retry timer. Configure these values by specifying the number of times that the TSP client tries to obtain the certificate in an allotted time. For both values, the default equals 0. You can configure up to 3 retry attempts by specifying
1 (for one retry), 2, or 3. You can configure no more than 30 seconds for each retry attempt.
•
If a power failure occurs while the JTAPI/TSP client attempts a session with CAPF, the client attempts to download the certificate after power gets restored.
22-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 22 Configuring Authentication and Encryption for CTI, JTAPI, and TAPI
CAPF System Interactions and Requirements for CTI, JTAPI, and TAPI Applications
CAPF System Interactions and Requirements for CTI, JTAPI, and
TAPI Applications
The following requirements exist for CAPF:
•
•
Before you configure the Application User and End User CAPF Profiles, verify that you performed all necessary tasks to install and configure the Cisco CTL Client. Verify that the Cluster Security
Mode in the Enterprise Parameters Configuration window is 1 (mixed mode).
To use CAPF, you must activate the Cisco Certificate Authority Proxy Function service on the first node.
•
•
•
Because generating many certificates at the same time may cause call-processing interruptions,
Cisco strongly recommends that you use CAPF during a scheduled maintenance window.
Ensure that the first node is functional and running during the entire certificate operation.
Ensure that the CTI/ JTAPI/TAPI application is functional during the entire certificate operation.
Configuration Checklist for Securing CTI, JTAPI, and TAPI
provides a list of tasks that you perform to secure the CTI/JTAPI/TAPI application.
Table 22-1 CTI/JTAPI/TAPI Security Configuration Checklist
Configuration Steps
Step 1
Verify that the CTI application and any JTAPI/TSP plug-ins are installed and running.
Tip
Assign the application user to the Standard CTI Enabled group.
Related Procedures and Topics
•
•
Computer Telephony Integration, Cisco
Unified Communications Manager
System Guide
Cisco JTAPI Installation Guide for Cisco
Unified Communications Manager
•
Cisco TAPI Installation Guide for Cisco
Unified Communications Manager
•
Cisco Unified Communications Manager
Administration Guide
OL-24964-01
Cisco Unified Communications Manager Security Guide
22-5
Chapter 22 Configuring Authentication and Encryption for CTI, JTAPI, and TAPI
Configuration Checklist for Securing CTI, JTAPI, and TAPI
Table 22-1 CTI/JTAPI/TAPI Security Configuration Checklist (continued)
Configuration Steps
Step 2
Verify that the following Cisco Unified Communications
Manager security features are installed (if not installed, install and configure these features):
•
•
•
Verify that you installed the CTL Client and the CTL file has run, so the CTL file is created.
Verify that you installed the CTL provider service and that the service is activated.
•
Related Procedures and Topics
•
Configuring the Cisco CTL Client, page 4-1
Updating CAPF Service Parameters, page 22-8
Cisco Unified Communications Manager
Administration Guide
•
Tip
Verify that you installed the CAPF service and that the service is activated. If necessary, update CAPF service parameters.
The CAPF service must run for the Cisco CTL Client to include the CAPF certificate in the CTL file. If you updated these parameters when you used CAPF for the phones, you do not need to update the parameters again.
Step 3
Step 4
Step 5
•
Verify that the cluster security mode is set to Mixed Mode.
(Cluster security mode configures the security capability for your standalone server or cluster.)
Tip
Tip
The CTI/JTAPI/TAPI application cannot access the
CTL file if the cluster security mode does not equal
Mixed Mode.
If you want CTIManager and the application to use a TLS connection, add the application user or end users to the Standard
CTI Secure Connection user group.
Adding Application and End Users to the
Security-Related Users Groups, page 22-7
A CTI application can be assigned to either an application user or an end user, but not both.
If you want to use SRTP, add the application user or end user to the Standard CTI Allow Reception of SRTP Key Material user group.
Adding Application and End Users to the
Security-Related Users Groups, page 22-7
The user must already exist in the Standard CTI Enabled and
Standard CTI Secure Connection user group. The application or end user cannot receive SRTP session keys if it does not exist in these three groups.
Role Configuration, Cisco Unified
Communications Manager Administration
Guide
Cisco Unified Communications Manager Assistant, Cisco QRT, and Cisco Web Dialer do not support encryption. CTI clients that connect to the CTIManager service may support encryption if the client sends voice packets.
Configure the Application User CAPF Profile or End User
CAPF Profile in Cisco Unified Communications Manager
Administration.
•
•
•
CAPF Overview for CTI, JTAPI, and
Configuring the Application User or End
CAPF Settings in the Application User and End User CAPF Profile Windows, page 22-11
22-6
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 22 Configuring Authentication and Encryption for CTI, JTAPI, and TAPI
Adding Application and End Users to the Security-Related Users Groups
Table 22-1 CTI/JTAPI/TAPI Security Configuration Checklist (continued)
Configuration Steps
Step 6
Enable the corresponding security-related parameters in the
CTI/JTAPI/TAPI application.
Related Procedures and Topics
Configuring JTAPI/TAPI Security-Related
Service Parameters, page 22-13
Adding Application and End Users to the Security-Related Users
Groups
The Standard CTI Secure Connection user group and the Standard CTI Allow Reception of SRTP Key
Material user group display in Cisco Unified Communications Manager Administration by default. You cannot delete these groups.
To secure the user connection to CTIManager, you must add the application user or end users to the
Standard CTI Secure Connection user group. You can assign a CTI application to either an application user or an end user, but not both.
If you want the application and CTIManager to secure the media streams, you must add the application user or end users to the Standard CTI Allow Reception of SRTP Key Material user group.
Before the application and end user can use SRTP, the user must exist in the Standard CTI Enabled and
Standard CTI Secure Connection user groups, which serve as a baseline configuration for TLS. SRTP connections require TLS. After the user exists in these groups, you can add the user to the Standard CTI
Allow Reception of SRTP Key Material user group. For an application to receive SRTP session keys, the application or end user must exist in three groups: Standard CTI Enabled, Standard CTI Secure
Connection, and Standard CTI Allow Reception of SRTP Key Material.
Because Cisco Unified Communications Manager Assistant, Cisco QRT, and Cisco Web Dialer do not support encryption, you do not need to add the application users, CCMQRTSecureSysUser,
IPMASecureSysUser, and the WDSecureSysUser, to the Standard CTI Allow Reception of SRTP Key
Material user group.
Tip
For information on deleting an application or end user from a user group, refer to the Cisco Unified
Communications Manager Administration Guide. For information about security-related settings in the
Role Configuration window, refer to the Cisco Unified Communications Manager Administration Guide.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
In Cisco Unified Communications Manager Administration, choose User Management > User Groups.
To display all user groups, click Find.
Depending on what you want to accomplish, perform one of the following tasks:
•
Verify that the application or end users exist in the Standard CTI Enabled group.
•
•
To add an application user or end users to the Standard CTI Secure Connection user group, click the
Standard CTI Secure Connection link.
To add an application user or end users to the Standard CTI Allow Reception of SRTP Key Material user group, click the Standard CTI Allow Reception of SRTP Key Material link.
To add an application user to the group, perform
Click the Add Application Users to Group button.
Cisco Unified Communications Manager Security Guide
OL-24964-01 22-7
Chapter 22 Configuring Authentication and Encryption for CTI, JTAPI, and TAPI
Activating the Certificate Authority Proxy Function Service
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
To find an application user, specify the search criteria; then, click Find.
Clicking Find without specifying search criteria displays all available options.
Check the check boxes for the application users that you want to add to the group; then, click Add
Selected.
The users display in the User Group window.
To add end users to the group, perform
through
Click the Add Users to Group button.
To find an end user, specify the search criteria; then, click Find.
Clicking Find without specifying search criteria displays all available options.
Check the check boxes for the end users that you want to add to the group; then, click Add Selected.
The users display in the User Group window.
Additional Information
See the
“Related Topics” section on page 22-14 .
Activating the Certificate Authority Proxy Function Service
Cisco Unified Communications Manager does not automatically activate the Certificate Authority Proxy
Function service in Cisco Unified Serviceability. For information on activating the Certificate Authority
Proxy Function service, refer to the Cisco Unified Serviceability Administration Guide.
To use the CAPF functionality, you must activate this service on the first node.
If you did not activate this service before you installed and configured the Cisco CTL Client, you must update the CTL file, as described in the
“Updating the CTL File” section on page 4-13
.
After you activate the Cisco Certificate Authority Proxy Function service, CAPF automatically generates a key pair and certificate that is specific for CAPF. The CAPF certificate, which the Cisco CTL
Client copies to your standalone server or all server(s) in the cluster, uses the .0 extension. To verify that the CAPF certificate exists, display the CAPF certificate at the Cisco Unified Communications
Operating System GUI.
Updating CAPF Service Parameters
The CAPF Service Parameter window provides information on the number of years that the certificate is valid, the maximum number of times that the system retries to generate the key, the key size, and so on
For the CAPF service parameters to display as Active in Cisco Unified Communications Manager
Administration, you must activate the Certificate Authority Proxy Function service in Cisco Unified
Serviceability.
Tip
If you updated the CAPF service parameters when you used CAPF for the phones, you do not need to update the service parameters again.
22-8
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 22 Configuring Authentication and Encryption for CTI, JTAPI, and TAPI
Finding an Application User or End User CAPF Profile
To update the CAPF service parameters, perform the following procedure:
Procedure
Step 1
Step 2
In Cisco Unified Communications Manager Administration, choose System > Service Parameters.
From the Server drop-down list box, choose the server.
Tip
Step 3
Step 4
Step 5
You must choose the first node in the cluster.
From the Service drop-down list box, choose the Cisco Certificate Authority Proxy Function service.
Verify that the word “Active” displays next to the service name.
Update the CAPF service parameters, as described in the help. To display help for the CAPF service parameters, click the question mark or the parameter name link.
For the changes to take effect, restart the Cisco Certificate Authority Proxy Function service in Cisco
Unified Serviceability.
Additional Information
See the
“Related Topics” section on page 22-14
.
Finding an Application User or End User CAPF Profile
To find an application or end user CAPF profile, perform the following procedure:
Procedure
Step 1
Step 2
In Cisco Unified Communications Manager Administration, choose one of the following options, depending on which profile you want to access:
•
User Management > Application User CAPF Profile
• User Management > End User CAPF Profile
The Find and List window displays. Records from an active (prior) query may also display in the window.
•
•
•
To find all records in the database, ensure the dialog box is empty; go to
To filter or search records
From the first drop-down list box, choose a search parameter
From the second drop-down list box, choose a search pattern.
Specify the appropriate search text, if applicable.
Note
To add additional search criteria, click the + button. When you add criteria, the system searches for a record that matches all criteria that you specify. To remove criteria, click the – button to remove the last added criterion or click the Clear Filter button to remove all added search criteria.
OL-24964-01
Cisco Unified Communications Manager Security Guide
22-9
Chapter 22 Configuring Authentication and Encryption for CTI, JTAPI, and TAPI
Configuring the Application User or End User CAPF Profile
Step 3
Step 4
Click Find.
All matching records display. You can change the number of items that display on each page by choosing a different value from the Rows per Page drop-down list box.
From the list of records that display, click the link for the record that you want to view.
Note
To reverse the sort order, click the up or down arrow, if available, in the list header.
The window displays the item that you choose.
Additional Information
See the
“Related Topics” section on page 22-14 .
Configuring the Application User or End User CAPF Profile
Use
Table 22-2 as a reference when you install/upgrade/troubleshoot locally significant certificates for
JTAPI/TAPI/CTI applications.
Tip
Cisco recommends that you configure Application User CAPF Profiles before you configure End User
CAPF Profiles.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
In Cisco Unified Communications Manager Administration, choose one of the following options:
•
User Management > Application User CAPF Profile.
•
User Management > End User CAPF Profile.
The Find and List window displays.
Perform one of the following tasks:
•
•
•
To add a new CAPF profile, click Add New in the Find window. (You can also display a profile and then click Add New.) The configuration window displays with the default settings for each field.
To copy an existing profile, locate the appropriate profile as described in
User or End User CAPF Profile” section on page 22-9
and click the Copy icon for that record in the
Copy column. (You can also display a profile and then click Copy.) The configuration window displays with the settings from the displayed profile.
To update an existing entry, locate and display the appropriate profile as described in “Finding an
Application User or End User CAPF Profile” section on page 22-9 . The configuration window
displays with the current settings.
Enter the appropriate settings as described in
.
Click Save.
Repeat the procedure for each application and end user that you want to use security.
22-10
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 22 Configuring Authentication and Encryption for CTI, JTAPI, and TAPI
CAPF Settings in the Application User and End User CAPF Profile Windows
Next Steps
If you configured the CCMQRTSecureSysUser, IPMASecureSysUser, or WDSecureSysUser in the
Application User CAPF Profile Configuration window, you must configure service parameters, as
Additional Information
See the
“Related Topics” section on page 22-14
.
CAPF Settings in the Application User and End User CAPF Profile
Windows
describes the CAPF settings in the Application User CAPF Profile Configuration and End
User CAPF Profile Configuration windows.
•
For configuration tips, see the
“CAPF System Interactions and Requirements for CTI, JTAPI, and
TAPI Applications” section on page 22-5 .
•
For related information and procedures, see the “Related Topics” section on page 22-14
.
Table 22-2 Application and End User CAPF Profile Configuration Settings
Setting
Application User
End User ID
Instance ID
Certificate Operation
Description
From the drop-down list box, choose the application user for the CAPF operation.This setting shows configured application users.
This setting does not display in the End User CAPF Profile window.
From the drop-down list box, choose the end user for the CAPF operation. This setting shows configured end users.
This setting does not display in the Application User CAPF Profile window.
Enter 1-128 alphanumeric characters (a-zA-Z0-9). The Instance ID identifies the user for the certificate operation.
You can configure multiple connections (instances) of an application.To secure the connection between the application and CTIManager, ensure that each instance that runs on the application PC (for end users) or server
(for application users) has a unique certificate.
This field relates to the CAPF Profile Instance ID for Secure Connection to CTIManager service parameter that supports web services and applications. For information on how to access this parameter, see the
“Configuring JTAPI/TAPI Security-Related Service Parameters” section on page 22-13
.
From the drop-down list box, choose one of the following options:
•
•
No Pending Operation—Displays when no certificate operation is occurring. (default setting)
Install/Upgrade—Installs a new or upgrades an existing locally significant certificate for the application.
OL-24964-01
Cisco Unified Communications Manager Security Guide
22-11
Chapter 22 Configuring Authentication and Encryption for CTI, JTAPI, and TAPI
Deleting an Application User CAPF or End User CAPF Profile
Table 22-2
Setting
Authentication Mode
Authentication String
Generate String
Key Size (bits)
Certificate Operation
Status
Application and End User CAPF Profile Configuration Settings (continued)
Operation Completes by
Description
The authentication mode for the Install/Upgrade certificate operation specifies By Authentication String, which means CAPF installs/upgrades or troubleshoots a locally significant certificate only when the user/administrator enters the CAPF authentication string in the
JTAPI/TSP Preferences window.
Manually enter a unique string or generate a string by clicking the
Generate String button.
Ensure that the string contains 4 to 10 digits.
To install or upgrade a locally significant certificate, the administrator must enter the authentication string in the JTAPI/TSP preferences GUI on the application PC. This string supports one-time use only; after you use the string for the instance, you cannot use it again.
If you want CAPF to automatically generate an authentication string, click this button. The 4- to10-digit authentication string displays in the
Authentication String field.
From the drop-down list box, choose the key size for the certificate. The default setting equals 1024. Other options include 512 and 2048.
Key generation, which is set at low priority, allows the application to function while the action occurs. Key generation may take up to 30 or more minutes to complete.
If you choose a 2048-bit key for the certificate, establishing a connection between the application and Cisco Unified Communications Manager may take more than 60 seconds. Unless you want to use the highest possible security level, do not configure the 2048-bit key.
This field, which supports all certificate operations, specifies the date and time by which you must complete the operation.
The values that display apply for the first node.
Use this setting with the CAPF Operation Expires in (days) enterprise parameter, which specifies the default number of days in which the certificate operation must be completed. You can update this parameter any time.
This field displays the progress of the certificate operation, such as pending, failed, or successful.
You cannot change the information that displays in this field.
Deleting an Application User CAPF or End User CAPF Profile
This section describes how to delete an Application User CAPF Profile or End User CAPF Profile from the Cisco Unified Communications Manager database.
22-12
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 22 Configuring Authentication and Encryption for CTI, JTAPI, and TAPI
Configuring JTAPI/TAPI Security-Related Service Parameters
Before You Begin
Before you can delete an Application User CAPF Profile or End User CAPF Profile from Cisco Unified
Communications Manager Administration, you must apply a different profile to the devices or delete all devices that use the profile. To find out which devices use the profile, choose Dependency Records from the Related Links drop-down list box in the Security Profile Configuration window and click Go.
If the dependency records feature is not enabled for the system, the dependency records summary window displays a message that shows the action that you can take to enable the dependency records; the message also displays information about high CPU consumption that is related to the dependency records feature. For more information about dependency records, refer to the Cisco Unified
Communications Manager System Guide.
Procedure
Step 1
Step 2
Step 3
Find the Application User CAPF Profile or End User CAPF Profile by using the procedure in the
“Finding an Application User or End User CAPF Profile” section on page 22-9 .
Perform one of the following tasks:
•
To delete multiple profiles, check the check boxes next to the appropriate check box in the Find and
List window; then, click Delete Selected. You can delete all configurable records for this selection by clicking Select All and then clicking Delete Selected.
•
To delete a single profile, check the check box next to the appropriate profile In the Find and List window; then, click Delete Selected.
When prompted to confirm the delete operation, click OK to delete or Cancel to cancel the delete operation.
Additional Information
See the
“Related Topics” section on page 22-14
.
Configuring JTAPI/TAPI Security-Related Service Parameters
After you configure the Application User CAPF Profile or End User CAPF Profile, you must configure the following service parameters for Cisco IP Manager Assistant service:
•
•
CTIManager Connection Security Flag
CAPF Profile Instance ID for Secure Connection to CTIManager
To access the service parameters, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
In Cisco Unified Communications Manager Administration, choose System > Service Parameters.
From the Server drop-down list box, choose the server where the Cisco IP Manager Assistant service is activated.
From the Service drop-down list box, choose the Cisco IP Manager Assistant service.
After the parameters display, locate the CTIManager Connection Security Flag and CAPF Profile
Instance ID for Secure Connection to CTIManager parameters.
OL-24964-01
Cisco Unified Communications Manager Security Guide
22-13
Chapter 22 Configuring Authentication and Encryption for CTI, JTAPI, and TAPI
Viewing the Certificate Operation Status for the Application or End User
Step 5
Step 6
Step 7
Update the parameters, as described in the help that displays when you click the question mark or parameter name link.
Click Save.
Repeat the procedure on each server where the service is activated.
Viewing the Certificate Operation Status for the Application or
End User
You can view the certificate operation status in a specific Application User or End User CAPF Profile configuration window (not the Find/List window) or in the JTAPI/TSP Preferences GUI window.
Where to Find More Information
•
•
•
•
•
•
Related Topics
•
Configuring the Cisco CTL Client, page 4-1
•
Understanding Authentication for CTI, JTAPI, and TAPI Applications, page 22-2
•
•
Understanding Encryption for CTI, JTAPI, and TAPI Applications, page 22-3
CAPF Overview for CTI, JTAPI, and TAPI Applications, page 22-4
CAPF System Interactions and Requirements for CTI, JTAPI, and TAPI Applications, page 22-5
Configuration Checklist for Securing CTI, JTAPI, and TAPI, page 22-5
•
•
•
Adding Application and End Users to the Security-Related Users Groups, page 22-7
Activating the Certificate Authority Proxy Function Service, page 22-8
Updating CAPF Service Parameters, page 22-8
Finding an Application User or End User CAPF Profile, page 22-9
•
•
Configuring the Application User or End User CAPF Profile, page 22-10
CAPF Settings in the Application User and End User CAPF Profile Windows, page 22-11
Deleting an Application User CAPF or End User CAPF Profile, page 22-12
Configuring JTAPI/TAPI Security-Related Service Parameters, page 22-13
Viewing the Certificate Operation Status for the Application or End User, page 22-14
Related Cisco Documentation
•
Cisco JTAPI Installation Guide for Cisco Unified Communications Manager
•
•
•
Cisco TAPI Installation Guide for Cisco Unified Communications Manager
Computer Telephony Integration, Cisco Unified Communications Manager System Guide
Cisco Unified Communications Manager Administration Guide
22-14
Cisco Unified Communications Manager Security Guide
OL-24964-01
P
A R T
5
Security for SRST References, Trunks, and
Gateways
C H A P T E R
23
Configuring a Secure Survivable Remote Site
Telephony (SRST) Reference
This chapter contains information on the following topics:
•
•
Overview for Securing the SRST, page 23-1
Configuration Tips for Securing the SRST, page 23-2
•
•
•
•
•
•
Secure SRST Configuration Checklist, page 23-2
Configuring Secure SRST References, page 23-3
Security Configuration Settings for SRST References, page 23-4
Deleting Security from the SRST Reference, page 23-5
If the SRST Certificate Is Deleted from the Gateway, page 23-5
Where to Find More Information, page 23-6
Overview for Securing the SRST
A SRST-enabled gateway provides limited call-processing tasks if the Cisco Unified Communications
Manager cannot complete the call.
Secure SRST-enabled gateways contain a self-signed certificate. After you perform SRST configuration tasks in Cisco Unified Communications Manager Administration, Cisco Unified Communications
Manager uses a TLS connection to authenticate with the Certificate Provider service in the
SRST-enabled gateway. Cisco Unified Communications Manager then retrieves the certificate from the
SRST-enabled gateway and adds the certificate to the Cisco Unified Communications Manager database.
After you reset the dependent devices in Cisco Unified Communications Manager Administration, the
TFTP server adds the SRST-enabled gateway certificate to the phone cnf.xml file and sends the file to the phone. A secure phone then uses a TLS connection to interact with the SRST-enabled gateway.
Tip
The phone configuration file only contains a certificate from a single issuer. Consequently, the system does not support HSRP.
Cisco Unified Communications Manager Security Guide
23-1 OL-24964-01
Chapter 23 Configuring a Secure Survivable Remote Site Telephony (SRST) Reference
Configuration Tips for Securing the SRST
Configuration Tips for Securing the SRST
Ensure that the following criteria are met to secure the connection between the secure phone and the
SRST-enabled gateway:
•
The SRST reference contains a self-signed certificate.
•
•
•
•
You configured Mixed Mode through the Cisco CTL Client.
You configured the phone for authentication or encryption.
You configured the SRST reference in Cisco Unified Communications Manager Administration.
You reset the SRST-enabled gateway and the dependent phones after the SRST configuration.
Note
Cisco Unified Communications Manager provides the PEM format files that contain phone certificate information to the SRST-enabled gateway.
For LSC authentication, download the CAPF root certificate (CAPF.der). This root certificate allows the secure SRST to verify the phone LSC during the TLS handshake.
•
When the cluster security mode equals nonsecure, the device security mode remains nonsecure in the phone configuration file, even though Cisco Unified Communications Manager Administration may indicate that the device security mode is authenticated or encrypted. Under these circumstances, the phone attempts nonsecure connections with the SRST-enabled gateway and
Cisco Unified Communications Manager.
Note
Cluster security mode configures the security capability for your standalone server or a cluster.
•
•
•
•
When the cluster security mode equals nonsecure, the system ignores the security-related configuration; for example, the device security mode, the Is SRST Secure? check box, and so on.
The configuration does not get deleted in from the database, but security is not provided.
The phone attempts a secure connection to the SRST-enabled gateway only when the cluster security mode equals Mixed Mode, the device security mode in the phone configuration file is set to authenticated or encrypted, the Is SRST Secure? check box is checked in the SRST Configuration window, and a valid SRST-enabled gateway certificate exists in the phone configuration file.
If you configured secure SRST references in a previous Cisco Unified Communications Manager release, the configuration automatically migrates during the upgrade.
If phones in encrypted or authenticated mode fail over to SRST, and, during the connection with
SRST, the cluster security mode switches from Mixed Mode to Nonsecure Mode, these phones will not fall back to Cisco Unified Communications Manager automatically. You must power down the
SRST router to force these phones to reregister to Cisco Unified Communications Manager. After phones fall back to Cisco Unified Communications Manager, you can power up SRST, and failover and fallback will be automatic again.
Secure SRST Configuration Checklist
Use
Table 23-1 to guide you through the SRST configuration process for security.
23-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 23 Configuring a Secure Survivable Remote Site Telephony (SRST) Reference
Configuring Secure SRST References
Table 23-1 Configuration Checklist for Securing the SRST
Configuration Steps
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Verify that you performed all necessary tasks on the
SRST-enabled gateway, so the device supports Cisco Unified
Communications Manager and security.
Related Procedures and Topics
Cisco IOS SRST Version System
Administrator Guide that supports this version of Cisco Unified Communications
Manager, which you can obtain at the following URL: http://www.cisco.com/univercd/cc/td/doc/pro duct/voice/srst/srst33/srst33ad/index.htm
Configuring the Cisco CTL Client, page 4-1
Verify that you performed all necessary tasks to install and configure the Cisco CTL Client.
Verify that a certificate exists in the phone.
Verify that you configured the phones for authentication or encryption.
Configure the SRST reference for security, which includes enabling the SRST reference in the Device Pool Configuration window.
Reset the SRST-enabled gateway and phones.
Refer to the Cisco Unified IP Phone documentation for your phone model.
Applying a Phone Security Profile, page 7-10
Configuring Secure SRST References, page 23-3
Configuring Secure SRST References, page 23-3
Configuring Secure SRST References
Consider the following information before you add, update, or delete the SRST reference in Cisco
Unified Communications Manager Administration:
•
•
Adding a Secure SRST Reference—The first time that you configure the SRST reference for
security, you must configure all settings that are described in Table 23-2 .
Updating a Secure SRST Reference—Performing SRST updates in Cisco Unified Communications
Manager Administration does not automatically update the SRST-enabled gateway certificate. To update the certificate, you must click the Update Certificate button; after you click the button, the contents of the certificate display, and you must accept or reject the certificate. If you accept the certificate, Cisco Unified Communications Manager replaces the SRST-enabled gateway certificate in the trust folder on the Cisco Unified Communications Manager server or on each Cisco Unified
Communications Manager server in the cluster.
•
Deleting a Secure SRST Reference—Deleting a secure SRST reference removes the SRST-enabled gateway certificate from the Cisco Unified Communications Manager database and the cnf.xml file in the phone.
For information on how to delete SRST references, refer to the Cisco Unified Communications
Manager Administration Guide.
To configure a secure SRST reference, perform the following procedure:
Procedure
Step 1
In Cisco Unified Communications Manager Administration, choose System > SRST.
OL-24964-01
Cisco Unified Communications Manager Security Guide
23-3
Chapter 23 Configuring a Secure Survivable Remote Site Telephony (SRST) Reference
Security Configuration Settings for SRST References
Step 2
Step 3
Step 4
Step 5
Step 6
The Find and List window displays.
Perform one of the following tasks:
•
To add a new SRST reference, click Add New in the Find window. (You can also display a profile and then click Add New.) The configuration window displays with the default settings for each field.
•
•
To copy an existing SRST reference, locate the appropriate SRST reference as described in the Cisco
Unified Communications Manager Administration Guide, and click the Copy icon for that record in the Copy column. (You can also display a profile and then click Copy.) The configuration window displays with the configured settings.
To update an existing SRST reference, locate the appropriate SRST reference as described in the
Cisco Unified Communications Manager Administration Guide. The configuration window displays with the current settings.
Enter the security-related settings as described in
For descriptions of additional SRST reference configuration settings, refer to the Cisco Unified
Communications Manager Administration Guide.
After you check the Is SRST Secure? check box, a dialog box displays a message that you must download the SRST certificate by clicking the Update Certificate button. Click OK.
Click Save.
To update the SRST-enabled gateway certificate in the database, click the Update Certificate button.
Step 7
Step 8
Step 9
Tip
This button displays only after you check the Is SRST Secure? check box and click Save.
The fingerprint for the certificate displays. To accept the certificate, click Save.
Click Close.
In the SRST Reference Configuration window, click Reset.
Next Steps
Verify that you enabled the SRST reference in the Device Pool Configuration window.
Additional Information
See the
“Related Topics” section on page 23-6
.
Security Configuration Settings for SRST References
Manager Administration.
•
For configuration tips, see the
“Configuration Tips for Securing the SRST” section on page 23-2 .
•
For related information and procedures, see the
“Related Topics” section on page 23-6 .
23-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 23 Configuring a Secure Survivable Remote Site Telephony (SRST) Reference
Deleting Security from the SRST Reference
Table 23-2 Configuration Settings for Secure SRST References
Setting
Is SRST Secure?
SRST Certificate Provider
Port
Update Certificate
Description
After you verify that the SRST-enabled gateway contains a self-signed certificate, check this check box.
After you configure the SRST and reset the gateway and dependent phones, the Cisco CTL Provider service authenticates to the Certificate
Provider service on the SRST-enabled gateway. The Cisco CTL Client retrieves the certificate from the SRST-enabled gateway and stores the certificate in the Cisco Unified Communications Manager database.
Tip
To remove the SRST certificate from the database and phone, uncheck this check box, click Save, and reset the dependent phones.
This port monitors requests for the Certificate Provider service on the
SRST-enabled gateway. Cisco Unified Communications Manager uses this port to retrieve the certificate from the SRST-enabled gateway. The
Cisco SRST Certificate Provider default port equals 2445.
After you configure this port on the SRST-enabled gateway, enter the port number in this field.
Tip
Tip
You may need to configure a different port number if the port is currently used or if you use a firewall and you cannot use the port within the firewall.The port number must exist in the range of 1024 and 49151; otherwise, the following message displays:
Port Numbers can only contain digits.
This button displays only after you check the Is SRST Secure? check box and click Save.
After you click this button, the Cisco CTL Client replaces the existing
SRST-enabled gateway certificate that is stored in the Cisco Unified
Communications Manager database, if a certificate exists in the database. After you reset the dependent phones, the TFTP server sends the cnf.xml file (with the new SRST-enabled gateway certificate) to the phones.
Deleting Security from the SRST Reference
To make the SRST reference nonsecure after you configure security, uncheck the Is SRTS Secure? check box in the SRST Configuration window. A message states that you must turn off the credential service on the gateway.
If the SRST Certificate Is Deleted from the Gateway
If the SRST certificate no longer exists in the SRST-enabled gateway, you must remove the SRST certificate from the Cisco Unified Communications Manager database and the phone.
To perform this task, uncheck the Is SRST Secure? check box and click Update in the SRST
Configuration window; then, click Reset Devices.
OL-24964-01
Cisco Unified Communications Manager Security Guide
23-5
Chapter 23 Configuring a Secure Survivable Remote Site Telephony (SRST) Reference
Where to Find More Information
Where to Find More Information
Related Topics
•
Overview for Securing the SRST, page 23-1
•
Configuration Tips for Securing the SRST, page 23-2
•
•
•
•
•
Secure SRST Configuration Checklist, page 23-2
Configuring Secure SRST References, page 23-3
Security Configuration Settings for SRST References, page 23-4
Deleting Security from the SRST Reference, page 23-5
If the SRST Certificate Is Deleted from the Gateway, page 23-5
Related Cisco Documentation
•
Cisco IOS SRST System Administrator Guide
•
Cisco Unified Communications Manager Administration Guide
23-6
Cisco Unified Communications Manager Security Guide
OL-24964-01
C H A P T E R
24
Configuring Encryption for Gateways and Trunks
This chapter contains information on the following topics:
•
Overview for Cisco IOS MGCP Gateway Encryption, page 24-1
•
•
•
•
•
Overview for H.323 Gateway and H.323/H.225/H.245 Trunk Encryption, page 24-2
Overview for SIP Trunk Encryption, page 24-3
Secure Gateway and Trunk Configuration Checklist, page 24-4
Considerations for Configuring IPSec in the Network Infrastructure, page 24-5
•
•
Considerations for Configuring IPSec Between Cisco Unified Communications Manager and the
Configuring the SRTP Allowed Check Box, page 24-6
Where to Find More Information, page 24-6
Overview for Cisco IOS MGCP Gateway Encryption
Cisco Unified Communications Manager supports gateways that use the MGCP SRTP package, which the gateway uses to encrypt and decrypt packets over a secure RTP connection. The information that gets exchanged during call setup determines whether the gateway uses SRTP for a call. If the devices support
SRTP, the system uses a SRTP connection. If at least one device does not support SRTP, the system uses a RTP connection. SRTP-to-RTP fallback (and vice versa) may occur for transfers from a secure device to a non-secure device, conferencing, transcoding, music on hold, and so on.
When the system sets up an encrypted SRTP call between two devices, Cisco Unified Communications
Manager generates a master encryption key and salt for secure calls and sends them to the gateway for the SRTP stream only. Cisco Unified Communications Manager does not send the key and salt for
SRTCP streams, which the gateway also supports. These keys get sent to the gateway over the MGCP signaling path, which you should secure by using IPSec. Although Cisco Unified Communications
Manager does not recognize whether an IPSec connection exists, the system sends the session keys to the gateway in the clear if IPSec is not configured. Confirm that the IPSec connection exists, so the session keys get sent through a secure connection.
Tip
If the MGCP gateway, which is configured for SRTP, is involved in a call with an authenticated device, for example, an authenticated phone that is running SCCP, a shield icon displays on the phone because
Cisco Unified Communications Manager classifies the call as authenticated. Cisco Unified
Cisco Unified Communications Manager Security Guide
24-1 OL-24964-01
Chapter 24 Configuring Encryption for Gateways and Trunks
Overview for H.323 Gateway and H.323/H.225/H.245 Trunk Encryption
Communications Manager classifies a call as encrypted if the SRTP capabilities for the devices are successfully negotiated for the call. If the MGCP gateway is connected to a phone that can display security icons, the phone displays the lock icon when the call is encrypted.
Overview for H.323 Gateway and H.323/H.225/H.245 Trunk
Encryption
H.323 gateways and gatekeeper or non-gatekeeper controlled H.225/H.323/H.245 trunks that support security can authenticate to Cisco Unified Communications Manager if you configure an IPSec association in the Cisco Unified Communications Operating System. For information on creating an
IPSec association between Cisco Unified Communications Manager and these devices, refer to the Cisco
Unified Communications Operating System Administration Guide.
The H.323, H.225, and H.245 devices generate the encryption keys. These keys get sent to Cisco Unified
Communications Manager through the signaling path, which you secure through IPSec. Although Cisco
Unified Communications Manager does not recognize whether an IPSec connection exists, the session keys get sent in the clear if IPSec is not configured. Confirm that the IPSec connection exists, so the session keys get sent through a secure connection.
In addition to configuring an IPSec association, you must check the SRTP Allowed check box in the device configuration window in Cisco Unified Communications Manager Administration; for example, the H.323 Gateway, the H.225 Trunk (Gatekeeper Controlled), the Inter-Cluster Trunk (Gatekeeper
Controlled), and the Inter-Cluster Trunk (Non-Gatekeeper Controlled) configuration windows. If you do not check this check box, Cisco Unified Communications Manager uses RTP to communicate with the device. If you check the check box, Cisco Unified Communications Manager allows secure and nonsecure calls to occur, depending on whether SRTP is configured for the device.
Caution
If you check the SRTP Allowed check box in Cisco Unified Communications Manager Administration,
Cisco strongly recommends that you configure IPSec, so security-related information does not get sent in the clear.
Cisco Unified Communications Manager does not confirm that you configured the IPSec connection correctly. If you do not configure the connection correctly, security-related information may get sent in the clear.
If the system can establish a secure media or signaling path and if the devices support SRTP, the system uses a SRTP connection. If the system cannot establish a secure media or signaling path or if at least one device does not support SRTP, the system uses a RTP connection. SRTP-to-RTP fallback (and vice versa) may occur for transfers from a secure device to a non-secure device, conferencing, transcoding, music on hold, and so on.
Tip
If the call uses pass-through capable MTP, if the audio capabilities for the device match after region filtering, and if the MTP Required check box is not checked for any device, Cisco Unified
Communications Manager classifies the call as secure. If the MTP Required check box is checked, Cisco
Unified Communications Manager disables audio pass-through for the call and classifies the call as nonsecure. If no MTP is involved in the call, Cisco Unified Communications Manager may classify the call as encrypted, depending on the SRTP capabilities of the devices.
For SRTP-configured devices, Cisco Unified Communications Manager classifies a call as encrypted if
24-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 24 Configuring Encryption for Gateways and Trunks
Overview for SIP Trunk Encryption
the SRTP Allowed check box is checked for the device and if the SRTP capabilities for the devices are successfully negotiated for the call. If the preceding criteria are not met, Cisco Unified Communications
Manager classifies the call as nonsecure. If the device is connected to a phone that can display security icons, the phone displays the lock icon when the call is encrypted.
Cisco Unified Communications Manager classifies outbound faststart calls over a trunk or gateway as nonsecure. If you check the SRTP Allowed check box in Cisco Unified Communications Manager
Administration, Cisco Unified Communications Manager disables the Enable Outbound FastStart check box.
Cisco Unified Communications Manager allows some types of gateways and trunks to transparently pass through the shared secret (Diffie-Hellman key) and other H.235 data between two H.235 endpoints, so the two endpoints can establish a secure media channel.
To enable the passing through of H.235 data, check the H.235 pass through allowed check box in the configuration settings of the following trunks and gateways:
•
H.225 Trunk
•
•
ICT Gatekeeper Control
ICT non-Gatekeeper Control
•
H.323 Gateway
For information about configuring trunks and gateways, see the Cisco Unified Communications Manager
Administration Guide.
Overview for SIP Trunk Encryption
SIP trunks can support secure calls both for signaling as well as media; TLS provides signaling encryption and SRTP provides media encryption.
To configure signaling encryption for the trunk, choose the following options when you configure the
SIP trunk security profile (in the System > Security Profile > SIP Trunk Security Profile window):
•
From the Device Security Mode drop-down list, choose “Encrypted.”
•
•
From the Incoming Transport Type drop-down list, choose “TLS.”
From the Outgoing Transport Type drop-down list, choose “TLS.”
After you configure the SIP trunk security profile, apply it to the trunk (in the Device > Trunk > SIP
Trunk configuration window).
To configure media encryption for the trunk, check the SRTP Allowed check box (also in the Device >
Trunk > SIP Trunk configuration window).
Caution
If you check this check box, Cisco strongly recommends that you use an encrypted TLS profile, so that keys and other security-related information do not get exposed during call negotiations. If you use a non- secure profile, SRTP will still work but the keys will be exposed in signaling and traces. In that case, you must ensure the security of the network between Cisco Unified Communications Manager and the destination side of the trunk.
For more information about configuring the SIP Trunk security profile, see the
Trunk Security Profile” chapter.
OL-24964-01
Cisco Unified Communications Manager Security Guide
24-3
Chapter 24 Configuring Encryption for Gateways and Trunks
Secure Gateway and Trunk Configuration Checklist
Secure Gateway and Trunk Configuration Checklist
Use Table 24-1 in conjunction with the document, Media and Signaling Authentication and Encryption
Feature for Cisco IOS MGCP Gateways, which provides information on how to configure your
Cisco IOS MGCP gateways for security. You can obtain this document at the following URL: http://www.cisco.com/en/US/products/sw/iosswrel/ps5207/products_feature_guide09186a0080357589
.html
Table 24-1 Configuration Checklist for Securing the MGCP Gateway
Configuration Steps
Step 1
Verify that you installed and configured the Cisco CTL Client; verify that the cluster security mode equals Mixed Mode.
Step 2
Step 3
Related Procedures and Topics
Configuring the Cisco CTL Client, page 4-1
Verify that you configured the phones for encryption.
Configure IPSec.
Tip
You may configure IPSec in the network infrastructure, or you may configure IPSec between Cisco Unified
Communications Manager and the gateway or trunk. If you implement one method to set up IPSec, you do not need to implement the other method.
•
Phone Security Overview, page 6-1
•
Considerations for Configuring IPSec in the Network Infrastructure, page 24-5
Considerations for Configuring IPSec
Between Cisco Unified Communications
Manager and the Gateway or Trunk, page 24-5
Step 4
Step 5
For H.323 IOS gateways and intercluster trunks, check the SRTP
Allowed check box in Cisco Unified Communications Manager
Administration.
For SIP trunks, configure the SIP trunk security profile and apply it to the trunk(s), if you have not already done so. Also, be sure to check the “SRTP Allowed” check box in the Device >
Trunk > SIP Trunk configuration window.
The SRTP Allowed check box displays in the
Trunk Configuration or Gateway
Configuration window. For information on how to display these windows, refer to the trunk and gateway chapters in the Cisco
Unified Communications Manager
Administration Guide.
•
•
Overview for SIP Trunk Encryption, page 24-3
Configuring the SIP Trunk Security
Step 6
Caution
If you check the “SRTP Allowed” check box, Cisco strongly recommends that you use an encrypted TLS profile, so that keys and other security-related information does not get exposed during call negotiations. If you use a non-secure profile, SRTP will still work but the keys will be exposed in signaling and traces. In that case, you must ensure the security of the network between Cisco Unified
Communications Manager and the destination side of the trunk.
Perform security-related configuration tasks on the gateway.
•
Media and Signaling Authentication and
Encryption Feature for Cisco IOS MGCP
Gateways
24-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 24 Configuring Encryption for Gateways and Trunks
Considerations for Configuring IPSec in the Network Infrastructure
Considerations for Configuring IPSec in the Network
Infrastructure
This document does not describe how to configure IPSec. Instead, it provides considerations and recommendations for configuring IPSec in your network infrastructure. If you plan to configure IPSec in the network infrastructure and not between Cisco Unified Communications Manager and the device, review the following information before you configure IPSec:
•
•
Cisco recommends that you provision IPSec in the infrastructure rather than in the Cisco Unified
Communications Manager itself.
Before you configure IPSec, consider existing IPSec or VPN connections, platform CPU impact, bandwidth implications, jitter or latency, and other performance metrics.
•
•
Review the Voice and Video Enabled IPSec Virtual Private Networks Solution Reference Network
Design Guide, which you can obtain at the following URL: http://www.cisco.com/application/pdf/en/us/guest/netsol/ns241/c649/ccmigration_09186a00801ea
79c.pdf
Review the Cisco IOS Security Configuration Guide, Release 12.2 (or later), which you can obtain at the following URL: http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_book09
186a0080087df1.html
•
•
•
•
Terminate the remote end of the IPSec connection in the secure Cisco IOS MGCP gateway.
Terminate the host end in a network device within the trusted sphere of the network where the telephony servers exist; for example, behind a firewall, access control list (ACL), or other layer three device.
The equipment that you use to terminate the host-end IPSec connections depends on the number of gateways and the anticipated call volume to those gateways; for example, you could use Cisco VPN
3000 Series Concentrators, Catalyst 6500 IPSec VPN Services Module, or Cisco Integrated Services
Routers.
Perform the steps in the order that is specified in the
“Secure Gateway and Trunk Configuration
Checklist” section on page 24-4 .
Caution
Failing to configure the IPSEC connections and verify that the connections are active may compromise privacy of the media streams.
Considerations for Configuring IPSec Between Cisco Unified
Communications Manager and the Gateway or Trunk
For information on configuring IPSec between Cisco Unified Communications Manager and the gateways or trunks that are described in this chapter, refer to the Cisco Unified Communications
Operating System Administration Guide.
OL-24964-01
Cisco Unified Communications Manager Security Guide
24-5
Chapter 24 Configuring Encryption for Gateways and Trunks
Configuring the SRTP Allowed Check Box
Configuring the SRTP Allowed Check Box
The SRTP Allowed check box displays in the following configuration windows in Cisco Unified
Communications Manager Administration:
•
H.323 Gateway Configuration window
•
•
•
•
H.225 Trunk (Gatekeeper Controlled) Configuration window
Inter-Cluster Trunk (Gatekeeper Controlled) Configuration window
Inter-Cluster Trunk (Non-Gatekeeper Controlled) Configuration window
SIP Trunk Configuration window
To configure the SRTP Allowed check box for H.323 gateways and gatekeeper or non-gatekeeper controlled H.323/H.245/H.225 trunks or SIP trunks, perform the following procedure:
Procedure
Step 1
Step 2
Find the gateway or trunk, as described in the Cisco Unified Communications Manager Administration
Guide.
After you open the configuration window for the gateway/trunk, check the SRTP Allowed check box.
Caution
If you check the “SRTP Allowed” check box for a SIP trunk, Cisco strongly recommends that you use an encrypted TLS profile, so keys and other security-related information are not exposed during call negotiations. If you use a non-secure profile, SRTP will still work but the keys will be exposed in signaling and traces. In that case, you must ensure the security of the network between Cisco Unified
Communications Manager and the destination side of the trunk.
Step 3
Step 4
Step 5
Click Save.
To reset the device, click Reset.
Verify that you configured IPSec correctly for H323. (For SIP, make sure you configured TLS correctly.)
Additional Information
See the
“Related Topics” section on page 24-6
.
Where to Find More Information
•
•
•
Related Topics
•
Authentication, Integrity, and Authorization Overview, page 1-17
•
Encryption Overview, page 1-22
•
Overview for Cisco IOS MGCP Gateway Encryption, page 24-1
Overview for H.323 Gateway and H.323/H.225/H.245 Trunk Encryption, page 24-2
Overview for SIP Trunk Encryption, page 24-3
Secure Gateway and Trunk Configuration Checklist, page 24-4
24-6
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 24 Configuring Encryption for Gateways and Trunks
Where to Find More Information
•
•
Considerations for Configuring IPSec in the Network Infrastructure, page 24-5
Considerations for Configuring IPSec Between Cisco Unified Communications Manager and the
Related Cisco Documentation
•
Cisco Unified Communications Operating System Administration Guide
•
Media and Signaling Authentication and Encryption Feature for Cisco IOS MGCP Gateways
•
•
Cisco IOS Security Configuration Guide, Release 12.2 (or later)
Voice and Video Enabled IPSec Virtual Private Networks Solution Reference Network Design Guide
OL-24964-01
Cisco Unified Communications Manager Security Guide
24-7
Where to Find More Information
Chapter 24 Configuring Encryption for Gateways and Trunks
24-8
Cisco Unified Communications Manager Security Guide
OL-24964-01
C H A P T E R
25
Configuring the SIP Trunk Security Profile
This chapter contains information on the following topics:
•
SIP Trunk Security Profile Overview, page 25-1
•
•
•
•
•
•
•
•
Configuration Tips for SIP Trunk Security Profile, page 25-1
Finding a SIP Trunk Security Profile, page 25-2
Configuring the SIP Trunk Security Profile, page 25-3
SIP Trunk Security Profile Configuration Settings, page 25-3
Applying a SIP Trunk Security Profile, page 25-8
Synchronizing a SIP Trunk Security Profile with Affected SIP Trunks, page 25-9
Deleting a SIP Trunk Security Profile, page 25-9
Where to Find More Information, page 25-10
SIP Trunk Security Profile Overview
Cisco Unified Communications Manager Administration groups security-related settings for the SIP trunk to allow you to assign a single security profile to multiple SIP trunks. Security-related settings include device security mode, digest authentication, and incoming/outgoing transport type settings. You apply the configured settings to the SIP trunk when you choose the security profile in the Trunk
Configuration window.
Installing Cisco Unified Communications Manager provides a predefined, nonsecure SIP trunk security profile for autoregistration. To enable security features for a SIP trunk, configure a new security profile and apply it to the SIP trunk. If the trunk does not support security, choose a nonsecure profile.
Only security features that the SIP trunk supports display in the security profile settings window.
Configuration Tips for SIP Trunk Security Profile
Consider the following information when you configure SIP trunk security profiles in Cisco Unified
Communications Manager Administration:
•
•
When you are configuring a SIP trunk, you must select a security profile in the Trunk Configuration window. If the device does not support security, apply a nonsecure profile.
You cannot delete a security profile that is currently assigned to a device.
OL-24964-01
Cisco Unified Communications Manager Security Guide
25-1
Chapter 25 Configuring the SIP Trunk Security Profile
Finding a SIP Trunk Security Profile
•
•
•
If you change the settings in a security profile that is already assigned to a SIP trunk, the reconfigured settings apply to all SIP trunks that are assigned that profile.
You can rename security files that are assigned to devices. The SIP trunks that are assigned the old profile name and settings assume the new profile name and settings.
If you configured the device security mode prior to a Cisco Unified Communications Manager 5.0 or later upgrade, Cisco Unified Communications Manager creates a profile for the SIP trunk and applies the profile to the device.
Finding a SIP Trunk Security Profile
To find a SIP trunk security profile, perform the following procedure:
Procedure
Step 1
Step 2
Choose System > Security Profile > SIP Trunk Security Profile.
The Find and List window displays. Records from an active (prior) query may also display in the window.
•
•
•
To find all records in the database, ensure the dialog box is empty; go to
.
To filter or search records
From the drop-down list box, choose a search parameter.
From the drop-down list box, choose a search pattern.
Specify the appropriate search text, if applicable.
Note
To add additional search criteria, click the + button. When you add criteria, the system searches for a record that matches all criteria that you specify. To remove criteria, click the – button to remove the last added criterion or click the Clear Filter button to remove all added search criteria.
Step 3
Step 4
Click Find.
All matching records display. You can change the number of items that display on each page by choosing a different value from the Rows per Page drop-down list box.
From the list of records that display, click the link for the record that you want to view.
Note
To reverse the sort order, click the up or down arrow, if available, in the list header.
The window displays the item that you choose.
Additional Information
See the
“Related Topics” section on page 25-10 .
25-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 25 Configuring the SIP Trunk Security Profile
Configuring the SIP Trunk Security Profile
Configuring the SIP Trunk Security Profile
To add, update, or copy a SIP trunk security profile, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
In Cisco Unified Communications Manager Administration, choose System > Security Profile > SIP
Trunk Security Profile.
Perform one of the following tasks:
•
To add a new profile, click Add New in the Find window. (You can also display a profile and then click Add New.) The configuration window displays with the default settings for each field.
•
•
To copy an existing security profile, locate the appropriate profile as described in
Trunk Security Profile” section on page 25-2
and click the Copy icon for that record in the Copy column. (You can also display a profile and then click Copy.) The configuration window displays with the configured settings.
To update an existing profile, locate and display the appropriate security profile as described in
“Finding a SIP Trunk Security Profile” section on page 25-2 . The configuration window displays
with the current settings.
Enter the appropriate settings as described in
Click Save.
Next Steps
After you create the security profile, apply it to the trunk, as described in the
Security Profile” section on page 25-8
.
If you configured digest authentication for SIP trunks, you must configure the digest credentials in the
SIP Realm window for the trunk and Application User window for applications that are connected through the SIP trunk, if you have not already done so.
If you enabled application-level authorization for applications that are connected through the SIP trunk, you must configure the methods that are allowed for the application in the Application User window, if you have not already done so.
Additional Information
See the
“Related Topics” section on page 25-10
.
SIP Trunk Security Profile Configuration Settings
describes the settings for the SIP Trunk Security Profile.
•
For configuration tips, refer to the
“Configuration Tips for SIP Trunk Security Profile” section on page 25-1
.
•
For related information and procedures, see the “Related Topics” section on page 25-10
.
OL-24964-01
Cisco Unified Communications Manager Security Guide
25-3
Chapter 25 Configuring the SIP Trunk Security Profile
SIP Trunk Security Profile Configuration Settings
Table 25-1 SIP Trunk Security Profile Configuration Settings
Setting
Name
Description
Device Security Mode
Description
Enter a name for the security profile. When you save the new profile, the name displays in the SIP Trunk Security Profile drop-down list box in the
Trunk Configuration window.
Enter a description for the security profile. The description can include up to 50 characters in any language, but it cannot include double-quotes
("), percentage sign (%), ampersand (&), back-slash (\), or angle brackets
(<>).
From the drop-down list box, choose one of the following options:
•
•
Non Secure—No security features except image authentication apply. A TCP or UDP connection opens to Cisco Unified
Communications Manager.
Authenticated—Cisco Unified Communications Manager provides integrity and authentication for the trunk. A TLS connection that uses NULL/SHA opens.
•
Encrypted—Cisco Unified Communications Manager provides integrity, authentication, and signaling encryption for the trunk. A
TLS connection that uses AES128/SHA opens for signaling.
Incoming Transport Type When Device Security Mode is Non Secure, TCP+UDP specifies the transport type.
When Device Security Mode is Authenticated or Encrypted, TLS specifies the transport type.
Note
The Transport Layer Security (TLS) protocol secures the connection between Cisco Unified Communications Manager and the trunk.
Outgoing Transport Type From the drop-down list box, choose the outgoing transport mode.
When Device Security Mode is Non Secure, choose TCP or UDP.
When Device Security Mode is Authenticated or Encrypted, TLS specifies the transport type.
Note
TLS ensures signaling integrity, device authentication, and signaling encryption for SIP trunks.
Tip
You must use UDP as the outgoing transport type when connecting SIP trunks between Cisco Unified Communications
Manager systems and IOS gateways that do not support TCP connection reuse. See “Understanding Session Initiation Protocol
(SIP)” in the Cisco Unified Communications Manager System
Guide for more information.
25-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 25 Configuring the SIP Trunk Security Profile
SIP Trunk Security Profile Configuration Settings
Table 25-1
Setting
Enable Digest
Authentication
SIP Trunk Security Profile Configuration Settings (continued)
Nonce Validity Time
X.509 Subject Name
Description
Check this check box to enable digest authentication. If you check this check box, Cisco Unified Communications Manager challenges all SIP requests from the trunk.
Digest authentication does not provide device authentication, integrity or confidentiality. Choose a security mode of Authenticated or Encrypted to use these features.
For more information on digest authentication, see
and
Configuring Digest Authentication for the
.
Tip
Use digest authentication to authenticate SIP trunk users on trunks that are using TCP or UDP transport.
Enter the number of minutes (in seconds) that the nonce value is valid.
The default value equals 600 (10 minutes). When the time expires, Cisco
Unified Communications Manager generates a new value.
Note
A nonce value, a random number that supports digest authentication, gets used to calculate the MD5 hash of the digest authentication password.
This field applies if you configured TLS for the incoming and outgoing transport type.
For device authentication, enter the subject name of the X.509 certificate for the SIP trunk device. If you have a Cisco Unified Communications
Manager cluster or if you use SRV lookup for the TLS peer, a single trunk may resolve to multiple hosts, which results in multiple X.509 subject names for the trunk. If multiple X.509 subject names exist, enter one of the following characters to separate the names: space, comma, semicolon, or a colon.
You can enter up to 4096 characters in this field.
Tip
The subject name corresponds to the source connection TLS certificate. Ensure subject names are unique for each subject name and port. You cannot assign the same subject name and incoming port combination to different SIP trunks.
Example: SIP TLS trunk1 on port 5061 has X.509 Subject Names my_cm1, my_cm2. SIP TLS trunk2 on port 5071 has X.509 Subject
Names my_cm2, my_cm3. SIP TLS trunk3 on port 5061 can have
X.509 Subject Name my_ccm4 but cannot have X.509 Subject
Name my_cm1.
OL-24964-01
Cisco Unified Communications Manager Security Guide
25-5
Chapter 25 Configuring the SIP Trunk Security Profile
SIP Trunk Security Profile Configuration Settings
Table 25-1 SIP Trunk Security Profile Configuration Settings (continued)
Setting
Incoming Port
Enable Application Level
Authorization
Description
Choose the incoming port. Enter a value that is a unique port number from 1024-65535. The default port value for incoming TCP and UDP SIP messages specifies 5060. The default SIP secured port for incoming TLS messages specifies 5061. The value that you enter applies to all SIP trunks that use the profile.
Tip
All SIP trunks that use TLS can share the same incoming port; all
SIP trunks that use TCP + UDP can share the same incoming port. You cannot mix SIP TLS transport trunks with SIP non-TLS transport trunk types on the same port.
Tip
If the incoming packet rate on a SIP trunk UDP port from a single
IP address exceeds the configured SIP Trunk UDP Port Throttle
Threshold during normal traffic, reconfigure the threshold. When a SIP trunk and SIP station share the same incoming UDP port,
Cisco Unified Communications Manager throttles packets based on the higher of the two service parameter values. You must restart the Cisco CallManager service for changes to this parameter to take effect.
Application-level authorization applies to applications that are connected through the SIP trunk.
If you check this check box, you must also check the Enable Digest
Authentication check box and configure digest authentication for the trunk. Cisco Unified Communications Manager authenticates a SIP application user before checking the allowed application methods.
When application level authorization is enabled, trunk-level authorization occurs first, and application-level authorization then occurs, which means that Cisco Unified Communications Manager checks the methods that are authorized for the trunk (in this security profile) before the methods that are authorized for the SIP application user in the Application User Configuration window.
Tip
Consider using application-level authorization if you do not trust the identity of the application or if the application is not trusted on a particular trunk; that is, application requests may come from a different trunk than you expect.
For information on configuring digest authentication for the trunk, see the
Configuring Digest Authentication for the SIP Trunk, page 26-1
. For more information about authorization, refer to
and
Interactions, page 1-7 . For more information about configuring
application level authorization at the Application User Configuration window, see the Cisco Unified Communications Manager Administration
Guide.
25-6
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 25 Configuring the SIP Trunk Security Profile
SIP Trunk Security Profile Configuration Settings
Table 25-1
Accept Out-of-Dialog
Refer
Accept Unsolicited
Notification
SIP Trunk Security Profile Configuration Settings (continued)
Setting
Accept Presence
Subscription
Accept Replaces Header
Description
If you want Cisco Unified Communications Manager to accept presence subscription requests that come via the SIP trunk, check this check box.
If you checked the Enable Application Level Authorization check box, go to the Application User Configuration window and check the Accept
Presence Subscription check box for any application users that are authorized for this feature.
When application-level authorization is enabled, if you check the Accept
Presence Subscription check box for the application user but not for the trunk, a 403 error message gets sent to the SIP user agent that is connected to the trunk.
If you want Cisco Unified Communications Manager to accept incoming non-INVITE, Out-of-Dialog REFER requests that come via the SIP trunk, check this check box.
If you checked the Enable Application Level Authorization check box, go to the Application User Configuration window and check the Accept
Out-of-Dialog Refer check box for any application users that are authorized for this method.
If you want Cisco Unified Communications Manager to accept incoming non-INVITE, unsolicited notification messages that come via the SIP trunk, check this check box.
If you checked the Enable Application Level Authorization check box, go to the Application User Configuration window and check the Accept
Unsolicited Notification check box for any application users that are authorized for this method.
If you want Cisco Unified Communications Manager to accept new SIP dialogs, which have replaced existing SIP dialogs, check this check box.
If you checked the Enable Application Level Authorization check box, go to the Application User Configuration window and check the Accept
Header Replacement check box for any application users that are authorized for this method.
OL-24964-01
Cisco Unified Communications Manager Security Guide
25-7
Chapter 25 Configuring the SIP Trunk Security Profile
Applying a SIP Trunk Security Profile
Table 25-1 SIP Trunk Security Profile Configuration Settings (continued)
Setting
Transmit Security Status
SIP V.150 Outbound SDP
Offer Filtering
Description
If you want Cisco Unified Communications Manager to transmit the security icon status of a call from the associated SIP trunk to the SIP peer, check this check box.
Default: This box is not checked.
From the drop-down list box, select one of the following filter options:
•
Use Default Filter—The SIP trunk uses the default filter that is indicated in the SIP V.150 Outbound SDP Offer Filtering service parameter. To locate the service parameter, go to System > Service
Parameters > Clusterwide Parameters (Device-SIP) in Cisco
Unified Communications Manager Administration.
•
•
•
No Filtering—The SIP trunk performs no filtering of V.150 SDP lines in outbound offers.
Remove MER V.150—The SIP trunk removes V.150 MER SDP lines in outbound offers. Select this option to reduce ambiguity when the trunk is connected to a pre-MER V.150 Cisco Unified
Communications Manager.
Remove Pre-MER V.150—The SIP trunk removes any non-MER compliant V.150 lines in outbound offers. Select this option to reduce ambiguity when your cluster is contained in a network of MER compliant devices that are incapable of processing offers with pre-MER lines.
Applying a SIP Trunk Security Profile
You apply a SIP trunk security profile to the trunk in the Trunk Configuration window. To apply a security profile to a device, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Find the trunk, as described in the Cisco Unified Communications Manager Administration Guide.
After the Trunk Configuration window displays, locate the SIP Trunk Security Profile setting.
From the security profile drop-down list box, choose the security profile that applies to the device.
Click Save.
To reset the trunk, click Apply Config.
Next Steps
If you applied a profile enabling digest authentication for SIP trunks, you must configure the digest credentials in the SIP Realm window for the trunk. See
“Configuring a SIP Realm” section on page 26-4
.
If you applied a profile enabling application-level authorization, you must configure the digest credentials and allowed authorization methods in the Application User window, if you have not already done so.
25-8
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 25 Configuring the SIP Trunk Security Profile
Synchronizing a SIP Trunk Security Profile with Affected SIP Trunks
Additional Information
See the
“Related Topics” section on page 25-10
.
Synchronizing a SIP Trunk Security Profile with Affected SIP
Trunks
To synchronize SIP trunks with a SIP Trunk Security Profile that has undergone configuration changes, perform the following procedure, which will apply any outstanding configuration settings in the least-intrusive manner possible. (For example, you may not need to perform a reset/restart on some affected devices.)
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Choose System > Security Profile > SIP Trunk Security Profile.
The Find and List Phone SIP trunk security profiles window displays.
Choose the search criteria to use.
Click Find.
The window displays a list of SIP trunk security profiles that match the search criteria.
Click the SIP trunk security profile to which you want to synchronize applicable SIP trunks. The SIP
Trunk Security Profile Configuration window displays.
Make any additional configuration changes.
Click Save.
Click Apply Config.
The Apply Configuration Information dialog displays.
Click OK.
Additional Information
See the
“Related Topics” section on page 25-10
.
Deleting a SIP Trunk Security Profile
This section describes how to delete a SIP trunk security profile from the Cisco Unified Communications
Manager database.
Before You Begin
Before you can delete a security profile from Cisco Unified Communications Manager Administration, you must apply a different profile to the devices or delete all devices that use the profile. To find out which devices use the profile, choose Dependency Records from the Related Links drop-down list box in the SIP Trunk Security Profile Configuration window and click Go.
OL-24964-01
Cisco Unified Communications Manager Security Guide
25-9
Chapter 25 Configuring the SIP Trunk Security Profile
Where to Find More Information
If the dependency records feature is not enabled for the system, the dependency records summary window displays a message that shows the action that you can take to enable the dependency records; the message also displays information about high CPU consumption that is related to the dependency records feature. For more information about dependency records, refer to the Cisco Unified
Communications Manager System Guide.
Procedure
Step 1
Step 2
Step 3
Perform one of the following tasks:
•
To delete multiple security profiles, perform one of these tasks in the Find and List window:
–
Check the check boxes next to the security profiles that you want to delete; then, click Delete
Selected.
•
–
You can delete all configurable records for this selection by clicking Select All and then clicking
Delete Selected.
To delete a single security profile, perform one of these tasks in the Find and List window:
–
–
Check the check box next to the security profile that you want to delete; then, click Delete
Selected.
Click the Name link for the security profile. After the specific Security Profile Configuration window displays, click Delete Selected.
When prompted to confirm the delete operation, click OK to delete or Cancel to cancel the delete operation.
Additional Information
See the
“Related Topics” section on page 25-10 .
Where to Find More Information
•
•
•
•
•
•
Related Topics
•
SIP Trunk Security Profile Overview, page 25-1
Configuration Tips for SIP Trunk Security Profile, page 25-1
Finding a SIP Trunk Security Profile, page 25-2
•
Configuring the SIP Trunk Security Profile, page 25-3
SIP Trunk Security Profile Configuration Settings, page 25-3
•
•
•
Applying a SIP Trunk Security Profile, page 25-8
Synchronizing a SIP Trunk Security Profile with Affected SIP Trunks, page 25-9
Deleting a SIP Trunk Security Profile, page 25-9
Digest Authentication, page 1-19
Cisco Unified Communications Manager Security Guide
25-10 OL-24964-01
Chapter 25 Configuring the SIP Trunk Security Profile
Related Cisco Documentation
Cisco Unified Communications Manager Administration Guide
Cisco Unified Communications Manager System Guide
Where to Find More Information
OL-24964-01
Cisco Unified Communications Manager Security Guide
25-11
Where to Find More Information
Chapter 25 Configuring the SIP Trunk Security Profile
25-12
Cisco Unified Communications Manager Security Guide
OL-24964-01
C H A P T E R
26
Configuring Digest Authentication for the SIP
Trunk
When you configure digest authentication for SIP trunks, Cisco Unified Communications Manager challenges the identity of the SIP user agent when it receives a SIP request on the SIP trunk. The SIP user agent, in turn, can challenge the identity of Cisco Unified Communications Manager when Cisco
Unified Communications Manager sends a SIP request to the trunk. For additional information on how digest authentication works for SIP trunks, see the
“Digest Authentication” section on page 1-19
.
This chapter contains information on the following topics:
•
SIP Trunk Digest Authentication Configuration Checklist, page 26-1
•
•
•
•
Configuring Digest Authentication Enterprise Parameters, page 26-2
Configuring the Digest Credentials in the Application User Configuration Window, page 26-2
Application User Digest Credential Configuration Settings, page 26-3
Finding a SIP Realm, page 26-3
•
•
•
•
Configuring a SIP Realm, page 26-4
SIP Realm Configuration Settings, page 26-5
Deleting a SIP Realm, page 26-5
Where to Find More Information, page 26-6
SIP Trunk Digest Authentication Configuration Checklist
describes the tasks to configure digest authentication for SIP trunks.
Table 26-1 SIP Trunk Security Configuration Checklist
Configuration Steps
Step 1
Configure the SIP trunk security profiles; make sure that you check the Enable Digest Authentication check box.
Step 2
Apply a SIP trunk security profile to the trunk.
Related Procedures and Topics
•
Configuring the SIP Trunk Security
•
Digest Authentication, page 1-19
Applying a SIP Trunk Security Profile, page 25-8
Cisco Unified Communications Manager Security Guide
26-1 OL-24964-01
Chapter 26 Configuring Digest Authentication for the SIP Trunk
Configuring Digest Authentication Enterprise Parameters
Table 26-1 SIP Trunk Security Configuration Checklist (continued)
Configuration Steps
Step 3
Configure the enterprise parameter, Cluster ID, if not configured.
Step 4
Step 5
This parameter supports Cisco Unified Communications
Manager challenges to the identity of the SIP user agent that is sending a SIP request on the SIP trunk.
If Cisco Unified Communications Manager challenges the identity of SIP user agents that are sending SIP requests on the
SIP trunk, configure the digest credentials for the application user in the Application User Configuration window.
•
•
If Cisco Unified Communications Manager responds to challenges from a trunk peer, configure the SIP realm.
Related Procedures and Topics
Configuring Digest Authentication Enterprise
•
•
Configuring the Digest Credentials in the
Application User Configuration Window, page 26-2
Application User Digest Credential
Configuration Settings, page 26-3
Digest Authentication, page 1-19
Configuring a SIP Realm, page 26-4
•
SIP Realm Configuration Settings, page 26-5
Configuring Digest Authentication Enterprise Parameters
To configure the enterprise parameter, Cluster ID, for digest authentication, choose System >
Enterprise Parameters in Cisco Unified Communications Manager Administration. Locate the Cluster
ID parameter and update the value, as described in the Help for the parameter. This parameter supports
Cisco Unified Communications Manager challenges to the identity of the SIP user agent that is sending a SIP request on the SIP trunk.
Tip
To access the Help for the parameter, click the question mark that displays in the Enterprise Parameters
Configuration window or click the parameter link.
Configuring the Digest Credentials in the Application User
Configuration Window
If Cisco Unified Communications Manager challenges the identity of a SIP user agent, you must configure the digest credentials for the application user in the Application User Configuration window in Cisco Unified Communications Manager Administration. Cisco Unified Communications Manager uses these credentials to verify the identity of SIP user agents that are sending requests through the SIP trunk.
To configure the digest credentials for an application user, perform the following procedure:
Procedure
Step 1
Find the application user, as described in the Cisco Unified Communications Manager Administration
Guide.
26-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 26 Configuring Digest Authentication for the SIP Trunk
Application User Digest Credential Configuration Settings
Step 2
Step 3
Step 4
Click the application user link.
After the specific Application User Configuration window displays, enter the appropriate settings, as
Click Save.
Additional Information
See the
“Related Topics” section on page 26-6 .
Application User Digest Credential Configuration Settings
describes the settings for the digest credential settings in the Application User Configuration window in Cisco Unified Communications Manager Administration. For related information and procedures, see the
“Related Topics” section on page 26-6
.
Table 26-2 Digest Authentication Credentials
Setting Description
Digest Credentials Enter a string of alphanumeric characters.
Confirm Digest Credentials To confirm that you entered the digest credentials correctly, enter the credentials in this field.
Finding a SIP Realm
To find a SIP Realm, perform the following procedure:
Procedure
Step 1
Step 2
In Cisco Unified Communications Manager Administration, choose User Management > SIP Realm.
The Find and List window displays. Records from an active (prior) query may also display in the window.
•
•
•
To find all records in the database, ensure the dialog box is empty; go to
To filter or search records
From the first drop-down list box, choose a search parameter.
From the second drop-down list box, choose a search pattern.
Specify the appropriate search text, if applicable.
Note
To add additional search criteria, click the + button. When you add criteria, the system searches for a record that matches all criteria that you specify. To remove criteria, click the – button to remove the last added criterion or click the Clear Filter button to remove all added search criteria.
Step 3
Click Find.
OL-24964-01
Cisco Unified Communications Manager Security Guide
26-3
Chapter 26 Configuring Digest Authentication for the SIP Trunk
Configuring a SIP Realm
Step 4
All matching records display. You can change the number of items that display on each page by choosing a different value from the Rows per Page drop-down list box.
From the list of records that display, click the link for the record that you want to view.
Note
To reverse the sort order, click the up or down arrow, if available, in the list header.
The window displays the item that you choose.
Next Steps
If you have not already done so, configure the Cluster ID enterprise parameter, as described in the
“Configuring Digest Authentication Enterprise Parameters” section on page 26-2 .
Additional Information
See the
“Related Topics” section on page 26-6
.
Configuring a SIP Realm
If Cisco Unified Communications Manager responds to challenges from one or more trunk peers, you must configure SIP Realm for each SIP trunk user agent that can challenge Cisco Unified
Communications Manager.
To add or update a SIP Realm, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
In Cisco Unified Communications Manager Administration, choose User Management > SIP Realm.
Perform one of the following tasks:
•
To add a new SIP Realm, click Add New in the Find window. (You can also display a SIP Realm and then click Add New.) The configuration window displays with the default settings for each field.
•
•
To copy an existing record, locate the appropriate record as described in
display a SIP Realm and then click Copy.) The configuration window displays with the configured settings.
To update an existing record, locate and display the appropriate SIP Realm, as described in
“Finding a SIP Realm” section on page 26-3
. The configuration window displays with the current settings.
Enter the appropriate settings as described in
.
Click Save.
Perform the procedure for all realms that you must add or update.
Next Steps
To ensure that digest authentication is successful, verify that the same settings that you configured in
Cisco Unified Communications Manager are configured on the SIP user agent.
26-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 26 Configuring Digest Authentication for the SIP Trunk
Additional Information
See the
“Related Topics” section on page 26-6 .
SIP Realm Configuration Settings
SIP Realm Configuration Settings
The SIP Realm provides the trunk-side credentials when Cisco Unified Communications Manager gets challenged by a trunk peer.
describes the settings for the SIP Realm. For related information and procedures, see the
“Related Topics” section on page 26-6 .
Table 26-3 SIP Realm Security Profile
Setting Description
Realm
User
Enter the domain name for the realm that connects to the SIP trunk; for example, SIPProxy1_xyz.com. You can use alphanumeric characters, period, dash, underscore, and space.
Enter the user name for the SIP user agent in this realm; for example, enter the Cisco Unified Communications Manager server name. The SIP trunk uses this user name to challenge this Cisco Unified
Communications Manager.
Digest Credentials Enter the password that Cisco Unified Communications Manager uses to respond to a challenge for this realm and user.
Confirm Digest Credentials Re-enter the password for verification.
Deleting a SIP Realm
This section describes how to delete a SIP Realm from the Cisco Unified Communications Manager database.
Procedure
Step 1
Step 2
Find the SIP Realm by using the procedure in the
“Finding a SIP Realm” section on page 26-3 .
Perform one of the following tasks:
•
To delete multiple SIP Realms, perform one of these tasks in the Find and List window:
•
–
–
Check the check boxes next to the realms that you want to delete; then, click Delete Selected.
You can delete all configurable records for this selection by clicking Select All and then clicking
Delete Selected.
To delete a single SIP Realm, perform one of these tasks in the Find and List window:
–
Check the check box next to the realm that you want to delete; then, click Delete Selected.
–
Click the Name link for the realm. After the specific SIP Realm Configuration window displays, click Delete Selected.
OL-24964-01
Cisco Unified Communications Manager Security Guide
26-5
Chapter 26 Configuring Digest Authentication for the SIP Trunk
Where to Find More Information
Step 3
When prompted to confirm the delete operation, click OK to delete or Cancel to cancel the delete operation.
Additional Information
See the
“Related Topics” section on page 26-6
Where to Find More Information
Related Topics
•
Digest Authentication, page 1-19
•
SIP Trunk Digest Authentication Configuration Checklist, page 26-1
•
•
•
•
•
Configuring Digest Authentication Enterprise Parameters, page 26-2
Configuring the Digest Credentials in the Application User Configuration Window, page 26-2
Application User Digest Credential Configuration Settings, page 26-3
Finding a SIP Realm, page 26-3
•
•
Configuring a SIP Realm, page 26-4
SIP Realm Configuration Settings, page 26-5
Deleting a SIP Realm, page 26-5
26-6
Cisco Unified Communications Manager Security Guide
OL-24964-01
C H A P T E R
27
Configuring a Cisco Unified Mobility Advantage
Server Security Profile
This chapter contains information on the following topics:
•
•
Cisco Unified Mobility Advantage Server Security Profile Overview, page 27-1
Finding a Cisco Unified Mobility Advantage Server Security Profile, page 27-2
•
•
•
•
•
Configuring a Cisco Unified Mobility Advantage Server Security Profile, page 27-2
Cisco Unified Mobility Advantage Server Security Profile Configuration Settings, page 27-3
Applying a Cisco Unified Mobility Advantage Server Security Profile, page 27-4
Deleting a Cisco Unified Mobility Advantage Server Security Profile, page 27-5
Where to Find More Information, page 27-5
Cisco Unified Mobility Advantage Server Security Profile
Overview
Cisco Unified Communications Manager Administration groups security-related settings to allow you to assign a single security profile to multiple Mobile Communicator clients. Security-related settings include device security mode, incoming transport type, and X.509 subject name. Configuring a Cisco
Unified Mobility Advantage server security profile in Cisco Unified Communications Manager
Administration automatically applies this profile to all configured Mobile Communicator clients on that
Cisco Unified Communications Manager.
Only the security features that the Cisco Unified Mobility Advantage server supports display in the security profile settings window.
Note
You cannot configure Cisco Unified Mobility Advantage servers in Cisco Unified Communications
Manager Administration. For information on setting up a security profile for a Cisco Unified Mobility
Advantage server, refer to your Cisco Unified Mobility Advantage documentation. Make sure that the
Cisco Unified Mobility Advantage Security Profile you configure on Cisco Unified Communications
Manager matches the security profile on the Cisco Unified Mobility Advantage servers. For information on configuring a Cisco Unity Cisco Unified Mobility Advantage server security profile, see the Cisco
Unified Communications Manager Security Guide.
Cisco Unified Communications Manager Security Guide
27-1 OL-24964-01
Finding a Cisco Unified Mobility Advantage Server Security Profile
Chapter 27 Configuring a Cisco Unified Mobility Advantage Server Security Profile
Finding a Cisco Unified Mobility Advantage Server Security
Profile
To find a Cisco Unified Mobility Advantage server security profile, perform the following procedure:
Procedure
Step 1
Step 2
In Cisco Unified Communications Manager Administration, choose System > Security Profile >
CUMA Server Security Profile.
The Find and List CUMA Server Security Profile window displays. Records from an active (prior) query may also display in the window.
•
•
•
To find all records in the database, ensure the dialog box is empty; go to
.
To filter or search records
From the first drop-down list box, choose a search parameter.
From the second drop-down list box, choose a search pattern.
Specify the appropriate search text, if applicable.
Note
To add additional search criteria, click the + button. When you add criteria, the system searches for a record that matches all criteria that you specify. To remove criteria, click the – button to remove the last added criterion or click the Clear Filter button to remove all added search criteria.
Step 3
Step 4
Click Find.
All matching records display. You can change the number of items that display on each page by choosing a different value from the Rows per Page drop-down list box.
From the list of records that display, click the link for the record that you want to view.
Note
To reverse the sort order, click the up or down arrow, if available, in the list header.
The window displays the item that you choose.
Additional Information
See the
“Related Topics” section on page 27-5
.
Configuring a Cisco Unified Mobility Advantage Server Security
Profile
To add, update, or copy a security profile, perform the following procedure:
27-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 27 Configuring a Cisco Unified Mobility Advantage Server Security Profile
Cisco Unified Mobility Advantage Server Security Profile Configuration Settings
Procedure
Step 1
Step 2
Step 3
Step 4
In Cisco Unified Communications Manager Administration, choose System > Security Profile >
CUMA Server Security Profile.
Perform one of the following tasks:
•
To add a new profile, click Add New in the Find window and continue with
•
•
Unified Mobility Advantage Server Security Profile” section on page 27-2
, click the Copy button next to the security profile that you want to copy, and continue with
.
Unified Mobility Advantage Server Security Profile” section on page 27-2 and continue with
When you click Add New, the configuration window displays with the default settings for each field.
When you click Copy, the configuration window displays with the copied settings.
Enter the appropriate settings as described in
Click Save.
Additional Information
See the
“Related Topics” section on page 27-5 .
Cisco Unified Mobility Advantage Server Security Profile
Configuration Settings
describes the settings for the Cisco Unified Mobility Advantage Server security profiles.
•
For configuration tips, see the
“Finding a Cisco Unified Mobility Advantage Server Security
.
•
For related information and procedures, see the “Related Topics” section on page 27-5
.
Table 27-1 Cisco Unified Mobility Advantage Server Security Profile
Setting
Name
Description
Description
Enter a name for the security profile.
Tip
Include the device model in the security profile name to help you find the correct profile when you are searching for or updating a profile.
Enter a description for the security profile.The description can include up to 50 characters in any language, but it cannot include double-quotes ("), percentage sign (%), ampersand (&), back-slash (\), or angle brackets
(<>).
OL-24964-01
Cisco Unified Communications Manager Security Guide
27-3
Chapter 27 Configuring a Cisco Unified Mobility Advantage Server Security Profile
Applying a Cisco Unified Mobility Advantage Server Security Profile
Table 27-1
Setting
Device Security Mode
Transport Type
Cisco Unified Mobility Advantage Server Security Profile (continued)
X.509 Subject Name
Description
From the drop-down list box, choose one of the following options:
•
•
Non Secure—No security features except image authentication exist for the Cisco Unified Mobility Advantage server. A TCP connection opens to Cisco Unified Communications Manager.
Authenticated—Cisco Unified Communications Manager provides integrity and authentication for the Cisco Unified Mobility
Advantage server. A TLS connection that uses NULL/SHA opens for signaling.
•
Encrypted—Cisco Unified Communications Manager provides integrity, authentication, and encryption for the Cisco Unified
Mobility Advantage server. A TLS connection that uses
AES128/SHA opens for signaling, and SRTP carries the media for all mobile calls.
When Device Security Mode is Non Secure, choose the following option from the drop-down list box:
•
TCP—Choose the Transmission Control Protocol to ensure that packets get received in the same order as the order in which they are sent. This protocol ensures that no packets get dropped, but the protocol does not provide any security.
When Device Security Mode is Authenticated or Encrypted, TLS specifies the Transport Type. TLS provides signaling integrity, device authentication, and signaling encryption (encrypted mode only).
(Required for Authenticated or Encrypted Device Security Mode setting.) This field applies if you configured TLS as the transport type.
X.509 is an ITU Telecommunication Standardization Sector standard for
Public Key Infrastructure in cryptography. The subject name corresponds to the source connection TLS certificate.
If multiple X.509 subject names exist, enter one of the following characters to separate the names: space, comma, semicolon, or a colon.
You can enter up to 4096 characters in this field.
Applying a Cisco Unified Mobility Advantage Server Security
Profile
No “Device Security Profile” field exists on the device configuration window for a Mobile
Communicator client, which means that you do not have to manually apply the Cisco Unified Mobility
Advantage Server Security profile to a client.
Configuring a Cisco Unified Mobility Advantage server security profile in Cisco Unified
Communications Manager Administration automatically applies this profile to all configured Mobile
Communicator clients on that Cisco Unified Communications Manager.
27-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 27 Configuring a Cisco Unified Mobility Advantage Server Security Profile
Deleting a Cisco Unified Mobility Advantage Server Security Profile
Additional Information
See the
“Related Topics” section on page 27-5 .
Deleting a Cisco Unified Mobility Advantage Server Security
Profile
This section describes how to delete a Cisco Unified Mobility Advantage server security profile from the
Cisco Unified Communications Manager database.
Procedure
Step 1
Step 2
Step 3
Find the security profile by using the procedure in the
“Finding a Cisco Unified Mobility Advantage
Server Security Profile” section on page 27-2
.
To delete a security profile, perform the following task:
•
In the Find and List window, check the check box next to the appropriate security profile; then, click
Delete Selected.
When prompted to confirm the delete operation, click OK to delete or Cancel to cancel the delete operation.
Additional Information
See the
“Related Topics” section on page 27-5 .
Where to Find More Information
Related Topics
•
Cisco Unified Mobility Advantage Server Security Profile Overview, page 27-1
•
•
•
•
•
•
Finding a Cisco Unified Mobility Advantage Server Security Profile, page 27-2
Finding a Cisco Unified Mobility Advantage Server Security Profile, page 27-2
Configuring a Cisco Unified Mobility Advantage Server Security Profile, page 27-2
Cisco Unified Mobility Advantage Server Security Profile Configuration Settings, page 27-3
Applying a Cisco Unified Mobility Advantage Server Security Profile, page 27-4
Deleting a Cisco Unified Mobility Advantage Server Security Profile, page 27-5
OL-24964-01
Cisco Unified Communications Manager Security Guide
27-5
Where to Find More Information
Chapter 27 Configuring a Cisco Unified Mobility Advantage Server Security Profile
27-6
Cisco Unified Communications Manager Security Guide
OL-24964-01
C H A P T E R
28
Configuring FIPS 140-2 Mode
This chapter contains information about the following topics:
•
Overview of FIPS 140-2, page 28-1
•
•
•
•
Enabling FIPS 140-2 Mode, page 28-2
Disabling FIPS 140-2 Mode, page 28-3
Checking the Status of FIPS 140-2 Mode, page 28-4
Rebooting a Server in FIPS 140-2 Mode, page 28-4
Overview of FIPS 140-2
FIPS, or Federal Information Processing Standard, is a U.S. and Canadian government certification standard that defines requirements that cryptographic modules must follow.
Cisco Unified Communications Manager 8.6 is FIPS 140-2 compliant, in accordance with the U.S.
National Institute of Standards (NIST), and can operate in FIPS mode, level 1 compliance.
When you enable FIPS 140-2 mode, Cisco Unified Communications Manager reboots, runs certification self-tests at startup, performs the cryptographic modules integrity check, and then regenerates the keying materials. At this point, Cisco Unified Communications Manager operates in FIPS 140-2 mode.
Cisco Unified Communications Manager 8.6 meets FIPS requirements, including the following: it performs startup self-tests and a restricts to a list of approved cryptographic functions.
Cisco Unified Communications Manager FIPS mode uses the following FIPS 140-2 level 1 validated cryptographic modules:
•
•
•
Openssl 0.9.8l with FIPS Module 1.2
RSA CryptoJ 4.1
Red Hat Openssl
Red Hat Openswan
•
•
NSS
In Cisco Unified Communications Manager, you can perform the following FIPS-related tasks:
•
•
•
Enable FIPS 140-2 mode
Disable FIPS 140-2 mode
Check the status of FIPS 140-2 mode
OL-24964-01
Cisco Unified Communications Manager Security Guide
28-1
Chapter 28 Configuring FIPS 140-2 Mode
Enabling FIPS 140-2 Mode
Note
By default, Cisco Unified Communications Manager is in non-FIPS mode. The administrator must enable FIPS mode.
Enabling FIPS 140-2 Mode
FIPS 140-2 is enabled through the CLI. For more information, see Command Line Interface Reference
Guide for Cisco Unifed Communications Solutions.
Consider the following information before you enable FIPS 140-2 mode on Cisco Unified
Communications Manager:
•
•
In single server clusters, because certificates get regenerated, you need to run the CTL Client or apply the “Prepare Cluster for Rollback to pre 8.0” enterprise parameter before enabling FIPS mode.
If either of these steps is not performed, the administrator must manually delete the ITL File after enabling FIPS mode.
After FIPS mode is enabled on a server, please wait until the server reboots and the phones re-register successfully before enabling FIPS on the next server.
Caution
Before you enable FIPS mode, we strongly recommend that you perform a system backup. If FIPS checks fail at start-up, the system halts and requires a recovery CD to be restored.
To enable FIPS 140-2 Mode, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Start a CLI session.
For more information, see Starting a CLI Session in the Command Line Interface Reference Guide for
Cisco Unifed Communications Solutions.
In the CLI, enter utils fips enable
The following prompts appear:
Security Warning: The operation will regenerate certificates for
1)CallManager
2)Tomcat
3)IPsec
4)TVS
5)CAPF
6)SSH
Any third party CA signed certificates that have been uploaded for the above components will need to be re-uploaded.
If the system is operating in mixed mode, then the CTL client needs to be run again to update the CTL file.
******************************************************************************
This will change the system to FIPS mode and will reboot.
******************************************************************************
Do you want to continue (yes/no)?
Enter yes.
The following message appears:
Generating certificates...
28-2
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 28 Configuring FIPS 140-2 Mode
Setting FIPS mode in operating system.
FIPS mode enabled successfully.
********************************************************
It is highly recommended that after your system restarts that a system backup is performed.
********************************************************
The system will reboot in a few minutes.
Cisco Unified Communications Manager reboots automatically.
Disabling FIPS 140-2 Mode
Note
Certificates and SSH key are regenerated automatically, in accordance with FIPS requirements.
Note
If you have a single server cluster and applied the “Prepare Cluster for Rollback to pre 8.0” enterprise parameter prior to enabling FIPS 140-2 mode, disable this enterprise parameter after making sure that all the phones registered successfully to the server.
Note
In FIPS mode, Cisco Unified Communications Manager uses RedHat Openswan (FIPS validated) in place of Racoon (non-FIPS validated). If the security policies in Racoon contain functions that are not
FIPS approved, the CLI command will ask you to redefine the security policies with FIPS approved functions and abort. For more information, see IPsec Management in the Cisco Unified Communications
Operating System Administration Guide.
Disabling FIPS 140-2 Mode
FIPS 140-2 is disabled through the CLI. For more information, see the Command Line Interface
Reference Guide for Cisco Unifed Communications Solutions.
Consider the following information before you disable FIPS 140-2 mode on Cisco Unified
Communications Manager:
•
In single or multiple server clusters, we strongly recommend that you run the CTL Client. If the CTL
Client is not run on a single server cluster, the administrator must manually delete the ITL File after disabling FIPS mode.
•
In multiple server clusters, each server must be disabled separately, because FIPS mode is disabled not cluster-wide but rather per server basis.
To disable FIPS 140-2 mode, perform the following procedure:
Procedure
Step 1
Step 2
Start a CLI Session.
For more information, see the Starting a CLI Session section in the Command Line Interface Reference
Guide for Cisco Unifed Communications Solutions.
In the CLI, enter utils fips disable
Cisco Unified Communications Manager reboots and is restored to non-FIPS mode.
OL-24964-01
Cisco Unified Communications Manager Security Guide
28-3
Chapter 28 Configuring FIPS 140-2 Mode
Checking the Status of FIPS 140-2 Mode
Note
Certificates and SSH key are regenerated automatically, in accordance with FIPS requirements.
Checking the Status of FIPS 140-2 Mode
To confirm that FIPS 1402 mode is enabled, you can check the status from the CLI.
To check the status of FIPS 140-2 mode, perform the following procedure:
Procedure
Step 1
Step 2
Start a CLI Session.
For more information, see the Starting a CLI Session section in the Command Line Interface Reference
Guide for Cisco Unifed Communications Solutions.
In the CLI, enter utils fips status
The following message appears to confirm that FIPS 140-2 mode is enabled.
admin:utils fips status
The system is operating in FIPS mode. Self test status:
- S T A R T ---------------------
Executing FIPS selftests runlevel is N 3
Start time: Thu Apr 28 15:59:24 PDT 2011
NSS self tests passed.
Kernel Crypto tests passed.
Operating System OpenSSL self tests passed.
Openswan self tests passed.
OpenSSL self tests passed.
CryptoJ self tests passed...
Rebooting a Server in FIPS 140-2 Mode
When a Cisco Unified Communications Manager server reboots in FIPS 140-2 mode, it will trigger FIPS startup self-tests in each of the FIPS 140-2 modules after rebooting.
Caution
If any of these self-tests fail, the CUCM server halts.
Note
A Cisco Unified Communications Manager server is automatically rebooted when FIPS is enabled or disabled with the corresponding CLI command. A user can also initiate a reboot.
28-4
Cisco Unified Communications Manager Security Guide
OL-24964-01
Chapter 28 Configuring FIPS 140-2 Mode
Rebooting a Server in FIPS 140-2 Mode
Caution
If the startup self-test failed because of a transient error, restarting the Cisco Unified Communications
Manager server fixes the issue. However, if the startup self-test error persists, it indicates a critical problem in the FIPS module and the only option is to use a recovery CD.
OL-24964-01
Cisco Unified Communications Manager Security Guide
28-5
Rebooting a Server in FIPS 140-2 Mode
Chapter 28 Configuring FIPS 140-2 Mode
28-6
Cisco Unified Communications Manager Security Guide
OL-24964-01
A
authentication device
digest
interactions
overview
restrictions
with CTI/JTAPI/TAPI applications
authentication string entering on phone
with CAPF
with CTI/JTAPI/TAPI applications
authorization configuration settings (table) for SIP trunk
configuring for SIP trunk
interactions
overview
B
barge encryption restrictions with
security icons
C
Certificate Authority Proxy Function (CAPF)
authentication string
OL-24964-01
I N D E X
entering on phone
CAPF service
configuration checklist (table)
configuration settings (table) for CTI/JTAPI/TAPI applications
for phones
configuring an application user or end user CAPF
configuring in Cisco Unified Serviceability
deleting an application user or end user CAPF
finding an application user or end user CAPF
finding phones using LSC or authentication string
generating CAPF report
installing
interaction with Cisco Unified IP Phone
interaction with IPv6 addressing
overview
updating service parameters
using for phone certificate operations
viewing certificate operation status for application user or end user
with CTI/JTAPI/TAPI applications
overview
updating service parameters
certificates external CAs
Firefox certificate
Safari certificate
Certificate Signing Requests (CSRs)
Cisco Unified Communications Manager Security Guide
IN-1
Index
Cisco Unified IP Phone authentication string
configuration checklist (table) for security
configuration settings (table) for CAPF
configuration tips for phone security profiles
deleting CTL file
disabling the PC Port setting
disabling the PC Voice VLAN Access setting
disabling the Setting Access setting
encrypted configuration file
interaction with CAPF
secure conference support
security icons
understanding security
viewing security settings
computer telephony integration (CTI) configuration checklist (table) for securing
secure user groups
adding application users and end users
conference bridge conference list
configuration checklist (table) for security
configuration tips for security
configuring minimum Meet-Me security
configuring packet capture on a secure conference bridge
configuring security
minimum Meet-Me security level
security
security icons
security requirements
security restrictions
configuration file encryption
CTL client
CAPF service
Cisco Unified Communications Manager Security Guide
IN-2
cluster security mode updating
configuration checklist (table)
configuration settings (table)
configuration tips
configuring
CTL client
CTL Provider service
installing
overview
security mode verifying
security token changing password
configuring CTL client
setting the Smart Card service
size limit
uninstalling
upgrading
verifying
version
CTL file determining
deleting on phone
updating
CTL Provider activating service
D
device authentication configuration settings (table) for phone that is running SCCP
for phone that is running SIP
for SIP trunk
OL-24964-01
configuring for phones
configuring for SIP trunk
overview
digest authentication
associating digest user with a phone
cluster ID
configuration checklist (table) for phones
for SIP trunk
configuration settings (table) for application user digest credentials
for end user
for phone that is running SIP
for SIP realm
for SIP trunk
configuring a SIP realm
configuring digest credentials for application user
for end user
configuring for phones
configuring for SIP trunk
configuring service parameters
deleting a SIP realm
finding a SIP realm
overview
E
encrypted configuration file configuration checklist (table)
configuration settings (table) for manual key
configuration tips
configuring manual key distribution
disabling
enabling
entering symmetric key
manual key configuration checklist (table)
manual key distribution
OL-24964-01
Index
phone support
symmetric key encryption with public key
understanding
using symmetric key encryption w/public key
verifying
encryption configuration checklist (table) for gateways and trunks
configuration settings (table) for phone that is running SCCP
for phone that is running SIP
for SIP trunk
configuring for phones
configuring SRTP allowed check box
configuring with barge
for H.323/H.225/H.245 trunk
for H.323 gateway
for MGCP gateway
for SIP trunk
installing
interactions
overview
restrictions
signaling configuring for phones
with CTI/JTAPI/TAPI applications
etoken
configuring CTL client
F
file authentication configuring for phones
overview
Cisco Unified Communications Manager Security Guide
IN-3
Index
H
HTTPS overview
virtual directories (table)
with Firefox
I
image authentication overview
integrity overview
configuration checklist (table) for IPSec
configuring
gateway or trunk considerations
infrastructure considerations
recommendations
J
JTAPI configuration checklist (table) for securing
configuring security service parameters
L
locally significant certificate (LSC) finding phones using
with CTI/JTAPI/TAPI applications
M
media encryption (See also encryption) overview
MGCP gateway
IN-4
Cisco Unified Communications Manager Security Guide
configuration checklist (table) for security
configuring
N
NMAP scans running
P
phone hardening configuring
disabling the PC Port setting
disabling the PC Voice VLAN Access setting
disabling the Setting Access setting
phone security profile synchronizing configuration to applicable phones
port
CTL Provider
Ethernet phone
SIP secure
protected call
S
secure conference
Cisco Unified IP Phone support
conference bridge requirements
conference list
configuration checklist (table)
configuration tips
configuring minimum Meet-Me security
configuring packet capture
configuring secure conference bridge
CTI support
interactions
minimum Meet-Me security level
restrictions
OL-24964-01
security icons
security overview
trunks and gateways
secure indication tone
secure sockets layer (SSL)
with HTTPS
security authentication overview
authorization overview
best practices
certificate types
configuration checklist for authentication and encryption (table)
CTL client overview
encryption overview
external CAs
features list
HTTPS
interactions
rebooting the cluster
rebooting the server
resetting devices
restarting Cisco Unified Communications Manager service
restrictions
SCCP calls (table)
system requirements
tokens
where to find more information
security mode cluster configuring
verifying
security profile
OL-24964-01
Index
applying for SIP trunk
applying to Cisco Unified Mobility Advantage
Server
applying to phones
configuration settings (table)
for phones that is running SIP
for phone that is running SCCP
for SIP trunk
configuring for phones
deleting for Cisco Unified Mobility Advantage
deleting for SIP trunk
finding for Cisco Unified Mobility Advantage servers
finding for phones
finding for SIP trunk
overview for Cisco Unified Mobility Advantage
overview for phones
security token configuring CTL client
signaling authentication overview
signaling encryption overview
SIP Trunk security profile synchronizing configuration to applicable SIP trunks
Site Administrator Security Token (SAST)
SRST configuration checklist (table) for securing
configuration tips for securing
overview for securing
troubleshooting
certificate deleted on gateway
SRST reference
Cisco Unified Communications Manager Security Guide
IN-5
Index
configuration settings (table) for security
configuring
troubleshooting deleting secured reference
T
TAPI configuration checklist (table) for securing
configuring security service parameters
Tftp service
transport layer security (TLS)
transport security and real-time protocol (RTP)
and secure real-time protocol (SRTP)
configuration settings (table) for phone that is running SCCP
for SIP trunk
configuring for phones that are running SIP
TLS
troubleshooting deleting CTL file on phone
SRST certificate deleted on gateway
V
voice messaging
configuration checklist (table) for security
security overview
security requirements
voice messaging port applying a security profile
applying a security profile using the Wizard
IN-6
Cisco Unified Communications Manager Security Guide
configuration checklist (table) for security
security overview
OL-24964-01
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project