|
|
Please provide road map for PQC capabilities for Adabas and Adabas add-ons
PQC Strategic Supplier RFI Questions
What is the core service type of the product you provide to JPMC?
What is the platform type of the product you provide to JPMC?
Which platform version(s) are you currently providing to JPMC?
What is the name of the interface associated with the product you provide to JPMC?
What type of interface does the product you provide to JPMC use?
What cryptographic protocol is used by the interface of the product you provide to JPMC?
What cryptographic function does the interface of the product perform?
If the interface cryptographic protocol is TLS, which platform version(s) have full feature parity with TLS 1.3?
If the interface cryptographic protocol is TLS, what is the release date for the platform version(s) with TLS 1.3 full feature parity?
If the interface cryptographic protocol is TLS, what TLS interface supported ciphers are available? (Optional)
If the interface cryptographic protocol is IPSec, which IKE versions are supported?
Which platform version(s) are considered PQC Safe Candidates?
What is the release date for the platform version(s) considered PQC Safe Candidates?
What is the development state of the platform version(s) considered PQC Safe Candidates?
What PQC algorithms are supported by the product you provide to JPMC?
please see attached IBM roadmap
Answer has been given.
New status: Done.
Hello Ben,
for Adabas on z/OS and Add-Ons, including Entire Net-Work, we do not implement any cryptographic function whatsoever directly.
For Transport Layer Security (TLS), we rely on IBM's AT-TLS.
This concerns the Net-Work components. However, configuration only.
No implementation / cryptography within our code.
For Adabas Encryption for z/OS (AEZ), we likewise fully rely on IBM's internal cryptographic implementation.
AEZ is calling IBM z/OS low-level I/O routines.
This is fully transparent to AEZ.
So, in both cases it is up to IBM's AT-TLS and/or ICSF.
HTH
Kind Regards,
Jürgen