Overview

This article explains Extensiv's upcoming enforcement of Transport Layer Security (TLS) 1.2 (or higher) for connections to Extensiv products, and what you can do to prepare.

Why the enforcement matters

TLS encrypts data in transit between your systems and Extensiv. Requiring TLS 1.2 helps protect your data, aligns with current industry security standards, and reduces exposure from older, weaker protocols.

Most modern devices and applications automatically use the highest TLS version both sides support. In many environments, no action is required.

When you might hear from Extensiv

If Extensiv detects traffic from your company's IP address using a protocol older than TLS 1.2, we may notify you.

Keep these limitations in mind:

• We can't identify a specific device, user, or workstation.
• We can share the type of client that connected (e.g., Windows desktop, Linux desktop, or Android, which may be a phone or a warehouse scanner OS, and similar categories).
  •  Note: Not all devices send identifying information.
• Each customer environment is unique. We can't provide step-by-step instructions for every network, device fleet, or custom integration.
   

Planning your next steps

To prepare for TLS 1.2 enforcement:

1. Review any notification from Extensiv, including the client type reported in the notification.

• If you need clarification about a notification you've received, contact Extensiv Support or your Customer Success Manager. 
• For environment-specific remediation guidance, work directly with your IT team.

2. Confirm your systems use TLS 1.2 or higher before the enforcement date.

• Identify systems that may still use an older TLS version, such as legacy operating systems, scanners, custom applications, or integrations.
• Plan updates or configuration changes before applying them.

3. The appropriate next steps depend on the type of client involved. Use the guidance below as a starting point for discussions with your IT team.