High-Value Targets Retailers Under Fire
|
|
|
- Phyllis Norton
- 10 years ago
- Views:
Transcription
1 High-Value Targets Retailers Under Fire Issue Like all organizations in the distributed industry sector, retail businesses are challenged with the objective of maintaining financial health and growing in an era when consumer behavior and shopping methods are evolving at a tremendous rate. In order to respond to such rapid evolution, these businesses are adopting the core concepts and principals associated with omni-channel retailing. Omni-channel retailing is the next generation of multi-channel retailing, with a focus on a seamless approach to consumer experience through all available shopping channels, e.g., mobile Internet-ready devices, computers, brick-and-mortar stores, television, radio, direct mail, catalog and so on. In order to accomplish this objective, retail businesses have deployed heavily customized software, rearchitected networks, established interconnectivity with new business partners, deployed specialized retail technology and further invested in web and mobile capabilities. And while retailers are working to ensure a more seamless experience and achieve customer market share, this integration can come at a hefty price far beyond the cost of implementation when capitalized upon by an attacker. Several characteristics of such networks in the retail environment help to make them a prime target for a sophisticated attacker: Diversified/distributed systems Rapid customization Integrated offerings High-value targets The compliance curse The checkbox approach Diversified/distributed systems The more diversified the system inventory, the more difficult it is to manage security effectively. Core tenets and services offered by information security departments are thinned across a diversified infrastructure, and the IT resources required to enforce security cannot act quickly enough to respond to remedial requirements. Common issues include: Decreased efficiencies in vulnerability identification, configuration enforcement and system patching Need for further customization and baselining of logging and monitoring resources in order to provide adequate coverage. As a result, detection and alerting capabilities are reduced. Need for additional ports and system interconnections to support diversified services. A larger number of legitimate services, protocols and interconnections make it significantly more difficult to identify malicious activity. Furthermore, the risks associated with diversification of systems are compounded when those systems span a vast and/or global network environment making the proverbial haystack larger, and finding the needle much more difficult..
2 Rapid customization In responding to consumer demand, retailers continually seek to enhance their internal technologies. Further, given the increased presence of analytical data, internal knowledge capital and pressures of management to be innovative, many retailers embark on development efforts to customize software in support of achieving business objectives. However, several risks can result from customization. For example, quickly developed applications may be developed insecurely and result in vulnerabilities that are later exploited. Integrated offerings Just as in many other industries, retail merchants often rely upon third-party vendors to support the business, and will often share cardholder data with these service providers, grant them access to the company networks, and/or allow them to place systems on those networks. Although this practice is commonly used to streamline and diversify offerings, it also poses risk by increasing the number of attack vectors. Merchants typically have limited visibility into business partner systems that are permitted to reside on a merchant s network. Without the ability to manage or monitor the system or review the system logs, it is difficult to know if and when a partner s system is compromised. It is important to ensure that contracts with partners include the right to a forensic review of their systems and system logs, in the event that an investigation is necessary. Partner systems that do not require access to cardholder data should be segmented from the cardholder data environment (CDE) or, if that s not possible, the merchant should treat that system as untrusted and encrypt the cardholder data (CHD) traffic on that internal segment to prevent eavesdropping. High-value targets Quite simply, most types of attackers (e.g., opportunistic attackers, organized criminals, cyber-terrorists) focus their efforts where there is the most profit to be gained. The result is that most malicious efforts and elaborate strategies are focused on exploiting vulnerabilities and systems specific to financial services institutions and retail businesses that process, store or transact personally identifiable information (PII). The compliance curse Compliance with Payment Card Industry Data Security Standards (PCI DSS) requirements has never been less of a guarantee of protection from credit card theft. The PCI DSS exists as a minimum security standard for merchants, and while this may reduce the risk of credit card theft to a level acceptable by the payment card brands, it does not eliminate the risk to businesses or address the sophisticated attacks to which they are exposed. To reduce the scope of their compliance obligations, some organizations have taken to segmenting their CDE; however, this segmentation is often not effective, as attackers can use connected zones as a way in, often leveraging common ports and services that are used legitimately within the environment. PCI DSS 3.0 attempts to qualify segmentation more strictly, but even this may not be enough. There is no requirement to encrypt card data at swipe or as it traverses the internal network. Therefore malware, such as traffic monitoring tools, key stroke loggers, memory scrappers, etc., that is introduced to the CDE and is able to evade anti-virus detection 1 could easily lead to credit card data being compromised. In addition, attackers frequently exploit privileged and service accounts, traditionally difficult to eliminate in the environment and a common exception ( compensating control ) for PCI. Other compliance standards (ISO 27001, NIST SP , COBIT) are too broad and high-level to address the specific vulnerabilities that attackers are exploiting. The SANS 20 Critical Security Controls for Effective Cyber Defense tie real-world attack types to specific security measures and controls, but require a high level of maturity in security capabilities and significant investment to achieve. While standards give comfort to senior management and third parties that security is being addressed, compliance can be a curse in the sense that it diverts security professionals time and attention from focusing on the specific risks to meeting general requirements. Security professionals should seek guidance relevant to their environment and focus on high-impact controls such as application whitelisting to help prevent malicious or unapproved programs from running, and implementing patch maintenance for third-party applications (e.g., PDF viewer, MS Office, ActiveX objects and other web browser plugins). 1 Research indicates that newly created malware has an anti-virus detection rate as low as 5 percent, Protiviti 2
3 The checkbox approach Once, checking the box literally meant leveraging a checklist as a method of demonstrating organizational diligence in the accomplishment of governance. Today, much as everything else within the world of cybersecurity, the checkbox approach has become more evolved. The results, however, are similarly ineffective in addressing specific real-life threats. In modern day box-checking, organizations default to the execution of compliance tasks that meet the bare minimum requirements to satisfy industry requirements (e.g., PCI DSS). Assessors attempt to validate the security of a globally distributed enterprise by having a third party execute services remotely, and by spending mere days in the evaluation of a network that takes hundreds of personnel thousands of hours annually to manage. While the checkbox approach and a casual table-top incident response exercise will still allow retailers to demonstrate their compliance with industry regulations, today s typical attack scenario is far more difficult to manage. Most attacker malware can leverage various means of exfiltration. It is being designed to circumvent controls specifically developed to prevent or detect attempts to gain access to critical systems and infrastructure processing sensitive data, including credit card data and other PII. Further to the point, the checkbox approach is not sufficient in the identification of the weakest links, or chinks in the armor, that exist in organizational defense networks and can be subject to attacker reconnaissance and exploitation. Challenges Organizations are not prepared for the inevitability of cyberattacks and to a certain extent, they never will be. Based on our execution of incident response services and interactions with the law enforcement community, we understand the following: Some hacker networks have more optimized development capabilities than many mid-sized businesses. Credit card memory scraping malware continues to evolve in its capabilities to store, exfiltrate, and delete traces of itself and the resulting output. Hackers do their homework and custom-design malicious code to interact with even proprietary systems residing within business environments. Malware is being designed to cloak itself and leverage the most common services deployed in retail businesses and their most common technologies. It is unfortunate, but in many cases, attacker networks implement better security controls in the design of their software than Fortune 500 companies, leveraging sophisticated encryption, not relying on common ports, and designing software with redundancy to ensure the availability and execution of their services within the victim environment. Our Point of View While this outlook seems bleak, there are many actions organizations can take to help minimize the duration and impact of such attacks. Compensate for your compensating controls Many organizations rely on cost/benefit or business justifications to limit their implementation of specific security controls. For example, while it may be easier to continue to allow for the clear-text transmission of hard-coded passwords and perform heightened periodic monitoring and alerting of authentications to cardholder systems as a compensating control, an attacker will still fully utilize the clear-text transmission to his or her advantage. Environment awareness Card systems are vast, and in the absence of intermediary devices that will log specific system interaction, it is difficult to pursue an advanced attack within a globally distributed POS or financial system network. Applying firewalls at the perimeter only helps to identify malicious behaviors traversing two segments, but not the malicious activities occurring between one and the other. For this reason, it is important to know your systems, and maintain gold images and configuration data that allow for comparison and analysis in the event of an attack. Protiviti 3
4 Logging Yes, logging. Anti-virus software only detects a percentage of malware intrusion detection and prevention tools (IDS and IPS) only capture events that have signature or rules they are designed to prevent. The only thing absolute to assist in investigations and analysis is the raw logs. And while space may be costly, organizations should acknowledge that a breach is inevitable and ask themselves the question: Does the cost of verbose logging which can shorten an investigation considerably outweigh the cost of a much longer investigation that results in inconclusive evidence and forces the company to notify more consumers of a potential breach than might have been actually impacted by the attack? Broaden your focus Compromise of critical infrastructure can have a dramatic impact on financial systems, even if they are segmented. For example, a domain controller in a far-removed domain or group deserves the same control as a point-of-sale server, due to the domain controller s administrative capabilities. How We Help Companies Succeed Protiviti has responded to some of the most significant and industry-relevant security breaches in the last decade. Some of the largest Wall Street companies turned to us for critical help with their responses to cyberattacks. In addition, Protiviti led the financial services community for the past several years in the development and planning of global situational tabletops designed to better prepare organizations for cyberattacks, consistent with emerging attacker trends and capabilities. If your company is suspecting a credit card breach, Protiviti is one of 12 firms qualified by the PCI SSC to perform an investigation. We are uniquely qualified to provide assistance in security services both in the wake of a cyberattack and as an agent to assist organizations in a proactive response to one. Apart from industry recognition as a leading provider of incident response and forensic services by the PCI SSC, Protiviti has deep expertise in the areas of response execution, forensic analysis and response plan development. Our expertise stems from multiple engagements, industry participation, extensive professional relationships, training, and dedication to the development and enhancement of incident response practices. Example Protiviti recently came to the assistance of a large organization that suspected a sophisticated breach had occurred but was unable to prove it. Since no readily apparent signs of the breach existed, Protiviti initiated comparison of gold" images to binaries which existed on our client s system, searching for telltale signs of malicious binaries. We identified and reverse-engineered the credit card memory scraping malware that was discovered through our process. The malware had been customized for our client s specific environment, and several of the malware elements used had not yet been detected by any known anti-virus signature. While on the ground, Protiviti s team quickly put in place plans and action items to securely identify and remove presence of the attackers. Managing the incident response included working with all stakeholders to coordinate various aspects of breach management. As a result of our work, our client was able to stop the breach quickly and prevent further compromise of customers credit card information. Moreover, the client is now fully confident that it can continue to operate safely following this incident. Protiviti 4
5 About Protiviti Protiviti ( is a global consulting firm that helps companies solve problems in finance, technology, operations, governance, risk and internal audit. Through our network of more than 70 offices in over 20 countries, we have served more than 35 percent of FORTUNE 1000 and FORTUNE Global 500 companies. We also work with smaller, growing companies, including those looking to go public, as well as with government agencies. Protiviti is a wholly owned subsidiary of Robert Half (NYSE: RHI). Founded in 1948, Robert Half is a member of the S&P 500 index. Contacts Rocco F. Grillo, CISSP Managing Director Global Incident Response Leader [email protected] Joseph A. Rivela, CISSP, GCIH Director Lead Response Coordinator [email protected] Boyd S. White, CISSP, GCIH Manager Response Team Lead [email protected] 2014 Protiviti Inc. An Equal Opportunity Employer. Protiviti is not licensed or registered as a public accounting firm and does not issue opinions on financial statements or offer attestation services
Franchise Data Compromise Trends and Cardholder. December, 2010
Franchise Data Compromise Trends and Cardholder Security Best Practices December, 2010 Franchise Data Security Agenda Cardholder Data Compromise Overview Breach Commonalities Hacking Techniques Franchisee
Payment Card Industry Data Security Standards
Payment Card Industry Data Security Standards Discussion Objectives Agenda Introduction PCI Overview and History The Protiviti Difference Questions and Discussion 2 2014 Protiviti Inc. CONFIDENTIAL: This
PCI Compliance. Top 10 Questions & Answers
PCI Compliance Top 10 Questions & Answers 1. What is PCI Compliance and PCI DSS? 2. Who needs to follow the PCI Data Security Standard? 3. What happens if I don t comply? 4. What are the basic requirements
Cyber - Security and Investigations. Ingrid Beierly August 18, 2008
Cyber - Security and Investigations Ingrid Beierly August 18, 2008 Agenda Visa Cyber - Security and Investigations Today s Targets Recent Attack Patterns Hacking Statistics (removed) Top Merchant Vulnerabilities
PCI Data Security Standards (DSS)
ENTERPRISE APPLICATION WHITELISTING SOLUTION Achieving PCI Compliance at the Point of Sale Using Bit9 Parity TM to Protect Cardholder Data PCI: Protecting Cardholder Data As the technology used by merchants
PCI Compliance Top 10 Questions and Answers
Where every interaction matters. PCI Compliance Top 10 Questions and Answers White Paper October 2013 By: Peer 1 Hosting Product Team www.peer1.com Contents What is PCI Compliance and PCI DSS? 3 Who needs
PCI DSS 3.0 : THE CHANGES AND HOW THEY WILL EFFECT YOUR BUSINESS
PCI DSS 3.0 : THE CHANGES AND HOW THEY WILL EFFECT YOUR BUSINESS CIVICA Conference 22 January 2015 WELCOME AND AGENDA Change is here! PCI-DSS 3.0 is mandatory starting January 1, 2015 Goals of the session
Best Practices for PCI DSS V3.0 Network Security Compliance
Best Practices for PCI DSS V3.0 Network Security Compliance January 2015 www.tufin.com Table of Contents Preparing for PCI DSS V3.0 Audit... 3 Protecting Cardholder Data with PCI DSS... 3 Complying with
Encryption and Tokenization: Protecting Customer Data. Your Payments Universally Amplified. Tia D. Ilori Sue Zloth September 18, 2013
Encryption and Tokenization: Protecting Customer Data Your Payments Universally Amplified Tia D. Ilori Sue Zloth September 18, 2013 Agenda Global Threat Landscape Real Cost of a Data Breach Evolution of
Is the PCI Data Security Standard Enough?
Is the PCI Data Security Standard Enough? By: Christina M. Freeman ICTN 6870 Advanced Network Security Abstract: This paper will present the researched facts on Payment Card Industry Data Security Standard
PCI DSS 3.0 Changes Bill Franklin Executive IT Auditor [email protected] January 23, 2014
PCI DSS 3.0 Changes Bill Franklin Executive IT Auditor [email protected] January 23, 2014 Agenda Introduction PCI DSS 3.0 Changes What Can I Do to Prepare? When Do I Need to be Compliant? Questions
Breach Findings for Large Merchants. 28 January 2015 Glen Jones Cyber Intelligence and Investigation Lester Chan Payment System Security
Breach Findings for Large Merchants 28 January 2015 Glen Jones Cyber Intelligence and Investigation Lester Chan Payment System Security Disclaimer The information or recommendations contained herein are
March 2012 www.tufin.com
SecureTrack Supporting Compliance with PCI DSS 2.0 March 2012 www.tufin.com Table of Contents Introduction... 3 The Importance of Network Security Operations... 3 Supporting PCI DSS with Automated Solutions...
New PCI Standards Enhance Security of Cardholder Data
December 2013 New PCI Standards Enhance Security of Cardholder Data By Angela K. Hipsher, CISA, QSA, Jeff A. Palgon, CPA, CISSP, QSA, and Craig D. Sullivan, CPA, CISA, QSA Payment cards a favorite target
Managed Hosting & Datacentre PCI DSS v2.0 Obligations
Any physical access to devices or data held in an Melbourne datacentre that houses a customer s cardholder data must be controlled and restricted only to approved individuals. PCI DSS Requirements Version
Global Partner Management Notice
Global Partner Management Notice Subject: Critical Vulnerabilities Identified to Alert Payment System Participants of Data Compromise Trends Dated: May 4, 2009 Announcement: To support compliance with
Defending Against Data Beaches: Internal Controls for Cybersecurity
Defending Against Data Beaches: Internal Controls for Cybersecurity Presented by: Michael Walter, Managing Director and Chris Manning, Associate Director Protiviti Atlanta Office Agenda Defining Cybersecurity
CHAPTER 3 : INCIDENT RESPONSE FIVE KEY RECOMMENDATIONS GLOBAL THREAT INTELLIGENCE REPORT 2015 :: COPYRIGHT 2015 NTT INNOVATION INSTITUTE 1 LLC
: INCIDENT RESPONSE FIVE KEY RECOMMENDATIONS 1 FIVE KEY RECOMMENDATIONS During 2014, NTT Group supported response efforts for a variety of incidents. Review of these engagements revealed some observations
Network Segmentation
Network Segmentation The clues to switch a PCI DSS compliance s nightmare into an easy path Although best security practices should be implemented in all systems of an organization, whether critical or
Advanced Threat Protection with Dell SecureWorks Security Services
Advanced Threat Protection with Dell SecureWorks Security Services Table of Contents Summary... 2 What are Advanced Threats?... 3 How do advanced threat actors operate?... 3 Addressing the Threat... 5
White Paper THE FOUR ATTACK VECTORS TO PREVENT OR DETECT RETAILER BREACHES. By James Christiansen, VP, Information Risk Management
White Paper THE FOUR ATTACK VECTORS TO PREVENT OR DETECT RETAILER BREACHES By James Christiansen, VP, Information Risk Management Executive Summary Security breaches in the retail sector are becoming more
Top Five Data Security Trends Impacting Franchise Operators. Payment System Risk September 29, 2009
Top Five Data Security Trends Impacting Franchise Operators Payment System Risk September 29, 2009 Top Five Data Security Trends Agenda Data Security Environment Compromise Overview and Attack Methods
CHEAT SHEET: PCI DSS 3.1 COMPLIANCE
CHEAT SHEET: PCI DSS 3.1 COMPLIANCE WHAT IS PCI DSS? Payment Card Industry Data Security Standard Information security standard for organizations that handle data for debit, credit, prepaid, e-purse, ATM,
Protecting Your Organisation from Targeted Cyber Intrusion
Protecting Your Organisation from Targeted Cyber Intrusion How the 35 mitigations against targeted cyber intrusion published by Defence Signals Directorate can be implemented on the Microsoft technology
How To Secure Your Store Data With Fortinet
Securing Wireless Networks for PCI Compliance Using Fortinet s Secure WLAN Solution to Meet Regulatory Requirements Introduction In the wake of many well-documented data breaches, standards such as the
How To Protect Your Credit Card Information From Being Stolen
Visa Account Information Security Tool Kit Welcome to the Visa Account Information Security Program 2 Contents 1. Securing cardholder data is everyone s concern 4 2. Visa Account Information Security (AIS)
ASSUMING A STATE OF COMPROMISE: EFFECTIVE DETECTION OF SECURITY BREACHES
ASSUMING A STATE OF COMPROMISE: EFFECTIVE DETECTION OF SECURITY BREACHES Leonard Levy PricewaterhouseCoopers LLP Session ID: SEC-W03 Session Classification: Intermediate Agenda The opportunity Assuming
whitepaper 4 Best Practices for Building PCI DSS Compliant Networks
4 Best Practices for Building PCI DSS Compliant Networks Cardholder data is a lucrative and tempting target for cyber criminals. Recent highly publicized accounts of hackers breaching trusted retailers
Overcoming PCI Compliance Challenges
Overcoming PCI Compliance Challenges Randy Rosenbaum - Security Services Exec. Alert Logic, CPISM Brian Anderson - Product Manager, Security Services, SunGard AS www.sungardas.com Goal: Understand the
PCI DSS Requirements - Security Controls and Processes
1. Build and maintain a secure network 1.1 Establish firewall and router configuration standards that formalize testing whenever configurations change; that identify all connections to cardholder data
Achieving Compliance with the PCI Data Security Standard
Achieving Compliance with the PCI Data Security Standard June 2006 By Alex Woda, MBA, CISA, QDSP, QPASP This article describes the history of the Payment Card Industry (PCI) data security standards (DSS),
PCI Compliance for Cloud Applications
What Is It? The Payment Card Industry Data Security Standard (PCIDSS), in particular v3.0, aims to reduce credit card fraud by minimizing the risks associated with the transmission, processing, and storage
V ISA SECURITY ALERT 13 November 2015
V ISA SECURITY ALERT 13 November 2015 U P DATE - CYBERCRIMINALS TARGE TING POINT OF SALE INTEGRATORS Distribution: Value-Added POS Resellers, Merchant Service Providers, Point of Sale Providers, Acquirers,
How NETGEAR ProSecure UTM Helps Small Businesses Meet PCI Requirements
How NETGEAR ProSecure UTM Helps Small Businesses Meet PCI Requirements I n t r o d u c t i o n The Payment Card Industry Data Security Standard (PCI DSS) was developed in 2004 by the PCI Security Standards
Full-Context Forensic Analysis Using the SecureVue Unified Situational Awareness Platform
Full-Context Forensic Analysis Using the SecureVue Unified Situational Awareness Platform Solution Brief Full-Context Forensic Analysis Using the SecureVue Unified Situational Awareness Platform Finding
How To Protect A Web Application From Attack From A Trusted Environment
Standard: Version: Date: Requirement: Author: PCI Data Security Standard (PCI DSS) 1.2 October 2008 6.6 PCI Security Standards Council Information Supplement: Application Reviews and Web Application Firewalls
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
Over 90% of all compromised merchants are PCI level 4 (small) merchants or merchants with less than 1 million transactions per year Over 80% of compromised systems were card present or in-person transactions
ARE YOU REALLY PCI DSS COMPLIANT? Case Studies of PCI DSS Failure! Jeff Foresman, PCI-QSA, CISSP Partner PONDURANCE
ARE YOU REALLY PCI DSS COMPLIANT? Case Studies of PCI DSS Failure! Jeff Foresman, PCI-QSA, CISSP Partner PONDURANCE AGENDA PCI DSS Basics Case Studies of PCI DSS Failure! Common Problems with PCI DSS Compliance
Preparing for PCI DSS 3.0 & Ensuring a Seamless Transition. November 2013
Preparing for PCI DSS 3.0 & Ensuring a Seamless Transition November 2013 Introductions Brian Serra PCI Practice Director Nick Puetz Managing Director - Strategic Services 2013 FishNet Security Inc. All
Administrative Improvements. Administrative Improvements. Scoping Guidance. Clarifications for Segmentation
The PCI DSS Lifecycle 1 The PCI DSS follows a three-year lifecycle PCI DSS 3.0 will be released in November 2013 Optional (but recommended) in 2014; Required in 2015 PCI SSC Community Meeting Update: PCI
The Importance of Cybersecurity Monitoring for Utilities
The Importance of Cybersecurity Monitoring for Utilities www.n-dimension.com Cybersecurity threats against energy companies, including utilities, have been increasing at an alarming rate. A comprehensive
Payment Card Industry Data Security Standard
Symantec Managed Security Services support for IT compliance Solution Overview: Symantec Managed Services Overviewview The (PCI DSS) was developed to facilitate the broad adoption of consistent data security
Template for PFI Final Incident Report for Remote Investigations
Payment Card Industry (PCI) Data Security Standard PFI Final Incident Report for Remote Investigations Template for PFI Final Incident Report for Remote Investigations Version 1.1 February 2015 Document
PCI Assessments 3.0 What Will the Future Bring? Matt Halbleib, SecurityMetrics
PCI Assessments 3.0 What Will the Future Bring? Matt Halbleib, SecurityMetrics About Us Matt Halbleib CISSP, QSA, PA-QSA Manager PCI-DSS assessments With SecurityMetrics for 6+ years SecurityMetrics Security
PCI DSS Policies Outline. PCI DSS Policies. All Rights Reserved. ecfirst. 2010. Page 1 of 7 www.ecfirst.com
Policy/Procedure Description PCI DSS Policies Install and Maintain a Firewall Configuration to Protect Cardholder Data Establish Firewall and Router Configuration Standards Build a Firewall Configuration
Redhawk Network Security, LLC 62958 Layton Ave., Suite One, Bend, OR 97701 [email protected] 866-605- 6328 www.redhawksecurity.
Planning Guide for Penetration Testing John Pelley, CISSP, ISSAP, MBCI Long seen as a Payment Card Industry (PCI) best practice, penetration testing has become a requirement for PCI 3.1 effective July
Security Management. Keeping the IT Security Administrator Busy
Security Management Keeping the IT Security Administrator Busy Dr. Jane LeClair Chief Operating Officer National Cybersecurity Institute, Excelsior College James L. Antonakos SUNY Distinguished Teaching
Everything You Wanted to Know about DISA STIGs but were Afraid to Ask
Everything You Wanted to Know about DISA STIGs but were Afraid to Ask An EiQ Networks White Paper 2015 EiQ Networks, Inc. All Rights Reserved. EiQ, the EiQ logo, the SOCVue logo, SecureVue, ThreatVue,
MITIGATING LARGE MERCHANT DATA BREACHES
MITIGATING LARGE MERCHANT DATA BREACHES Tia D. Ilori Ed Verdurmen January 2014 1 DISCLAIMER The information or recommendations contained herein are provided "AS IS" and intended for informational purposes
Using Automated, Detailed Configuration and Change Reporting to Achieve and Maintain PCI Compliance Part 4
WHITEPAPER Using Automated, Detailed Configuration and Change Reporting to Achieve and Maintain PCI Compliance Part 4 An in-depth look at Payment Card Industry Data Security Standard Requirements 10, 11,
Case 2:13-cv-01887-ES-JAD Document 282-2 Filed 12/09/15 Page 1 of 116 PageID: 4879. Appendix A
Case 2:13-cv-01887-ES-JAD Document 282-2 Filed 12/09/15 Page 1 of 116 PageID: 4879 Appendix A Case 2:13-cv-01887-ES-JAD Document 282-2 Filed 12/09/15 Page 2 of 116 PageID: 4880 Payment Card Industry (PCI)
Introduction. PCI DSS Overview
Introduction Manage Engine Desktop Central is part of ManageEngine family that represents entire IT infrastructure with products such as Network monitoring, Helpdesk management, Application management,
Thoughts on PCI DSS 3.0. September, 2014
Thoughts on PCI DSS 3.0 September, 2014 Speaker Today Jeff Sanchez is a Managing Director in Protiviti s Los Angeles office. He joined Protiviti in 2002 after spending 10 years with Arthur Andersen s Technology
PCI Requirements Coverage Summary Table
StillSecure PCI Complete Managed PCI Compliance Solution PCI Requirements Coverage Summary Table January 2013 Table of Contents Introduction... 2 Coverage assumptions for PCI Complete deployments... 2
Security Breaches and Vulnerability Experiences Overview of PCI DSS Initiative and CISP Payment Application Best Practices Questions and Comments
Security in the Payment Card Industry OWASP AppSec Seattle Oct 2006 Hap Huynh, Information Security Specialist, Visa USA [email protected] Copyright 2006 - The OWASP Foundation Permission is granted to copy,
Information Supplement: Requirement 6.6 Code Reviews and Application Firewalls Clarified
Standard: Data Security Standard (DSS) Requirement: 6.6 Date: February 2008 Information Supplement: Requirement 6.6 Code Reviews and Application Firewalls Clarified Release date: 2008-04-15 General PCI
Payment Card Industry Data Security Standard Training. Chris Harper Vice President of Technical Services Secure Enterprise Computing, Inc.
Payment Card Industry Data Security Standard Training Chris Harper Vice President of Technical Services Secure Enterprise Computing, Inc. March 27, 2012 Agenda Check-In 9:00-9:30 PCI Intro and History
AIRDEFENSE SOLUTIONS PROTECT YOUR WIRELESS NETWORK AND YOUR CRITICAL DATA SECURITY AND COMPLIANCE
AIRDEFENSE SOLUTIONS PROTECT YOUR WIRELESS NETWORK AND YOUR CRITICAL DATA SECURITY AND COMPLIANCE THE CHALLENGE: SECURE THE OPEN AIR Wirelesss communication lets you take your business wherever your customers,
White Paper Achieving PCI Data Security Standard Compliance through Security Information Management. White Paper / PCI
White Paper Achieving PCI Data Security Standard Compliance through Security Information Management White Paper / PCI Contents Executive Summary... 1 Introduction: Brief Overview of PCI...1 The PCI Challenge:
Payment Card Industry (PCI) Data Security Standard ROC Reporting Instructions for PCI DSS v2.0
Payment Card Industry (PCI) Data Security Standard ROC Reporting Instructions for PCI DSS v2.0 September 2011 Changes Date September 2011 Version Description 1.0 To introduce PCI DSS ROC Reporting Instructions
PCI COMPLIANCE REQUIREMENTS COMPLIANCE CALENDAR
PCI COMPLIANCE REQUIREMENTS COMPLIANCE CALENDAR AUTHOR: UDIT PATHAK SENIOR SECURITY ANALYST [email protected] Public Network Intelligence India 1 Contents 1. Background... 3 2. PCI Compliance
How to complete the Secure Internet Site Declaration (SISD) form
1 How to complete the Secure Internet Site Declaration (SISD) form The following instructions are designed to assist you in completing the SISD form that forms part of your Merchant application. Once completed,
Payment Card Industry (PCI) Data Security Standard PFI Final Incident Report. Template for PFI Final Incident Report. Version 1.1.
Payment Card Industry (PCI) Data Security Standard PFI Final Incident Report Template for PFI Final Incident Report Version 1.1 February 2015 Document Changes Date Version Description August 2014 1.0 To
Becoming PCI Compliant
Becoming PCI Compliant Jason Brown - [email protected] Enterprise Security Architect Enterprise Architecture Department of Technology, Management and Budget State of Michigan @jasonbrown17 History
GFI White Paper PCI-DSS compliance and GFI Software products
White Paper PCI-DSS compliance and Software products The Payment Card Industry Data Standard () compliance is a set of specific security standards developed by the payment brands* to help promote the adoption
An article on PCI Compliance for the Not-For-Profit Sector
Level 8, 66 King Street Sydney NSW 2000 Australia Telephone +61 2 9290 4444 or 1300 922 923 An article on PCI Compliance for the Not-For-Profit Sector Page No.1 PCI Compliance for the Not-For-Profit Sector
PAYMENT CARD INDUSTRY (PCI) COMPLIANCE HISTORY & OVERVIEW
PAYMENT CARD INDUSTRY (PCI) COMPLIANCE HISTORY & OVERVIEW David Kittle Chief Information Officer Chris Ditmarsch Network & Security Administrator Smoker Friendly International / The Cigarette Store Corp
INFORMATION SUPPLEMENT. Migrating from SSL and Early TLS. Version 1.0 Date: April 2015 Author: PCI Security Standards Council
Version 1.0 Date: Author: PCI Security Standards Council Executive Summary The time to migrate is now. For over 20 years Secure Sockets Layer (SSL) has been in the market as one of the most widely-used
AlienVault for Regulatory Compliance
AlienVault for Regulatory Compliance Overview of Regulatory Compliance in Information Security As computers and networks have become more important in society they and the information they contain have
Are You Ready For PCI v 3.0. Speaker: Corbin DelCarlo Institution: McGladrey LLP Date: October 6, 2014
Are You Ready For PCI v 3.0 Speaker: Corbin DelCarlo Institution: McGladrey LLP Date: October 6, 2014 Today s Presenter Corbin Del Carlo QSA, PA QSA Director, National Leader PCI Services Practice 847.413.6319
Payment Card Industry (PCI) Data Security Standard PFI Final Incident Report. Template for PFI Final Incident Report. Version 1.0.
Payment Card Industry (PCI) Data Security Standard PFI Final Incident Report Template for PFI Final Incident Report Version 1.0 August 2014 Document Changes Date Version Description August 2014 1.0 To
Cybersecurity and internal audit. August 15, 2014
Cybersecurity and internal audit August 15, 2014 arket insights: what we are seeing so far? 60% of organizations see increased risk from using social networking, cloud computing and personal mobile devices
Payment Card Industry (PCI) Data Security Standard. Summary of Changes from PCI DSS Version 2.0 to 3.0
Payment Card Industry (PCI) Data Security Standard Summary of s from Version 2.0 to 3.0 November 2013 Introduction This document provides a summary of changes from v2.0 to v3.0. Table 1 provides an overview
SAQ D Compliance. Scott St. Aubin Senior Security Consultant QSA, CISM, CISSP
SAQ D Compliance Scott St. Aubin Senior Security Consultant QSA, CISM, CISSP Ground Rules WARNING: Potential Death by PowerPoint Interaction Get clarification Share your institution s questions, challenges,
TASK -040. TDSP Web Portal Project Cyber Security Standards Best Practices
Page 1 of 10 TSK- 040 Determine what PCI, NERC CIP cyber security standards are, which are applicable, and what requirements are around them. Find out what TRE thinks about the NERC CIP cyber security
Top Three POS System Vulnerabilities Identified to Promote Data Security Awareness
CISP BULLETIN Top Three POS System Vulnerabilities Identified to Promote Data Security Awareness November 21, 2006 To support compliance with the Cardholder Information Security Program (CISP), Visa USA
Enterprise Cybersecurity: Building an Effective Defense
: Building an Effective Defense Chris Williams Scott Donaldson Abdul Aslam 1 About the Presenters Co Authors of Enterprise Cybersecurity: How to Implement a Successful Cyberdefense Program Against Advanced
Professional Services Overview
Professional Services Overview INFORMATION SECURITY ASSESSMENT AND ADVISORY NETWORK APPLICATION MOBILE CLOUD IOT Praetorian Company Overview HISTORY Founded in 2010 Headquartered in Austin, TX Self-funded
Securing OS Legacy Systems Alexander Rau
Securing OS Legacy Systems Alexander Rau National Information Security Strategist Sample Agenda 1 Today s IT Challenges 2 Popular OS End of Support & Challenges for IT 3 How to protect Legacy OS systems
NATIONAL CYBER SECURITY AWARENESS MONTH
NATIONAL CYBER SECURITY AWARENESS MONTH Tip 1: Security is everyone s responsibility. Develop an awareness framework that challenges, educates and empowers your customers and employees to be part of the
TOP 10 WAYS TO ADDRESS PCI DSS COMPLIANCE. ebook Series
TOP 10 WAYS TO ADDRESS PCI DSS COMPLIANCE ebook Series 2 Headlines have been written, fines have been issued and companies around the world have been challenged to find the resources, time and capital
BAE Systems PCI Essentail. PCI Requirements Coverage Summary Table
BAE Systems PCI Essentail PCI Requirements Coverage Summary Table Introduction BAE Systems PCI Essential solution can help your company significantly reduce the costs and complexity of meeting PCI compliance
PCI Compliance - A Realistic Approach. Harshul Joshi, CISM, CISA, CISSP Director, Information Technology CBIZ MHM [email protected]
PCI Compliance - A Realistic Approach Harshul Joshi, CISM, CISA, CISSP Director, Information Technology CBIZ MHM [email protected] What What is PCI A global forum launched in September 2006 for ongoing enhancement
PCI DSS. Payment Card Industry Data Security Standard. www.tuv.com/id
PCI DSS Payment Card Industry Data Security Standard www.tuv.com/id What Is PCI DSS? PCI DSS (Payment Card Industry Data Security Standard) is the common security standard of all major credit cards brands.the
SolarWinds Security Information Management in the Payment Card Industry: Using SolarWinds Log & Event Manager (LEM) to Meet PCI Requirements
SolarWinds Security Information Management in the Payment Card Industry: Using SolarWinds Log & Event Manager (LEM) to Meet PCI Requirements SolarWinds Security Information Management in the Payment Card
Alert (TA14-212A) Backoff Point-of-Sale Malware
Alert (TA14-212A) Backoff Point-of-Sale Malware Original release date: July 31, 2014 Systems Affected Point-of-Sale Systems Overview This advisory was prepared in collaboration with the National Cybersecurity
AIRDEFENSE SOLUTIONS PROTECT YOUR WIRELESS NETWORK AND YOUR CRITICAL DATA SECURITY AND COMPLIANCE
AIRDEFENSE SOLUTIONS PROTECT YOUR WIRELESS NETWORK AND YOUR CRITICAL DATA SECURITY AND COMPLIANCE THE CHALLENGE: SECURE THE OPEN AIR Wirelesss communication lets you take your business wherever your customers,
Protect Your IT Infrastructure from Zero-Day Attacks and New Vulnerabilities
Protect Your IT Infrastructure from Zero-Day Attacks and New Vulnerabilities Protecting a business s IT infrastructure is complex. Take, for example, a retailer operating a standard multi-tier infrastructure
North Carolina Office of the State Controller Technology Meeting
PCI DSS Security Awareness Training North Carolina Office of the State Controller Technology Meeting April 30, 2014 agio.com A Note on Our New Name Secure Enterprise Computing was acquired as the Security
ADDING NETWORK INTELLIGENCE TO VULNERABILITY MANAGEMENT
ADDING NETWORK INTELLIGENCE INTRODUCTION Vulnerability management is crucial to network security. Not only are known vulnerabilities propagating dramatically, but so is their severity and complexity. Organizations
Section 3.9 PCI DSS Information Security Policy Issued: June 2016 Replaces: January 2015
Section 3.9 PCI DSS Information Security Policy Issued: June 2016 Replaces: January 2015 I. PURPOSE The purpose of this policy is to establish guidelines for processing charges on Payment Cards to protect
PCI Requirements Coverage Summary Table
StillSecure PCI Complete Managed PCI Compliance Solution PCI Requirements Coverage Summary Table December 2011 Table of Contents Introduction... 2 Coverage assumptions for PCI Complete deployments... 2
