Use this grid to identify which Broadcom product release are compatible with PCI DSS standards. If maintenance is required:
Launch Mainframe Compatibility Main Page
The following grid contains a list of all Broadcom mainframe products and releases. The column values include:
| IN PROGRESS | The validation of the product is in progress. |
| NO | The release of this product will not be validated. |
| YES | The product has been certified and is compatible. |
| N/A | The compatibility does not apply. |
Product List
Please refer to the Product Lifecycle Page for additional information.Fix Category: CA.Function.PCI.DSS.V3.2
What product version is needed to support the requirement for running
TLS 1.1 or higher and certify this security/audit mandate?
CA Database Management Solutions for IMS for z/OS� is not certified for
PCI compliance, however, if you require a secure connection between
CA Database Management Solutions for IMS for z/OS - v20
and CA Datacom/AD - 15.0, use z/OS Application Transparent Transport
Layer Security (AT-TLS).
Fix Category: CA.Function.PCI.DSS.V3.2
Guidance:
A TPX customer must run TPX with security option turned on (Preferred
(preferred choice: SAF) to rensure that all users logged onto CA TPX
with credentials validated using a security call from CA TPX.
An alternative method would be to turned on USER security option in
CA TPX and code the appropriate CA TPX exits.
In addition, since CA TPX utilizes VTAM for all transmissions,
the customer should turned on VTAM session-level encryption.
VTAM utilizes Integrated Cryptographic Services Facility (ICSF)
for session level encryption. ICSF interfaces with CPACF, but will
not select CPACF for VTAM SLE because VTAM is secure key only.
VTAM SLE support is provided through the optional cryptographic
coprocessors, accessed using ICSF application program interfaces
(APIs).
Fix Category: CA.Function.PCI.DSS.V3.2
Guidance:
A TPX customer must run TPX with security option turned on (Preferred
(preferred choice: SAF) to rensure that all users logged onto CA TPX
with credentials validated using a security call from CA TPX.
An alternative method would be to turned on USER security option in
CA TPX and code the appropriate CA TPX exits.
In addition, since CA TPX utilizes VTAM for all transmissions,
the customer should turned on VTAM session-level encryption.
VTAM utilizes Integrated Cryptographic Services Facility (ICSF)
for session level encryption. ICSF interfaces with CPACF, but will
not select CPACF for VTAM SLE because VTAM is secure key only.
VTAM SLE support is provided through the optional cryptographic
coprocessors, accessed using ICSF application program interfaces
(APIs).
Fix Category: CA.Function.PCI.DSS.V3.2
CA Vantage SRM MVS: YES - HTTPS for DS8XXX support (Documented)
CA Vantage REST API server: YES (Documented)
CA Vantage Windows Client: N/A - Only through AT-TLS (Documented)
CA Vantage Web Client MTC-M: YES - Optional (Documented)
Fix Category: CA.Function.PCI.DSS.V3.2
CA Vantage SRM MVS: YES - HTTPS for DS8XXX support (Documented)
CA Vantage REST API server: YES (Documented)
CA Vantage Windows Client: N/A - Only through AT-TLS (Documented)
CA Vantage Web Client MTC-M: YES - Optional (Documented)
This page last updated 6 Feb 2026 03:00:23