QSA_New_V4 Questions and Answers

PCI DSSRequirement 12.1.1requires that security policies and procedures be disseminated to all relevant personnel and that those individualsunderstand and acknowledgethe policies. While review and update frequencies are also part of compliance, the most complete and correct answer is that policies must be shared with affected parties.

Option A:Incorrect. Encryption is not specifically required for policy documents.

Option B:Incorrect. Limiting access to only management contradicts the requirement for distribution.

Option C:Incorrect. The correct review cycle per Requirement 12.1.2 isannually, not quarterly.

Option D:Correct. Policies and procedures must be understood and acknowledged by all affected parties.

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.

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 toPCI DSS Scope Definitions (Section 4.2.1), any system thatcan impact the security of the CDEisin scope, even if it doesn’t store cardholder data. An LDAP server providing authentication to systems in the CDEdirectly affects access control, so it'sin scope.

Option A:✅Correct. Systems providingauthentication services to the CDEarein scope.

Option B:❌Incorrect. LDAP does not need to store card data to be in scope.

Option C:❌Incorrect. Influence over access security makes it in scope regardless of data processing.

Option D:❌Incorrect. Scope isn’t limited to DMZ-linked systems.

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.​

There areseparate Attestation of Compliance (AOC) templatesfor different use cases, specifically formerchantsandservice providers, and forSAQsversusROCs. Each template is tailored to match the reporting needs of that assessment type.

Option A:✅Correct. PCI SSC publishes distinct AOC templates depending on whether the entity is a merchant or service provider, and depending on whether they are completing an SAQ or ROC.

Option B:❌Incorrect. The AOC is not signed by PCI SSC. It must be signed by the assessed entity and, where applicable, the QSA or ISA.

Option C:❌Incorrect. ROCs and SAQs use different AOC formats.

Option D:❌Incorrect. Both the entity and the assessor (if applicable)mustsign.

 Customized Approach Overview:

Under PCI DSS v4.0, entities can use a Customized Approach to meet requirements by implementing controls tailored to their environment. This allows flexibility while still achieving the intent of the security requirement.

 Role of Assessors:

Assessors (QSAs) are responsible for evaluating both the implementation of customized controls and ensuring these controls fulfill the security objectives of the PCI DSS requirements​​.

QSAs must document the evaluation, evidence reviewed, and results in the Report on Compliance (ROC).

 Controls Matrix and Targeted Risk Analysis (TRA):

The Controls Matrix and TRA are key components of the Customized Approach. QSAs assist in verifying the accuracy and completeness of these tools during assessments​​.

 Documenting in the ROC:

The ROC must include a narrative explaining the assessor’s findings regarding the customized control, validation methods, and any evidence collected​.

 Relevant PCI DSS v4.0 Guidance:

Appendix D and E of the PCI DSS v4.0 ROC Template emphasize that QSAs can evaluate and confirm adherence to the Customized Approach provided this is documented comprehensively in the ROC​.

As perRequirement 2.2.1, the purpose of limiting each server to one primary function is toreduce the risk of functions with lower security needs compromising more critical functions.

Option A:❌Incorrect. PCI DSS discourages combining different security-level functions.

Option B:✅Correct. This is the intent: toprevent lower-security processes from weakening high-security environments.

Option C:❌Incorrect. Functions shouldn’t depend on one another for security.

Option D:❌Incorrect. PCI DSS encourages raising security, not lowering it.

PerSection 11 and 12of PCI DSS v4.0.1, assessors arerequired to use the official PCI SSC ROC Reporting Template. This ensures uniformity and completeness across all assessments. The same requirement applies to bothmerchants and service providersundergoing afull assessment (ROC).

Option A:✅Correct. PCI SSC mandates use of its official ROC template.

Option B:❌Incorrect. Custom assessor templates arenot permitted.

Option C:❌Incorrect. Assessorsmust notcreate their own templates.

Option D:❌Incorrect. The ROC template is used forbothmerchants and service providers, where applicable.

Requirement10.2.2mandates that all access to audit trails must be logged. This ensures that any tampering, viewing, or deletion of audit data is traceable. It supports the broader goal of maintaining audit trail integrity and accountability.

Option A:Incorrect. PCI DSS does not require logging use of end-user messaging.

Option B:Incorrect. There’s no explicit requirement to log access to external websites.

Option C:Correct. PCI DSS mandates loggingall access to audit trailsto detect and respond to unauthorised attempts.

Option D:Incorrect. Logging all network transmissions is not feasible and not required.

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.

TheSoftware Security Framework (SSF)is intended to support entities usingbespoke and custom softwarewithin the Cardholder Data Environment (CDE). If the software is developed and maintained in accordance with theSecure Software Lifecycle (SLC) Standard, it can help demonstrate secure software development practices and potentially reduce the number of applicable PCI DSS requirements.

Option A:Incorrect. Not all payment software qualifies unless developed under SSF standards.

Option B:Incorrect. PCI PTS devices follow different hardware security standards.

Option C:Incorrect. PA-DSS has been retired; those applications are now listed as “Acceptable Only for Pre-Existing Deployments”.

Option D:Correct. Software developed under the Secure SLC Standard may help an entity meet some requirements in PCI DSS Requirement 6.

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.

 Attestation of Compliance (AOC):

The AOC is a document that confirms an entity’s compliance with PCI DSS requirements. It is signed by the entity (merchant or service provider) and the Qualified Security Assessor (QSA) if a QSA is involved.

 Different AOC Templates:

PCI DSS provides distinct templates for service providers and merchants, tailored to their respective roles and responsibilities within the cardholder data environment (CDE)​​.

 Invalid Options:

B:PCI SSC does not sign AOCs; they are signed by the merchant/service provider and the QSA.

C:AOCs differ between ROCs and SAQs, so the same template is not universally used.

D:Both the merchant/service provider and the QSA/ISA (Internal Security Assessor) must sign the AOC when applicable.

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.

Requirement 11.5.1mandates that organisations deployintrusion-detection or prevention toolstomonitor traffic and generate alertsfor suspicious activity. The goal is tonotify personnel quicklyof a possible breach.

Option A:❌Incorrect. IDS/IPS isnot requiredon every component — only where it adds value.

Option B:✅Correct. IDS/IPS must be configured toalert on potential compromises.

Option C:❌Incorrect. Segmentation is a separate concern under Requirement 1.

Option D:❌Incorrect. IDS is not for discovering cardholder data.

Scope definition in PCI DSS v4.0.1 (Section 4)includesany system that can impact the security of the CDE. Time synchronization servers such asNTParecritical to log integrity(Requirement 10.6), and if they provide services to CDE systems,they are in scopeeven if they do not directly process cardholder data.

Option A:❌Incorrect. Scope is broader than just databases.

Option B:❌Incorrect. Time serversimpact log security, so they are in scope.

Option C:❌Incorrect. PCI DSS scope includes systems thataffect the securityof CDE, not just those storing card data.

Option D:✅Correct. Internal NTP servers providing services to the CDE arein scope.