PCI DSSRequirement 12.8.4mandates that an entitymonitor the compliance status of third-party service providers (TPSPs) at least annually, especially when those TPSPs store, process, or transmit account data on the entity's behalf.
* Option A:Incorrect. Entities are not responsible for conducting ASV scans on TPSPs.
* Option B:Incorrect. There is no quarterly risk assessment requirement for TPSPs.
* Option C:Incorrect. Incident response testing for TPSPs is not a direct responsibility of the entity.
* Option D:Correct. Annual monitoring of TPSP compliance is explicitly required.
Reference:PCI DSS v4.0.1 - Requirement 12.8.4.

PerRequirement 10.6.1, PCI DSS mandates that time-synchronization technology be used, andsystems must be synchronized to a central time serverthat itself receives time from an approved external source. This ensures logs can be accurately correlated.
* Option A:Incorrect. Time inconsistency arises if each system operates independently.
* Option B:Incorrect. Time configuration must berestricted to authorised personnel only.
* Option C:Correct. Time should be sourced from a centralised server which is in sync with reliable external sources.
* Option D:Incorrect. Each system peering independently can cause inconsistencies.
Reference:PCI DSS v4.0.1 - Requirement 10.6.1.1.

According toRequirement 12.10.1, an effectiveincident response plan (IRP)must include steps to detect, respond to, and contain incidents such asunauthorised wireless access points. PCI DSS11.2.1also mandates quarterly rogue AP detection.
* Option A:#Incorrect. Notification to PCI SSC is not required; notification goes toacquirers/payment brands.
* Option B:#Correct. The IRP must includeresponse to unauthorised wireless access detection.
* Option C:#Incorrect. Records must beretained, not deleted.
* Option D:#Incorrect. Retaliatory or offensive actions arenot allowed or recommended.
References:
PCI DSS v4.0.1 - Requirements 12.10.1 and 11.2.1.

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.
References:
PCI DSS v4.0.1 - Section 4: Scope of PCI DSS Requirements;
Requirement 10.6.1.1.

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.
Reference:PCI DSS v4.0.1 - Requirement 6, and Appendix F: PCI Software Security Framework Reference.