Cisco CP-7975G Administration Guide - Page 29

Feature, Description, Configuring Security on the Cisco Unified, IP Phone, - load file

Page 29 highlights

Chapter 1 An Overview of the Cisco Unified IP Phone Understanding Security Features for Cisco Unified IP Phones Table 1-4 Overview of Security Features Feature Image authentication Customer-site certificate installation Device authentication File authentication Signaling Authentication Manufacturing installed certificate Secure SRST reference Media encryption Signaling encryption CAPF (Certificate Authority Proxy Function) Security profiles Description Signed binary files (with the extension .sbn) prevent tampering with the firmware image before it is loaded on a phone. Tampering with the image causes a phone to fail the authentication process and reject the new image. Each Cisco Unified IP Phone requires a unique certificate for device authentication. Phones include a manufacturing installed certificate (MIC), but for additional security, you can specify in Cisco Unified Communications Manager Administration that a certificate be installed by using the CAPF (Certificate Authority Proxy Function). Alternatively, you can install an LSC from the Security Configuration menu on the phone. See Configuring Security on the Cisco Unified IP Phone, page 3-16 for more information. 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 does not register phones unless they can be authenticated by the Cisco Unified Communications Manager. 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 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 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 nonsecure, authenticated, encrypted, or protected. See Understanding Security Profiles, page 1-16 for more information. OL-23092-01 Cisco Unified IP Phone Administration Guide for Cisco Unified Communications Manager 8.5 1-15

  • 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
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266

1-15
Cisco Unified IP Phone Administration Guide for Cisco Unified Communications Manager 8.5
OL-23092-01
Chapter 1
An Overview of the Cisco Unified IP Phone
Understanding Security Features for Cisco Unified IP Phones
Table 1-4
Overview of Security Features
Feature
Description
Image authentication
Signed binary files (with the extension .sbn) prevent tampering with the firmware
image before it is loaded on a phone. Tampering with the image causes a phone to
fail the authentication process and reject the new image.
Customer-site certificate installation
Each Cisco Unified IP Phone requires a unique certificate for device
authentication. Phones include a manufacturing installed certificate (MIC), but for
additional security, you can specify in Cisco Unified Communications Manager
Administration that a certificate be installed by using the CAPF (Certificate
Authority Proxy Function). Alternatively, you can install an LSC from the Security
Configuration menu on the phone. See
Configuring Security on the Cisco Unified
IP Phone, page 3-16
for more information.
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 does not
register phones unless they can be authenticated by the
Cisco Unified Communications Manager.
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 and SIP 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 nonsecure, authenticated, encrypted, or protected.
See
Understanding Security Profiles, page 1-16
for more information.