QSA_New_V4 Qualified Security Assessor V4 Exam Questions and Answers

Requirement 9.6.1mandates theclassification of mediaso that appropriatehandling, storage, and disposalprocedures are applied based on thesensitivity of the data. This ensures that media storing cardholder data is not treated the same as media containing non-sensitive content.

Option A:✅Correct. Classifying media enablesrisk-appropriate protections.

Option B:❌Incorrect. Movement schedules are not mandated.

Option C:❌Incorrect. Labeling is a recommended control but not the primary intent.

Option D:❌Incorrect. Destruction must bebased on data classification, not uniform timing.

PCI DSS Requirement 12.7 mandates that organizations perform background checks on personnel who have access to the cardholder data environment (CDE) to ensure that individuals with malicious intent do not gain access to sensitive cardholder data.​

Option A:Incorrect. While conducting background checks on all personnel is a good security practice, PCI DSS specifically requires checks for those with access to the CDE.​

Option B:Correct. Background checks are required for personnel with access to the CDE to mitigate the risk of insider threats.​

Option C:Incorrect. Visitors are not typically subjected to background checks but should be escorted and monitored while in sensitive areas.

Under theCustomized Approach, assessors are responsible forderiving and documenting the testing proceduresinAppendix E of the Report on Compliance (ROC). The assessor must ensure the controlmeets the requirement objectiveand validate it throughcustom testing.

Option A:❌Incorrect. Ongoing monitoring is the entity’s responsibility, not the assessor’s.

Option B:✅Correct. The assessor must derive anddocument testingin Appendix E.

Option C:❌Incorrect. The entity documents control details; the assessor documents test results.

Option D:❌Incorrect. Theentitymust perform the targeted risk analysis, not the assessor.

Formulti-tenant service providers,isolation and segmentationare critical. As perRequirement 12.10.3, each customer’s environment must besegregated and protectedsuch that no tenant can access another’s data or systems.

Option A:✅Correct. This is the foundational control —isolation of customer environments.

Option B:❌Incorrect. Exposing system config files is a security risk.

Option C:❌Incorrect. Shared user IDs areexplicitly prohibitedby Requirement 8.2.1.

Option D:❌Incorrect. Customers should only access their own logs.

PCI DSSRequirement 11.5.2mandates the use of file-integrity monitoring (FIM) or change-detection tools to monitorcritical filessuch as system binaries, configuration files, and system parameters.

Option A:❌Incorrect. Manuals are not critical system files.

Option B:❌Incorrect. Regularly changing files (e.g., logs or temp files) are typically excluded.

Option C:❌Incorrect. Policies and procedures are reviewed but not subject to FIM.

Option D:✅Correct. System config and parameter files must bemonitored for unauthorised changes.

According toRequirement 1.2.1of PCI DSS v4.0.1, network security controls (NSCs), such as firewalls and segmentation controls, are used torestrict and control trafficbetween trusted and untrusted networks. This includes logical or physical network segmentation.

Option A:Incorrect. Anti-malware is addressed in Requirement 5.

Option B:Correct. NSCs control and restrict inbound and outbound traffic between logical and physical network segments.

Option C:Incorrect. Vulnerability management is under Requirement 6.

Option D:Incorrect. PAN encryption is covered in Requirement 3.5.

TheSecure Software Lifecycle (SLC) Standardis part of PCI’sSoftware Security Framework (SSF). If an entity ' s software is developed under aPCI-recognised Secure SLC process, it maysatisfy parts of Requirement 6, especially around secure coding practices and vulnerability management.

Option A:❌Incorrect. SLC compliance alone doesn’t grant full PCI DSS compliance.

Option B:✅Correct. Secure SLC can help meetmany of the development-related controls.

Option C:❌Incorrect. There isimpact— potentially reducing scope/testing.

Option D:❌Incorrect. The software remainsin scope, but fewer controls may need to be separately validated.

 Definition of Quarterly:

PCI DSS defines " quarterly " as occurring once within each calendar quarter. This means the activity must happen at least once in Q1, Q2, Q3, and Q4, with no rigid restrictions on specific days​​.

 Clarification on Other Options:

B:While 95–97 days approximates a quarter, it is not mandated as a rigid timeframe.

C/D:Fixed dates (e.g., 15th or 1st of specific months) are not prescribed in PCI DSS.

Requirement 8.4.2defines multi-factor authentication (MFA) asauthentication that requires at least two of the following:

Something you know (password/PIN)

Something you have (smart card/token)

Something you are (biometric)

Option A:❌Incorrect. Presenting the same token twice is stillsingle-factor.

Option B:❌Incorrect. Two passwords arestill one factor— “something you know”.

Option C:✅Correct. Password (something you know) + smart card (something you have) =MFA.

Option D:❌Incorrect. Fingerprint and thumbprint are bothbiometrics, so one factor.

According toRequirement 3.5.1.2, whendisk-level encryptionis used (e.g., full disk encryption), access control must beseparate from the operating systemto prevent unauthorised users from bypassing controls by booting the system.

Option A:✅Correct. Disk encryption must useindependent authentication mechanisms.

Option B:❌Incorrect. Sharing authentication with the OSviolates independence.

Option C:❌Incorrect. Association with local accounts may not ensure separate access control.

Option D:❌Incorrect. Key storage within user accounts is not secure or compliant.

Requirement 5.2.1.1clarifies thatanti-malware solutions are requiredonall in-scope systems,unlessthe system is evaluated asnot at risk for malware(e.g., Linux-based appliances with no Internet access). These risk evaluations must be documented and justified (5.2.3.1).

Option A:❌Incorrect. PCI DSS allows exceptions for systems not at risk.

Option B:❌Incorrect. Anti-malware applies to systems, not portable media per se.

Option C:❌Incorrect. Anti-malware scope is broader than just PAN-storing systems.

Option D:✅Correct. Systems not at risk can be excluded if justified and documented.

According toRequirement 8.2.1, PCI DSS mandates that all users be assigned aunique IDbefore accessing system components or cardholder data. This ensuresaccountability, enabling identification of actions taken by each user.

Option A:❌Incorrect. Password strength is addressed underRequirement 8.3, not unique ID.

Option B:❌Incorrect. Shared accounts areprohibitedregardless of admin status.

Option C:✅Correct. Unique IDs ensure thateach user ' s actions can be traced.

Option D:❌Incorrect. Group accounts are discouraged in favour of individual accountability.

As per thePCI DSS Glossary, “bespoke and custom software” is defined assoftware that is developed specifically for, and often by, the entity using it. This includes internally developed applications and externally developed applications created specifically for the entity.

Option A:❌Incorrect. Not all third-party software is custom — much is commercial off-the-shelf (COTS).

Option B:❌Incorrect. Customisability does not equal bespoke development.

Option C:✅Correct. Bespoke software is tailoredby or forthe entity’s specific needs.

Option D:❌Incorrect. Virtual terminals are payment interfaces, not types of software.

Thesettlement phaseis when:

Themerchant’s acquiring bank pays the merchant, and

Theissuing bank bills the cardholder.

This occursafter authorization and clearinghave already taken place.

Option A:❌Incorrect. Authorization verifies the card and funds but doesn’t trigger payment.

Option B:❌Incorrect. Clearing exchanges transaction details between banks but doesn’t finalise funds.

Option C:✅Correct. Settlement is whenfunds are actually transferred.

Option D:❌Incorrect. Chargebacks reverse transactions, not settle them.

 Compensating Controls Definition and Purpose

A compensating control is an alternate measure that satisfies the intent of a specific PCI DSS requirement and provides an equivalent level of security.

The rationale and risk mitigation must be explicitly documented using the Compensating Control Worksheet (CCW).

 Mandatory Documentation

PCI DSS v4.0 mandates the use of a CCW when implementing compensating controls. This applies regardless of acquirer approvals​​.

The CCW requires detailed documentation including:

Constraints preventing the original requirement from being implemented.

Justification for the compensating control.

Description of the control and evidence of its effectiveness.

 Using Existing Requirements

If an existing PCI DSS requirement (e.g., Requirement 5 for antivirus) is already implemented and can mitigate the risks of not meeting another requirement, it may qualify as a compensating control​​.

 Approval and Review Process

QSAs must validate the implementation, effectiveness, and appropriateness of compensating controls during the assessment process​

Track equivalent data— whether from a magnetic stripe or embedded chip — falls underSensitive Authentication Data (SAD)and mustnot be stored after authorisation, even if encrypted. This is covered underRequirement 3.3.1and Table 3 in PCI DSS v4.0.1.

Option A:❌Incorrect. SADmust not be stored after authorisation, regardless of encryption.

Option B:✅Correct. Track equivalent data is explicitly defined asSAD.

Option C:❌Incorrect. SAD is fullyin-scopefor PCI DSS.

Option D:❌Incorrect. Requirement 3.2 and 3.3 specifically address SAD.

 Requirement for Secure Transmission:

PCI DSS Requirement 4.1 mandates that cardholder data sent over open public networks must be protected with strong cryptographic protocols. Accepting only trusted keys ensures data integrity and prevents unauthorized access​​.

 Key Validation Practices:

Trusted keys and certificates are verified to ensure authenticity. Using untrusted keys compromises the security of the encrypted communication.

 Prohibited Practices:

A/D:Configuring protocols to accept all certificates or lower encryption strength violates PCI DSS encryption guidelines.

B:Proprietary protocols are not inherently compliant unless they meet strong cryptographic standards.

 Testing and Verification:

Assessors verify the implementation of trusted keys by examining encryption settings, reviewing certificate chains, and conducting tests to confirm only trusted connections are accepted​​.

 Key Management Requirements:

PCI DSS Requirement 3.5 specifies the protection of cryptographic keys, including encryption, storage in secure cryptographic devices (SCDs), or as key components to ensure security and prevent unauthorized access​​.

 Clarifications on Cryptographic Key Protection:

A/B:Public keys and key strength requirements are not specified in this context.

D:Separation of duties mandates that key-encrypting and data-encrypting keys must not be assigned to the same custodian.

 Testing and Validation:

QSAs verify compliance by examining key management practices, storage mechanisms, and access controls for cryptographic keys during the assessment​.

Compensating controls are alternative measures implemented when an entity cannot meet a specific PCI DSS requirement due to legitimate technical or business constraints. These controls must sufficiently mitigate the associated risk and be commensurate with the intent of the original PCI DSS requirement.​

Option A:Incorrect. Even if all other PCI DSS requirements are met, a compensating control is necessary when a specific requirement cannot be directly satisfied.​

Option B:Correct. A compensating control must effectively address and mitigate the risk associated with the inability to meet a particular PCI DSS requirement.​

Option C:Incorrect. While existing controls can support a compensating control, they must collectively address the risk of the unmet requirement and cannot merely be another existing PCI DSS requirement.​

Option D:Incorrect. A compensating control worksheet is mandatory to document the rationale, assessment, and validation of the compensating control, regardless of acquirer approval.​

For detailed guidance on compensating controls, refer toAppendix B: Compensating Controlsin thePCI DSS v4.0.1document.​