Skip to main content
Founding Partner + 7-Day Trial
Back to docs
PQC-BANK-002PQC-BANK-003PQC-BANK-004PQC-BANK-005PQC-BANK-006HIGHPCI-DSS 4.0.1 · ANSI X9.143 (TR-31) · ANSI X9.24 · EU DORA · FS-ISAC

Banking TR-31/TR-34 Key Blocks, Mainframe ICSF & Open Banking FAPI 2.0

Severity: HIGH

Financial payment rails combine strict symmetric key-block hygiene with long-lived asymmetric PKI across ATMs, POS terminals, HSMs, IBM z/OS ICSF mainframes, and Open Banking APIs. CipherMap flags legacy DES/TDEA TR-31 Version A/B/C key headers (PQC-BANK-003), classical RSA-2048 CMS key transport in TR-34 / X9.24-2 Remote Key Loading and 64-bit ANSI X9.9/X9.19 Retail MACs (PQC-BANK-005), z/OS ICSF CSNB* classical token verbs, and Open Banking FAPI 2.0 / PSD3 profiles pinned exclusively to PS256 or ES256 without hybrid mTLS or post-quantum JWS agility (PQC-BANK-006).

Remediation checklist

  • Migrate legacy TR-31 Version A/B/C key blocks to Version D AES Key Derivation Binding and replace ANSI X9.9/X9.19 3DES MACs with AES-128/256-CMAC.
  • Plan ATM/POS TR-34 Remote Key Loading upgrades to hybrid ML-KEM-768 + RSA-OAEP-3072 CMS key transport and PKCS#11 v3.2 CKM_ML_KEM / CKM_ML_DSA HSM mechanisms.
  • Shield Open Banking FAPI 2.0 ingress gateways immediately with hybrid X25519MLKEM768 mTLS via ciphermap fix . --wrapper envoy --offline while staging composite ML-DSA-65 + ES256 JWS/DPoP tokens.

Illustrative Code Examples

These fragments explain migration direction. They are not complete applications or compiler-verified patches for your project.

Vulnerable — classical TR-34 RSA-2048 RKL & PS256-only FAPI 2.0 DPoP profile

terminal · zsh
const fapiConfig = {
  rklProfile: "TR34_2PASS_RSA_2048",
  iso8583Mac: "ANSI_X9_19_3DES",
  dpopSigningAlgValuesSupported: ["PS256", "ES256"],
}

Migration direction — AES-CMAC + TR-31 Version D + composite ML-DSA-65 FAPI 2.0 agility

terminal · zsh
const fapiConfig = {
  keyBlockVersion: "TR31_VERSION_D_AES256",
  iso8583Mac: "AES_256_CMAC",
  dpopSigningAlgValuesSupported: ["ML-DSA-65-ES256", "ES256"],
}

Scan your own repository for PQC-BANK-002 locally (0 code egress)

Preview proposed changes free with ciphermap fix . --dry-run --offline --no-telemetry. Eligibility depends on the installed build, call shape, module format, and migration context. The bundled RSA fixture has a classical key-size candidate; that does not make it post-quantum secure. Persisted digests and unsupported contexts may be declined. Applying supported candidates requires an entitlement, explicit verifier consent, and the required project tools. Review the actual verification result before adopting a change.

Other rule families