QSA_New_V4 Sample Questions Answers

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

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.

Internal vulnerability scanning is addressed underRequirement 11.3.1. According to PCI DSS, internal vulnerability scansmust be conducted at least once every three monthsandafter any significant changein the environment, such as new system components, changes in network topology, firewall rule changes, or product upgrades.

Option A:Correct. Scans must be performed after significant changes.

Option B:Incorrect. Internal scansdo not require an ASV. ASVs are required for external vulnerability scans (Requirement 11.3.2).

Option C:Incorrect. A QSA is not required to perform internal scans. They can be performed by qualified internal staff or third-party providers.

Option D:Incorrect. Internal scans arerequired quarterly, not annually.

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.

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.

TheROC Reporting Templaterequires assessors todocument how the requirement was verifiedas “In Place”. This includesmethods used, evidence reviewed, and how compliance was determined.

Option A:❌Incorrect. Project plans are relevant for “In Progress”, not “In Place”.

Option B:✅Correct. “In Place” requires an explanation ofassessor observations and validation.

Option C:❌Incorrect. This applies to “Not in Place”.

Option D:❌Incorrect. This applies to non-compliance scenarios.

Stateful inspection (or stateful packet filtering)tracks the state of active connections and determines which packets are part of a valid session.Requirement 1.4.2references the use of network security controls (NSCs) withstateful filteringcapability to allow legitimate trafficonly in response to trusted requests.

Option A:❌Incorrect. Firewall admin procedures are not what “stateful” refers to.

Option B:✅Correct. “Stateful responses” mean tracking existing connections toblock unauthorised or spoofed responses.

Option C:❌Incorrect. That describes configuration management, not stateful filtering.

Option D:❌Incorrect. Logging is important but not part of stateful inspection.

PCI DSSRequirement 8.4.2requiresmulti-factor authentication (MFA)to consist of two or moreindependent authentication factors. MFA must alsonot involve shared credentials, so each certificate must be tied to a specific individual.

Option A:❌Incorrect. MFA must apply toall applicable users, not just admins.

Option B:✅Correct. This meets PCI DSS: unique credentials per user and non-shared certificates.

Option C:❌Incorrect. Retaining certificates post-employment is a risk, not a compliance action.

Option D:❌Incorrect. PCI DSS doesn’t mandate 90-day certificate rotation; rather, secure usage and revocation are key.

 PAN Transmission Protection

PCI DSS Requirement 4.1 mandates strong cryptography for PAN during transmission over both public and private wireless networks to prevent unauthorized interception​​.

 Incorrect Options

Options B and D: PAN protection is not required for private wired networks.

Option C: PAN must be protected during transmission over public wireless networks.

PerRequirement 10.5.1.2, audit logs must be retained forat least one year, and the mostrecent three months must be readily availablefor analysis. This ensures traceability of security events over both short and longer-term periods.

Option A:✅Correct. Matches both duration and availability criteria.

Option B:❌Incorrect. Two years is not required.

Option C:❌Incorrect. The retention period is misstated.

Option D:❌Incorrect. One month is insufficient for immediate access.

As specified underRequirement 11.5.2.1, comparisons of critical files (e.g., config files, executables) using change-detection mechanisms (e.g., FIM tools)must occur at least weekly. This ensures timely detection of unauthorized changes or tampering.

Option A:✅Correct. Weekly is theminimum frequencyrequired.

Option B:❌Incorrect. A defined "period" is not sufficient unless it's weekly or more frequent.

Option C:❌Incorrect. Scans should not wait for changes; they should detectunexpectedones.

Option D:❌Incorrect. Monthly is too infrequent for PCI DSS compliance.

When a cryptographic key is retired and replaced, it is essential to ensure that the retired key is no longer used for encryption purposes to maintain the security of the cryptographic system.​

Option A:Correct. Retired keys must not be used for encryption operations to prevent potential security vulnerabilities. However, they may be retained for decryption purposes if necessary, such as decrypting existing data encrypted under the retired key.​

Option B:Incorrect. PCI DSS does not specify a mandatory retention period for retired cryptographic key components before disposal. Retention periods should align with the entity's data retention policies and legal requirements.​

Option C:Incorrect. Assigning a new key custodian is not a mandatory requirement upon key retirement and replacement, though proper key management practices should ensure that custodianship is clearly defined and documented.​

Option D:Incorrect. While data encrypted under a retired key should be re-encrypted with the new key or securely managed, PCI DSS does not mandate the destruction of such data solely due to key retirement.​

For more information on cryptographic key management practices, refer toRequirement 3: Protect Stored Account Datain thePCI DSS v4.0.1document.​Wikipedia

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.

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.

Requirement 1.3.7andRequirement 3.3.1emphasise thatdatabases storing cardholder data must not be directly accessible from the Internet or untrusted networks. The database must be behind firewalls and accessible only via controlled, authorised connections.

Option A:❌Incorrect. Combining servers may violate the one-function-per-server rule (Requirement 2.2.1).

Option B:✅Correct. The database must be protected fromdirect public access.

Option C:❌Incorrect. Web servers often reside in the DMZ; moving them internally could increase risk.

Option D:❌Incorrect. Network performance is not a PCI DSS concern —security isolation is.

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.

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.

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.

PerRequirement 7.2.5and8.2.2, PCI DSS recommends thatonly application-layer accessbe allowed to databases storing cardholder data, preventing users from issuing direct SQL queries or accessing the database via administrative tools.

Option A:✅Correct. Restricting database access toprogrammatic (application-layer) methodsis strongly preferred and aligns with PCI DSS guidance.

Option B:❌Incorrect. Admins should not have unrestricted access unless justified and monitored.

Option C:❌Incorrect. Application IDs must not be used interactively by individuals (Requirement 8.6.1).

Option D:❌Incorrect. Shared accounts are disallowed (Requirement 8.2.1).