AWS payment-cryptography documentation change
Summary
Updated example KeyArn to full ARN format and added example KeyCheckValue in response documentation
Security assessment
The KeyCheckValue addition demonstrates how to validate cryptographic key integrity, which is a security feature. However, there is no evidence this addresses a specific security vulnerability. The change improves clarity for a security-related field but does not resolve an existing issue.
Diff
diff --git a/payment-cryptography/latest/userguide/use-cases-issuers.networkfunctions.mastercard.md b/payment-cryptography/latest/userguide/use-cases-issuers.networkfunctions.mastercard.md index b90f3d070..3b3ab38ac 100644 --- a//payment-cryptography/latest/userguide/use-cases-issuers.networkfunctions.mastercard.md +++ b//payment-cryptography/latest/userguide/use-cases-issuers.networkfunctions.mastercard.md @@ -34 +34 @@ The response echoes back the request parameters, including an ARN for subsequent - "KeyArn": "hrh6qgbi3sk4y3wq", + "KeyArn": "arn:aws:payment-cryptography:us-east-2:111122223333:key/hrh6qgbi3sk4y3wq", @@ -51 +51 @@ The response echoes back the request parameters, including an ARN for subsequent - "KeyCheckValue": "", + "KeyCheckValue": "08D7B4", @@ -62 +62 @@ The response echoes back the request parameters, including an ARN for subsequent -Take note of the `KeyArn` that represents the key, for example _hrh6qgbi3sk4y3wq_. You need that in the next step. +Take note of the `KeyArn` that represents the key, for example _arn:aws:payment-cryptography:us-east-2:111122223333:key/hrh6qgbi3sk4y3wq_. You need that in the next step.