Frequently Asked Question
What is meant by "at risk" and "at-risk timeframe" referenced in the Final PFI Report?
When completing the spreadsheet referenced within the Final PFI Report under Appendix C: Impacted Entities, an account is considered "at risk" if evidence indicates the account number was exposed (i.e. accessible to any unauthorized entity, process, source, etc.) during the incident under investigation. The "At-Risk Timeframe" refers to the period of time the account numbers for this breached entity were at risk during the incident under investigation.
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 account numbers stored in the environment; the "at-risk timeframe" would not date back to the oldest account number stored, as the at-risk timeframe only refers to the timeframe itself — the period of time the account numbers were at risk (approximately 60 hours in this scenario) — regardless of how many numbers were exposed or how long they were stored. Details about the data exposed/at risk are covered under section 3.4 of the report, where the PFI describes the possible exposure, the volume of cards at risk, etc. for the affected Payment Brands.
Related
-
What evidence is a TPSP expected to provide to customers to demonstrate PCI DSS compliance?
-
Does PCI SSC consider guidance from other standards organizations when making updates to PCI standards?
-
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?
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
-
What evidence is a TPSP expected to provide to customers to demonstrate PCI DSS compliance?
-
Does PCI SSC consider guidance from other standards organizations when making updates to PCI standards?
-
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?
-
Do PCI DSS requirements for keyed cryptographic hashing apply to previously hashed PANs?
-
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?
Most Recently Updated
-
Where can I find the current version of PCI DSS?
-
Why are there multiple PCI DSS Self-assessment Questionnaires (SAQs)?
-
What is a PCI DSS Self-Assessment Questionnaire?
-
Are Mobile Payments on COTS (MPoC) solutions, Software-based PIN Entry on COTS (SPoC)™ solutions, or Contactless Payments on COTS (CPoC™) solutions eligible for a P2PE Solution approval?
-
How can an entity meet PCI DSS requirements for PAN masking and truncation if it has migrated to 8-digit BINs?