Announcement of change to TLS support as of January 1, 2027

2BA is continuously working on improving its services. An important part of this is ensuring stable, reliable, and secure data exchange with our systems.

As part of this further development, 2BA supports TLS 1.3 and TLS 1.2, of which a portion of the currently allowed TLS 1.2 configurations are being phased out. In doing so, 2BA follows the guidelines of the National Cyber Security Centre (NCSC). More information on this can be found in the document TLS Guidelines 2025, which is available via the NCSC website. An overview of the recommended TLS configurations can be found on page 28 of this document (Appendix B: List of cipher suites).

As of January 1, 2027, 2BA will only support the TLS versions and cipher suites listed below.

TLS 1.2 (Sufficient)
• TLS_ECDHE_ECDSA_WITH_AES_128_CCM
• TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_256_CCM
• TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256

TLS 1.3 (Good)
• TLS_AES_256_GCM_SHA384
• TLS_CHACHA20_POLY1305_SHA256

TLS 1.3 (Sufficient)
• TLS_AES_128_CCM_SHA256
• TLS_AES_128_GCM_SHA256

We request all users and integration owners to check in a timely manner whether their applications, systems, and integrations support these protocols and cipher suites. If you have any doubts about this, please contact your PIM or ERP software vendor. This will prevent disruptions in communication with 2BA services after January 1, 2027.