Frequently Asked Question

What does "Window of Payment Card Data Storage" mean in the Final PFI Report template?
Window of Payment Card Data Storage (section 3.1 of the Final PFI Report template) indicates:
- The timeframe for which account or payment card data was being stored – this may include expired accounts and/or card data. It answers the question, 'What is the date range of all accounts and/or payment card data stored, including expired account/payment card data'?
- Overall timeframe of exposed account/card data. Note the Window of payment card data storage is not limited to the "at-risk timeframe" which refers to the period of time the account numbers were at risk (see Section 3.4 of the Final PFI Report template and FAQ 1448). The Window of payment card data storage includes the full date range (time window) of the actual accounts/card data that were exposed during the at-risk timeframe.
Example: The at-risk timeframe is Jan 1 – Jan 31, 2019 (31 days). The unauthorized data disclosure includes account/payment card data dating back to March 2012. The Window of payment card data storage would be March 1, 2012 - January 31, 2019.
January 2019
Article Number: 1462
Related
-
Are Approved Scanning Vendors and Qualified Security Assessors considered third-party service providers for PCI DSS Requirements 12.8 and 12.9?
-
What are the expectations for entities when assigning risk rankings to vulnerabilities and resolving or addressing those vulnerabilities?
-
Is phishing-resistant authentication alone acceptable as multi-factor authentication for PCI DSS Requirements 8.4.1 and 8.4.3?
Featured FAQ Articles
Featured
-
Do PCI DSS requirements for keyed cryptographic hashing apply to previously hashed PANs?
-
Is the PCI DSS Attestation of Compliance intended to be shared?
-
How does an entity report the results of a PCI DSS assessment for new requirements that are noted in PCI DSS as best practices until a future date?
-
Where do I direct questions about complying with PCI standards?
-
Can SAQ eligibility criteria be used as a guide for determining applicability of PCI DSS requirements for merchant assessments documented in a Report on Compliance?
Most Popular
-
Are Approved Scanning Vendors and Qualified Security Assessors considered third-party service providers for PCI DSS Requirements 12.8 and 12.9?
-
What are the expectations for entities when assigning risk rankings to vulnerabilities and resolving or addressing those vulnerabilities?
-
Is phishing-resistant authentication alone acceptable as multi-factor authentication for PCI DSS Requirements 8.4.1 and 8.4.3?
-
Are passkeys synced across devices, implemented according to the FIDO2 requirements, acceptable for use as phishing-resistant authentication to meet PCI DSS Requirement 8.4.2?
-
How should PCI DSS v4.x requirements noted as superseded by another requirement be reported after 31 March 2025?
Most Recently Updated
-
Are Approved Scanning Vendors and Qualified Security Assessors considered third-party service providers for PCI DSS Requirements 12.8 and 12.9?
-
Can a compensating control be used for requirements with a periodic or defined frequency, where an entity did not perform the activity within the required timeframe?
-
How often must service providers test penetration testing segmentation controls under PCI DSS?
-
Are merchants allowed to request card-verification codes/values from cardholders?
-
What is the maximum period of time that cardholder data can be stored?