End of support announcements

Over time, Diligent needs to end support for certain apps, products, and back-end technologies used in our software. End of support (EOS) is part of the overall end of life process (EOL).

If you have an on-premise, installed Diligent product that has reached EOS or EOL, the product may continue to work for a period of time. However, Diligent makes no guarantee that the product will continue to work, and is under no obligation to support EOS/EOL products or technologies.

Continued use of an EOS/EOL product is at your own risk.

Supported versions of Analytics

We support the current and immediately previous major versions of Analytics.

Where possible, we may support customers using older versions of Analytics. However, for the best level of service, we recommend that you upgrade to a supported version of Analytics.

Version Supported End of support date
19.x Yes  
18.x Yes  
17.x No December 4, 2025
16.x No February 3, 2025
15.x No November 3, 2023
14.x No June 15, 2022
13.x No November 19, 2020
12.x No November 2018
11.x and earlier No November 2017 and earlier

Removal of Microsoft Access Database Engine 2016

Microsoft Access Database Engine 2016 (ADE 2016) has been removed from Analytics, beginning with version 19, to align with Microsoft's end of support for the component (October 14, 2025). This change impacts you if you use Analytics for import or export connectivity with older Excel (*.xls) or Access files (*.mdb).

If you already have ADE 2016 installed on your computer, import and export connectivity with older Excel and Access files continues to work in Analytics 19 or previous versions. However, your IT department may require removal of ADE 2016 from your computer as a potential security vulnerability. If removal is required, import and export connectivity with older Excel and Access files will stop working in all installed versions of Analytics. You will need to move to an alternative method of working with *.xls or *.mdb files.

For more information, see Working with older Excel (*.xls) or Access files (*.mdb).

TLS security protocol and cipher suite

TLS (Transport Layer Security) is the network security protocol that Diligent uses to ensure secure communications between the Diligent One Platform and external applications, including those in our own product suite. A cipher suite is the collection of encryption algorithms that TLS uses to encrypt and decrypt data transmissions.

As part of maintaining the robust security posture of our products, we periodically update our implementation of TLS to stay current with evolving technological developments.

TLS 1.2

Change date: September 03, 2026

Effective from September 03, 2026, we are strengthening TLS 1.2 security for connections between on-premises Robots Agent and the Diligent One Platform. As part of this change, we are enforcing the AWS ELB security policy ELBSecurityPolicy-FS-1-2-Res-2020-10, which requires Perfect Forward Secrecy cipher suites.

Affected customers

If any of the following scenarios apply to you or your organization, action is required on your part:

  • Unsupported server operating system Robots Agent is installed on Windows Server 2012 R2 or older. See Robots Agent server requirements.

  • Windows Server 2016 environment not validated If your Windows Server 2016 environment is not validated for the required TLS 1.2 cipher suites, Robots Agent may stop communicating with the Diligent One Platform and scheduled automation may be affected.

  • TLS disabled on the server Regardless of server operating system, TLS 1.2 is disabled on the server where Robots Agent is installed.

  • Network proxy/firewall devices misconfigured Proxy/firewall devices on your organization's network are not configured to support TLS 1.2, or the required TLS cipher suite.

  • Unsupported local operating system Analytics is locally installed on Windows 7 or older. See Analytics local operating system.

Note

Work with your IT team to configure the server and proxy/firewall devices as required. Diligent Support can provide general guidance if you need assistance.

Robots Agent server requirements

  • Robots Agent servers must run Windows Server 2016 or later. Windows Server 2019 or later is recommended.

  • Windows Server 2012 R2 and earlier are not supported.

  • Windows Server 2016 environments should be validated to confirm support for the required TLS 1.2 cipher suites. Windows Server 2019 or later environments are expected to support the required configuration.

  • TLS 1.2 must be enabled on the server.

  • Ensure TLS 1.2 is not disabled in the Windows registry under:

    • HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client

  • Verify that:

    • Enabled is not set to 0

    • DisabledByDefault is not set to 1

  • For Windows Server 2016, run the Windows Server compatibility test script to verify cipher suite support, TLS 1.2 configuration, connectivity, and critical TLS updates before the enforcement date. Windows Server 2019 or later environments are expected to support the required configuration.

    There are two diagnostic tools to help you verify compatibility:

    • Tool 1 Windows Server Compatibility Test. This tool verifies that your Windows Server supports the required cipher suites and TLS 1.2 configuration.

      Steps to test

      1. Copy the Test-ELBSecurityPolicy.ps1 script and save it to a file in a local folder (such as, C:\Temp).

      2. Open PowerShell as Administrator.

      3. If required, allow script execution:

        Set-ExecutionPolicy Unrestricted -Scope Process

      4. Run the script:

        .\Test-ELBSecurityPolicy.ps1

      5. Review the output and the generated report file.

      The tool tests the following:

      • The available cipher suites on your Windows system.

      • TLS 1.2 configuration and registry settings.

      • Connectivity to Diligent endpoints using TLS 1.2.

      • Windows update status for critical TLS updates.

      The expected result is:

      [PASS] This system is compatible with ELBSecurityPolicy-FS-1-2-Res-2020-10

    If the compatibility test fails, remediate the TLS configuration or upgrade the server operating system.

  • Tool 2 Proxy/firewall detection and testing. This tool detects if a TLS-intercepting proxy is in use and whether it supports the required cipher suites.

    Steps to test

    1. Copy the Test-ProxyTLSSupport.ps1 script and save it to a file in a local folder (such as, C:\Temp).

    2. Open PowerShell as Administrator.

    3. Run the script:

      .\Test-ProxyTLSSupport.ps1

    4. Review the detailed output.

    The tool tests the following:

    • Detects proxy configuration (system, environment variables, manual).

    • Identifies if TLS interception occurs.

    • Tests cipher suite negotiation through the proxy.

    • Verifies compatibility with Diligent endpoints.

Proxy and firewall requirements

If your organization uses a direct internet connection or a transparent proxy, no additional proxy changes are required.

If your organization uses a TLS-intercepting proxy or firewall for SSL/TLS inspection, that device must also support TLS 1.2 and at least one of the following cipher suites:

  • TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

  • TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

  • TLS_DHE_RSA_WITH_AES_128_GCM_SHA256

  • TLS_DHE_RSA_WITH_AES_256_GCM_SHA384

Unsupported cipher suites

Cipher suites without Forward Secrecy, including suites that use static RSA key exchange, are no longer accepted.

Impact

If the server or proxy/firewall does not meet these requirements after ELBSecurityPolicy-FS-1-2-Res-2020-1 is enforced, Robots Agent will no longer be able to communicate with the Diligent One Platform, and scheduled automation that depends on the agent may stop working.

Support

Work with your IT team to validate and update your environment as needed. Diligent Support can provide general guidance to help troubleshoot any issues identified.

Analytics local operating system

If you have Analytics installed on Windows 7 or older, you need to upgrade your computer operating system if you want to run any ACLScript command or other process that communicates with the Diligent One Platform. Supported operating systems for Analytics are Windows 10 and 11.

TLS 1.0 and 1.1

End of support date: January 31, 2021

For your security, as of January 31, 2021, ACL versions 11.x or older may cease to work due to critical security improvements that ACL 11.x may not support.

We recommend that anyone still using ACL 11.x upgrades to the latest version as soon as possible so that their work is not interrupted.

We'd also like to remind customers that Diligent policy is to support the current and previous major versions of ACL. ACL 11.x has not been supported since the release of ACL Analytics 13.

Background

Across the industry, technology companies are taking action to secure vulnerabilities by dropping support of the older encryption protocols, TLS 1.0 and 1.1 (for example, Transport Layer Security 1.0 and 1.1 disablement).

As of January 31, 2021, Diligent One Platform will no longer accept connections using TLS 1.0 and 1.1. All applications will need to communicate to Diligent One Platform using TLS 1.2+.

Impact

All applications that interact with Diligent One Platform must use TLS 1.2 or greater to connect:

  • Web browsers

  • ACL Analytics

  • Excel Add-in

  • Mobile Apps

  • Custom API Scripts

TLS 1.2 is supported by the product versions listed below. If you are using these versions of software or later, dropping support of TLS 1.0/1.1 will have no impact:

If you are using a version of ACL or AX older than those listed above, we recommend you upgrade to a supported version as soon as possible.

If your security policies won't allow you to upgrade from ACL 11

ACL Analytics version 11.x's activation is the same as the current versions of ACL (12-16). In other words, there is no difference between how ACL 11 activates and ACL 16 activates, other than ACL 11 uses TLS 1.0/1.1, while newer versions use updated TLS protocols. Please contact your Diligent representative if you would like clarification on the activation methodology.

Direct Link

Direct Link reached end of support on June 30, 2025. While your existing installation will continue to work for a period of time, we recommend migrating to the SAP connector to ensure compatibility, support, and improved performance.

Benefits of SAP connector

Benefits Description
Query building

  • Build complex queries with joins and filters using a clickable interface.

  • Queries are written in SQL, making scripts easier to read and maintain (compared to the Direct Link XML-based commands).
Optimized server resource usage

  • Data is retrieved in small batches, reducing load on the SAP server.

  • Minimizes the risk of timeouts or queries being canceled by SAP Basis.
Minimal script changes

  • SAP connector tables use the same field names and types as Direct Link.

  • Update only the import step; your existing analysis logic remains intact.
Modern, SAP-certified technology

  • Built with the latest SAP standards.

  • Certified for the latest S/4 HANA releases.

Prepare for end of support

  1. Contact your CSM (Customer Success Manager) to get access to the SAP connector.

  2. Install the SAP connector add-on on your SAP server. For more information, see Set up the ACL Connector for SAP.

  3. Set up the ACL Connector for SAP:

    1. Configure your SAP connection in Analytics. For more information, see Connecting to SAP.

    2. Update your scripts to use the new import command.

    3. Test your scripts to validate the results.

TLS security protocol

TLS (Transport Layer Security) is the network security protocol that Diligent uses to ensure secure communications between the Diligent One Platform and external applications, including those in our own product suite.

As part of maintaining the robust security posture of our products, we periodically update our implementation of TLS to stay current with evolving technological developments.

TLS 1.2

Change date: October 2025

Effective October 2025, we are changing how TLS 1.2 on the Diligent One Platform communicates with the Robots Agent and Analytics. Specifically, we are removing support for TLS cipher suites (encryption algorithms) that are no longer considered secure by the industry.

This change affects only those customers who have the Robots Agent or Analytics installed on older, unsupported operating systems.

Robots Agent

If you have the Robots Agent installed on Windows Server 2012 R2 or older, you need to upgrade your server to a more recent, supported operating system (Windows Server 2016 or later).

Once the TLS 1.2 changes occur, instances of the Robots Agent on Windows Server 2012 R2 or older will no longer be able to communicate with the Diligent One Platform, or with the Robots app on the platform. The inability to communicate will prevent the Robots Agent from functioning correctly and any program of scheduled data analysis implemented by your organization will no longer run.

If you need help with the upgrade process, contact Diligent Support for assistance.

Analytics

If you have Analytics installed on Windows 7 or older, you need to upgrade your computer operating system if you want to run any ACLScript command or other process that communicates with the Diligent One Platform. Supported operating systems for Analytics are Windows 10 and 11.

TLS 1.0 and 1.1

End of support date: January 31, 2021

For your security, as of January 31, 2021, ACL versions 11.x or older may cease to work due to critical security improvements that ACL 11.x may not support.

We recommend that anyone still using ACL 11.x upgrades to the latest version as soon as possible so that their work is not interrupted.

We'd also like to remind customers that Diligent policy is to support the current and previous major versions of ACL. ACL 11.x has not been supported since the release of ACL Analytics13.

Background

Across the industry, technology companies are taking action to secure vulnerabilities by dropping support of the older encryption protocols, TLS 1.0 and 1.1 (for example, Transport Layer Security 1.0 and 1.1 disablement).

As of January 31, 2021, Diligent One Platform will no longer accept connections using TLS 1.0 and 1.1. All applications will need to communicate to Diligent One Platform using TLS 1.2.

Impact

All applications that interact with Diligent One Platform must use TLS 1.2 or greater to connect:

  • Web browsers

  • ACL Analytics

  • Excel Add-in

  • Mobile Apps

  • Custom API Scripts

TLS 1.2 is supported by the product versions listed below. If you are using these versions of software or later, dropping support of TLS 1.0/1.1 will have no impact:

If you are using a version of ACL or AX older than those listed above, we recommend you upgrade to a supported version as soon as possible.

If your security policies won't allow you to upgrade from ACL 11

ACL Analytics version 11.x's activation is the same as the current versions of ACL (12-16). In other words, there is no difference between how ACL 11 activates and ACL 16 activates, other than ACL 11 uses TLS 1.0/1.1, while newer versions use updated TLS protocols. Please contact your Diligent representative if you would like clarification on the activation methodology.

Analytics Exchange

Event Description Date
Last maintenance release Expected date for a final maintenance release. August 2021
End of support The last date after which product support will no longer be available. January 1, 2023

Why are we ending support of AX?

Many of our AX customers have successfully moved to the ACL Robotics platform. These customers have not only eliminated complex and costly upgrades, but are now enjoying the benefits of new script management features, and full access to Results workflows, visualizations, and storyboards. The decision to end support for AX will allow us to focus on innovating our Robotics platform faster, and ultimately deliver a better experience.

If you are still happily using AX, don't worry. You can continue to use AX until the end of support date, but we recommend that you contact your Diligent representative to create a plan to migrate to ACL Robotics as soon as possible.

Can I still perform my data analytics on-premise with ACL Robotics?

Your organizational data can still stay on-premise with ACL Robotics. ACL Robotics includes access to the cloud-based Results and Storyboards apps for remediating and visualizing your data analytic results, but using these components is optional.

The difference is that program, script, and user management are in the Diligent One cloud platform. This eliminates the need for lengthy upgrades for new functionality.

Note that Diligent One is FedRAMP and SOC 2 certified.

Resources for moving from AX to Robotics:

  1. Watch Level up from AX to ACL Robotics. This on-demand webinar covers the benefits of migration, what you need to know before getting started, and how Diligent can help.
  2. Get ready to migrate. Read the Analytics Exchange to Robots migration guide.

Rsam version 9.2

Event Description Date
End of support announcement The date we announced the end-of-support plans. September 18, 2020
Last maintenance release The final release in this stream of Rsam. December 22, 2020
End of software maintenance After this date, Diligent will no longer provide features, fixes, or security updates. March 1, 2021
End of support The last date after which product support will no longer be available. July 1, 2021

We encourage you to upgrade to version 10 of Rsam to take advantage of new features and other enhancements that will make your Rsam experience even better. To learn more about version 10, see Rsam Help. To get started upgrading, contact Support or your account rep.

Internet Explorer

End of support date: September 1, 2021

In light of Microsoft announcing end of support plans for Internet Explorer 11 on Microsoft 365, effective September 1, 2021, the Internet Explorer browser is no longer supported by Diligent.

Microsoft discouraged the use of Internet Explorer as a default browser. To allow us to continue to take advantage of modern web standards to deliver improved functionality, security, and the best possible user experience across all of our products, we have ended support for Internet Explorer meaning that as of September 1, 2021 we no longer fix bugs and limitations that are specific to Internet Explorer.