How To Protect Your Data From Being Stolen

Similar documents
PDQ Guide for the PCI Data Security Standard Self-Assessment Questionnaire C (Version 1.1)

PCI DSS Policies Outline. PCI DSS Policies. All Rights Reserved. ecfirst Page 1 of 7

Payment Card Industry - Achieving PCI Compliance Steps Steps

Credit Card Acceptance Policy. Vice Chancellor of Business Affairs. History: Effective July 1, 2011 Updated February 2013

PCI COMPLIANCE GUIDE For Merchants and Service Members

Josiah Wilkinson Internal Security Assessor. Nationwide

TOP 10 WAYS TO ADDRESS PCI DSS COMPLIANCE. ebook Series

New PCI Standards Enhance Security of Cardholder Data

paypoint implementation guide

PCI PA - DSS. Point XSA Implementation Guide. Atos Worldline Banksys XENTA SA. Version 1.00

Enforcing PCI Data Security Standard Compliance

Data Security for the Hospitality

Customer PCI 3.0 Changes = New Opportunity For You. Giles Witherspoon-Boyd SecurityMetrics

Section 3.9 PCI DSS Information Security Policy Issued: June 2016 Replaces: January 2015

Accelerating PCI Compliance

Introduction. PCI DSS Overview

Global Partner Management Notice

PCI DSS 3.0 Changes Bill Franklin Executive IT Auditor January 23, 2014

How To Comply With The Pci Ds.S.A.S

74% 96 Action Items. Compliance

TASK TDSP Web Portal Project Cyber Security Standards Best Practices

PCI Assessments 3.0 What Will the Future Bring? Matt Halbleib, SecurityMetrics

COLORADO STATE UNIVERSITY Financial Procedure Statements FPI 6-6

University of Sunderland Business Assurance PCI Security Policy

Credit Card Security

PCI PA - DSS. Point ipos Implementation Guide. Version VeriFone Vx820 using the Point ipos Payment Core

Implementation Guide

How NETGEAR ProSecure UTM Helps Small Businesses Meet PCI Requirements

Becoming PCI Compliant

PCI Data Security Standards

CONTENTS. PCI DSS Compliance Guide

MONITORING AND VULNERABILITY MANAGEMENT PCI COMPLIANCE JUNE 2014

PCI Compliance - A Realistic Approach. Harshul Joshi, CISM, CISA, CISSP Director, Information Technology CBIZ MHM hjoshi@cbiz.com

Client Security Risk Assessment Questionnaire

Comodo HackerGuardian. PCI Security Compliance The Facts. What PCI security means for your business

Project Title slide Project: PCI. Are You At Risk?

PCI PA - DSS. Point BKX Implementation Guide. Version Atos Xenta, Atos Xenteo and Atos Yomani using the Point BKX Payment Core

Cyber - Security and Investigations. Ingrid Beierly August 18, 2008

PCI DSS Requirements - Security Controls and Processes

Franchise Data Compromise Trends and Cardholder. December, 2010

PCI DSS Presentation University of Cincinnati

How To Protect Data From Attack On A Network From A Hacker (Cybersecurity)

Payment Card Industry (PCI) Compliance. Management Guidelines

PCI-DSS: A Step-by-Step Payment Card Security Approach. Amy Mushahwar & Mason Weisz

PCI DSS Overview. By Kishor Vaswani CEO, ControlCase

La règlementation VisaCard, MasterCard PCI-DSS

Policies and Procedures

worldpay.com Understanding the 12 requirements of PCI DSS SaferPayments Be smart. Be compliant. Be protected.

8/17/2010. Over 90% of all compromised merchants are PCI level 4 (small) merchants or merchants with less than 1 million transactions per year

Achieving Compliance with the PCI Data Security Standard

Adyen PCI DSS 3.0 Compliance Guide

How To Protect Your Business From A Hacker Attack

Information Security Services. Achieving PCI compliance with Dell SecureWorks security services

Payment Card Industry Data Security Standards.

PCI COMPLIANCE REQUIREMENTS COMPLIANCE CALENDAR

Property of CampusGuard. Compliance With The PCI DSS

Payment Card Industry - Data Security Standard (PCI-DSS) Security Policy

Network Segmentation

Your Compliance Classification Level and What it Means

PCI Compliance Top 10 Questions and Answers

Qualified Integrators and Resellers (QIR) Implementation Statement

You Can Survive a PCI-DSS Assessment

Automate PCI Compliance Monitoring, Investigation & Reporting

Payment Card Industry (PCI) Data Security Standard. Summary of Changes from PCI DSS Version 2.0 to 3.0

Frequently Asked Questions

PCI Compliance. Top 10 Questions & Answers

PCI DSS. CollectorSolutions, Incorporated

The 12 Essentials of PCI Compliance How it Differs from HIPPA Compliance Understand & Implement Effective PCI Data Security Standard Compliance

Credit Cards and Oracle: How to Comply with PCI DSS. Stephen Kost Integrigy Corporation Session #600

Payment Card Industry Self-Assessment Questionnaire

It Won t Happen To Me! A Network and PCI Security Webinar Presented By FMS and VendorSafe

What does it mean to be secure?

Payment Card Industry (PCI) Data Security Standard ROC Reporting Instructions for PCI DSS v2.0

What are the PCI DSS requirements? PCI DSS comprises twelve requirements, often referred to as the digital dozen. These define the need to:

Data Security, Fraud Prevention, and Cost Control. Mike Dorland, CPP Regional Marketing Representative Michigan Retailers Association

Two Approaches to PCI-DSS Compliance

Continuous compliance through good governance

PCI: The Dark Side. May 2012 Roanoke, VA

MasterCard PCI & Site Data Protection (SDP) Program Update. Academy of Risk Management Innovate. Collaborate. Educate.

AUTOMATING AUDITS AND ENSURING CONTINUOUS COMPLIANCE WITH ALGOSEC

Bottom line you must be compliant. It s the law. If you aren t compliant, you are leaving yourself open to fines, lawsuits and potentially closure.

University of Dayton Credit / Debit Card Acceptance Policy September 1, 2009

Technology Innovation Programme

How To Protect Your Credit Card Information From Being Stolen

A Rackspace White Paper Spring 2010

PCI Compliance. How to Meet Payment Card Industry Compliance Standards. May cliftonlarsonallen.com CliftonLarsonAllen LLP

Transcription:

DATA SECURITY & PCI DSS COMPLIANCE PROTECTING CUSTOMER DATA

WHAT IS PCI DSS? PAYMENT CARD INDUSTRY DATA SECURITY STANDARD A SET OF REQUIREMENTS FOR ANY ORGANIZATION OR MERCHANT THAT ACCEPTS, TRANSMITS OR STORES ANY CARDHOLDER DATA. THERE ARE SIX GOALS AND TWELVE REQUIREMENTS.

PCI SCOPE ANY SYSTEM COMPONENT IN OR CONNECTED TO THE CARDHOLDER DATA ENVIRONMENT COMPUTERS REGISTERS SCALES WIRELESS ANY NETWORK DEVICE

NETWORK SEGMENTATION CREATE SEPARATE YET ALSO SECURE NETWORK FOR ROLES AND SERVICES THAT DO NOT NEED TO BE IN THE CARD HOLDER DATA ENVIRONMENT. MANAGER COMPUTERS SCALES CUSTOMER WIRELESS KIOSKS PRINTERS

GOAL 1: BUILD AND MAINTAIN A SECURE NETWORK REQUIREMENT 1:INSTALL AND MAINTAIN A FIREWALL CONFIGURATION TO PROTECT CARDHOLDER DATA. MAKE SURE YOU HAVE PROPER INTERNET SAFEGUARDS. REQUIREMENT 2: DO NOT USE VENDOR SUPPLIED DEFAULTS FOR SYSTEM PASSWORDS AND OTHER SECURITY PARAMETERS. ALWAYS CHANGE PASSWORDS ON ALL NETWORK DEVICES. DO NOT HAVE EASY PASSWORDS

WHAT A FIREWALL DOES ALLOWS GOOD TRAFFIC (EMAIL, WEB, VPN) DENIES BAD TRAFFIC (HACK ATTEMPTS, PORT SCANNING) DETERMINES WHERE GOOD TRAFFIC GOES MONITORS WHO IS TRYING TO BREECH AND FROM WHERE FIRST AND BEST LINE OF DEFENSE

GOAL 2: PROTECT CARDHOLDER DATA REQUIREMENT 3: PROTECT STORED CARDHOLDER DATA. KEEP STORED CARDHOLDER INFORMATION SECURE. IF ONSITE STORAGE NEEDED KEEP IN SECURE DATABASE. DO NOT KEEP IN UNSECURE DOCUMENTS, SUCH AS EXCEL, WORD REQUIREMENT 4: ENCRYPT TRANSMISSION OF CARDHOLDER DATA ACROSS OPEN, PUBLIC NETWORKS. TALK TO POS VENDOR TO MAKE SURE ALL TRANSMISSIONS HAVE PROPER ENCRYPTION. KNOW AT WHAT POINT DATA IS ENCRYPTED, FROM SOURCE TO DESTINATION

WHAT IS ENCRYPTION? THE PROCESS OF ENCODING DATA SO THAT ONLY AUTHORIZED DEVICES CAN READ IT. REQUIRES A ENCRYPTION KEY ON BOTH SIDES OF TRANSMISSION TO SEND AND THEN READ DATA. HARDWARE AND SOFTWARE CAN ENCRYPT. SYMMETRIC OR PUBLIC KEYS. HTTP VS. HTTPS

GOAL 3: MAINTAIN A VULNERABILITY MANAGEMENT PROGRAM REQUIREMENT 5: PROTECT ALL SYSTEMS AGAINST MALWARE AND REGULARLY UPDATE ANTI-VIRUS SOFTWARE OR PROGRAMS. INCLUDES POS DEVICES. IF IT CAN BE INFECTED WITH MALWARE IT NEEDS PROTECTING. REQUIREMENT 6: DEVELOP AND MAINTAIN SECURE SYSTEMS AND APPLICATIONS. KEEP COMPUTERS UP TO DATE ON PATCHES. INVESTIGATE EMERGING SECURITY FLAWS TO MAKE SURE YOU ARE NOT EFFECTED.

GOAL 4: IMPLEMENT STRONG ACCESS CONTROL MEASURES REQUIREMENT 7: RESTRICT ACCESS TO CARDHOLDER DATA BY BUSINESS NEED TO KNOW. KEEP CARDHOLDER DATA OUT OF THE HANDS OF UNAUTHORIZED PERSONNEL. KEEP TO SELECT FEW. REQUIREMENT 8: IDENTIFY AND AUTHENTICATE ACCESS TO SYSTEM COMPONENTS. UNIQUE LOGINS FOR USERS. UNSUCCESSFUL PASSWORD LOCKOUTS. PASSWORD COMPLEXITY. REQUIREMENT 9: RESTRICT PHYSICAL ACCESS TO CARDHOLDER DATA. CAMERAS AND ACCESS CONTROLS TO SENSITIVE AREAS. NO PUBLICLY ACCESSIBLE NETWORK JACKS

GOAL 5: REGULARLY MONITOR AND TEST NETWORKS REQUIREMENT 10: TRACK AND MONITOR ALL ACCESS TO NETWORK RESOURCES AND CARDHOLDER DATA. TURN ON NETWORK AND LOGIN AUDITING. REQUIREMENT 11: REGULARLY TEST SECURITY SYSTEMS AND PROCESSES. HAVE A VENDOR PERFORM QUARTERLY INTERNAL AND EXTERNAL NETWORK SCANS. IDENTIFY POSSIBLE ISSUES. STARTING JAN 1 2015 ALSO INCLUDES PENETRATION TESTING.

GOAL 6: MAINTAIN AN INFORMATION SECURITY POLICY REQUIREMENT 12:MAINTAIN A POLICY THAT ADDRESSES INFORMATION SECURITY FOR ALL PERSONNEL. DOCUMENT PROCEDURES IN YOUR IT ENVIRONMENT. TEST AND REVIEW ON A TIMELY BASIS.

BE PROACTIVE! ANALYZE YOUR RISK. DO SOMETHING BEFORE YOU ARE MADE TO DO SOMETHING. CHECK WITH VENDORS TO MAKE SURE THEY ARE UP TO DATE. TALK WITH PAYMENT PROCESSORS OR BANK ON THEIR LATEST EFFORTS AGAINST BREECHES. MAKE SURE YOU ARE PROTECTED. INSURANCE, BREECH PROTECTION TO COVER FINES, FORENSIC COSTS ETC.

JASON@KCSTECH.COM SALES@KCSTECH.COM