Jun 7, 2024 · A recent vulnerability in the supported TLS ciphers has been identified by the FAPI Working Group. The Consumer Data Standards inherit adoption of the same ciphers.

Jul 1, 2024 · There are some relevant TLS considerations in the FAPI profile, so it is proposed that the standard is changed to clearly adopt section 8.5 of FAPI 1 Advanced, and then further …

Jan 16, 2020 · There has been a request from a number of participants in the phase 2 implementation that the requirement for security end points marked as requiring TLS to modify …

Jul 25, 2024 · + Endpoints specified as MTLS MUST be configured according to the [Certificate Trust Model] in the [Certificate Management] section. + Endpoints specified as TLS MUST be …

Nov 14, 2019 · If intended, we would need to customise our security infrastructure to support TLS-MA instead of TLS. To align with standard approaches, and the approach used for the registry …

Oct 9, 2018 · The recommendations for Secure Use of Transport Layer Security in BCP195 shall be followed, with the following additional requirements: - TLS version 1.2 or later shall be used …

Dec 10, 2019 · The authorize end point is not intended to use the CDR CA root for its TLS certificate and this is stated in the errata. It will be corrected in the next standards update.

NAB supports the proposed new approach for the TLS certificate requirement for both Data Holders and Accredited Data Recipients. For the DH error response described under point 3 of …

We are keen to understand how communication between participants and the register is secured. We assume that: Register discovery APIs will be secured using TLS-MA with a register issued …

The client registration endpoint MUST be protected by transport-layer security (TLS 1.2 or better) The transport layer MUST be mutually authenticated using certificates chaining to the …