The Unique Alternative to the Big Four ® 25 th Annual Conference of the Association of Local Government Auditors (ALGA) Understanding Payment Card Industry.

Slides:



Advertisements
Similar presentations
Surviving the PCI Self -Assessment James Placer, CISSP West Michigan Cisco Users Group Leadership Board.
Advertisements

Evolving Challenges of PCI Compliance Charlie Wood, PCI QSA, CRISC, CISA Principal, The Bonadio Group January 10, 2014.
.. PCI Payment Card Industry Compliance October 2012 Presented By: Jason P. Rusch.
PCI DSS for Retail Industry
Payment Card Industry Data Security Standard Tom Davis and Chad Marcum Indiana University.
PCI-DSS Erin Benedictson Information Security Analyst AAA Oregon/Idaho.
Complying With Payment Card Industry Data Security Standards (PCI DSS)
2014 PCI DSS Meeting OSU Business Affairs Process Improvement Team (PIT) Robin Whitlock & Dan Hough 10/28/2014.
JEFF WILLIAMS INFORMATION SECURITY OFFICER CALIFORNIA STATE UNIVERSITY, SACRAMENTO Payment Card Industry Data Security Standard (PCI DSS) Compliance.
Property of CampusGuard Compliance With The PCI DSS.
Credit Card Compliance Regulations Mandated by the Payment Card Industry Standards Council Accounting and Financial Services.
© Vendor Safe Technologies 2008 B REACHES BY M ERCHANT T YPE 70% 1% 9% 20% Data provided by Visa Approved QIRA November 2008 from 475 Forensic Audits.
PCI Compliance Forrest Walsh Director, Information Technology California Chamber of Commerce.
Data Security Standard. What Is PCI ? Who Does It Apply To ? Who Is Involved With the Compliance Process ? How We Can Stay Compliant ?
Visa Cemea Account Information Security (AIS) Programme
Payment Card Industry (PCI) Data Security Standard (DSS) Compliance Commonwealth of Massachusetts Office of the State Comptroller March 2007.
Copyright Security-Assessment.com 2005 Payment Card Industry Digital Security Standards Presented By Carl Grayson.
GPUG ® Summit 2011 November 8-11 Caesars Palace – Las Vegas, NV Payment Processing Online and Within Dynamics GP PCI Compliance and Secure Payment Processing.
CSE 4482, 2009 Session 21 Personal Information Protection and Electronic Documents Act Payment Card Industry standard Web Trust Sys Trust.
Contact Center Security Strategies Grant Sainsbury Practice Director, Dimension Data.
Why Comply with PCI Security Standards?
Introduction to PCI DSS
Northern KY University Merchant Training
Payment Card Industry (PCI) Data Security Standard
PCI's Changing Environment – “What You Need to Know & Why You Need To Know It.” Stephen Scott – PCI QSA, CISA, CISSP
Disclaimer Copyright Michael Chapple and Jane Drews, This work is the intellectual property of the authors. Permission is granted for this material.
Web Advisory Committee June 17,  Implementing E-commerce at UW  Current Status and Future Plans  PCI Data Security Standard  Questions.
Network security policy: best practices
PCI DSS The Payment Card Industry (PCI) Data Security Standard (DSS) was developed by the PCI Security Standards Council to encourage and enhance cardholder.
Payment Card Industry Data Security Standard (PCI DSS) By Roni Argetsinger
PCI 3.0 Boot Camp Payment Card Industry Data Security Standards 3.0.
MasterCard Site Data Protection Program Program Alignment.
Protecting Your Credit Card Security Environment (PCI) September 26, 2012 Jacob Arthur, CPA, QSA, CEH Timothy Agee, CISA, CGEIT, QSA FDH Consulting Frasier,
The influence of PCI upon retail payment design and architectures Ian White QSA Head of UK&I and ME PCI Team September 4, 2013 Weekend Conference 7 & 8.
An Introduction to PCI Compliance. Data Breach Trends About PCI-SSC 12 Requirements of PCI-DSS Establishing Your Validation Level PCI Basics Benefits.
NUAGA May 22,  IT Specialist, Utah Department of Technology Services (DTS)  Assigned to Department of Alcoholic Beverage Control  PCI Professional.
The Payment Card Industry (PCI) Data Security Standard: What it is and why you might find it useful Fred Hopper, CISSP TASK - 27 March 2007.
PCI requirements in business language What can happen with the cardholder data?
Date goes here PCI COMPLIANCE: What’s All the Fuss? Mark Banbury Vice President and CIO, Plan Canada.
PCI: As complicated as it sounds? Gerry Lawrence CTO
Credit Card Processing Gail “Montreal” Shoffey Keeler August 14, 2007.
PCI DSS Readiness Presented By: Paul Grégoire, CISSP, QSA, PA-QSA
Introduction to Payment Card Industry Data Security Standard
Introduction To Plastic Card Industry (PCI) Data Security Standards (DSS) April 28,2012 Cathy Pettis, SVP ICUL Service Corporation.
PCI Compliance: The Gateway to Paradise PCI Compliance: The Gateway to Paradise.
Data Security and Payment Card Acceptance Presented by: Brian Ridder Senior Vice President First National September 10, 2009.
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
PCI Training for PointOS Resellers PointOS Updated September 28, 2010.
ThankQ Solutions Pty Ltd Tech Forum 2013 PCI Compliance.
1 Payment Card Industry (PCI) Security Standard Developed by the PCI Security Council formed by major card issuers: Visa, MasterCard, American Express,
Jon Bonham, CISA, QSA Director, ERC
Standards in Use. EMV June 16Caribbean Electronic Payments LLC2.
By: Matt Winkeler.  PCI – Payment Card Industry  DSS – Data Security Standard  PAN – Primary Account Number.
The Payment Card Industry Data Security Standard (PCI DSS) is a proprietary information security standard for organizations that handle branded credit.
Introduction to PCI DSS
Payment Card Industry Data Security Standards
Payment Card Industry (PCI) Rules and Standards
PCI DSS Improve the Security of Your Ecommerce Environment
Payment Card Industry (PCI) Rules and Standards
Performing Risk Analysis and Testing: Outsource or In-house
PCI-DSS Security Awareness
Payment Card Industry (PCI) Data Security Standard (DSS) Compliance
Payment card industry data security standards
Internet Payment.
Breaches by Merchant Type
Session 11 Other Assurance Services
Payment Card Industry (PCI) Data Security Standard (DSS) Compliance
PCI Compliance : Whys and wherefores
Payment Card Industry (PCI) Data Security Standard (DSS) Compliance
Presented by: Jeff Soukup
Presentation transcript:

The Unique Alternative to the Big Four ® 25 th Annual Conference of the Association of Local Government Auditors (ALGA) Understanding Payment Card Industry Data Security Standards Assessments and Compliance Auditing Presented by: Bert Nuehring and Kevin O’Sullivan May 7, 2013

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 2 Audit | Tax | Advisory | Risk | Performance What is PCI?  The PCI Security Standards Council is an open global forum, launched in 2006, that is responsible for the development, management, education, and awareness of the PCI Security Standards, including the Data Security Standard (PCI DSS), Payment Application Data Security Standard (PA-DSS), and PIN Transaction Security (PTS) requirements.  The Council's five founding global payment brands -- American Express, Discover Financial Services, JCB International, MasterCard Worldwide, and Visa Inc. -- have agreed to incorporate the PCI DSS as the technical requirements of each of their data security compliance programs. Each founding member also recognizes the QSAs, PA-QSAs and ASVs certified by the PCI Security Standards Council.

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 3 Audit | Tax | Advisory | Risk | Performance What is PCI?

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 4 Audit | Tax | Advisory | Risk | Performance What is PCI?

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 5 Audit | Tax | Advisory | Risk | Performance PCI Brand Compliance Requirements  Level 1: entities perform annual onsite assessment (ROC)  May hire a QSA or use internal resources  entities report to acquirer(s) using Report on Compliance (ROC)  Level 2: entities may perform self assessment  entities report using appropriate Self Assessment Questionnaire (SAQ)  Level 3 & Level 4: entities validation and reporting requirements vary by payment brand and/or the acquirer

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 6 Audit | Tax | Advisory | Risk | Performance Report on Compliance (RoC)  For Level 1 entities as defined in the previous slide  A PCI On-site Assessment analyzes the applicability and implementation of all requirements within the PCI DSS in order to determine whether sufficient controls or adequate compensating controls are in place. The goal is to validate your organization’s compliance with the PCI DSS in order to issue a Report on Compliance (RoC)  At a high level, the ROC provides a comprehensive summary of assessment activities performed and information collected during the assessment.  The information contained in a ROC must provide enough detail and coverage to verify the entity’s compliance status. The assessor should clearly  describe how the validation activities were performed and how the resultant findings were reached for each section of the ROC. structions.pdf

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 7 Audit | Tax | Advisory | Risk | Performance Self Assessment Questionnaire (SAQ)  This is a questionnaire that a entity can fill out by itself which is a subset of the ROC.  SAQ A: Card-Not-Present (e-commerce or MO/TO) entities, all cardholder data functions outsourced. This would never apply to face-to-face entities  SAQ B: Imprint-only entities with no electronic cardholder data storage, or standalone, dial-out terminal entities with no electronic card holder data storage  SAQ C/VT: entities using only web-based virtual terminals, segmented from all other systems, no electronic cardholder data storage  SAQ C: entities with payment application systems connected to the internet, segmented from all other systems, no electronic cardholder data storage  SAQ D: All other entities (not included in descriptions for SAQs A, B, or C above) and all service providers defined by a payment brand as eligible to complete an SAQ.

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 8 Audit | Tax | Advisory | Risk | Performance Self Assessment Questionnaire (SAQ)

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 9 Audit | Tax | Advisory | Risk | Performance 6 Objectives and 12 Requirements

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 10 Audit | Tax | Advisory | Risk | Performance Requirement 1: Install and maintain a firewall configuration to protect cardholder data Firewalls are devices that control computer traffic allowed between an entity’s networks (internal) and untrusted networks (external), as well as traffic into and out of the Cardholder Data Environment. A firewall examines all network traffic and blocks those transmissions that do not meet the specified security criteria.

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 11 Audit | Tax | Advisory | Risk | Performance Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters Malicious individuals (external and internal to an entity) often use vendor default passwords and other vendor default settings to compromise systems. These passwords and settings are well known by hacker communities and are easily determined via public information.

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 12 Audit | Tax | Advisory | Risk | Performance Requirement 3: Protect stored cardholder data Protection methods such as encryption, truncation, masking, and hashing are critical components of cardholder data protection. Methods for minimizing risk include not storing cardholder data unless absolutely necessary, truncating cardholder data if full PAN (Primary Account Number) is not needed, and not sending unprotected PANs using end-user messaging technologies, such as a and instant messaging.

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 13 Audit | Tax | Advisory | Risk | Performance Requirement 4: Encrypt transmission of cardholder data across open, public networks Sensitive information must be encrypted during transmission over networks that are easily accessed by malicious individuals. Misconfigured wireless networks and vulnerabilities in legacy encryption and authentication protocols continue to be targets of malicious individuals who exploit these vulnerabilities to gain privileged access to cardholder data environments.

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 14 Audit | Tax | Advisory | Risk | Performance Requirement 5: Use and regularly update anti-virus software or programs Protection methods such as encryption, truncation, masking, and hashing are critical components of cardholder data protection. Methods for minimizing risk include not storing cardholder data unless absolutely necessary, truncating cardholder data if full PAN is not needed, and not sending unprotected PANs using end- user messaging technologies, such as a and instant messaging.

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 15 Audit | Tax | Advisory | Risk | Performance Requirement 6: Develop and maintain secure systems and applications Protection methods such as encryption, truncation, masking, and hashing are critical components of cardholder data protection. Methods for minimizing risk include not storing cardholder data unless absolutely necessary, truncating cardholder data if full PAN is not needed, and not sending unprotected PANs using end- user messaging technologies, such as a and instant messaging.

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 16 Audit | Tax | Advisory | Risk | Performance Requirement 7: Restrict access to cardholder data by business need to know To ensure critical data can only be accessed by authorized personnel, systems and processes must be in place to limit access based on need to know and according to job responsibilities. “Need to know” is when access rights are granted to only the least amount of data and privileges needed to perform a job.

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 17 Audit | Tax | Advisory | Risk | Performance Requirement 8: Assign a unique ID to each person with computer access. Assigning a unique identification (ID) to each person with access ensures that each individual is uniquely accountable for his or her actions. When such accountability is in place, actions taken on critical data and systems are performed by, and can be traced to, known and authorized users.

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 18 Audit | Tax | Advisory | Risk | Performance Requirement 9: Restrict physical access to cardholder data Any physical access to data or systems that house cardholder data provides the opportunity of individuals to access devices or data and to remove systems or hardcopies, and should be appropriately restricted. For the purposes of requirement 9, “onsite personnel” refers to full-time and part- time employees, temporary employees, contractors and consultants who are physically present on the entity’s premises. A “visitor” refers to a vendor, guest of any onsite personnel, service workers, or anyone who needs to enter the facility for a short duration, usually not more than one day. “Media” refers to all paper and electronic media containing cardholder data.

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 19 Audit | Tax | Advisory | Risk | Performance Requirement 10: Track and monitor all access to network resources and cardholder data Logging mechanisms and the ability to track user activities are critical in preventing, detecting, or minimizing the impact of a data compromise. The presence of logs in all environments allows thorough tracking, alerting, and analysis when something does go wrong. Determining the cause of a compromise is very difficult, if not impossible, without system activity logs.

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 20 Audit | Tax | Advisory | Risk | Performance Requirement 11: Regularly test security systems and processes Vulnerabilities are being discovered continually by malicious individual and researchers, and being introduced by new software. System components, processes, and custom software should be tested frequently to ensure security controls continue to reflect a changing environment.

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 21 Audit | Tax | Advisory | Risk | Performance Requirement 12: Maintain a policy that addresses information security for all personnel A strong security policy sets the security tone for the whole entity and informs personnel what is expected of them. All personnel should be aware of the sensitivity of data and their responsibilities for protecting it. For the purposes of requirement 12, “personnel” refers to full time and part-time employees, temporary employees, contractors and consultants who are “resident” on the entity’s site or otherwise have access to the cardholder data environment.

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 22 Audit | Tax | Advisory | Risk | Performance Reducing the Scope of PCI The goal is to reduce the access to Cardholder Data to the smallest footprint possible and separate that part of the network. Network Segmentation  Network segmentation of, or isolating (segmenting), the cardholder data environment from the remainder of the corporate network is not a PCI DSS requirement. However, it is recommended as a method that may reduce:  The scope of the PCI DSS assessment  The cost of the PCI DSS assessment  The cost and difficulty of implementing and maintaining PCI DSS controls  The risk to an organization (reduced by consolidating cardholder data into fewer, more c ontrolled locations) Tokenization-  Replace Credit Card number with a token which refers to a separate database which has the Credit Card number in it.

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 23 Audit | Tax | Advisory | Risk | Performance PCI-DSS 3.0  This October, the Payment Card Industry Security Standards Council will be issuing a major update to the PCI Data Security Standards (PCI DSS 3.0). It will be effective January 1,  To help entities prepare for this update, the council also issued a new PCI DSS eCommerce guidelines Information Supplement on how to better secure themselves and achieve compliance. _eCommerce_Guidelines.pdf

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 24 Audit | Tax | Advisory | Risk | Performance Highlights to PCI-DSS 3.0 Understanding Compliance vs. Security  Compliance addresses some security measures but there are many areas of your website that can still be vulnerable.  All areas where customer information is entered and/or stored must be protected with additional measures like SSL encryption. Additionally, non-purchase pages are also applicable if you have an update feature where customers can update their payment or account information. Avoiding Common Security Risks  While there are many dangers eCommerce entities face when it comes to securing their websites, SQL injection and cross-site scripting (XSS) attacks are some of the most common, yet most often overlooked.  it is important for entities to go beyond just following PCI regulations and work with third parties to address these and other easy-to-fix vulnerabilities.

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 25 Audit | Tax | Advisory | Risk | Performance Highlights to PCI-DSS 3.0 Evaluating Third Parties  Many entities don’t realize that the responsibility to ensure PCI compliance continues even after payment processing or other functions are outsourced to a third party.  Even if another company is handling part or the entire environment, entities still need to know where and how cardholder data is dealt with by the vendors to which they outsource.

The Unique Alternative to the Big Four ® © 2013 Crowe Horwath LLP 26 Audit | Tax | Advisory | Risk | Performance Crowe Horwath LLP is an independent member of Crowe Horwath International, a Swiss verein. Each member firm of Crowe Horwath International is a separate and independent legal entity. Crowe Horwath LLP and its affiliates are not responsible or liable for any acts or omissions of Crowe Horwath International or any other member of Crowe Horwath International and specifically disclaim any and all responsibility or liability for acts or omissions of Crowe Horwath International or any other Crowe Horwath International member. Accountancy services in Kansas and North Carolina are rendered by Crowe Chizek LLP, which is not a member of Crowe Horwath International. This material is for informational purposes only and should not be construed as financial or legal advice. Please seek guidance specific to your organization from qualified advisers in your jurisdiction. © 2013 Crowe Horwath LLP For more information, contact: Bert Nuehring Direct (630) Kevin O’Sullivan Direct (973)