This chapter provides an overview of credit card encryption and discusses how to:
Implement credit card encryption.
Secure the credit card components.
Change the credit card encryption key.
Synchronize re-encrypted data with PeopleSoft Enterprise Financials.
PeopleTools Pluggable Cryptography is an advanced security framework that introduces a new security model for applications to encrypt and decrypt credit card data. This feature adds greater security to the credit card data handling system as well as upgrades existing credit card data.
Credit card encryption is available to PeopleSoft Enterprise CRM implementations that are integrated with PeopleSoft Enterprise Financials.
Strong Encryption
Pluggable Cryptography protects critical PeopleSoft data and enables more secure data communication with other businesses. It enables you to extend and improve cryptographic support for your data in PeopleTools. By incrementally acquiring stronger and more diverse algorithms for encrypting data, Pluggable Cryptography offers strong cryptography with the flexibility to change and grow.
Enhanced cryptography capability is provided by PeopleSoft pluggable encryption technology (PET), which employs 3DES algorithms and 168-bit encryption keys to secure data.
Features
Applying Pluggable Cryptography to your system:
Improves the system's ability to protect credit card data during transfer and storage.
Upgrades existing credit card data.
Protects data during information display.
Once upgraded, the system displays credit card numbers so as to mask them. Before upgrade, the system displayed all digits of a credit card number, whether display-only or editable. The feature modifies the display to show only the last four digits, replacing each preceding digit with an X.
Standards
PeopleTools Pluggable Cryptography complies with the cardholder data protection requirements of the Payment Card Industry (PCI) Security Standards Council and with Visa's Cardholder Information Security Program (CISP). When you enable this feature, credit card numbers for external third-party payers, such as customers or students, are encrypted.
Note. This feature upgrades credit card numbers that are shared with the PeopleSoft Financials or a third-party database; it does not upgrade those stored internally in the CRM database, such as company-owned or employee credit cards.
See Also
Enterprise PeopleTools 8.50 PeopleBook: Security Administration, “Securing Data with Pluggable Cryptography”
To enhance the security of credit card transactions, the CRM system supports the inclusion of verification number in the credit card authorization process. A verification number, also known as a card identification number, card authentication value, or card validation code depending on the card company, is a 3-digit or 4-digit code that is printed on the back or the face of the credit card. The number is associated uniquely to the card account number as well as the physical credit card. For transactional components that support credit card payments, a field is available to capture the verification number of the credit card. When a transaction, paid by credit card, is submitted, the specified credit card information and the verification number are sent to the authorization process.
In compliance with the guidelines recommended by the PCI Security Standards Council regarding sensitive authentication data, the verification number is removed permanently from the database once the authorization process completes (passed or failed). In situations where the card data is accepted but not immediately authorized (for example, future dated orders that are saved in the database and not submitted until the order date is reached), the verification number is stored in an encrypted format and is masked with XXX when displayed in the field until the value is deleted after authorization.
Here are a list of transactional components that support credit card payments and accepts verification number for authorization processing:
Support Case.
Credit card transactions are not applicable to HelpDesk and HR HelpDesk cases.
Order (agent-facing and customer-facing).
For canceled orders (which can be orders that are not yet submitted, or expired orders that are canceled by a batch process on a regular basis), their saved verification numbers are deleted from the database.
For future dated orders, their verification numbers are stored in the database, and will be removed when the fulfill by date is reached AND the orders are submitted.
For bulk orders, credit card information (including the verification number) is transferred to their child orders. Upon submission, the verification number is removed from the database and no longer appears on the parent and child orders.
Agreement.
Service order.
Prepaid account.
Verification number is not supported in non-prepaid accounts.
Note. Because of its sensitive nature, verification number is not stored or displayed in the section of the Person component where credit card entries are stored, nor it is passed to another system (for example, supply chain system) through integration points.
Integration Technology
PeopleSoft Enterprise CRM uses the Integration Broker messaging technology (SOAP) to perform credit card authorizations with Cybersource (certified third-party vendor).
To facilitate message exchange between the PeopleSoft and Cybersource systems, an application engine program (CYB_SOAP_REQ) is used to transform authorization request and response messages to the appropriate format for the system that receives them.
The system delivers a node called PSFT_CYB in Integration Broker as part of the integration setup. This node contains the Cybersource-specific HTTP connector settings for contacting the authorization servers via SOAP as well as message transformation and routing settings.
Note. This SOAP-based integration uses core Integration
Broker functionality that is available in all PeopleTools versions, which
ensures backward and forward compatibility without reliance on third-party
software support. Because it is a native PeopleTools functionality, it is
easier for customers to set up, deploy and maintain.
This integration uses secure SSL (secure sockets layer) encryption.
Customers who use other non-Cybersource third-party vendors for credit
card authorizations can also leverage this SOAP solution with few custom modifications.
These changes include an updated node definition and routing properties for
their vendors, and possibly a new transformation program (or an updated one
based on the delivered transformation program) that formats messages circulating
between PeopleSoft and their vendors. The underlying Enterprise Components
message stubs and transaction triggers remain the same.
To avoid the potential issue of storing and displaying sensitive data in the Integration Broker logs and Service Operations Monitor, the log detail setting in the routing definition for the messages is set to No Logging as delivered.
General Settings for Credit Card Authorizations with Cybersource
A system-wide setting is available to make the provision of credit card verification number mandatory for authorization processing. When the setting is enabled, an error message appears if the user fails to enter a verification number when the credit card transaction is being submitted to authorization. In the case of an order, it is put on credit card hold if the verification number is not present.
For security verification purposes, the CRM system requires that the Cybersource user ID, merchant ID and merchant key be provided on the Installation Options page. These fields are included in the SOAP message for security verification during credit card authorization.
See Setting Up General Options.
Cybersource SOAP Connectivity
Refer to the CRM installation guide for more information on how to set up the integration with Cybersource, which includes these high-level steps:
Set up the web server with SSL certificate provided by Cybersource and new proxy server setting.
Make sure to enter your Cybersource user ID, merchant ID and merchant key information on the Installation Options page.
Make sure the PSFT_CYB node is set up properly (connector and routing information in particular) and activated.
Test the connectivity using the Test Credit Card Interface component.
See PeopleSoft Enterprise Customer Relationship Management 9.1 Supplemental Installation Guide
See Also
Submitting Credit Card Information for Authorization
Managing Shipping, Product, and Payment Options from the Checkout Page
Managing Account Balance and Payments
You must perform these tasks to implement the new functionality:
Make sure that the PeopleSoft Financials database that you integrate with is set up to support credit card encryption.
Secure the credit card component.
Upgrade existing credit card data.
See PeopleSoft Enterprise Customer Relationship Management Upgrade, “Complete Database Changes,” Encrypting Credit Card Data
Contact Global Support before attempting to upgrade your data, if you have customized your system in any of the following ways:
Added any records containing credit card number fields.
Added a credit card number field to any records.
Deleted any records found in the grid on the Upgrade Credit Card Numbers component.
Deleted a credit card number field from any records found in the grid on the Upgrade Credit Card Numbers component.
Customized the credit card encryption processing functionality in any way.
Changed whether or how any particular credit card field is encrypted.
Change the credit card encryption key.
You must specify the user roles that have access to credit card components.
Securing the components involves these general steps:
Add the Credit Card Component menu (CCENCRYPTION_MENU) to the appropriate permission list.
Provide security for the new credit card components:
See Providing Security for Credit Card Components.
FS_CC_UPGRADE
FS_CC_CNVRT
Provide security to the new portal registries:
See Providing Security for the Portal Registries.
CREDIT_CARD_ENCRYPTION (Credit Card Encryption folder)
FS_CC_UPGRADE_GBL (Upgrade Credit Card Numbers content registry)
FS_CC_CNVRT_GBL (Change Encryption Key content registry)
(Optional) Change the security group for the FS_CC_CNVRT Application Engine process definition.
Run the portal security synchronization process (PeopleTools, Portal, Portal Security Sync).
Clear the application and web server caches.
You must add CCENCRYPTION_MENU to the appropriate permission list. You may want to choose a security administration role.
See Also
PeopleSoft Enterprise PeopleTools 8.50 PeopleBook: Security Administration, “Setting Up Permission Lists,” Managing Permission Lists
To provide access to the new PeopleSoft components:
Navigate to PeopleTools, Security, Permissions & Roles, Permission Lists, Pages.
Add the menu name CCENCRYPTION_MENU.
Click Edit Components.
The Components page appears.
Locate the FS_CC_UPGRADE component to which you want to grant access.
(By default, no components are authorized when adding a menu.)
Click the Edit Pages button for each component to which you want to grant access.
The Page Permissions page appears.
Specify the actions that a user can complete on the page.
Click OK on the Page Permissions page, and then again on the Component Permissions page.
Note. Perform this procedure twice, once for the FS_CC_UPGRADE component and again for the FS_CC_CNVRT component.
See Also
Enterprise PeopleTools 8.50 PeopleBook: Security Administration, “Setting Up Permission Lists”
You must provide security for the new folder and content registries on the portal.
For Folder:
Navigate to PeopleTools, Portal, Structure and Content.
In the Folders list, click on the links Set Up CRM, then Utilities.
Click the Edit link next to the Credit Card Encryption folder name.
Click the Folder Security tab.
On the Folder Administration page, select the permission lists that you want to have access to the Credit Card Encryption menu.
For Content Registries:
Navigate to PeopleTools, Portal, Structure and Content.
In the Folders list, click on the links Set Up CRM, then Utilities, then Credit Card Encryption.
Click the Edit link for Upgrade Credit Card Numbers (FS_CC_UPGRADE_GBL).
On the Security tab, make sure the permission list displayed corresponds to the CCENCRYPTION_MENU permission list.
Repeat steps 3 and 4 for Change Encryption Key (FS_CC_CNVRT_GBL).
Note. When you complete all security tasks, delete your browser cache so that you can view the new portal registries in the menu navigation.
See Also
Enterprise PeopleTools 8.50 PeopleBook: Portal Technology, “Administering Portals”
You can optionally change the security group for the FS_CC_CNVRT Application Engine process definition.
To change the security group:
Navigate to PeopleTools, Process Scheduler, Processes.
Select Process Name in the Search By field.
Enter FS_CC_CNVRT in the begins with field.
Click the Search button.
On the Process Definition page, select the Process Definition Options tab.
Modify the security group in the Process Groups grid.
This section describes how to:
Re-encrypt credit card data.
Change the encryption key.
You can change the credit card encryption key at any time.
Page Name |
Definition Name |
Navigation |
Usage |
FS_CC_CNVRT |
Set Up CRM, Utilities, Credit Card Encryption, Change Encryption Key |
Change the key used to encrypt credit card numbers. Run the utility to re-encrypt credit card numbers using a new encryption key. |
To change the encryption key at any time after the initial conversion, you must first re-encrypt all credit card data.
To re-encrypt credit card data:
If this is the first re-encryption following the initial conversion and you have not secured the FS_CC_CNVRT component, complete the steps in the “Securing the Credit Card Components” section in this chapter.
See Securing the Credit Card Component.
Complete the steps for the FS_CC_CNVRT component only. Securing FS_CC_CNVRT secures both the FS_CC_CNVRT component and the FS_CC_CNVRT portal registry.
Navigate to Set Up CRM, Utilities, Credit Card Encryption, Change Encryption Key.
Click the Generate Random Key button to generate a new random hexadecimal encryption key.
Clicking this button generates a new, random hexadecimal encryption key. You can modify this key, but you must format it as a 24-byte string in hexadecimal notation. The first two characters must be 0x, and the remainder must be exactly 48 characters and consist of both numeric digits and the lowercase letters a through f.
If the values in the Re-encrypt Action column are not Decrypt, then Encrypt, click the Crypt Action button until Decrypt, then Encrypt appears in the column.
Click the Run button to start the conversion process.
The Credit Card Conversion process converts each field in the grid. If the process fails for any reason, you can restart the process; it will resume where it stopped. If you can not restart the process, run it from the beginning. The system will bypass fields that have already been processed.
Access the Credit Card Number Re-Encrypt page (Set Up CRM, Utilities, Credit Card Encryption, Change Encryption Key).
Crypt Action |
Toggle the value in the Re-Encrypt Action column in the grid. |
Generate Random Key |
Generate a random key in the format needed by the encryption algorithms used for credit card encryption and decryption profiles. |
(Encryption key) |
If you want to modify the generated key or enter your own, you must format it as a 24-byte hex string. The first two characters must be 0x and the remainder must be exactly 48 characters that consist of both numeric digits and the lowercase letters a through f. |
Record (Table) Name |
Displays the record name. |
Field Name |
Displays the field name. |
Re-Encrypt Action |
Values include:
|
Any change in CRM data requires that it be propagated to the PeopleSoft Financials database, which is described in the PeopleSoft PeopleBooks for your software release. Recommended references follow.
See Also
PeopleSoft Enterprise Components for CRM 9.1 PeopleBook, “Activating Messaging EIPs”
PeopleSoft Enterprise Components for CRM 9.1 PeopleBook, “Performing a Full Data Publish of Current Effective Data”
Integrating with PeopleSoft Financial Management Services