Welcome!

@CloudExpo Authors: Automic Blog, William Schmarzo, Elizabeth White, Dalibor Siroky, Mehdi Daoudi

Related Topics: @CloudExpo, Mobile IoT, Cloud Security

@CloudExpo: Blog Feed Post

PCI DSS: What You Need to Know By @GiladPN | @CloudExpo

Lack of education and awareness around payment security

By Lohit Mehta

Every organization should follow a proactive rather than a reactive approach to protect against threats, risks, and vulnerabilities to which if their IT infrastructure is exposed can lead to data loss, regulatory penalties, lawsuits, and damaged reputation. Moving on the same lines, to reduce credit card fraud via its exposure, a standard known as Payment Card Industry Data Security Standard (PCI DSS) was formed.

History

Payment Card Industry Security Standards Council (PCI SSC) had developed a standard known as PCI Data Security Standard (PCI DSS), which comprises 12 core security areas to protect credit card holder data from theft, misuse, etc. These requirements apply to all entities involved in payment card processing, including merchants, processors, and 3rd party service providers that store, process and transmit cardholder data. PCI DSS originally began as five different programs:

  • Visa’s Cardholder Information Security Program
  • MasterCard’s Site Data Protection
  • American Express’ Data Security Operating Policy
  • Discover’s Information Security and Compliance
  • JCB’s Data Security Program

The motive of the above listed companies was to protect the card holder by providing some guidelines to merchants or any other entity which is involved in storing, processing and transmitting cardholder data. From the above listed companies, a PCI Security Standards Council (SSC) was formed, and the first version of PCI DSS 1.0 was released in December 2004. Because of rapid changes in technology, new mode of payments, attack vectors, regulatory laws, etc., this version got back to back updates from 1.1 to 1.2. PCI subsequent versions 2.0 and 3.0 were released in October 2010 and November 2013 respectively.

One major theme that forms the basis of PCI-DSS 3.0, apart from some notable ones like education and awareness around payment security, increased flexibility to handle risks, and security as a shared responsibility, is to make PCI-DSS a Business As Usual (BAU) practice. The purpose of this document is to outlay the key drivers that led to PCI-DSS 3.0. Below are the key drivers and challenges that lead to PCI-DSS 3.0.

Lack of education and awareness around payment security

PCI DSS Encryption Requirements PCI Security Compliance PCI DSS Encryption PCI Compliance  PCI DSS Encryption PCI DSS: What You Need to Know

Due to lack of education and awareness around payment security, employees usually leave security holes in their developed applications by not following best security practices to code, picking up weak passwords, and sharing company information on public and social platforms. PCI-DSS 3.0 has incorporated requirements such as 8.4 that focus on personnel trainings, guidance around payment security, guidance for selecting and protecting authentication credentials, instructions to change passwords in case of any suspicion detected, etc.

The PCI-DSS council has gone a step ahead and also focuses on major sales points where card data is processed ie. POS terminal and brings these terminals under scope, as attacks on POS devices like cloning, addition of card skimmers, etc. are on a high. Requirement 9.9 which is to “Protect devices that capture card data via direct physical interaction with the card from tampering and substitution” is added to address the POS threat challenge. This requirement will now make organizations maintain an up-to date list of devices deployed at various sites. This list will contain information about POS devices such as:

  • Unique serial number of the device
  • Make and model of device
  • Location details at which it is deployed.

This requirement also focuses on providing training for end-personnel to be aware about the attempted tampering or replacement of authentic POS devices. Organizations need to conduct periodic reviews of devices to check for any evidence of substitution or tampering.

Third party security challenges

As per the security investigation report, 63 percent of security deficiencies that can result in breach or loss of cardholder data falls in the 3rd party IT landscape, whose business function is to process, transmit and store cardholder data received either from merchant or service providers. To handle crises whenever there is a breach resulting in cardholder data loss and no one to take ownership of that, PCI has added requirements 12.8, 12.9 to made it clear that both the engaging parties need to seal the deal with a written agreement, which should state a clear responsibility matrix. This requirement also requires the organization to do a proper due-diligence of the IT landscape, process, services offered, and security controls in place before entering into a formal agreement.

Along with the above stated requirement, PCI has also stated an additional requirement for service providers with requirement number 8.5.1 to maintain unique credentials for each customer when accessing their premises remotely for services like support of POS systems. This requirement will prevent the compromise of multiple customers’ account profiles in case the service provider used the same credentials for all the service providers and that in turn is compromised. Also service providers must set up strong credentials to access customer premises and should adopt best practice policies like a password change policy, etc.

Anti-malware solutions

The earlier PCI-DSS 2.0 standard specifies that there should be an antivirus solution deployed to protect the CDE environment from viruses, malware, etc. and that it should be completely updated with the latest patches and signatures, but the requirement did not specify about the access control settings over the AV software, such as access control over the AV manager, meaning who can only disable the AV solution and who can view its logs and edit the configuration changes. However in PCI-DSS 3.0, requirement 5.3 now requires organizations to deploy tighter policy based controls around antivirus solution that will require authorization to access and alter the configuration settings of the AV solution.

To keep controls deployment and maintenance costs in check, merchants generally come up with a classification of important endpoints that will be covered under security controls deployment like antivirus. Though asset classifications is a good practice, merchants do not generally update these lists with the ever-changing threat landscape. Keeping this in check, PCI-DSS has added a new requirement 5.1.2 which requires merchants to identify and evaluate evolving threats against systems which are not commonly affected by malicious software like mainframes, so as to develop a tighter antivirus security around all the systems in the CDE environment. Merchants can take guidance from vendors to understand the changing threat landscape and to evaluate whether their unprotected systems come under newly discovered vulnerabilities.

Penetration testing

One of the key drivers and significant changes in PCI-DSS 3.0 is addition of the requirement for merchants to conduct penetration testing on their cardholder environment. SSC has laid emphasis on the point that merchants/service providers must adopt an industry wide accepted penetration testing like NIST SP 800-15. PCI requirements also need to conduct penetration tests not only at the application level but also at the network level against devices that are deployed at the perimeter (say for segregation) or deployed inside CDE environment. PCI requirement 13.4 would require providers to conduct:

  • Annual penetration tests on the external network and when there is any significant change in infrastructure or applications deployed in CDE environment.
  • Annual penetration tests on the internal network and when there is any significant change in infrastructure or applications deployed in CDE environment.
  • Annual penetration tests on the boundary defense of CDE environment or around the segmentation controls that are used to isolate the CDE environment to check their effectiveness.
  • Adopt the cyclic process of Test (Conduct Penetration testing (PT)) > Remediate (Fix Vulnerabilities) > Re-Test (Conduct PT again) until all the vulnerabilities found are fixed.
  • Requires merchants/service providers to retain the Penetration testing results and remediation activities as per the adopted industry driven approach.

Inventory list

PCI has made it mandatory for retailers to maintain an inventory list of all the in-scope devices for CDE environment. With addition of requirement 2.4 which states, “Maintain an inventory of systems components that in scope of PCI DSS”, PCI made sure that retailers keep updating their inventory list with the already in action system components or to any newly added one. To avoid any confusion, PCI has also mentioned in some drilled down requirements what all needs to be put in the inventory list, such as:

  • Requirement no 11.1.1 states that “maintain an inventory of authorized wireless access points including a documented business justification ” will require retailers to maintain an inventory list for all access points with a proper business justification.
  • Requirement no 9.7.1 states that to “Properly maintain inventory logs of all media and conduct media inventories at least annually” will require retailers to maintain an inventory list of all the media so that stolen or missing media should not go unnoticed.
  • Requirement no 12.3.4 requires retailers to maintain an inventory of all physical devices with proper labeling to mark any unapproved installations.

However, the above stated requirement to maintain an inventory list will be very difficult for organizations to maintain until they fully practice the requirement no 1.1.3 which requires organizations to maintain an updated data flow diagram (DFD) to showcase all the controls that are in CDE environment. With an updated DFD, organizations will be able to classify what is in-scope and out of scope for their CDE environment.

Business as Usual (BaU)

One of the major themes of PCI-DSS 3.0 is to make it as a Business as Usual (BAU) Practice rather than compliance. As PCI-DSS covers a majority of mid-sized business that either do not have a large IT department or they have very few information security groups which can work to keep their business PCI-DSS-ready for audits and to incorporate any last minute hiccups. Making PCI-DSS as a BAU will require organizations to keep their PCI-DSS checklist updated regularly with any change in their CDE environment. Merchants should keep a check and document all the changes done in their cardholder data environment (CDE). These includes:

  • Regular monitoring of security controls like firewall, AV solutions, access controls, IDS/IPS, Security Incident and Event Management (SIEM), etc. in CDE environment to ensure that they are correct, updated and their functioning is secure.
  • Reviewing the security posture of the CDE environment with addition of new systems and devices, changes in configurations of security controls, organizational structure changes, etc.
  • Reviewing latest best practices, support issued by vendors for the security devices that are placed in CDE environment to make sure that the cardholder data is secured from evolving threats.

Conclusion

PCI-DSS 3.0 has incorporated some good new requirements as per the changing threat landscape, included the end user to understand about payment security, and clarified some statements for proper understanding of merchants and 3rd party service providers. Some of the changed requirements that are incorporated in PCI DSS 3.0 are termed as best practice for some time now, after which they will become mandatory for every organization to implement. PCI DSS 3.0 will surely make merchants, service providers or any entity that is processing, storing and transmitting cardholder data and is under PCI scope to revisit and enhance their existing strategy for protecting cardholder information.

References

https://www.pcisecuritystandards.org/documents/PCI_DSS_v3.pdf

Author Bio:
Lohit Mehta is a Security Researcher for the InfoSec Institute. He has experience working with RFPs/RFIs; Security HLD and LLD design; Network Security elements like Firewall, IDS/IPS, DLP, Reverse proxy, WAF; in Public Key Infrastructure(PKI); in Application Security testing for OWASP Top 10; in Compliance’s like PCI-DSS 2.0,3.0 , ISO 27k1, HIPPA; with Cloud Service Provider’s such as AWS; in Security Incident and Event Management(SIEM) with tools like Splunk; in Vulnerability Testing.

The post PCI DSS: What You Need to Know appeared first on Porticor Cloud Security.

More Stories By Gilad Parann-Nissany

Gilad Parann-Nissany, Founder and CEO at Porticor is a pioneer of Cloud Computing. He has built SaaS Clouds for medium and small enterprises at SAP (CTO Small Business); contributing to several SAP products and reaching more than 8 million users. Recently he has created a consumer Cloud at G.ho.st - a cloud operating system that delighted hundreds of thousands of users while providing browser-based and mobile access to data, people and a variety of cloud-based applications. He is now CEO of Porticor, a leader in Virtual Privacy and Cloud Security.

@CloudExpo Stories
Enterprises are adopting Kubernetes to accelerate the development and the delivery of cloud-native applications. However, sharing a Kubernetes cluster between members of the same team can be challenging. And, sharing clusters across multiple teams is even harder. Kubernetes offers several constructs to help implement segmentation and isolation. However, these primitives can be complex to understand and apply. As a result, it’s becoming common for enterprises to end up with several clusters. Thi...
In his session at 21st Cloud Expo, Carl J. Levine, Senior Technical Evangelist for NS1, will objectively discuss how DNS is used to solve Digital Transformation challenges in large SaaS applications, CDNs, AdTech platforms, and other demanding use cases. Carl J. Levine is the Senior Technical Evangelist for NS1. A veteran of the Internet Infrastructure space, he has over a decade of experience with startups, networking protocols and Internet infrastructure, combined with the unique ability to it...
"ZeroStack is a startup in Silicon Valley. We're solving a very interesting problem around bringing public cloud convenience with private cloud control for enterprises and mid-size companies," explained Kamesh Pemmaraju, VP of Product Management at ZeroStack, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"Space Monkey by Vivent Smart Home is a product that is a distributed cloud-based edge storage network. Vivent Smart Home, our parent company, is a smart home provider that places a lot of hard drives across homes in North America," explained JT Olds, Director of Engineering, and Brandon Crowfeather, Product Manager, at Vivint Smart Home, in this SYS-CON.tv interview at @ThingsExpo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"Codigm is based on the cloud and we are here to explore marketing opportunities in America. Our mission is to make an ecosystem of the SW environment that anyone can understand, learn, teach, and develop the SW on the cloud," explained Sung Tae Ryu, CEO of Codigm, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"Infoblox does DNS, DHCP and IP address management for not only enterprise networks but cloud networks as well. Customers are looking for a single platform that can extend not only in their private enterprise environment but private cloud, public cloud, tracking all the IP space and everything that is going on in that environment," explained Steve Salo, Principal Systems Engineer at Infoblox, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Conventio...
The question before companies today is not whether to become intelligent, it’s a question of how and how fast. The key is to adopt and deploy an intelligent application strategy while simultaneously preparing to scale that intelligence. In her session at 21st Cloud Expo, Sangeeta Chakraborty, Chief Customer Officer at Ayasdi, provided a tactical framework to become a truly intelligent enterprise, including how to identify the right applications for AI, how to build a Center of Excellence to oper...
"IBM is really all in on blockchain. We take a look at sort of the history of blockchain ledger technologies. It started out with bitcoin, Ethereum, and IBM evaluated these particular blockchain technologies and found they were anonymous and permissionless and that many companies were looking for permissioned blockchain," stated René Bostic, Technical VP of the IBM Cloud Unit in North America, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Conventi...
Gemini is Yahoo’s native and search advertising platform. To ensure the quality of a complex distributed system that spans multiple products and components and across various desktop websites and mobile app and web experiences – both Yahoo owned and operated and third-party syndication (supply), with complex interaction with more than a billion users and numerous advertisers globally (demand) – it becomes imperative to automate a set of end-to-end tests 24x7 to detect bugs and regression. In th...
High-velocity engineering teams are applying not only continuous delivery processes, but also lessons in experimentation from established leaders like Amazon, Netflix, and Facebook. These companies have made experimentation a foundation for their release processes, allowing them to try out major feature releases and redesigns within smaller groups before making them broadly available. In his session at 21st Cloud Expo, Brian Lucas, Senior Staff Engineer at Optimizely, discussed how by using ne...
Large industrial manufacturing organizations are adopting the agile principles of cloud software companies. The industrial manufacturing development process has not scaled over time. Now that design CAD teams are geographically distributed, centralizing their work is key. With large multi-gigabyte projects, outdated tools have stifled industrial team agility, time-to-market milestones, and impacted P&L stakeholders.
"Cloud Academy is an enterprise training platform for the cloud, specifically public clouds. We offer guided learning experiences on AWS, Azure, Google Cloud and all the surrounding methodologies and technologies that you need to know and your teams need to know in order to leverage the full benefits of the cloud," explained Alex Brower, VP of Marketing at Cloud Academy, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clar...
"MobiDev is a software development company and we do complex, custom software development for everybody from entrepreneurs to large enterprises," explained Alan Winters, U.S. Head of Business Development at MobiDev, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Agile has finally jumped the technology shark, expanding outside the software world. Enterprises are now increasingly adopting Agile practices across their organizations in order to successfully navigate the disruptive waters that threaten to drown them. In our quest for establishing change as a core competency in our organizations, this business-centric notion of Agile is an essential component of Agile Digital Transformation. In the years since the publication of the Agile Manifesto, the conn...
In his session at 21st Cloud Expo, James Henry, Co-CEO/CTO of Calgary Scientific Inc., introduced you to the challenges, solutions and benefits of training AI systems to solve visual problems with an emphasis on improving AIs with continuous training in the field. He explored applications in several industries and discussed technologies that allow the deployment of advanced visualization solutions to the cloud.
Vulnerability management is vital for large companies that need to secure containers across thousands of hosts, but many struggle to understand how exposed they are when they discover a new high security vulnerability. In his session at 21st Cloud Expo, John Morello, CTO of Twistlock, addressed this pressing concern by introducing the concept of the “Vulnerability Risk Tree API,” which brings all the data together in a simple REST endpoint, allowing companies to easily grasp the severity of the ...
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
"NetApp is known as a data management leader but we do a lot more than just data management on-prem with the data centers of our customers. We're also big in the hybrid cloud," explained Wes Talbert, Principal Architect at NetApp, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Coca-Cola’s Google powered digital signage system lays the groundwork for a more valuable connection between Coke and its customers. Digital signs pair software with high-resolution displays so that a message can be changed instantly based on what the operator wants to communicate or sell. In their Day 3 Keynote at 21st Cloud Expo, Greg Chambers, Global Group Director, Digital Innovation, Coca-Cola, and Vidya Nagarajan, a Senior Product Manager at Google, discussed how from store operations and ...
"We're focused on how to get some of the attributes that you would expect from an Amazon, Azure, Google, and doing that on-prem. We believe today that you can actually get those types of things done with certain architectures available in the market today," explained Steve Conner, VP of Sales at Cloudistics, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.