Effective March 1, 2026, Numetric will no longer support any data connections utilizing TLS 1.2 cryptographic protocols. All data connections must utilize TS 1.3 to establish a secure data connection with Numetric’s data platform.

TLS is a cryptographic protocol that provides authentication and data encryption between different endpoints (e.g., a client connecting to a web server). New versions of each protocol have been released to address vulnerabilities and support the strongest and most secure cipher suites and algorithms. As a best practice, you should configure your servers to support the latest protocol versions to ensure you are using only the strongest algorithms and ciphers, but equally as important is to disable the older versions.

Continuing to support old versions of the protocols can leave you vulnerable to downgrade attacks, where hackers force connections to your server to use older versions of the protocols that have known exploits. This can leave your encrypted connections (whether between a site visitor and your web server, machine to machine, etc.) open to man-in-the-middle and other types of attacks. In 2020, Numetric discontinued support for TLS 1.1 and TLS 1.0 protocols.

To test your individual browser/operating system compliance with this security standard, you can navigate to cloud.beta-numetric.com. If the standard login page displays, your operating system and browser are compliant. Accessing cloud.beta-numetric.com with a non-compliant browser or operating system will result in an error message.

If your agency utilizes an API, or other data connection with AASHTOWare Safety/Numetric, this can be tested by using api.beta-numetric.com. A compliant configuration will receive a valid HTTP response from the API. A non-compliant configuration will result in TLS or SSL handshake errors.