Security & Compliance, Sikich LLP



Similar documents
PCI DSS Presentation University of Cincinnati

Josiah Wilkinson Internal Security Assessor. Nationwide

Payment Card Industry Data Security Standard Training. Chris Harper Vice President of Technical Services Secure Enterprise Computing, Inc.

AIS Webinar. Payment Application Security. Hap Huynh Business Leader Visa Inc. 1 April 2009

Frequently Asked Questions

Breach Findings for Large Merchants. 28 January 2015 Glen Jones Cyber Intelligence and Investigation Lester Chan Payment System Security

Qualified Integrators and Resellers (QIR) Implementation Statement

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

New PCI Standards Enhance Security of Cardholder Data

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

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

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

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

Franchise Data Compromise Trends and Cardholder. December, 2010

PCI Data Security Standards. Presented by Pat Bergamo for the NJTC February 6, 2014

Preventing. Payment Card Fraud. Is your business protected?

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

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

Payment Card Industry (PCI) Data Security Standard

White Paper September 2013 By Peer1 and CompliancePoint PCI DSS Compliance Clarity Out of Complexity

TNHFMA 2011 Fall Institute October 12, 2011 TAKING OUR CUSTOMERS BUSINESS FORWARD. The Cost of Payment Card Data Theft and Your Business

How To Protect Your Data From Being Stolen

Security. Tiffany Trent-Abram VP, Global Product Management. November 6 th, One Connection - A World of Opportunities

Payment Card Industry Security Standards PCI DSS, PCI-PTS and PA-DSS

PLACE GROUP UK LONDON STUDENT HOUSING GROUP PAYMENT CARD INDUSTRY DATA SECURITY STANDARD COMPLIANCE STATEMENT PCI DSS (09) VERSION: 2009PCIDSSP4S01

Property of CampusGuard. Compliance With The PCI DSS

Payment Card Industry - Achieving PCI Compliance Steps Steps

PCI DSS FAQ. The twelve requirements of the PCI DSS are defined as follows:

Data Security Basics for Small Merchants

PCI Compliance for Cloud Applications

A MERCHANTS GUIDE TO THE PAYMENT APPLICATION DATA SECURITY STANDARD (PA-DSS)

BAE Systems PCI Essentail. PCI Requirements Coverage Summary Table

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

Introduction to PCI DSS

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

PCI Compliance: How to ensure customer cardholder data is handled with care

Payment Card Industry Data Security Standard (PCI DSS) Q & A November 6, 2008

Protecting Personal Information: The Massachusetts Data Security Regulation (201 CMR 17.00)

Your Compliance Classification Level and What it Means

PAI Secure Program Guide

Achieving Compliance with the PCI Data Security Standard

Security Breaches and Vulnerability Experiences Overview of PCI DSS Initiative and CISP Payment Application Best Practices Questions and Comments

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

PCI COMPLIANCE GUIDE For Merchants and Service Members

Policy for Protecting Customer Data

PCI Compliance Top 10 Questions and Answers

PCI DSS Compliance for Cloud-Based Contact Centers Mitigating Liability through the Standardization of Processes for cloud-based contact centers.

PCI Requirements Coverage Summary Table

Fraud Protection, You and Your Bank

Presented By: Bryan Miller CCIE, CISSP

Payment Card Industry (PCI) Data Security Standard

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

SecurityMetrics Introduction to PCI Compliance

PCI Requirements Coverage Summary Table

Data Security & PCI Compliance & PCI Compliance Securing Your Contact Center Securing Your Contact Session Name :

The Cost of Payment Card Data Theft and Your Business. Aaron Lego Director of Business Development

Policies and Procedures

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

Practice Good Enterprise Security Management. Presented by Laurence CHAN, MTR Corporation Limited

Payment Card Industry (PCI) Data Security Standard

Varonis Systems & The Payment Card Industry Data Security Standard (PCI DSS)

University of Sunderland Business Assurance PCI Security Policy

Accepting Payment Cards and ecommerce Payments

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

Two Approaches to PCI-DSS Compliance

Best practices and insight to protect your firm today against tomorrow s cybersecurity breach

PCI Compliance. Top 10 Questions & Answers

HOW SECURE IS YOUR PAYMENT CARD DATA?

CHEAT SHEET: PCI DSS 3.1 COMPLIANCE

An article on PCI Compliance for the Not-For-Profit Sector

PCI: The Dark Side. May 2012 Roanoke, VA

PCI Security Compliance

Becoming PCI Compliant

Maintaining PCI-DSS compliance. Daniele Bertolotti Antonio Ricci

Credit Card Processing Overview

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

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

Why Is Compliance with PCI DSS Important?

Payment Card Industry (PCI) Data Security Standard. Attestation of Compliance for Self-Assessment Questionnaire C-VT. Version 2.0

What To Do if Compromised. Visa USA Fraud Investigations and Incident Management Procedures

Key Steps to Meeting PCI DSS 2.0 Requirements Using Sensitive Data Discovery and Masking

PCI DSS Payment Card Industry Data Security Standard. Merchant compliance guidelines for level 4 merchants

PCI Data Security Standards

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

PCI: It Never Ends. Why?

Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire D and Attestation of Compliance

Payment Card Industry Data Security Standard (PCI DSS) v1.2

PCI Compliance. Crissy Sampier, Longwood University Edward Ko, CampusGuard

MIT s Information Security Program for Protecting Personal Information Requiring Notification. (Revision date: 2/26/10)

PCI Compliance: Protection Against Data Breaches

Transcription:

Mark Shelhart, CFI, CISSP, QSA Security & Compliance, Sikich LLP

1. Credit card breaches 2. Disgruntled IT, bad leaver 3. Personal records breach 4. Vendor network connections (and contracts) 5. Everything else 6. Bi Bring your own device or BYOD (yes, very low on this list) 7. Lost/stolen machines

Magnetic stripe data is the information on the BACK of a credit card Contains account number, name, expiration and many hidden digits needed to process a transaction

No other personal data (SSNs, street address, etc.) Track data is the holy grail for data thieves

The investigation Fines by the card brands Reissuance costs and fraud from issuing banks Regulatory penalties Loss of IT time Increased IT/audit budgets

General counsel Information technology Emotionally committed Already overworked Outside counsel Public relations Federal law enforcement Executive leadership How do YOU define the word breach?

Who found the breach? Customers? Law enforcement? Bank? Containment Catch the bad guy, or Stop the bleeding Acquisition Analysis Customer notification Regulatory notification Rebuilding Brand Technology

Your investigation Catch the bad guy versus stop the attack, versus prevent future attacks State laws 47 states prescribe timing (30-45 days), format and content of required consumer notification State Attorneys General 19 states require separate notices to AG Focus on consumer protection Varying interpretations

(and have been for years)

Attackers used to target major metro area Looking for back of house (BOH), POS, Micros One laptop could scan 1 million IPs in four hours ~1,200 would become potential victims i > 50 would be easy targets Many merchants were STORING track data TJX > 90 million records

Target: Major sporting arena Magnitude: This single location housed 80,000 people twice a week Method of entry: Remote access; no anti-virus

Details: The attacker s malware specifically looked for programs named after popular tokenization applications Date range: 14 months

Requirement 1: Install and maintain a firewall configuration to protect cardholder data Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters Requirement 3: Protect stored cardholder data Requirement 4: Encrypt transmission of cardholder data across open, public networks

Requirement 5: Use and regularly update anti-virus software or programs Requirement 6: Develop and maintain secure systems and applications Requirement 7: Restrict access to cardholder data by business need-to-know Requirement 8: Assign a unique ID to each person with computer access

Requirement 9: Restrict physical access to cardholder data Requirement 10: Track and monitor all access to network resources and cardholder data Requirement 11: Regularly test security systems and processes Requirement 12: Maintain a policy that addresses information security for all personnel

More focused/targeted attacks based on time and effort efficiency i Why target thousands of IPs for random scanning if I can get data from one access point? Fraudulent cards are being sold based on a more targeted and geographically based approach Selling by card brand, BIN and even ZIP code Attackers are entering the premises Terminal swaps grocery, liquor stores ATM physical breach

Rare but growing attack vector Dangerous as it also captures PIN information Attackers often replace the remote/desolate device Prevention examine machines daily

Vendor remote access Vendor servers on network Often IT does not have control No anti-virus, not patched, weak passwords Vendor on network with BYOD Vendors without incident response details in their contract

Resellers and integrators are the Achilles heel of POS users 100-1,000 businesses can be breached in a matter of hours Resellers often make quasi- strong passwords Attackers quickly figure these out

Backoff also has some direct correlation to phishing attacks Attackers are phishing IT people to gain LogMeIn credentials IT people are smart, but often busy IT people p often don t apply the same security to their own PCs

Main areas of focus: Third-party service provider due diligence Service correlation to PCI DSS requirements Written agreements and policies/procedures Monitoring service provider compliance status

Typically covers up to $50k or $100k Forensic investigation Fines and penalties Card replacement costs Some plans cover POS system upgrades Makes the post-breach process better all around For the merchant Allows things to move faster/easier to work with For the acquirer Knows they will not be left holding the bag on all the possible costs

Cyber insurance typically covers: Forensic investigation (overlap with breach protection) Should include first party and third party activities Crisis management costs notifications, etc. May include coverage of consumer civil suits relating to identity theft

Securing remote access ( 14 & 15 breaches) Must be turned on by a human at the store locations Two-factor authentication Management, not just IT, should get notification when someone is working on the critical systems Firewalls that block outbound connectivity i Your board should understand what whitelisting means Corporations (and firewall vendors) should not let merchants opt out

Segmentation Corporate networks and guest wireless should be separate from critical systems Site-to-site to communication should be forbidden, even for IT functions

PCI or otherwise TJX (2006) Target (2013) Reduce your liability This includes infrastructure Patching server in Office A should not reach Office B

Block outbound connectivity whitelist, not blacklist for critical infrastructure Segmentation Users (and servers) in Office A should not be able to access Office B Remote access Control it, MONITOR it 11:00 p.m. remote access is no different than an employee in the office at 11:00 p m employee in the office at 11:00 p.m. Two-factor authentication, no exceptions

Service accounts (or any unchanged passwords) Integrate humans into security monitoring Vendors Fix contracts to allow audits and investigations Vendors also include the cloud

If the last 30 minutes did not scare you: Corporate espionage Would your competitors want to know your success methods, your budget? Domestic or foreign Road warrior dangers Tradeshow spying

Mark Shelhart, CFI, CISSP, QSA Sikich LLP mshelhart@sikich.com www.sikich.com 877 877.403.5227 403 5227 x221