800.800.4239 Mon-Fri 7am-7:30pm CT
Send E-Mail Answer within 2 hours.
Financial Regulatory Compliance: An Ever-Evolving Demand Learn how to better assess risks and assure compliance.
Read the Whitepaper »
PCI Compliance Solutions from CDW ensure your organization’s engagement in payment card transactions adheres to the PCI Data Security (or PCI DSS) Standard.
The PCI DSS is a document drafted by the PCI Security Standards Council, a consortium of representatives from the payment card industry. It provides a yardstick by which networks can be declared either fit or unfit for payment card transactions.
A concise plan to become and remain PCI compliant will eliminate “compliance confusion,” which is likely to put your data at risk. It is essential to expertly navigate through the PCI DSS twelve‑part framework to ensure that your operating networks handle payment card data securely and accurately.
Tailoring your network to conform to PCI DSS requirements reduces the risk associated with adopting many different solutions with respect to payment card data security.
Implementing PCI compliance solutions enables your organization to:
The PCI DSS represents a collection of good security practices. If your organization embraces those requirements for its cardholder data environment, it encourages those practices to bleed over into other areas as well.
The first step is to take the mystery out of PCI compliance and evaluate how it can be integrated into your organization as a whole:
The next step is to initiate a project plan. A compliance plan begins with gap analysis. In PCI compliance terms, this means three things:
The PCI DSS is comprehensive and can cascade through many areas of an organization. As a result, there is no one‑size‑fits‑all solution for compliance. There are four basic steps to customize PCI compliance to your organization:
A plan for compliance should begin with an effort to define—as narrowly as possible—the scope of the cardholder data environment. This often is a subtle and complex question, but minimizing the scope of what must be evaluated for compliance is the single most important factor in most compliance plans.
Once the question of scope is properly settled, the next step is to determine how compliance will be evaluated. For most organizations, this means identifying the proper Self‑Assessment Questionnaire (SAQ). Some organizations will discover that they have special responsibilities because of services they provide, or because of payment processing software they have written.
What obstacles stand between your organization's current state and compliance? Once these have been identified, it is essential to make a project plan to close those gaps. This may require:
Finally, the organization needs to execute that plan and submit the proper materials. Typically, an organization would submit a completed attestation of compliance, along with four passing quarterly external vulnerability scan reports from an Approved Scanning Vendor (ASV), to the organization’s processor or acquiring bank.
Your CDW Account Manager and certified specialists are ready to assist you with every phase of choosing and leveraging the right solution for your cardholder data environment. Our approach includes:
The Organization: Johnson County Community College The Location: Overland Park, KS The Project: Overhauling network infrastructure to support students’ personal devices. Get the story »
Calming PCI Compliance Qualms»