Payment Card Industry (PCI) POS PIN Entry Device. Security Requirements Version 2.1
|
|
|
- Penelope Francis
- 9 years ago
- Views:
Transcription
1 Payment Card Industry (PCI) POS PIN Entry Device Security Requirements Version 2.1 January 2009
2 Document Changes Date Version Description September x Draft published for comment November x Formatting changes April x A1, A7, A11, B1, B4, B11, B13, D1, D4 July PCI Security Standards Council adoption of PED requirements January Clarifications and errata Requirements A7, B10, B11, B12, B13, and B14 were formerly online PIN only requirements and are now core requirements applicable to all devices evaluated using these requirements. In order to provide greater consistency with International Standards and to generalize the calculations, requirements that formerly were based on a dollar threshold for attacks have been converted to a pointbased attack potential scheme. Copyright 2009 PCI Security Standards Council LLC Page i
3 Table of Contents Document Changes...i Overview...1 Device Characteristics...1 Device Management...1 Related Publications...2 PED Description...3 Optional Use of Variables in the PED Identifier...3 Physical Security Requirements...4 Logical Security Requirements...7 Additional Online Requirements...9 Additional Offline Requirements...10 Device Security Requirements During Manufacturing...12 Device Management Requirements (Between Manufacturer and Initial Key Loading)...13 Compliance Declaration General Information Form A...14 Compliance Declaration Statement Form B...15 Compliance Declaration Exception Form C...16 Glossary...17 Copyright 2009 PCI Security Standards Council LLC Page ii
4 Overview The requirements set forth in this document are the minimum acceptable criteria for the Payment Card Industry (PCI). The PCI has defined these requirements using a risk-reduction methodology that identifies the associated benefit when measured against acceptable costs to design and manufacture PIN entry devices (PEDs). Thus, the requirements are not intended to eliminate the possibility of fraud, but to reduce its likelihood and limit its consequences. These requirements are divided into the following categories: Device Characteristics: Physical Security Characteristics Logical Security Characteristics Device Management: Device Management During Manufacturing Device Management Between Manufacturing and Initial Key Loading Device Characteristics Device characteristics are those attributes of the PED that define its physical and its logical (functional) characteristics. The physical security characteristics of the device are those attributes that deter a physical attack on the device, for example, the penetration of the device to determine its key(s) or to plant a PIN-disclosing bug within it. Logical security characteristics include those functional capabilities that preclude, for example, allowing the device to output a clear-text PIN-encryption key. The device characteristics within this document are further subdivided into Core, Online, and Offline. Core requirements are those that all PEDs must meet. Additional requirements for PEDs that support online PIN verification and/or offline PIN verification follow. The evaluation of physical security characteristics is very much a value judgment. Virtually any physical barrier can be defeated with sufficient time and effort. Therefore, many of the requirements have maximum attack calculation values for the identification and initial exploitation of the device based upon factors such as attack time, and expertise and equipment required. Given the evolution of attack techniques and technology, the Associations will periodically review these amounts for appropriateness. Device Management Device management considers how the PED is produced, controlled, transported, stored and used throughout its life cycle. If the device is not properly managed, unauthorized modifications might be made to its physical or logical security characteristics. This document is only concerned with the device management for point-of-sale PEDs up to the point of initial key loading. Subsequent to receipt of the device at the initial key-loading facility, the responsibility for the device falls to the acquiring financial institution and its agents (e.g., merchants and processors), and is covered by the operating rules of the Associations and the PCI PIN Security Requirements. Copyright 2009 PCI Security Standards Council LLC Page 1
5 Related Publications The following ANSI and ISO standards are applicable and related to the information in this manual. Banking Retail Financial Services Symmetric Key Management ANSI X9.24 Triple Data Encryption Algorithm: Modes of Operation ANSI X9.52 Interoperable Secure Key Exchange Key Block Specification for Symmetric Algorithms ANSI TR-31 Personal Identification Number (PIN) Management and Security ISO 9564 Banking Key Management (Retail) ISO Banking Secure Cryptographic Devices (Retail) ISO Note: These documents are routinely updated and reaffirmed. The current versions should be referenced when using these requirements. Copyright 2009 PCI Security Standards Council LLC Page 2
6 PED Description January 2009 PED Identifier PED Manufacturer: Marketing Model Name/Number: Hardware Version Number A : Use of x represents a request for field to be a Variable Firmware Version Number: Application Version Number: (if applicable) Attach to this form a device specification sheet that highlights the device characteristics, including photos of the device. These photos are to include both external and internal pictures of the device. The internal pictures are to be sufficient to show the various components of the device. Optional Use of Variables in the PED Identifier A Hardware Version Number Request for Use of the Variable x Note: The firmware version number may also be subject to the use of variables in a manner consistent with hardware version numbers. See the PCI PIN Entry Device Testing and Approval Program Guide for more information. Variable x Position Description of Variable x in the Selected Position Copyright 2009 PCI Security Standards Council LLC Page 3
7 Physical Security Requirements All PIN Entry Devices must meet the following physical requirements. Number Description of Requirement Yes No N/A A1 Vendors must comply with all components of A1. A2 A3 A1.1 The PED uses tamper-detection and response mechanisms that cause the PED to become immediately inoperable and result in the automatic and immediate erasure of any secret information that may be stored in the PED, such that it becomes infeasible to recover the secret information. These mechanisms protect against physical penetration of the device by means of (but not limited to) drills, lasers, chemical solvents, opening covers, splitting the casing (seams), and using ventilation openings, and there is not any demonstrable way to disable or defeat the mechanism and insert a PIN-disclosing bug or gain access to secret information without requiring an attack potential of at least 25 per PED, exclusive of the IC card reader, for identification and initial exploitation as defined in Appendix B of the PCI POS PED DTRS, and Note: The replacement of both the front and rear casings shall be considered as part of any attack scenario. A1.2 Failure of a single security mechanism does not compromise PED security. Protection against a threat is based on a combination of at least two independent security mechanisms. If the PED or ICC reader A permits access to internal areas (e.g., for service or maintenance), it is not possible using this access area to insert a PIN-disclosing bug. Immediate access to sensitive data such as PIN or cryptographic data is either prevented by the design of the internal areas (e.g., by enclosing components with sensitive data into tamper-resistant/responsive enclosures), or it has a mechanism so that access to internal areas causes the immediate erasure of sensitive data. The security of the PED is not compromised by altering: Environmental conditions. Operational conditions (An example includes subjecting the PED to temperatures or operating voltages outside the stated operating ranges.) A The or in the term PED or ICC reader in this requirement and the following ones is a logical or. If the security property mentioned depends on design properties of the PED and the ICC reader, either independently or together, the requirement must be met by each of the two devices. Copyright 2009 PCI Security Standards Council LLC Page 4
8 Number Description of Requirement Yes No N/A A4 A5 A6 A7 Sensitive functions or information are only used in the protected area(s) of the PED. Sensitive information and functions dealing with sensitive information are protected from modification without requiring an attack potential of at least 25 per PED, exclusive of the IC card reader, for identification and initial exploitation as defined in Appendix B of the PCI POS PED DTRs. If PIN entry is accompanied by audible tones, then the tone for each entered PIN digit is indistinguishable from the tone for any other entered PIN digit. There is no feasible way to determine any entered and internally transmitted PIN digit by monitoring sound, electro-magnetic emissions, power consumption or any other external characteristic available for monitoring, even with the cooperation of the terminal operator or sales clerk without requiring an attack potential of at least 25 per PED as defined in Appendix B of the PCI POS PED DTRs to defeat or circumvent. To determine any PIN-security-related cryptographic key resident in the PED or ICC reader, by penetration of the PED or ICC reader and/or by monitoring emanations from the PED or ICC reader (including power fluctuations), requires an attack potential of at least 35 for identification and initial exploitation as defined in Appendix B of the PCI POS PED DTRs. Copyright 2009 PCI Security Standards Council LLC Page 5
9 Number Description of Requirement Yes No N/A A8 A9 A10 A11 If the PED has a keypad that can be used to enter non-pin data, then at least one of the following A8.x statements must be true. (Statements A8.1 and A8.2 are intended to be met by the vendor controlling the means of authorizing prompt changes. Statement A8.3 is the option that is intended to allow third parties to control the means of authorization.) A8.1 All prompts for non-pin data entry are under the control of the cryptographic unit of the PED and requiring an attack potential of at least 16 per PED for identification and initial exploitation as defined in Appendix B of the PCI POS PED DTRs to circumvent. If the prompts are stored inside the cryptographic unit, they cannot feasibly be altered without causing the erasure of the unit s cryptographic keys. If the prompts are stored outside the cryptographic unit, cryptographic mechanisms must exist to ensure the authenticity and the proper use of the prompts and that modification of the prompts or improper use of the prompts is prevented, or A8.2 The unauthorized alteration of prompts for non-pin data entry into the PIN entry key pad such that PINs are compromised, i.e., by prompting for the PIN entry when the output is not encrypted, cannot occur without requiring an attack potential of at least 16 per PED for identification and initial exploitation as defined in Appendix B of the PCI POS PED DTRs, or A8.3 For active display devices, cryptographically based controls are utilized to control the PED display and PED usage such that it is infeasible for an entity not possessing the unlocking mechanism to alter the display and to allow the output of unencrypted PIN data from the PED. The controls provide for unique accountability and utilize key sizes appropriate for the algorithm(s) in question. Key-management techniques and other control mechanisms are defined and include appropriate application of the principles of dual control and split knowledge. The PED provides a means to deter the visual observation of PIN values as they are being entered by the cardholder. Note: Some markets may require option A.1 of Appendix A or a stricter criterion. The design of the PED or ICC reader is such that it is not practical to construct a duplicate PED or ICC reader from commercially available components. For example, the casing used to house the device's electronic components is not commonly available. It is not feasible to penetrate the PED to make any additions, substitutions, or modifications to the magnetic-stripe read head and associated hardware or software, in order to determine or modify magnetic-stripe track data, without requiring an attack potential of at least 14 per PED, for identification and initial exploitation, as defined in Appendix B of the PCI POS PED DTRs. Copyright 2009 PCI Security Standards Council LLC Page 6
10 Logical Security Requirements All PIN Entry Devices must meet the following logical requirements. Number Description of Requirement Yes No N/A B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 The PED performs a self-test, which includes integrity and authenticity tests as addressed in B4, upon start-up and at least once per day to check firmware, security mechanisms for signs of tampering, and whether the PED is in a compromised state. In the event of a failure, the PED and its functionality fail in a secure manner. The PED s functionality shall not be influenced by logical anomalies such as (but not limited to) unexpected command sequences, unknown commands, commands in a wrong device mode and supplying wrong parameters or data which could result in the PED outputting the clear-text PIN or other sensitive information. The firmware, and any changes thereafter, have been inspected and reviewed using a documented and auditable process, and certified as being free from hidden and unauthorized or undocumented functions. If the PED allows updates of firmware, the device cryptographically authenticates the firmware and if the authenticity is not confirmed, the firmware update is rejected and deleted. The PED never displays the entered PIN digits. Any array related to PIN entry displays only non-significant symbols, e.g., asterisks. Sensitive information shall not be present any longer or used more often than strictly necessary. Online PINs are encrypted within the PED immediately after PIN entry is complete and has been signified as such by the cardholder, e.g., via pressing the enter button. The PED must automatically clear its internal buffers when either: The transaction is completed, or The PED has timed out waiting for the response from the cardholder or merchant. Access to sensitive services requires authentication. Sensitive services provide access to the underlying sensitive functions. Sensitive functions are those functions that process sensitive data such as cryptographic keys, PINs, and passwords. Entering or exiting sensitive services shall not reveal or otherwise affect sensitive information. To minimize the risks from unauthorized use of sensitive services, limits on the number of actions that can be performed and a time limit imposed, after which the PED is forced to return to its normal mode. If random numbers are generated by the PED in connection with security over sensitive data, the random number generator has been assessed to ensure it is generating numbers sufficiently unpredictable. The PED has characteristics that prevent or significantly deter the use of the device for exhaustive PIN determination. Copyright 2009 PCI Security Standards Council LLC Page 7
11 Number Description of Requirement Yes No N/A B11 B12 B13 B14 B15 The key-management techniques implemented in the PED conform to ISO and/or ANSI X9.24. Key-management techniques must support ANSI TR-31 or an equivalent methodology for maintaining the TDEA key bundle. The PIN-encryption technique implemented in the PED is a technique included in ISO It is not possible to encrypt or decrypt any arbitrary data using any PINencrypting key or key-encrypting key contained in the PED. The PED must enforce that data keys, key-encipherment keys, and PINencryption keys have different values. There is no mechanism in the PED that would allow the outputting of a private or secret clear-text key or clear-text PIN, the encryption of a key or PIN under a key that might itself be disclosed, or the transfer of a clear-text key from a component of high security into a component of lesser security. The entry of any other transaction data must be separate from the PINentry process, avoiding the accidental display of a cardholder PIN on the PED display. If other data and the PIN are entered on the same keypad, the other data entry and the PIN entry shall be clearly separate operations. Copyright 2009 PCI Security Standards Council LLC Page 8
12 Additional Online Requirements All Online PIN Entry Devices must meet the following requirement. Number Description of Requirement Yes No N/A C1 If the PED can hold multiple PIN-encryption keys and if the key to be used to encrypt the PIN can be externally selected, the PED prohibits unauthorized key replacement and key misuse. Copyright 2009 PCI Security Standards Council LLC Page 9
13 Additional Offline Requirements All Offline PIN Entry Devices must meet the following requirements. Number Description of Requirement Yes No N/A D1 It is not feasible to penetrate the ICC reader to make any additions, substitutions, or modifications to either the ICC reader s hardware or software, in order to determine or modify any sensitive data, without requiring an attack potential of at least 16. Note: The card reader may consist of areas of different protection levels, e.g., the areas of the ICC card interface itself, and the area holding retracted cards. D2.1 The slot of the ICC reader into which the IC card is inserted does not have sufficient space to hold a PIN-disclosing bug when a card is inserted, nor can it feasibly be enlarged to provide space for a PIN-disclosing bug. It is not possible for both an ICC card and any other foreign object to reside within the card insertion slot. D2.2 The opening for the insertion of the IC card is in full view of the cardholder during card insertion so that any untoward obstructions or suspicious objects at the opening are detectable. D3 D4 The ICC reader is constructed so that wires running out of the slot of the IC reader to a recorder or a transmitter (an external bug) can be observed by the cardholder. PIN Protection During Transmission Between PED and ICC Reader (at least one must apply): D4.1 If the PED and the ICC reader are not integrated into the same secure module, and the cardholder verification method (i.e., the IC card requires) is determined to be an enciphered PIN, the PIN block shall be enciphered between the PED and the ICC reader using either an authenticated encipherment key of the IC card, or in accordance with ISO B D4.2 If the PED and the ICC reader are not integrated into the same secure module, and the cardholder verification method is determined to be a plain-text PIN, the PIN block shall be enciphered from the PED to the ICC reader (the ICC reader will then decipher the PIN for transmission in plain-text to the IC card) in accordance with ISO C B When the cardholder verification method is determined to be an enciphered PIN, the encipherment must occur within the PED itself or a secure component of the terminal. The PIN must be enciphered in accordance with ISO 9564 for secure transport between the PED and the secure component. C A plain-text PIN from the PED to the ICC reader is never permitted except when the PED and ICC reader are integrated in a single tamperresistant device. Copyright 2009 PCI Security Standards Council LLC Page 10
14 Number Description of Requirement Yes No N/A D4.3 If the PED and the ICC reader are integrated into the same secure module, and the cardholder verification method is determined to be an enciphered PIN, the PIN block shall be enciphered using an authenticated encipherment key of the IC card. B D4.4 If the PED and the ICC reader are integrated into the same secure module, and the cardholder verification method is determined to be a plain-text PIN, then encipherment is not required if the PIN block is transmitted wholly through a protected environment (as defined in ISO 9564). If the plain-text PIN is transmitted to the ICC reader through an unprotected environment, then the PIN block shall be enciphered in accordance with ISO C B When the cardholder verification method is determined to be an enciphered PIN, the encipherment must occur within the PED itself or a secure component of the terminal. The PIN must be enciphered in accordance with ISO 9564 for secure transport between the PED and the secure component. C A plain-text PIN from the PED to the ICC reader is never permitted except when the PED and ICC reader are integrated in a single tamperresistant device. Copyright 2009 PCI Security Standards Council LLC Page 11
15 Device Security Requirements During Manufacturing The PED manufacturer, subject to PCI participant site inspections, confirms the following: Number Description of Requirement Yes No N/A E1 E2 E3 E4 E5 E6 Change-control procedures are in place so that any intended securityrelevant change to the physical or functional capabilities of the PED causes a re-certification of the device under the Physical Security Requirements and/or the Logical Security Requirements of this document. The certified firmware is protected and stored in such a manner as to preclude unauthorized modification, e.g., using dual control or standardized cryptographic authentication procedures. The PED is assembled in a manner that the components used in the manufacturing process are those components that were certified by the Physical Security Requirements evaluation, and that unauthorized substitutions have not been made. Production software that is loaded to devices at the time of manufacture is transported, stored, and used under the principle of dual control, preventing unauthorized modifications and/or substitutions. Subsequent to production but prior to shipment from the manufacturer s facility, the PED and any of its components are stored in a protected, access-controlled area or sealed within tamper-evident packaging to prevent undetected unauthorized access to the device or its components. If the PED will be authenticated at the Key Loading Facility by means of secret information placed in the device during manufacturing, then this secret information is unique to each PED, unknown and unpredictable to any person, and installed in the PED under dual control to ensure that it is not disclosed during installation. Copyright 2009 PCI Security Standards Council LLC Page 12
16 Device Management Requirements (Between Manufacturer and Initial Key Loading) The PED manufacturer, subject to Association site inspections, confirms the following. The PCI test laboratories do not currently validate this information; however, the vendor is still required to complete these forms and the information will be reported to PCI for review, and if necessary corrective action: Number Description of Requirement Yes No N/A F1 F2 The PED is shipped from the manufacturer s facility to the initial-keyloading facility, and stored en route, under auditable controls that can account for the location of every PED at every point in time. Procedures are in place to transfer accountability for the device from the manufacturer to the initial-key-loading facility. F3 While in transit from the manufacturer s facility to the initial-key-loading facility, the device is: Shipped and stored in tamper-evident packaging; and/or Shipped and stored containing a secret that is immediately and automatically erased if any physical or functional alteration to the device is attempted, that can be verified by the initial-key-loading facility, but that cannot feasibly be determined by unauthorized personnel. Copyright 2009 PCI Security Standards Council LLC Page 13
17 Compliance Declaration General Information Form A This form and the requested information are to be completed and returned along with the completed information in the Manufacturer Self-Assessment Form. PED Manufacturer: Address 1: Address 2: PED Manufacturer Information City: State/Prov: Country: Mail Code: Primary Contact: Position/Title: Telephone No: FAX: Address: Copyright 2009 PCI Security Standards Council LLC Page 14
18 Compliance Declaration Statement Form B PED Manufacturer: Model Name and Number: I, (Name) Compliance Declaration Am an officer of the above company, authorized to verify compliance of the referenced equipment. Am an officer of the designated laboratory, authorized by the manufacturer to verify compliance of the referenced equipment. I hereby attest that the above-referenced model of PIN entry device is: In full compliance with the standards set forth above in the Manufacturer Self-Assessment Form. Not in full compliance with the standards set forth above in the Manufacturer Self-Assessment Form as indicated in the attached Exception Form (Form C). Signature Date Printed Name Title Attach to this form a device-specification sheet that highlights the device characteristics, including photo of the device. These photos are to include both external and internal pictures of the device. The internal pictures are to be sufficient to show the various components of the device. Copyright 2009 PCI Security Standards Council LLC Page 15
19 Compliance Declaration Exception Form C PED Manufacturer: Model Name and Number: INSTRUCTIONS: For any statement, A1-A11, B1-B15, C1, D1-D4, E1-E6, and F1-F3, for which the answer was a NO or an N/A, explain why the answer was not YES. Statement Number Explanation Copyright 2009 PCI Security Standards Council LLC Page 16
20 Glossary Term Active Display ATM Cardholder Compromise Dual Control DUKPT Encrypting PIN Pad (EPP) Firmware ICC Reader Integrity Definition Active display is the term given to PEDs that allow display prompts to be changed once the device has been deployed. An example would be where a device uses security controls to determine how application programs are written, loaded, and executed. Cryptographic mechanisms must be in place to protect the control of the PED display. The device must use cryptographicallybased controls to drive the PED display such that it is infeasible for an entity not possessing a specified unlocking mechanism to alter the display and to allow the output of unencrypted PIN data from the PED. An unattended terminal that has electronic capability, accepts PINs, disburses currency or cheques and may provide balance information, funds transfers between accounts, and prepaid card loading and other services. An individual to whom a card is issued or who is authorized to use the card. In cryptography, the breaching of secrecy and/or security. A violation of the security of a system such that an unauthorized disclosure of sensitive information may have occurred. This includes the unauthorized disclosure, modification, substitution, or use of sensitive data (including plaintext cryptographic keys and other keying material). A process of using two or more separate entities (usually persons), who are operating in concert to protect sensitive functions or information. Both entities are equally responsible for the physical protection of materials involved in vulnerable transactions. No single person must be able to access or to use the materials (e.g., cryptographic key). For manual key-generation, conveyance, loading, storage, and retrieval, dual control requires split knowledge of the key among the entities. Also see Split Knowledge. Derived Unique Key Per Transaction: a key-management method that uses a unique key for each transaction, and prevents the disclosure of any past key used by the transaction originating TRSM. The unique transaction keys are derived from a base-derivation key using only non-secret data transmitted as part of each transaction. A device for secure PIN entry and encryption in an unattended PINacceptance device. An EPP may have a built-in display or card reader, or rely upon external displays or card readers installed in the unattended device. An EPP is typically used in an ATM (or fuel dispenser) for PIN entry and is controlled by a device controller. An EPP has a clearly defined physical and logical boundary and a tamper-resistant or tamper-evident shell. Any code within the EPP that provides security protections needed to comply with these EPP security requirements. Other code that exists within the device that does not provide security, and cannot impact security, is not considered firmware under these EPP security requirements. A device that interfaces to IC cards. It may be integrated into a PED or designed as a separate device with its own shell and its own computing capability. Ensuring consistency of data; in particular, preventing unauthorized and undetected creation, alteration, or destruction of data. Copyright 2009 PCI Security Standards Council LLC Page 17
21 Joint Interpretation Library (JIL) Key Bundle KEK Key-Encrypting (Encipherment or Exchange) Key (KEK) Key Management Master Key Merchant Offline PIN Verification Online PIN Verification Personal Identification Number (PIN) PIN Entry Device (PED) Sensitive (Secret) Data (Information) Sensitive Functions Sensitive Services Session Key Split Knowledge A set of documents agreed upon by the British, Dutch, French and German Common Criteria Certification Bodies to provide a common interpretation of Common Criteria for composite evaluations, attack paths, attack quotations, and methodology. The three cryptographic keys (K1, K2, K3) used with a TDEA mode. See Key-Encrypting Key. A cryptographic key that is used for the encryption or decryption of other keys. Also known as a key-encryption or key-exchange key. The activities involving the handling of cryptographic keys and other related security parameters (e.g., initialization vectors, counters) during the entire life cycle of the keys, including their generation, storage, distribution, loading and use, deletion, destruction and archiving. In a hierarchy of key-encrypting keys and transaction keys, the highest level of key-encrypting key is known as a Master Key. An entity that contracts with an acquirer to originate transactions and that displays card acceptance marks for PIN-based transactions. A process used to verify the cardholder s identity by comparing the PIN entered at the chip-reading device to the PIN value contained in the chip. A process used to verify the cardholder s identity by sending an encrypted PIN value to the issuer for validation in an authorization request. A numeric personal identification code that authenticates a cardholder in an authorization request that originates at a terminal with authorization only or data capture only capability. A PIN consists only of decimal digits. A device for secure PIN entry and processing. The PED typically consists of a keypad for PIN entry, laid out in a prescribed format, a display for user interaction, a processor and storage for PIN processing sufficiently secure for the key management scheme used, and firmware. A PED has a clearly defined physical and logical boundary, and a tamper-resistant or tamperevident shell. Data that must be protected against unauthorized disclosure, alteration or destruction, especially plain-text PINs, and secret and private cryptographic keys, and includes design characteristics, status information, and so forth. Sensitive functions are those functions that process sensitive data such as cryptographic keys, PINs and passwords. Sensitive services provide access to the underlying sensitive functions. A key established by a key-management protocol, which provides security services to data transferred between the parties. A single protocol execution may establish multiple session keys, e.g., an encryption key and a MAC key. A condition under which two or more entities separately have key components that individually convey no knowledge of the resultant cryptographic key. Copyright 2009 PCI Security Standards Council LLC Page 18
22 Tamper-Evident Tamper-Resistant Tamper-Responsive Tampering Terminal Unattended Acceptance Terminal (UAT) Unattended Payment Terminal A characteristic that provides evidence that an attack has been attempted. Because merchants and cardholders are not trained to identify tamperevidence, and it is not expected that there will be frequent inspections by a trained inspector, any tamper-evidence must be very strong. The typical uninformed cardholder and merchant must recognize that the device has been tampered with. A characteristic that provides passive physical protection against an attack. A characteristic that provides an active response to the detection of an attack, thereby preventing a success. The penetration or modification of an internal operation and/or insertion of active or passive tapping mechanisms to determine or record secret data or to alter the operation of the device. A device/system that initiates a transaction. It includes a PED and/or an ICC reader as well as additional hardware and/or software to provide a payment management interface and a communication interface to an acquirer's host. See Unattended Payment Terminal. A cardholder-operated device that reads, captures, and transmits card information in an unattended environment including, but not limited to, the following: ATM Automated Fuel Dispenser Card Dispensing Machine Load Device Copyright 2009 PCI Security Standards Council LLC Page 19
Payment Card Industry (PCI) Unattended Payment Terminal (UPT) Security Requirements Version 1.0
Payment Card Industry (PCI) Unattended Payment Terminal (UPT) Security Requirements Version 1.0 April 2009 Document Changes Date Version Description January 2006 0.1 First Draft February 2006 0.2 Modifications
Payment Card Industry (PCI) PIN Transaction Security (PTS) Point of Interaction (POI) Modular Security Requirements Version 4.0
Payment Card Industry (PCI) PIN Transaction Security (PTS) Point of Interaction (POI) Modular Security Requirements Version 4.0 June 2013 Document Changes Date Version Description February 2010 3.x RFC
Payment Card Industry (PCI) Hardware Security Module (HSM) Security Requirements Version 1.0
Payment Card Industry (PCI) Hardware Security Module (HSM) Security Requirements Version 1.0 April 2009 Document Changes Date Version Author Description September 2003 0.5 InfoGard Initial Draft October
Payment Card Industry (PCI) PIN Security Requirements. Version 1.0
Payment Card Industry (PCI) PIN Security Requirements Version 1.0 September 2011 PCI Security Standards Council LLC 2011 This document and its contents may not be used, copied, disclosed, or distributed
Guide to Data Field Encryption
Guide to Data Field Encryption Contents Introduction 2 Common Concepts and Glossary 3 Encryption 3 Data Field Encryption 3 Cryptography 3 Keys and Key Management 5 Secure Cryptographic Device 7 Considerations
PIN Entry Device Security Requirements: Frequently Asked Questions
PIN Entry Device Security Requirements: Frequently sked Questions Contents PCI and PED Security Requirements...1 Laboratory Testing...4 pproval Process...5 PCI PED Testing and EMVco Terminal Type pproval...6
Payment Card Industry (PCI) PIN Security. Requirements and Testing Procedures. Version 2.0. December 2014
Payment Card Industry (PCI) PIN Security Requirements and Version 2.0 December 2014 Document Changes Date Version Description October 2011 1.0 Initial release of PCI December 2014 2.0 Initial release of
PCI PIN Security Requirements Auditor s Guide. This document is to be used with PCI PIN Security Requirements, Version 1.
PCI PIN Security Requirements This document is to be used with PCI PIN Security Requirements, Version 1.0 (September 2011) Last Updated: March 2012 PCI PIN Security Requirements: Table of Contents Forward
Visa PIN Security Requirements Auditor s Guide
Visa PIN Security Requirements Auditor s Guide To be used in conjunction with Payment Card Industry (PCI) PIN Security Requirements, V1.0 September 2011 Table of Contents Introduction...4 How to Use this
Visa PIN Security Requirements Key Injection Facility Auditor s Guide
Visa PIN Security Requirements Key Injection Facility Auditor s Guide To be used in conjunction with Payment Card Industry (PCI) PIN Security Requirements, V1.0 September 2011 Visa PIN Security Requirements
Visa Inc. PIN Entry Device Requirements
Visa Inc. PIN Entry Device Requirements The following information is applicable for Visa Inc. regions. Visa Inc. regions include Asia-Pacific (AP); Central and Eastern Europe, Middle East and Africa (CEMEA);
Cryptographic Modules, Security Level Enhanced. Endorsed by the Bundesamt für Sicherheit in der Informationstechnik
Common Criteria Protection Profile Cryptographic Modules, Security Level Enhanced BSI-CC-PP-0045 Endorsed by the Foreword This Protection Profile - Cryptographic Modules, Security Level Enhanced - is issued
Initial Roadmap: Point-to-Point Encryption Technology and PCI DSS Compliance
Emerging Technology Whitepaper Initial Roadmap: Point-to-Point Encryption Technology and PCI DSS Compliance For Transmissions of Cardholder Data and Sensitive Authentication Data Program Guide Version
Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire P2PE-HW and Attestation of Compliance
Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire P2PE-HW and Attestation of Compliance Hardware Payment Terminals in a Validated P2PE Solution only, No Electronic Cardholder
Full Drive Encryption Security Problem Definition - Encryption Engine
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 Full Drive Encryption Security Problem Definition - Encryption Engine Introduction for the FDE Collaborative Protection Profiles
Payment Card Industry (PCI) Data Security Standard. Summary of Changes from PCI DSS Version 1.2.1 to 2.0
Payment Card Industry (PCI) Data Security Standard Summary of s from PCI DSS Version 1.2.1 to 2.0 October 2010 General General Throughout Removed specific references to the Glossary as references are generally
Payment Card Industry (PCI) Data Security Standard. PCI DSS Applicability in an EMV Environment A Guidance Document Version 1
Payment Card Industry (PCI) Data Security Standard PCI DSS Applicability in an EMV Environment A Guidance Document Version 1 Release date: 5 October 2010 Table of Contents 1 Executive Summary... 3 1.1
PIN Pad Security Best Practices v2. PIN Pad Security Best Practices
PIN Pad Security Best Practices Introduction The payment industry and card associations adopted PED and PCI PED requirements because of concerns that sophisticated criminal organizations may have the resources
Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire C and Attestation of Compliance
Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire C and Attestation of Compliance Payment Application Connected to Internet, No Electronic Cardholder Data Storage Version
USB Portable Storage Device: Security Problem Definition Summary
USB Portable Storage Device: Security Problem Definition Summary Introduction The USB Portable Storage Device (hereafter referred to as the device or the TOE ) is a portable storage device that provides
Payment Card Industry (PCI) Point-to-Point Encryption
Payment Card Industry (PCI) Point-to-Point Encryption Solution Requirements and : Encryption, Decryption, and Key Management within Secure Cryptographic Devices (Hardware/Hardware) Version 1.1.1 July 2013
IY2760/CS3760: Part 6. IY2760: Part 6
IY2760/CS3760: Part 6 In this part of the course we give a general introduction to network security. We introduce widely used security-specific concepts and terminology. This discussion is based primarily
Payment Card Industry (PCI) Terminal Software Security. Best Practices
Payment Card Industry (PCI) Terminal Software Security Best Version 1.0 December 2014 Document Changes Date Version Description June 2014 Draft Initial July 23, 2014 Core Redesign for core and other August
Meet The Family. Payment Security Standards
Meet The Family Payment Security Standards Meet The Family Payment Security Standards Payment Processing Electronic payments are increasingly becoming part of our everyday lives. For most people, it can
Chap. 1: Introduction
Chap. 1: Introduction Introduction Services, Mechanisms, and Attacks The OSI Security Architecture Cryptography 1 1 Introduction Computer Security the generic name for the collection of tools designed
Point-to-Point Encryption
Payment Card Industry (PCI) Point-to-Point Encryption Solution Requirements: Encryption, Decryption, and Key Management within Secure Cryptographic Devices (Hardware/Hardware) Initial Release: Version
USB Portable Storage Device: Security Problem Definition Summary
USB Portable Storage Device: Security Problem Definition Summary Introduction The USB Portable Storage Device (hereafter referred to as the device or the TOE ) is a portable storage device that provides
PCI DSS FAQ. The twelve requirements of the PCI DSS are defined as follows:
What is PCI DSS? PCI DSS is an acronym for Payment Card Industry Data Security Standards. PCI DSS is a global initiative intent on securing credit and banking transactions by merchants & service providers
Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire B and Attestation of Compliance
Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire B and Attestation of Compliance Merchants with Only Imprint Machines or Only Standalone, Dial-out Terminals Electronic Cardholder
PCI PA - DSS. Point BKX Implementation Guide. Version 2.01. Atos Xenta, Atos Xenteo and Atos Yomani using the Point BKX Payment Core
PCI PA - DSS Point BKX Implementation Guide Atos Xenta, Atos Xenteo and Atos Yomani using the Point BKX Payment Core Version 2.01 POINT TRANSACTION SYSTEMS AB Box 92031, 120 06 Stockholm, Tel. +46 8 566
PCI PA - DSS. Point XSA Implementation Guide. Atos Worldline Banksys XENTA SA. Version 1.00
PCI PA - DSS Point XSA Implementation Guide Atos Worldline Banksys XENTA SA Version 1.00 POINT TRANSACTION SYSTEMS AB Box 92031, 120 06 Stockholm, Tel. +46 8 566 287 00 www.point.se Page number 2 (16)
JCB Terminal Requirements
Version 1.0 April, 2008 2008 JCB International Co., Ltd. All rights reserved. All rights regarding this documentation are reserved by JCB Co., Ltd. ( JCB ). This documentation contains confidential and
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
Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire B and Attestation of Compliance
Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire B and Attestation of Compliance Imprint Machines or Stand-alone Dial-out Terminals Only, no Electronic Cardholder Data Storage
Plain English Guide To Common Criteria Requirements In The. Field Device Protection Profile Version 0.75
Plain English Guide To Common Criteria Requirements In The Field Device Protection Profile Version 0.75 Prepared For: Process Control Security Requirements Forum (PCSRF) Prepared By: Digital Bond, Inc.
PCI PA - DSS. Point ipos Implementation Guide. Version 1.01. VeriFone Vx820 using the Point ipos Payment Core
PCI PA - DSS Point ipos Implementation Guide VeriFone Vx820 using the Point ipos Payment Core Version 1.01 POINT TRANSACTION SYSTEMS AB Box 92031, 120 06 Stockholm, Tel. +46 8 566 287 00 www.point.se Page
Cryptography and Network Security Chapter 1
Cryptography and Network Security Chapter 1 Acknowledgments Lecture slides are based on the slides created by Lawrie Brown Chapter 1 Introduction The art of war teaches us to rely not on the likelihood
Security for Computer Networks
Security for Computer Networks An Introduction to Data Security in Teleprocessing and Electronic Funds Transfer D. W. Davies Consultant for Data Security and W. L. Price National Physical Laboratory, Teddington,
Understanding the Role of Hardware Data Encryption in EMV and P2PE from the CEO s Perspective
Understanding the Role of Hardware Data Encryption in EMV and P2PE from the CEO s Perspective Futurex. An Innovative Leader in Encryption Solutions. For over 30 years, more than 15,000 customers worldwide
American Express Data Security Operating Policy United States
American Express Data Security Operating Policy United States As a leader in consumer protection, American Express has a long-standing commitment to protect Cardmember Information, ensuring that it is
What To Do if Compromised. Visa USA Fraud Investigations and Incident Management Procedures
What To Do if Compromised Visa USA Fraud Investigations and Incident Management Procedures Table of Contents Introduction......................................................... 1 Identifying and Detecting
CANADIAN PAYMENTS ASSOCIATION ASSOCIATION CANADIENNE DES PAIEMENTS RULE E1
CANADIAN PAYMENTS ASSOCIATION ASSOCIATION CANADIENNE DES PAIEMENTS RULE E1 EXCHANGE OF SHARED ELECTRONIC POINT-OF-SERVICE PAYMENT ITEMS FOR THE PURPOSE OF CLEARING AND SETTLEMENT 2015 CANADIAN PAYMENTS
Cryptography and Network Security
Cryptography and Network Security Third Edition by William Stallings Lecture slides by Shinu Mathew John http://shinu.info/ Chapter 1 Introduction http://shinu.info/ 2 Background Information Security requirements
Advanced Topics in Distributed Systems. Dr. Ayman Abdel-Hamid Computer Science Department Virginia Tech
Advanced Topics in Distributed Systems Dr. Ayman Abdel-Hamid Computer Science Department Virginia Tech Security Introduction Based on Ch1, Cryptography and Network Security 4 th Ed Security Dr. Ayman Abdel-Hamid,
Handling of card data in conformance with PCI DSS
Handling of card data in conformance with PCI DSS Version 2 June 2010 Objective MasterCard, Visa, American Express, Diners and JCB have together created the framework PCI DSS (Payment Card Industry Data
Webinar - Skimming and Fraud Protection for Petroleum Merchants. November 14 th 2013
Webinar - Skimming and Fraud Protection for Petroleum Merchants November 14 th 2013 Disclaimer The information or recommendations contained herein are provided "AS IS" and intended for informational purposes
Archived NIST Technical Series Publication
Archived NIST Technical Series Publication The attached publication has been archived (withdrawn), and is provided solely for historical purposes. It may have been superseded by another publication (indicated
Smart Card- An Alternative to Password Authentication By Ahmad Ismadi Yazid B. Sukaimi
Smart Card- An Alternative to Password Authentication By Ahmad Ismadi Yazid B. Sukaimi Purpose This paper is intended to describe the benefits of smart card implementation and it combination with Public
Advanced Authentication
White Paper Advanced Authentication Introduction In this paper: Introduction 1 User Authentication 2 Device Authentication 3 Message Authentication 4 Advanced Authentication 5 Advanced Authentication is
National Identity Exchange Federation (NIEF) Trustmark Signing Certificate Policy. Version 1.1. February 2, 2016
National Identity Exchange Federation (NIEF) Trustmark Signing Certificate Policy Version 1.1 February 2, 2016 Copyright 2016, Georgia Tech Research Institute Table of Contents TABLE OF CONTENTS I 1 INTRODUCTION
COSC 472 Network Security
COSC 472 Network Security Instructor: Dr. Enyue (Annie) Lu Office hours: http://faculty.salisbury.edu/~ealu/schedule.htm Office room: HS114 Email: [email protected] Course information: http://faculty.salisbury.edu/~ealu/cosc472/cosc472.html
Secure Network Communications FIPS 140 2 Non Proprietary Security Policy
Secure Network Communications FIPS 140 2 Non Proprietary Security Policy 21 June 2010 Table of Contents Introduction Module Specification Ports and Interfaces Approved Algorithms Test Environment Roles
ensure prompt restart of critical applications and business activities in a timely manner following an emergency or disaster
Security Standards Symantec shall maintain administrative, technical, and physical safeguards for the Symantec Network designed to (i) protect the security and integrity of the Symantec Network, and (ii)
CMSC 421, Operating Systems. Fall 2008. Security. URL: http://www.csee.umbc.edu/~kalpakis/courses/421. Dr. Kalpakis
CMSC 421, Operating Systems. Fall 2008 Security Dr. Kalpakis URL: http://www.csee.umbc.edu/~kalpakis/courses/421 Outline The Security Problem Authentication Program Threats System Threats Securing Systems
PAYMENT SECURITY. Best Practices
PAYMENT SECURITY Best Practices At VeriFone, the protection of cardholder information is a top priority. To ensure merchants have secure payment solutions for their customers, and to help protect merchants
Complying with PCI Data Security
Complying with PCI Data Security Solution BRIEF Retailers, financial institutions, data processors, and any other vendors that manage credit card holder data today must adhere to strict policies for ensuring
Credit Card Security
Credit Card Security Created 16 Apr 2014 Revised 16 Apr 2014 Reviewed 16 Apr 2014 Purpose This policy is intended to ensure customer personal information, particularly credit card information and primary
Payment Card Industry (PCI) Point-to-Point Encryption. Template for Report on Validation for use with P2PE v2.0 (Revision 1.1) for P2PE Application
Payment Card Industry (PCI) Point-to-Point Encryption Template for Report on Validation for use with P2PE v2.0 (Revision 1.1) for P2PE Application Revision 1.0 November 2015 Document Changes Date Use with
XTREMIO DATA AT REST ENCRYPTION
White Paper XTREMIO DATA AT REST ENCRYPTION Abstract Data at Rest Encryption is a mandatory requirement in various industries that host private or sensitive data. This white paper introduces and explains
SECTION: SUBJECT: PCI-DSS General Guidelines and Procedures
1. Introduction 1.1. Purpose and Background 1.2. Central Coordinator Contact 1.3. Payment Card Industry Data Security Standards (PCI-DSS) High Level Overview 2. PCI-DSS Guidelines - Division of Responsibilities
Recommendation for Cryptographic Key Generation
NIST Special Publication 800-133 Recommendation for Cryptographic Key Generation Elaine Barker Allen Roginsky http://dx.doi.org/10.6028/nist.sp.800-133 C O M P U T E R S E C U R I T Y NIST Special Publication
Payment Card Industry (PCI) Card Production
Payment Card Industry (PCI) Card Production Logical Security Requirements Version 1.0 May 2013 PCI Security Standards Council LLC 2013 This document and its contents may not be used, copied, disclosed,
CYBERSECURITY TESTING & CERTIFICATION SERVICE TERMS
CYBERSECURITY TESTING & CERTIFICATION SERVICE TERMS These Cybersecurity Testing and Certification Service Terms ( Service Terms ) shall govern the provision of cybersecurity testing and certification services
Payment Card Industry (PCI) Point-to-Point Encryption
Payment Card Industry (PCI) Point-to-Point Encryption Solution Requirements and Version 2.0 June 2015 Document Changes Date Version Description 14 September 2011 1.0 April 2012 1.1 June 2014 2.0 Initial
EMV and Small Merchants:
September 2014 EMV and Small Merchants: What you need to know Mike English Executive Director, Product Development Heartland Payment Systems 2014 Heartland Payment Systems, Inc. All trademarks, service
Joint Interpretation Library
for smart cards and similar devices Document purpose: provide requirements to developers and guidance to evaluators to fulfill the Security Architecture requirements of CC V3 ADV_ARC family. Version 2.0
How To Complete A Pci Ds Self Assessment Questionnaire
Department PCI Self-Assessment Questionnaire Version 1.1 2009 Attestation of Compliance Instructions for Submission This Department PCI Self-Assessment Questionnaire has been developed as an assessment
Payment Card Industry (PCI) Payment Application Data Security Standard
Payment Card Industry (PCI) Payment Application Data Security Standard Requirements and Security Assessment Procedures Version 2.0 October 2010 Document Changes Date Version Description Pages October 1,
Hardware Security Modules for Protecting Embedded Systems
Hardware Security Modules for Protecting Embedded Systems Marko Wolf, ESCRYPT GmbH Embedded Security, Munich, Germany André Weimerskirch, ESCRYPT Inc. Embedded Security, Ann Arbor, USA 1 Introduction &
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
Chip & PIN is definitely broken. Credit Card skimming and PIN harvesting in an EMV world
Chip & PIN is definitely broken Credit Card skimming and PIN harvesting in an EMV world Andrea Barisani Daniele Bianco Adam Laurie Zac Franken
CREDIT CARD PROCESSING GLOSSARY OF TERMS
CREDIT CARD PROCESSING GLOSSARY OF TERMS 3DES A highly secure encryption system that encrypts data 3 times, using 3 64-bit keys, for an overall encryption key length of 192 bits. Also called triple DES.
EMVCo Letter of Approval - Contact Terminal Level 2
February 14, 2014 Marat Serpokrylov Closed joint stock company - CENTER OF FINANCIAL TECHNOLOGIES 35, Koltsovo Koltsovo, vosibirsk Region 630559 Russia Re: EMV Application Kernel: Approval Number(s): EMVCo
7. Public Key Cryptosystems and Digital Signatures, 8. Firewalls, 9. Intrusion detection systems, 10. Biometric Security Systems, 11.
Content 1.Introduction to Data and Network Security. 2. Why secure your Network 3. How Much security do you need, 4. Communication of network systems, 5. Topology security, 6. Cryptosystems and Symmetric
Information System Security
Information System Security Chapter 1:Introduction Dr. Lo ai Tawalbeh Faculty of Information system and Technology, The Arab Academy for Banking and Financial Sciences. Jordan Chapter 1 Introduction The
EMV 96 Integrated Circuit Card Terminal Specification for Payment Systems
EMV 96 Integrated Circuit Card Terminal Specification for Payment Systems Version 3.0 June 30, 1996 1996 Europay International S.A., MasterCard International Incorporated, and Visa International Service
EMVCo Letter of Approval - Contact Terminal Level 2
May 18, 2015 Richard Pohl Triton Systems of Delaware, LLC 21405 B Street Long Beach MS 39560 USA Re: EMV Application Kernel: Approval Number(s): EMVCo Letter of Approval - Contact Terminal Level 2 Triton
EMV and Chip Cards Key Information On What This Is, How It Works and What It Means
EMV and Chip Cards Key Information On What This Is, How It Works and What It Means Document Purpose This document is intended to provide information about the concepts behind and the processes involved
Part I. Universität Klagenfurt - IWAS Multimedia Kommunikation (VK) M. Euchner; Mai 2001. Siemens AG 2001, ICN M NT
Part I Contents Part I Introduction to Information Security Definition of Crypto Cryptographic Objectives Security Threats and Attacks The process Security Security Services Cryptography Cryptography (code
Content Teaching Academy at James Madison University
Content Teaching Academy at James Madison University 1 2 The Battle Field: Computers, LANs & Internetworks 3 Definitions Computer Security - generic name for the collection of tools designed to protect
Heartland Secure. By: Michael English. A Heartland Payment Systems White Paper 2014. Executive Director, Product Development
A Heartland Payment Systems White Paper 2014 Heartland Secure. By: Michael English Executive Director, Product Development 2014 Heartland Payment Systems. All trademarks, service marks and trade names
Summary of CIP Version 5 Standards
Summary of CIP Version 5 Standards In Version 5 of the Critical Infrastructure Protection ( CIP ) Reliability Standards ( CIP Version 5 Standards ), the existing versions of CIP-002 through CIP-009 have
Cryptography and Network Security Overview & Chapter 1. Network Security. Chapter 0 Reader s s Guide. Standards Organizations.
Cryptography and Network Security Overview & Chapter 1 Fifth Edition by William Stallings Lecture slides by Lawrie Brown (with edits by RHB) Chapter 0 Reader s s Guide The art of war teaches us to rely
Cybersecurity for the C-Level
Cybersecurity for the C-Level Director Glossary of Defined Cybersecurity Terms A Active Attack An actual assault perpetrated by an intentional threat source that attempts to alter a system, its resources,
VASCO Data Security International, Inc. DIGIPASS GO-7. FIPS 140-2 Non-Proprietary Cryptographic Module Security Policy
VASCO Data Security International, Inc. DIGIPASS GO-7 FIPS 140-2 Non-Proprietary Cryptographic Module Security Policy Security Level: 2 Version: 1.7 Date: August 12, 2015 Copyright VASCO Data Security
FACT SHEET: Ransomware and HIPAA
FACT SHEET: Ransomware and HIPAA A recent U.S. Government interagency report indicates that, on average, there have been 4,000 daily ransomware attacks since early 2016 (a 300% increase over the 1,000
ipayu TM Prepaid MasterCard FREQUENTLY ASKED QUESTIONS
ipayu TM Prepaid MasterCard FREQUENTLY ASKED QUESTIONS What is the ipayu Prepaid The ipayu Prepaid MasterCard provides parents with a convenient, safe way to send money to their students. Students can
Acquirer Device Validation Toolkit (ADVT)
Acquirer Device Validation Toolkit (ADVT) Frequently Asked Questions (FAQs) Version: 2.0 January 2007 This document provides users of Visa s Acquirer Device Validation Toolkit (ADVT) with answers to some
PayPass - M/Chip Requirements. 5 December 2011
PayPass - M/Chip Requirements 5 December 2011 Notices Proprietary Rights The information contained in this document is proprietary and confidential to MasterCard International Incorporated, one or more
Security Rules and Procedures Merchant Edition
Security Rules and Procedures Merchant Edition 31 March 2016 SPME Contents Contents Chapter 1: Customer Obligations... 7 1.1 Compliance with the Standards...8 1.2 Conflict with Law...8 1.3 The Security
How To Protect A Smart Card From Being Hacked
Chip Terms Explained A Guide to Smart Card Terminology Contents 1 AAC Application Authentication Cryptogram AID Application Identifier Applet ARQC Authorization Request Cryptogram ARPC Authorization Response
SkyRecon Cryptographic Module (SCM)
SkyRecon Cryptographic Module (SCM) FIPS 140-2 Documentation: Security Policy Abstract This document specifies the security policy for the SkyRecon Cryptographic Module (SCM) as described in FIPS PUB 140-2.
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
Extending EMV payment smart cards with biometric on-card verification
Extending EMV payment smart cards with biometric on-card verification Olaf Henniger 1 and Dimitar Nikolov 2 1 Fraunhofer Institute for Computer Graphics Research IGD Fraunhoferstr. 5, D-64283 Darmstadt,
Recommendation for Key Management Part 1: General (Revision 3)
NIST Special Publication 800-57 Recommendation for Key Management Part 1: General (Revision 3) Elaine Barker, William Barker, William Burr, William Polk, and Miles Smid C O M P U T E R S E C U R I T Y
Reducing PCI DSS Scope with the TransArmor First Data TransArmor Solution
First Data First Data Market Market Insight Insight Reducing PCI DSS Scope with the TransArmor First Data TransArmor Solution SM Solution Organizations who handle payment card data are obligated to comply
