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
-
Which date format should be used when completing PCI SSC documents that request dates?
-
Do ASV scans in SAQ A apply to merchants with webpages that redirect to TPSPs or include TPSPs’ embedded iframes?
-
Are authentication values from a 3DS transaction considered sensitive authentication data for PCI DSS purposes?
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
-
What are acceptable formats for truncation of primary account numbers?
-
For PCI DSS, why is storage of sensitive authentication data (SAD) after authorization not permitted even when there are no primary account numbers (PANs) in an environment?
-
How does an e-commerce merchant meet the SAQ A eligibility criteria for scripts?
-
If an organization provides software or functionality that runs on a consumer's device (for example, smartphones, tablets, or laptops) and is used to accept payment account data, can the organization store card verification codes for those consumers?
-
Are truncated Primary Account Numbers (PAN) required to be protected in accordance with PCI DSS?
Most Recently Updated
-
Which date format should be used when completing PCI SSC documents that request dates?
-
Are authentication values from a 3DS transaction considered sensitive authentication data for PCI DSS purposes?
-
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?
-
Does PCI DSS define which versions of TLS must be used?
-
Do ASV scans in SAQ A apply to merchants with webpages that redirect to TPSPs or include TPSPs’ embedded iframes?