AWS payment-cryptography documentation change
Summary
Added support for ISO_Format_4 (AES encryption), expanded valid PIN encoding formats, and made GenerationKeyCheckValue optional.
Security assessment
Introducing ISO_Format_4 with AES encryption enhances cryptographic options, which is a security feature. No explicit vulnerability is addressed.
Diff
diff --git a/payment-cryptography/latest/DataAPIReference/API_GeneratePinData.md b/payment-cryptography/latest/DataAPIReference/API_GeneratePinData.md index cea50ed54..340107424 100644 --- a//payment-cryptography/latest/DataAPIReference/API_GeneratePinData.md +++ b//payment-cryptography/latest/DataAPIReference/API_GeneratePinData.md @@ -106 +106 @@ Required: Yes -The PIN encoding format for pin data generation as specified in ISO 9564. AWS Payment Cryptography supports `ISO_Format_0` and `ISO_Format_3`. +The PIN encoding format for pin data generation as specified in ISO 9564. AWS Payment Cryptography supports `ISO_Format_0`, `ISO_Format_3` and `ISO_Format_4`. @@ -111,0 +112,2 @@ The `ISO_Format_3` PIN block format is the same as `ISO_Format_0` except that th +The `ISO_Format_4` PIN block format is the only one supporting AES encryption. + @@ -114 +116 @@ Type: String -Valid Values: `ISO_FORMAT_0 | ISO_FORMAT_3 | ISO_FORMAT_4` +Valid Values: `ISO_FORMAT_0 | ISO_FORMAT_1 | ISO_FORMAT_3 | ISO_FORMAT_4` @@ -140 +142 @@ Pattern: `[0-9]+` -Required: Yes +Required: No