Polycom 1500/1800/2000/4000 manual Non-hashed Passwords, Self-signed Certificate Creation

Ultra Secure Mode

Non-hashed Passwords

All non-hashed passwords are stored encrypted as set out in the table below.

Non-hashed Passwords - Encryption

Connection	Storage type	Previous	From
		Versions	Version 8.1
SNMPv3	Community permissions which are not	Non encrypted	AES 256
Two passwords: Authentication	the PW to connect to SNMP are not
/ Privacy	Saved Encrypted
Exchange	Non encrypted – Feature disabled in	Non encrypted	AES 256
	Ultra Secure Mode
RV v.35 serial ports – password	Reversible – AES_128 with 256 Bytes	AES 256	AES 256
for login	Key (2048 Bits)
H.323 authentication –	Reversible – AES_128 with 256 Bytes	AES 256	AES 256
password	Key (2048 Bits)
SIP digest – password	Reversible – AES_128 with 256 Bytes	AES 256	AES 256
	Key (2048 Bits)

In compliance with UC APL requirements, PKI Self-signed Certificates are supported for the both the Default Management and IP Network Services.

Amixture of Self-signed and CA-signed Certificates is supported, however a CA-signed certificate will always override a Self-signed Certificate.

Self-signed Certificate Creation

Self-signed Certificates are created during:

●Initial system start-up before any CA-signed Certificates have been installed.

●IP Network Services creation.

●Network Services updates that result in Host Name changes.

●Daily validity checks of Self-signed Certificates.

●Backup and Restore of the system configuration

Self-signed Certificate field values are automatically inserted when the certificate is created Self-signed Certificates are indicated in the Certification Repository - Issued By field.

Polycom®, Inc. 874