POLY SYSTEMS - MICROSOFT O365 TLS VERSION SUPPORT
- Severity
-
Medium
- Advisory ID
-
PLYGN18-07
- Initial public release
-
07/05/2018
- Last update
-
03/14/2022
- Category
-
Poly
Summary
Microsoft O365 Will Stop Support for TLS 1.0 and 1.1 in October of 2018
From Microsoft: “As of October 31, 2018, Office 365 will no longer support TLS 1.0 and 1.1. This means that Microsoft will not fix new issues that are found in clients, devices, or services that connect to Office 365 by using TLS 1.0 and 1.1.
Note This doesn't mean Office 365 will block TLS 1.0 and 1.1 connections. There is no official date for disabling or removing TLS 1.0 and 1.1 in the TLS service for customer connections. The eventual deprecation date will be determined by customer telemetry and is not yet known. After a decision is made, there will be an announcement six months in advance unless we become aware of a known compromise, in which case we may have to act in less than six months to protect customers who use the services.”
Once Office 365 deprecates support for these protocols, all communications to and from Office 365 servers will need to use TLS 1.2. See the list of Polycom products in the Impact and Risk section below that will no longer connect or be supported.
Devices will not register to any Skype for Business server if TLS is updated to TLS 1.2
If upgrading to TLS 1.2 using Skype for Business Servers (on-premises), additional devices listed below will no longer be able to register to Skype for Business or be supported. Compliance requirements such as Payment Card Industry Date Security Standard (PCI-DSS) will require that customers implement a more secure encryption protocol – TLS 1.1 or higher (TLS v1.2 is strongly encouraged) by June 30th 2018 in order to meet the PCI Data Security Standard (PCI DSS) for safeguarding payment data.
Resolution
Insert the Solution section information here.
SOLUTION
No direct solution.
WORKAROUND
If using these products, continue to use them with Skype for Business Server 2015
(on-premises) with out updating to TLS 1.2
Microsoft Links: Deprecating support for TLS 1.0 and 1.1
Poly Links:
Other Links:
Affected products
Identify the affected products for this issue.
|
Products |
Firmware |
Fix |
|---|---|---|
|
CX500 Phone |
N/A |
See Workaround |
|
CX600 Phone |
N/A |
See Workaround |
|
CX700 Phone |
N/A |
See Workaround |
|
CX3000 Conference Phone |
N/A |
See Workaround |
|
CX8000 Skype Room System |
N/A |
See Workaround |
Revision history
This document has been revised according to the following information.
|
Version |
Description |
Date |
|---|---|---|
|
2.0 |
Format changes |
03/14/2022 |
|
1.1 |
Updated information based on Microsoft changes |
11/09/2018 |
|
1.0 |
Initial Release |
07/05/2018 |
Additional information
Follow these links for additional information.
- Third-party security patches
-
Third-party security patches that are to be installed on systems running Poly software products should be applied in accordance with the customer's patch management policy.
- Contact
-
Any customer using an affected system who is concerned about this vulnerability within their deployment should contact Poly Technical Support – (888) 248-4143, (916) 928-7561, or visit the Poly Support Site.
- Security bulletin archive
-
To view released Security Bulletins, visit https://support.hp.com/security-bulletins.
It is strongly recommended that security related information being communicated to HP be encrypted using PGP, especially exploit information.
Legal information
©2022 Plantronics, Inc. All rights reserved.
TrademarksPoly, the propeller design, and the Poly logo are trademarks of Plantronics, Inc. All other trademarks are property of their respective owners. No portion hereof may be reproduced or transmitted in any form or by any means, for any purpose other than the recipient's personal use, without the express written permission of Poly.
DisclaimerWhile Poly uses reasonable efforts to include accurate and up-to-date information in this document, Poly makes no warranties or representations as to its accuracy. Poly assumes no liability or responsibility for any typographical errors, out of date information, or any errors or omissions in the content of this document. Poly reserves the right to change or update this document at any time. Individuals are solely responsible for verifying that they have and are using the most recent Technical Bulletin.
Limitation of LiabilityPoly and/or its respective suppliers make no representations about the suitability of the information contained in this document for any purpose. Information is provided "as is" without warranty of any kind and is subject to change without notice. The entire risk arising out of its use remains with the recipient. In no event shall Poly and/or its respective suppliers be liable for any direct, consequential, incidental, special, punitive, or other damages whatsoever (including without limitation, damages for loss of business profits, business interruption, or loss of business information), even if Poly has been advised of the possibility of such damages.
Enter a topic to search our knowledge library
What can we help you with?
Need Help?