Frequently Asked Question
What is meant by "At-Risk Timeframe" and at risk referenced in the Final PFI Report?
The At-Risk Timeframe refers to the period of time data elements, such as account data, were at risk for this Entity Under Investigation during the incident under investigation. A data element is considered at risk if evidence indicates the data element was exposed (i.e. per the Final PFI Report template v3.3, Section 3.4 “a data element was accessible to the Entity under investigation or any unauthorized entity, process, source, etc.”) during the incident under investigation.
The "At-Risk Timeframe" as identified in the Final PFI Report template, Appendix C refers to the period of time during the incident under investigation when data was vulnerable. For example, consider a scenario where evidence (e.g., system/access logs) indicates that an unauthorized entity breached the cardholder data environment's security controls on 2024-04-14T18:30:00 and was discovered by the breached entity (who subsequently took the system offline to limit the exposure) 2024-04-17T07:15:00.
The at-risk timeframe is considered to have been from 6:30PM on April 14th when the breach occurred, through 7:15AM on April 17th when the breached system was taken offline (approximately 60 hours).
Further considering the scenario above, suppose the breached entity had several years' worth of data elements stored in the environment. In this case, regardless of how many data elements were exposed or how long they were stored, the at-risk timeframe:
- would not date back to the oldest data element stored, and
- only refers to the timeframe itself — the period of time the data elements were at risk (approximately 60 hours in this scenario).
For additional information please contact your case-specific Payment Brand representative.
Related
-
When should an entity implement PCI DSS requirements noted as best practices until a future date?
-
For PCI DSS, can multi-factor authentication (MFA) implementations indicate the success of a factor prior to presentation of subsequent factors?
-
What is the completion date for PCI DSS assessments documented in a Report on Compliance and its related Attestations of Compliance?
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 for determining applicability of PCI DSS requirements for assessments documented in a Report on Compliance?
Most Popular
-
When should an entity implement PCI DSS requirements noted as best practices until a future date?
-
For PCI DSS, can multi-factor authentication (MFA) implementations indicate the success of a factor prior to presentation of subsequent factors?
-
What is the completion date for PCI DSS assessments documented in a Report on Compliance and its related Attestations of Compliance?
-
What is the completion date for PCI DSS assessments documented in a Self-Assessment Questionnaire and its related Attestations of Compliance?
-
How does PCI DSS Requirement 6.4.3 apply to 3DS scripts called from a merchant check-out page as part of 3DS processing?
Most Recently Updated
-
When should an entity implement PCI DSS requirements noted as best practices until a future date?
-
What is meant by "At-Risk Timeframe" and at risk referenced in the Final PFI Report?
-
Does PCI DSS Requirement 8.2.2 allow users to share authentication credentials?
-
For PCI DSS, can multi-factor authentication (MFA) implementations indicate the success of a factor prior to presentation of subsequent factors?
-
What is the completion date for PCI DSS assessments documented in a Report on Compliance and its related Attestations of Compliance?