Organizations outsourcing card data to the cloud face significant security risks. As soon as an organization adds other players to the offsite card-management mix, ensuring compliance with the PCI Data Security Standard becomes increasingly challenging. Cloud users and cloud service providers need to understand what their roles and responsibilities are when it comes to protecting this data. Storing, processing and transmitting cardholder data in the cloud brings the cloud environment into scope for PCI-DSS.
The Payment Card Industry Data Security Standard (PCI DSS) provides data protection requirements for organizations that process card payments. These requirements have even been adopted as law by some US states (e.g., Minnesota, Nevada, Washington). While organizations that fully comply with PCI DSS are considered compliant credit-card processors, compliance and security are not one in the same.
Recorded: 2011 Listen Now
Annual costs of data management are soaring. So how can your business stay ahead of the curve to achieve and maintain compliance with the Payment Card Industry Data Security Standards (PCI DSS) and still deal with potentially millions of points of vulnerability?
This session will focus on the value of internal tokenization in reducing scope and potential audit costs at the datacenter, with a specific focus on post-payment applications, databases, loyalty tracking systems, data warehousing, and business applications.
This event will discuss an overall payment security landscape, the costs associated with managing payment data, and the benefits of Tokenization. Attendees will learn how payment security solutions, such as encryption and tokenization can go beyond complying with PCI–DSS requirements and reduce the scope of PCI, while keeping data safe and alleviating the overall impact on your business.
Understanding and complying with the PCI Data Security Standard (PCI DSS) can be a daunting task - especially if your organization has limited time and resources. The new PCI DSS 2.0 standard, which took effect Jan. 1, requires testing a virtualized environment to ensure that if you put multiple accounts onto a single processor, there is still segregation of data and all the data is protected.