 Scope of Change-Detection Mechanisms

PCI DSS v4.0 requires the implementation of a change-detection mechanism (e.g., file-integrity monitoring) to monitor unauthorized changes to critical files.

Critical files include system configuration and parameter files, application executable files, and scripts used in administrative functions​​.

 Intent of Monitoring System Files

These files often control security settings and operational parameters of systems within the Cardholder Data Environment (CDE). Unauthorized changes could compromise system security.

 Exclusions

Documents like application vendor manuals and security policies do not qualify as files requiring integrity monitoring since they do not directly impact the security posture or operational functions of systems in the CDE.

PCI DSS allows for theuse of truncation and hashingfor protecting PAN, butRequirement 3.4.1and its guidance warn againstcombining hashed and truncated PANsin such a way that the original PAN could be reconstructed. If both formats exist,controls must ensurethey can't be used together to reverse-engineer the PAN.

Option A:✅Correct. Controls must ensure PAN cannot be reconstructed using both versions.

Option B:❌Incorrect. A hashed PAN does not need truncation — hashing is a separate mechanism.

Option C:❌Incorrect. PCI DSS aims to prevent correlation, not encourage it.

Option D:❌Incorrect. They can coexist, but must be secured so that PAN cannot be derived.

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.

 Purpose of Classifying Media

PCI DSS v4.0 emphasizes the need to classify media based on the sensitivity of the data it contains. Media classification ensures appropriate handling, storage, and destruction processes​​.

 Media Protection Requirements

Media containing cardholder data must be securely stored, transferred, and destroyed when no longer needed.

Classification informs the level of protection required, such as encryption, physical security, or controlled access​​.

 Incorrect Options

Option B: Moving media quarterly is not a requirement.

Option C: Labeling as "Confidential" is insufficient without a comprehensive protection strategy.

Option D: Destruction schedules should depend on retention requirements and data sensitivity, not a universal timeline.

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

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.

According toSection 12.2.3.3 of PCI DSS v4.0.1, aPartial Assessmentis defined as a result whereat least one PCI DSS requirement is marked as “Not Tested.”This is typically seen duringgap assessments or pre-validation efforts, not official compliance validation.

Option A:❌Incorrect. SAQs are self-assessments; Partial Assessment is a different concept.

Option B:❌Incorrect. Interim drafts are not labeled as “Partial”.

Option C:❌Incorrect. That is a misinterpretation of segmentation by payment channel.

Option D:✅Correct. "Not Tested" = Partial Assessment.

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 6.4.3.1clarifies that if live PANs are to be used in testing, the test environment mustmeet all applicable PCI DSS controls. Thus,testing with live PAN is only allowed if the test environment is within the CDEand fully secured.

Option A:❌Incorrect. Testing should not happen in production.

Option B:❌Incorrect. It must be within the CDE if live PAN is involved.

Option C:✅Correct. Live PANs can be used inpre-production environments within the CDE.

Option D:❌Incorrect. There’s no requirement to test only within QSA environments.

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.

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.

 Visitor Management Requirements:

PCI DSS Requirement 9.3 specifies that visitors must be escorted at all times in areas where cardholder data is present to prevent unauthorized access or breaches​​.

 Invalid Options:

B:Visitor badges must be distinguishable from employee badges.

C:Visitor logs are necessary but do not need detailed personal information like addresses.

D:Retaining visitor identification for 30 days is not a requirement.

 Mandatory ROC Template

PCI DSS v4.0 mandates the use of the PCI SSC-provided ROC Template for all Reports on Compliance​​.

This ensures standardization, completeness, and accuracy in documenting compliance assessments.

 Sections of the ROC Template

The ROC includes mandatory sections:

Assessment Overview:General details, scope validation, and assessment findings.

Findings and Observations:Detailed compliance status per requirement.

 Prohibited Practices

Assessors cannot use self-created ROC templates. Deviation from the PCI SSC-approved template may result in rejection of the report​​.

 Key Changes in v4.0

Enhanced focus on the integrity of reporting and inclusion of specific findings to ensure alignment with PCI DSS objectives.

Added support for the customized approach within the ROC structure​​.

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.

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.

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.

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.

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