Card Security ID Is Not Masked In Logs
(Doc ID 2494410.1)
Last updated on MARCH 20, 2019
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.21.0 and laterInformation in this document applies to any platform.
Symptoms
On Oracle Communications Billing and Revenue Management(BRM), 7.5.0.21.0 Version, Paymentech Manager,
ACTUAL BEHAVIOR
---------------
The card security ID (PIN_FLD_SECURITY_ID) in BRM is not masked like the Credit Card (or bank account #) is in PIN_FLD_DEBIT_NUM. The latter must be encrypted when stored in the database, but the former may not even be stored. It is just transmitted once to Paymentech and NEVER stored anywhere.
This card security ID mandate for PCI must imply that logging a card security ID in clear text is not allowed.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |