Cisco 7921G Administration Guide - Page 23

Feature, Description, Cisco Unified IP Phone 7921G supports only the Secure Hash

Page 23 highlights

Chapter 1 Overview of the Cisco Unified Wireless IP Phone 7921G Understanding Security Features for Cisco Unified IP Phones OL-15985-01 Table 1-2 Overview of Security Features (continued) Feature Device authentication File authentication Signaling Authentication Manufacturing installed certificate Secure SRST reference Media encryption Signaling encryption CAPF (Certificate Authority Proxy Function) Security profiles Encrypted configuration files Description Occurs between the Cisco Unified Communications Manager server and the phone when each entity accepts the certificate of the other entity. Determines whether a secure connection between the phone and a Cisco Unified Communications Manager should occur, and, if necessary, creates a secure signaling path between the entities using TLS protocol. Cisco Unified Communications Manager will not register phones unless authenticated by the Cisco Unified Communications Manager. Cisco Unified IP Phone 7921G supports only the Secure Hash Algorithm-1 (SHA-1) signature algorithm. 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. 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 a 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 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 it 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 non-secure, authenticated, or encrypted. See the "Understanding Security Profiles" section on page 1-10 for more information. Lets you ensure the privacy of phone configuration files. Cisco Unified Wireless IP Phone 7921G Administration Guide for Cisco Unified Communications Manager Release 7.0 1-9

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234

1-9
Cisco Unified Wireless IP Phone 7921G Administration Guide for Cisco Unified Communications Manager Release 7.0
OL-15985-01
Chapter 1
Overview of the Cisco Unified Wireless IP Phone 7921G
Understanding Security Features for Cisco Unified IP Phones
Device authentication
Occurs between the Cisco Unified Communications Manager server
and the phone when each entity accepts the certificate of the other
entity. Determines whether a secure connection between the phone
and a Cisco
Unified
Communications Manager should occur, and, if
necessary, creates a secure signaling path between the entities using
TLS protocol. Cisco Unified Communications Manager will not
register phones unless authenticated by the Cisco Unified
Communications Manager.
Cisco Unified IP Phone 7921G supports only the Secure Hash
Algorithm-1 (SHA-1) signature algorithm.
File authentication
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. Files that fail authentication are not
written to Flash memory on the phone. The phone rejects such files
without further processing.
Signaling Authentication
Uses the TLS protocol to validate that no tampering has occurred to
signaling packets during transmission.
Manufacturing installed
certificate
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.
Secure SRST reference
After you configure a 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.
Media encryption
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.
Signaling encryption
Ensures that all SCCP signaling messages that are sent between the
device and the Cisco Unified Communications Manager server are
encrypted.
CAPF (Certificate Authority
Proxy Function)
Implements parts of the certificate generation procedure that are too
processing-intensive for the phone, and it 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.
Security profiles
Defines whether the phone is non-secure, authenticated, or
encrypted. See the
“Understanding Security Profiles” section on
page 1-10
for more information.
Encrypted configuration files
Lets you ensure the privacy of phone configuration files.
Table 1-2
Overview of Security Features (continued)
Feature
Description