How to use PCI/DSS Accelerator to implement PCI compliance
Configure IBM Security Guardium’s PCI/DSS Accelerator and create a series of policies and reports, in order to meet PCI/DSS requirements.
PCI/DSS (Payment Card Industry/ Data Security Standard) is a set of technical and operational requirements designed to protect cardholder data.
Value-added: Give customers a whole view of PCI/DSS and provide predefined policies and reports to save configuration time.
Follow these steps:
-
Configure PCI role.
-
Configure reports and policies that follow the requirements.
Configure PCI role
-
Login via the Guardium GUI page using the “accessmgr” user account. Select a user (in this case, user1), and click on Roles.
-
In the user role form, check PCI, and then save the assignment.
Implement PCI accelerator
Log on using “user1” and click Accelerators.

- Overview
-
-
Click PCI Accelerator for Compliance.
-
Click PCI Data Security Standard.
-


- Plan and Organize
-
Plan and Organize
Click the Overview for an introduction of how the predefined reports follow the compliance.
-
Cardholder Server IPs List: Cardholder information database server list. According to the company's actual situation, set the PCI Authorized Server IPs group information, which specifies the database server that stores cardholder information.
-
Cardholders Databases: Cardholder information database. Set the PCI Cardholder DB: designated group information, which is stored in the database's cardholder information.
-
Cardholder Objects: Cardholder information object. This needs to set the PCI Cardholder Sensitive objects.
-
DB Clients to Servers Map: Client/server mapping and PCI Authorized Server IPs set group information, which specifies the database servers storing cardholder information. Query can be used to find client access to the cardholder database.
-
Active DB Users: Administrator in addition to categories of users, which visited the cardholder database. Set the “PCI Authorized Server IPs” and “PCI Admin Users”.
-
Cardholder DB Administration: Cardholder database management operations. Set the PCI Authorized Server IPs and Admin Users.
-
Authorized Source Programs: Credit program access. Set the PCI Authorized Server IPs, PCI Authorized Source Programs. Procedure for recording Credit Cardholder database access.
-
Unauthorized Application Access: Non-credit program access. Set the PCI Authorized Server IPs, PCI Authorized Source Programs. Records of credit program for the cardholder database access.
-
8.5.8 Shared Accounts: PCI eighth requirements to have each person having computer access to be assigned a unique ID. Set PCI Authorized Server IPs to count the number of times the same database username is trying to access from the cardholder database IP.
In the statements, click to view a report form, and then determine what specific group content needs to be filled in.
Here is the actual name of the group:
Navigate to Modify Existing Groups selection, select the group name.
, and in theClick Modify (the pencil icon) and go to Manage Members for Selected Group page. Add new members.
The group can also be filled through a customized query.
-
- PCI Req. 10 Track & Monitor
-
Click the Overview for an introduction of how the Guardium monitor and predefined reports follow the compliance.
- 10.2 and 10.3 Automation - Use the online help Protect help book and Comply Help book to automate this section.
- 10.2.1 Data Access - PCI Access to cardholder data, Set the PCI Authorized Server IPs and PCI Admin Users.
- 10.2.2 Admin Activity - PCI Activity by Admin. user. Set the PCI Authorized Server IPs and PCI Admin Users.
- 10.2.3 Audit Trail Access - To follow this section completely, at least four kinds of reports must be defined: Logins to SQLGuard; User activity audit trails on Guardium server; Scheduled job exceptions; and, User to-to lists. Navigate to to create reports as you need.
- 10.2.4 Invalid Access - PCI - Invalid Login Access Attempts: record the login failed try in the database. PCI - Unauthorized Application access: record the database access not defined in PCI Authorized Source Programs.
- These three sections can also use the Monitor and Audit Help Book in the embedded online help - 10.2.6 Initialization Log, 10.5 Secure audit trails, and 10.6 Access Auditing.
- PCI Req. 11 Ongoing Validation
-
Click Overview for a discussion on the importance of vulnerabilities assessment. Click
to build an assessment process.
- PCI Policy Monitoring
Click Overview to introduce the Policy.
-
To show your current policy installations, navigate to
and choose a suitable policy for installation. -
Policy Violations - Records of violation operations.