Download PCI Data Security Standard (PCI DSS) and more Exams Nursing in PDF only on Docsity!
PCIP Exam 2023
PCI Data Security Standard (PCI DSS) The PCI DSS applies to all entities that store, process , and/or transmit cardholder data. It covers technical and operational system components included in or connected to cardholder data. If you accept or process payment cards, PCI DSS applies to you. Sensitive Authentication Data Merchants, service providers, and other entities involved with payment card processing must never store sensitive authentication data after authorization. This includes the 3- or 4- digit security code printed on the front or back of a card (CVD), the data stored on a card's magnetic stripe or chip (also called "Full Track Data") - and personal identification numbers (PIN) entered by the cardholder. Card Verification Data Codes (CVD) 3 or 4 digit code that further authenticates a not-present cardholder Visa-CVV MC- CVC Discover- CVD JCB-CAV AmEx- CID Requirement 1 Install and maintain a firewall configuration to protect cardholder data Network devices in scope for Requirement 1 Firewalls and Routers- Routers connect traffic between networks, Firewalls control the traffic between networks and within internal network
QIR Qualified Integrators & Resellers Qualified Integrators & Resellers - authorized by the SSC to implement, configure and/or support PA-DSS payment applications. Visa requires all level 4 merchants use QIRs for POS application and terminal installation and servicing Compensating Controls An alternative control , put in place to satisfy the requirement for a security measure that is deemed too difficult or impractical to implement at the present time. Permitted reasons for using Compensating Controls Organizations needing an alternative to security requirements that could not be met due to legitimate technological OR documented business constraints , but has sufficiently mitigated the risk associated with the requirement through implementation of other compensating controls Examples of Compensating Controls (i) Segregation of Duties (SOD) and (ii) Encryption Compensating Controls must:
- Meet the intent and rigor of the original stated requirement;
- Provide a similar level of defense as the original stated requirement;
- Be "above and beyond" other PCI DSS requirements (not simply in compliance with other PCI DSS requirements); and
- Be commensurate with the additional risk imposed by not adhering to the original stated requirement. Compensating Controls Worksheet
- Constraint; 2) Objective; 3) Identified Risk; 4) Define Compensating Control; 5)Validate Controls; 6) Maintenance (COIDVM) Card Data that cannot be stored by Merchants, Service providers after authorization Sensitive Authentication Data. i) 3- or 4- digit security code printed on the front or back of a card, ii) data stored on a card's magnetic stripe or chip (also called "Full Track Data"), and iii) personal identification numbers (PIN) entered by the cardholder Card Data that MAY be stored i) cardholder name, ii) service code (identifies industry iii) Personal Account Number (PAN) iv) expiration date may be stored. Network Segmentation The process of isolating the cardholder data environment from the remainder of an entity's network Not a requirement but strongly recommended. Report on Compliance (ROC) Prepared at the time of the assessment of PCI compliance and comprehensively provides details about the assessment approach and compliance standing against each PCI DSS requirement
numbers are replaced with tokens in all other databases and applications. Not storing cardholder data anywhere greatly simplifies the scope of PCI Requirement. Who makes up the PCI Security Standards Council?
- Five payment brands (Am Ex, JCB, Visa, MC, Discover), and 2) Payment Organizations (merchants, banks, processors, hardware and software developers, point of sale vendors). Card Processing Authorization - who does the merchant request and receive authorization from to complete the purchase? What is provided to the merchant? The Issuer provides an Authorization Code to the merchant Card Processing Clearing - who shares what? Acquirer and Issuer exchange payment information- usually 24 hr period in U.S. Card Processing Settlement - who does acquirer pay? What does Issuer do?
- Acquirer pays merchant and 2) Issuer bills cardholder (i.e. cardholder is charged)
- Reconciliation takes place, issuer records, posts the transaction which appears on the cardholder's monthly statement What are the 3 steps in Payment Card Processing?
- Authorization 2) Clearing 3) Settlement Functions associated with Acquirers Authorize , Clear and Settle to merchant Who ultimately approves the purchase? Issuer
Which step does the Payment Brand Network provide complete reconciliation to the merchant bank? Clearing How long is PCIP qualification valid? 3 years Which takes precedence...local laws or PCI Standards? Local Laws Payment Brand Network The cc brands (e.g. Am Ex, Discover). Discover and Amex are BOTH the card network and issuing bank- having their own financial institutions issue the cc's to consumers Visa and MasterCard are card networks only and do NOT issue cc's- they have third party issuing banks do it for them. What do Acquirer's do for their merchants? Authorize -- Clear -- Settle for their merchant Who ultimately approves the purchase? Issuer In which step does the Payment Brand Network provide complete reconciliation to the merchant bank? Clearing (PA-DSS) Payment Application Data Security Standard Third party payment applications that authorize and settle Examples- POS, Shopping Cart Role of Payment Brand Network
- Develop and Enforce Compliance Programs , 2) Accept validation documentation from approved QSA, PA-QSA, and ASV companies, and
- endorse the QSA, PA-QSA and ASV company qualification criteria Point to Point Encryption (P2PE) Requirements 1- Secure encryption of payment card data at Point of Interaction (POI) 2- Validated apps at the POI 3- Secure environment of encryption and decryption devices 4- Manage decryption environment and ALL decrypted account data 5- Use source encryption technologies and cryptographic key elements-like key generation, distribution, loading and injection, administration and usage May reduce PCI-DSS scope for Merchant -Geared toward provider of point to point solution (e.g. Processor, Acquirer, payment gateway (e.g. PayPal) (PA-DSS) Payment Application DSS Most payment application (PA-DSS) requirements are equivalent of PCI-DSS -Geared toward the Application providers P2PE P2PE- Incorporates requirements from PTS, PCI-DSS, PA-DSS, and PCI-PIN Protects cc data from point of capture to processing (PCI-PTS) PIN - Transaction Security Devices PCI-PTS applies to pin entry devices/ point of interaction devices (POI), Encrypting Pin Pads (EPP), Point of Sale devices (POS), Hardware (or host) security modules (HSMs), Unattended Payment Terminals (UPT)s, and non-PIN entry module -Geared toward Device Manufacturers PCI-PTS - what does the program ensure against?
Do NOT use vendor-supplied default passwords and other security parameters (ALL default passwords)
- inventory system components
- Ensure non-console access to network devices, servers and other components is encrypted -Sources of industry accepted system hardening (configuration) standards (Req. 2)
- Center for Internet Security (CIS)
- International Organization for Standardization (ISO)
- SysAdmin Audit Network Security (SANS) Institute
- National Institute of Standards Technology (NIST) Req. 2.1 When should all vendor defaults be removed or disabled? BEFORE installing a system on the network (includes wireless devices connected to the CHD environment or used to transmit CHD data. (SSH) Secure Shell (Req. 2.2.2-2.2.3) Considered secure Segmentation consists of what? 1)Logical Controls, or 2) physical controls or 3) a combo of both e.g. Firewalls/routers between CHD and corporate network Card holder data ( CHD) environment is comprised of what? People , Processes and Technologies that store, transmit or process CHD or SAD Are untrusted networks (e.g. internet) in scope for PCI-DSS No, they are not in scope, but to protect in-scope systems and data from untrusted networks , PCI-DSS requirements must be implemented What is a flat network? A network without adequate segmentation -results in the entire network being in scope for PCI DSS assessment How frequently does an entity have to confirm PCI DSS scope? Annually -must identify locations and flows of CHD -identify all systems connected to, or if compromised could impact the CDE How frequently do segmentation controls have to be tested? At least annually (Req. 11.3.4) Maximum PAN digits that may be displayed First 6 or last 4 digits -POS receipt stricter requirements trumps How to render PAN unreadable?
- One way hash functions based on strong cryptography
- Truncation
- Index Tokens and Securely Stored Pads 4 ) Strong Cryptography Requirement 3 Protect stored cardholder data -PAN and SAD -after authorization it cannot be stored (even if encrypted-SAD) -issuers exception for business need
Requirement 3. Protect PAN on display (printed receipts, screens, printouts) -different from Req. 3.4- protect PAN stored on databases or soft files Req. 3.2 Do NOT Store SAD after authorization Don't store SAD ( sensitive authentication data) after authorization -render unrecoverable
- Exception for Issuers - may store SAD if business need and secure Req. 3.2.2 Track Data Track data located in magnetic stripe back of card -Track equivalent data found on the Chip - but has a unique code Req. 3.4 If stored, PAN must be Unreadable PAN must be unreadable if stored Tech. Solutions to make unreadable: -One way hash functions of the entire PAN -truncation -index tokens w/ secure pads -strong cryptography Req. 3.2. Don't store PIN after authorization Req. 3.6. Manual clear text cryptographic key management if used, must be managed by:
- Split Knowledge and 2) Dual Control
- One person alone cannot access the authentication materials of another Req. 4 Protect card holder data transmitted across open public network (internet) using encryption -use strong cryptography -verify certificates -use industry best practices (e.g. IEEE 802.11i) Req. 5 Protect all systems against malware and regularly update antivirus software -deploy antivirus software on systems COMMONLY susceptible to malicious software (Malware)- not required on systems not commonly affected by malware Zero Day Term for attacks on previously UNKNOWN vulnerabilities Req. 6. Develop internal and external software securely -include web based administrative access -include security when defining requirements for software development -for apps , get rid of development, test accounts, test user ids and passwords from the production code before it goes live- could give away info about app functionality Req. 6 Maintain and develop secure systems and applications
- identify security vulnerabilities (at a minimum identify all high risk vulnerabilities)
- Change passwords at least every 90 days
- New password should not duplicate prior 4 passwords
- First time use and Reset passwords should be different for each user Req. 8.3 Use Multi-Factor Authentication to Secure CDE Requires a min. 2 of 3 authentication methods (Req. 8.2) before access granted- cannot use one factor twice
- applies only to those with admin and non-console access ( access to system over network and not direct ) to CDE
- does NOT apply to app or system accounts performing automated functions Req. 9 Restrict Physical Access to CHD Control physical access to all systems that store , process and transmit CHD -applies to all personnel on-site
- visitor - anyone onsite less than 1 day Req. 9.1 Restrict access to what? how? Use controls in facility to prevent access to (badges) and to monitor systems (video cameras) in sensitive areas (e.g. data center, server room) that house CDE -excludes public facing areas (e.g. POS-retail/cashier)
- restrict access to publicly accessible network jacks (disable or escort guests) -can be logical, or physical controls or combo
- restrict access to wireless access points Req. 10.3 Which details should be included in audit?
- User ID, 2) Type of Event, 3) Date and Time 4) Indicate Success or Failure 5) Origin of Event 6) identify affected data, system component, resource Req. 10.4 Time Synchronization Use time synchronization technology for all CRITICAL system clocks -need consistent times-helps establish sequence of events
- protect time data for forensic investigation -time settings from industry accepted time sources Req. 10.4 Review logs how often? Review security events and logs of systems that store CHD or SAD DAILY -includes logs of ALL critical systems and ALL server and system components performing security functions -review all other system components periodically Req. 10 Track and Monitor Access to what? Track and monitor network resources and CDE
- audit trails- retain for 1 year Req. 10.8 Applies to who? Applies to service providers only. -requires formal process to d etect and alert critical security fails Req. 11 Regularly Test Security Systems and Processes-how,when?
- identify and test all wireless access points quarterly -testing methods: wireless network scans , network access control (NAC), wireless IDS/IPS -physical/logical inspection of system components and infrastructure -11.2 3 types of vulnerability scanning required by PCI- DSs 1)run internal vulnerability scans quarterly (ASV not required) and 2)External vulnerability scans quarterly (at least)( ASV required ) and 3) Internal and External scans after each significant change in network Req. 11.2 For initial PCI Compliance - are 4 quarterly scans necessary? No, if the assessor verifies I) the most recent scan result was passing
- company has documented policies and procedures requiring quarterly scanning 3) vulnerabilities in the scan were corrected and shown in the re-scan -All subsequent years require scans each quarter Sec. 11.3 Penetration Testing Req. 10.7 Retention period for Audit Trail Retain audit trail for 1 year -minimum of 3 months audit trail available for analysis Sec. 11.4 Penetration testing Monitor all traffic at the perimeter of CDE and critical points of CDE Req. 12 Maintain a strong information security policy Review policy annually and update when environment changes Req. 12.2 Risk Assessment Implement a risk assessment process -perform annually and when significant environment changes (e.g. merger, acquisition) -identify critical assets, threat, and vulnerabilities -document formally the risk after the assessment Req. 12.3 Develop Personnel Usage Policy Policy should address permitted and prohibited use of devices and technology (e.g. laptop) Req. 12.6 Train Personnel on Security Policy Training at hire and annually Personnel should acknowledge policy annually Req. 12.10 Incidence Response Plan (IRP) Implement an IRP If breach: -notify payment brand Req. 12.11 Security reviews- Service Providers Only Perform reviews quarterly -maintain documentation of review -sign-off from personnel responsible for PCI DSS compliance PCI DSS Compliance Levels Level 1- 6MM + trans/yr Level 2 - 1-6MM trans/yr Level 3 - 20K-1MM trans/yr Level 4 - less than 20K trans/yr Process by which PAN is replaced with a surrogate value Tokenization Well suited for sending small bursts of data (e.g. email and web browsing) GPRS General Packet Radio Service
- Mobile data service available to users of GSM mobile phones -recognized for efficient use of limited bandwith -great for sending small bursts of data GSM Global System for Mobile Communications Popular standard for mobile phones and networks
Merchant Level 4 Level 4 Criteria- Less than 20K Visa or MC E-Commerce transactions per year AND all other merchants processing up to 1MM Visa or MC transactions annually Level 4 Validation Requirements-
- Annual SAQ
- Quarterly network scan by ASV
- Attestation of Compliance When should an EMV chip deployment be used? When there appears to be a spike in card-no present transactions SHRED Secure Reading and Exchange of Data -is a set of PCI PTS requirements intended to protect/encrypt card data in payment terminals PCI DSS requirement that refers to restricting physical access to cardholder data? Req. 9 QSA- is it a data security firm? Yes, a QSA is a data security firm (not a certification b/c it does not leave w/ the individual). Applies to ASVs also. PCIP is the only stand alone certification that follows an individual when they leave a firm. External scans performed by an ASV...components may not contain any vulnerability that has been assigned a Common Vulnerability Scoring System (CVSS) score equal to or higher than what? 4.0 CVSS score Of the 6 PCI DSS goals, the goal "Implement Strong Access Control Measures" refers to which PCI DSS Requirements? Req.'s 7, 8 and 9 -Req. 7 Restrict access to cardholder data by business need to know -Req. 8 Identify and authenticate access to system components -Req. 9 Restrict physical access to cardholder data SAQ B MOTO and NO Internet Imprint- old school slide across paper Dial out stand alone- connected to a phone line (land line) -most risk comes from physical terminal Card present AND Card Not Present
SAQ B-IP
MOTO AND Internet PTS- PIN Transaction Security -stand alone device that uses IP (internet) connected POI devices -card present and card not present -not connected to any other system in your environment
- paper copies of receipts (nothing stored electronically) Difference between SAQ B and SAQ B-IP? How data is transmitted between the terminal and the processor SAQ-B - phone line SAQ B-IP - internet SAQ C Payment App using internet (e.g. square) or, computer with internet MOTO (card no present) and POS (card present) SAQ C-VT sends payment via a virtual payment terminal solution accessed by an internet connected web browser (e.g. Venmo, Zelle, Cash) -payment just goes between terminal and web browser -lower risk than e-commerce -computer is not connected to any other systems -no hardware attached
- e.g. call centers SAQ D Applies to all e-commerce merchants that don't meet other SAQ req's and ALL SERVICE PROVIDERS (unless more than 300K transactions per year then ROC required) (e.g. hosting provider, manage firewalls)
- Card holder data is STORED -card holder data accepted on website (e-commerce) or MOTO
- even if merchant does not store data, but no other SAQs apply, must use SAQ D, or if some req's fall outside of another SAQ, have to use SAQ D
- consumer enters cc info on check out page of merchant website SAQ A E-commerce and/or MOTO
Which appendixes address Compensating Controls? B and C What is the primary defining factor for cardholder data? PAN -only cardholder data that must be encrypted when at rest (stored) excluding SAD that can never be stored -name and exp. date WITHOUT PAN is not cardholder data for PCI Changes to the PCI standards follow a defined lifecycle, which is how many months? Stages? 36 months, 8 stages Appendix A1 applies to what? Shared Hosting Providers (Req. 2.6) Section 3- What are the sub-requirements? Protect Stored Cardholder Data SSMUKKI S tore-limit storage time-3. S AD-no storing SAD after authorization- 3. M ask- mask the PAN- first 6, last 4- - 3. U nreadable- render PAN unreadable- one way# function-truncate. 3.4.. K eys (Protect)- keys for encryption-protect them-3. K eys (Manage)- manage keys for cryptography- 3. I S Policy- IS policies in place and known by all- 3. FIPS Federal Information Processing Standards What is a dependency in the context of PA DSS? Hardware OR Software What are first six digits on payment card called? BIN- Bank identifier number -identifies who the merchant is In MFA- Multi Factor Authentication , a password or passphrase is? Something you are--validates Identity -Req. 8. -need two forms of separate authentication Which form does a PA QSA attest to the results of a PA DSS? ROV - Report on Validation Req. 10- How long do you need to keep audit trail history? 1 year For external scans, no component may contain any vulnerability that has been assigned a CVSS base score equal to or higher than?
CVSS
Common Vulnerability Scoring System -rates scoring vulnerability for software -0-10 scoring, 10 most severe Payment Card Industry Security Standards for Manufacturers PCI PTS- Pin Transaction Security -governs manufacturers of the devices Who does PCI TSP apply to? Token Service Providers EMV Chip -prevents cards from being cloned -creates a unique transaction code with each purchase -is best for protecting card-present transactions Ransomware -fastest growing malware threat -can be delivered by phishing email PCI as a whole should be organized around what? Business As Usual If stored cardholder data cannot be encrypted or otherwise rendered unreadable, you should refer to which PCI DSS appendix? Appendix B and C--Compensating Controls Does using a PA-DSS app reduce the merchant's CDE scope? No Penetration testing falls under which PCI DSS requirement? 3 Anti-virus refers to which PCI DSS requirement? 5 How frequently monitor service provider's compliance Annually How frequently maintain and implement policies and procedures to manage service providers you share CHD? Req.? Annually Req. 12. How frequently do service providers have to perform and document reviews, and why? Req? Req. 12.
- quarterly -to make sure personnel are following security policies Restrict access to publicly accessible network jacks, wireless access points, gateways, telecom lines, handheld devices, etc.--req? Req. 9 Lockout user ID--how many attempts? Req.? no more than 6 attempts Req. 8 Define access on a to CHD on a business need to know- req? Req. 7 Systems only receive time from designated time servers- req? 10- Track and monitor all access to network resources and cardholder data. Test, Development and Production environments are separately maintained- req.?
