Understanding Security Features for Cisco Unified IP Phones
Table 1-4
Overview of Security Features (continued)
Feature
File authentication
Signaling Authentication
Manufacturing installed
certificate
Secure SRST reference
Media encryption
Signaling encryption
CAPF (Certificate Authority
Proxy Function)
Security profiles
Encrypted configuration
files
Optional disabling of the
web server functionality for
a phone
Cisco Unified IP Phone Administration Guide for Cisco Unified Communications Manager 8.6 (SCCP and SIP)
1-14
Description
Validates digitally signed files that the phone downloads. The phone validates the signature to
make sure that file tampering did not occur after file creation. Files that fail authentication are
not written to Flash memory on the phone. The phone rejects such files without further
processing.
Uses the TLS protocol to validate that no tampering has occurred to signaling packets during
transmission.
Each Cisco Unified IP Phone contains a unique manufacturing installed certificate (MIC),
which is used for device authentication. The MIC is a permanent, unique proof of identity for
the phone, and allows Cisco Unified Communications Manager to authenticate the phone.
After you configure an SRST reference for security and then reset the dependent devices in
Cisco Unified Communications Manager Administration, the TFTP server adds the SRST
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 router.
Uses SRTP to ensure that the media streams between supported devices proves secure and that
only the intended device receives and reads the data. 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.
Ensures that all SCCP and SIP signaling messages that are sent between the device and the
Cisco Unified Communications Manager server are encrypted.
Implements parts of the certificate generation procedure that are too processing-intensive for
the phone, and interacts with the phone for key generation and certificate installation. The
CAPF can be configured to request certificates from customer-specified certificate authorities
on behalf of the phone, or it can be configured to generate certificates locally.
Defines whether the phone is nonsecure, authenticated, encrypted, or protected. See
Understanding Security Profiles, page 1-15
Lets you ensure the privacy of phone configuration files.
You can prevent access to a phone's web page, which displays a variety of operational
statistics for the phone.
Chapter 1
An Overview of the Cisco Unified IP Phones
for more information.
OL-23091-01