Introduction

About this update

This update applies to AWS2-hosted customers only and provides clarification on how platform APIs operate with respect to TLS versions, along with our migration expectations.

As previously communicated, including as part of platform releases in May 2025, the platform provides two integration endpoints, aligned to different TLS versions. These endpoints operate in parallel to support an orderly transition.

API Endpoints and TLS Versions

• TLS 1.2 (current endpoint – supported until 31 December 2026)
  https://itouch.vision/integration/806/

• TLS 1.3 (new endpoint – target standard)
  https://service.itouchvision.com/integration/806/

The API functionality is identical across both endpoints; the difference relates solely to the transport security protocol used during connection establishment. Customers select the endpoint appropriate to their TLS capability.

Transport Security Roadmap – Key Points

• TLS 1.2 will remain supported until 31 December 2026
• TLS 1.3 is the required target standard for all customers
• Any new integrations or major upgrades should be implemented against TLS 1.3
• TLS 1.2 should now be treated as a temporary compatibility measure, not a long‑term standard.

Why Migration to TLS 1.3 Is Necessary

• TLS 1.3 is the current protocol standard and reflects modern security baselines
• It removes older legacy negotiation and cryptographic mechanisms
• It improves efficiency through a simplified handshake process
• It aligns platform integrations with current security, interoperability, and lifecycle expectations

What This Means in Practice

• Customers who currently depend on TLS 1.2 have additional time to complete infrastructure and application changes
• Migration planning should continue now rather than being deferred until the end of the support period
• TLS 1.2 support beyond 31 December 2026 should not be assumed
• Delaying migration increases delivery risk, particularly where changes are required across servers, middleware, proxies, operating systems, or third‑party integration layers

Recommended Actions

• Review all systems that establish secure outbound connections to the platform APIs
• Confirm TLS 1.3 support across application runtimes, servers, gateways, proxies, firewalls, and inspection devices
• Complete testing in non‑production environments before progressing to live implementation
• Plan to complete migration well in advance of the TLS 1.2 retirement date

We are maintaining TLS 1.2 support during this transition period to allow for customer implementation lead times. However, the long‑term platform standard is TLS 1.3, and AWS2 customers should continue to align all integrations to that target.

If technical support is required during testing, validation, or migration planning, our team is available to assist.