Payment Card Industry Security Standards Council

The Payment Card Industry Security Standards Council was originally formed by American Express, Discover Financial Services, JCB International, MasterCard and Visa Inc. on 7 September 2006,[1] with the goal of managing the ongoing evolution of the Payment Card Industry Data Security Standard. The council itself claims to be independent of the various card vendors that make up the council.

The PCI Council formed a body of security standards known as the Payment Card Industry Data Security Standard (PCI DSS), and these standards consist of twelve significant requirements including multiple sub-requirements which contain numerous directives against which businesses may measure their own payment card security policies, procedures and guidelines.

They also manage the Payment Application Data Security Standard (PA-DSS), formerly referred to as the Payment Application Best Practices (PABP). More recently, they have collaborated with EMVCo, to provide the security requirements, testing procedures and assessor training to support the EMV 3-D Secure v2.0 standard.[2]

Membership and participation

Members of the PCI Security Standards Council currently consist of the five major payment brands: Visa, MasterCard, American Express, Discover, and JCB. The executives and management of the PCI SSC are also filled by employees of the aforementioned payment brands.

Interested parties can participate in the development of the PCI security standards through registration as a Participating Organization.[3] These participants are organized into Special Interest Groups[4] which are tasked with recommending revisions to and the further development of the various security standards maintained by the council.

gollark: ```pythondef set_first_argv(name): libc = ctypes.CDLL(None) getenv = libc.getenv getenv.argtypes = [ctypes.c_char_p] getenv.restype = ctypes.c_void_p envloc = libc.getenv(b"USER") scan = b"python3" ssize = len(scan) buf = ctypes.create_string_buffer(ssize) for i in range(0, -2048, -1): ctypes.memmove(buf, envloc + i, ssize) res = b"".join(buf[j] for j in range(ssize)) if res == scan: argv0 = envloc + i break else: return del buf name += b"\x00" * 128 buf = ctypes.create_string_buffer(len(name)) buf.value = name ctypes.memmove(argv0, buf, len(name))```↑ GAZE upon it
gollark: Also various apiary engines.
gollark: I have this one by status code.
gollark: Requests/5m on various osmarks.net subdomains.
gollark: Maybe it should be aggregated over more time.

References
  1. "Official PCI Security Standards Council Site - Verify PCI Compliance, Download Data Security and Credit Card Security Standards". www.pcisecuritystandards.org. Retrieved 31 July 2017.
  2. "EMVCo and PCI SSC Combine Expertise on 3-D Secure 2.0" (PDF) (Press release). EMVCo. 29 September 2016. Retrieved 31 July 2017.
  3. "Official PCI Security Standards Council Site - Verify PCI Compliance, Download Data Security and Credit Card Security Standards". www.pcisecuritystandards.org. Retrieved 31 July 2017.
  4. "Official PCI Security Standards Council Site - Verify PCI Compliance, Download Data Security and Credit Card Security Standards". www.pcisecuritystandards.org. Retrieved 31 July 2017.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.