NUAGA May 22, 2014.  IT Specialist, Utah Department of Technology Services (DTS)  Assigned to Department of Alcoholic Beverage Control  PCI Professional.

Slides:



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

ISACA January 8, IT Auditor at Cintas Corporation Internal Audit Department Internal Security Assessor (ISA) Certification September 2010 Annual.
PCI Compliance: The Gateway to Paradise PCI Compliance: The Gateway to Paradise.
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.
Online Banking Fraud Prevention Recommendations and Best Practices This document provides you with fraud prevention best practices that every employee.
PCI Compliance Forrest Walsh Director, Information Technology California Chamber of Commerce.
Jeff Williams Information Security Officer CSU, Sacramento
Security Controls – What Works
Information Security Policies and Standards
Payment Card Industry (PCI) Data Security Standard (DSS) Compliance Commonwealth of Massachusetts Office of the State Comptroller March 2007.
Defense-in-Depth Against Malicious Software Jeff Alexander IT Pro Evangelist Microsoft Australia
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.
Kevin R Perry August 12, Part 1: High Level Changes & Clarifications.
Stephen S. Yau CSE , Fall Security Strategies.
Why Comply with PCI Security Standards?
Introduction to PCI DSS
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.
Payment Card Industry Data Security Standard (PCI DSS) By Roni Argetsinger
PCI 3.0 Boot Camp Payment Card Industry Data Security Standards 3.0.
Security Risk Management Marcus Murray, CISSP, MVP (Security) Senior Security Advisor, Truesec
PCI DSS Managed Service Solution October 18, 2011.
Protecting Your Credit Card Security Environment (PCI) September 26, 2012 Jacob Arthur, CPA, QSA, CEH Timothy Agee, CISA, CGEIT, QSA FDH Consulting Frasier,
The Right Choice for Call Recording OAISYS and PCI DSS Compliance Managing Payment Card Industry Compliance with OAISYS Call Recording Solutions.
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.
Teresa Macklin Information Security Officer 27 May, 2009 Campus-wide Information Security Activities.
PCI requirements in business language What can happen with the cardholder data?
PCI: As complicated as it sounds? Gerry Lawrence CTO
Credit Card Processing Gail “Montreal” Shoffey Keeler August 14, 2007.
Security Baseline. Definition A preliminary assessment of a newly implemented system Serves as a starting point to measure changes in configurations and.
Introduction to Payment Card Industry Data Security Standard
Important acronyms AO = authorizing official ISO = information system owner CA = certification agent.
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.
Ali Pabrai, CISSP, CSCS ecfirst, chairman & ceo Preparing for a HIPAA Security Audit.
Data Security and Payment Card Acceptance Presented by: Brian Ridder Senior Vice President First National September 10, 2009.
Information Security 2013 Roadshow - PCI. Roadshow Outline  What IS PCI  Why we Care about PCI  What PCI Means to You and Me.
Chapter 2 Securing Network Server and User Workstations.
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,
Payment Card Industry (PCI) Data Security Standard Version 3.1
Information Security Measures Confidentiality IntegrityAccessibility Information cannot be available or disclosed to unauthorized persons, entities or.
The Unique Alternative to the Big Four ® 25 th Annual Conference of the Association of Local Government Auditors (ALGA) Understanding Payment Card Industry.
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.
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
Introduction to PCI DSS
Payment Card Industry Data Security Standards
Payment Card Industry (PCI) Rules and Standards
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
Critical Security Controls
Secure Software Confidentiality Integrity Data Security Authentication
Internet Payment.
Session 11 Other Assurance Services
Joe, Larry, Josh, Susan, Mary, & Ken
Payment Card Industry (PCI) Data Security Standard (DSS) Compliance
Payment Card Industry (PCI) Data Security Standard (DSS) Compliance
Contact Center Security Strategies
Presentation transcript:

NUAGA May 22, 2014

 IT Specialist, Utah Department of Technology Services (DTS)  Assigned to Department of Alcoholic Beverage Control  PCI Professional (PCIP) and PCI Internal Security Assessor (ISA) Certification 4/2014  Annual re-certification  Currently responsible for PCI security for all 44 of the DABC’s retail stores  18 Years Experience with DTS/DABC

 Easton-Bell Sports  Bright Horizons  Bell-Canada  Several major hotel chains ◦ These breaches have all occurred by exploiting weaknesses in the systems and processes of a third-party business partner.

 The PCI DSS represents a common set of industry tools and measurements to help ensure the safe handling of sensitive information.  The standard provides an actionable framework for developing a robust data security process - including preventing, detecting and reacting to security incidents.  Applies to any entity that stores, processes and/or transmits CHD.

PCI Data Security Standard Requirements PCI DSS is the global data security standard that any business of any size must adhere to in order to accept payment cards, and to store, process, and/or transmit cardholder data. It presents common sense steps that mirror best security practices. Goals PCI DSS Requirements – Validated by Self or Outside Assessment Build and Maintain a Secure Network1. Install and maintain a firewall configuration to protect cardholder data 2. Do not use vendor-supplied defaults for system passwords and other security parameters Protect Cardholder Data 3. Protect stored data 4. Encrypt transmission of cardholder data across open, public networks Maintain a Vulnerability Management Program5. Use and regularly update anti-virus software or programs 6. Develop and maintain secure systems and applications Implement Strong Access Control Measures7. Restrict access to cardholder data by business need-to-know 8. Assign a unique ID to each person with computer access 9. Restrict physical access to cardholder data Regularly Monitor and Test Networks10. Track and monitor all access to network resources and cardholder data 11. Regularly test security systems and processes Maintain an Information Security Policy12. Maintain a policy that addresses information security for all personnel

 Build and Maintain a Secure Network  Protect Card Holder Data  Maintain a Vulnerability Management Program  Implement Strong Access Control Measures  Regularly Monitor and Test Networks  Maintain an Information Security Policy

The updated versions of PCI DSS and PA-DSS will:  Provide stronger focus on some of the greater risk areas in the threat environment  Provide increased clarity on PCI DSS & PA-DSS requirements  Build greater understanding on the intent of the requirements and how to apply them  Improve flexibility for all entities implementing, assessing, and building to the Standards  Drive more consistency among assessors  Help manage evolving risks / threats  Align with changes in industry best practices  Clarify scoping and reporting  Eliminate redundant sub-requirements and consolidate documentation

The PCI Standards are updated based on feedback from the industry, per the standards development lifecycle as well as in response to current market needs. Common challenge areas and drivers for change include:  Lack of education and awareness  Weak passwords, authentication  Third-party security challenges  Slow self-detection, malware  Inconsistency in assessments

 1.1.x - Clarified that firewall and router standards have to be both documented and implemented.  Clarified what the network diagram must include and added a new requirement (1.1.3) for a current diagram that shows cardholder data flows.  New requirement to maintain an inventory of system components in scope for PCI DSS  New requirement to evaluate malware threats for any systems not considered to be commonly affected by malicious software

 New requirement to ensure that anti-virus solutions are actively running and cannot be disabled or altered by users unless specifically authorized by management on a per-case basis  6.1 -Clarified the process for identifying and risk ranking new vulnerabilities and (6.2) patching critical vulnerabilities  New requirement for coding practices to protect against broken authentication and session management  New requirement to cover definition of access needs for each role  Clarified requirements for two-factor authentication applies to users, administrators, and all third parties, including vendor access for support or maintenance

 New requirement for service providers with remote access to customer devices, to use unique authentication credentials for each customer  9.9.x - New requirement to protect devices that capture payment card data via direct physical interaction with the card from tampering and substitution  – Enhanced requirement to include changes to identification and authentication mechanisms (including creation of new account, elevation of privileges) and all changes, additions and deletions to accounts with root or admin privileges

 11.1.x -New requirement to include an inventory of authorized wireless access points and scanning for unauthorized wireless devices  New requirement to implement a methodology for penetration testing, to also include verification that segmentation methods are operational and effective (11.3.4)  Clarified that the risk assessment should be performed at least annually and after significant changes to the environment  Clarified the responsibilities for the service provider’s written agreement/acknowledgement

 New requirement to maintain information about which PCI requirements are managed by each service provider, and which are managed by the entity  New requirement for service providers to provide a written agreement/acknowledgment to their customers  x - Clarified the intent for alerts from security monitoring systems to be included in the incident response plan

 Implementing security into business as usual (BAU) activities  Audit ready anytime  In my opinion, the PCI Data Security Standard is not a policy or procedure. PCI-DSS is a lifestyle!

Kevin Perry  DTS/DABC 