Frequently Asked Question
Do all PCI DSS requirements apply to every system component?
PCI DSS requirements apply to all system components, unless it is has been verified that a particular requirement is not applicable for a particular system. Decisions about the applicability of PCI DSS requirements are not to be based on an entity's perception of the risk of not implementing the requirement. Organizations may not choose which PCI DSS requirements they want to implement, and risk assessments cannot be used as a means of avoiding or bypassing applicable PCI DSS requirements.
The applicability of specific PCI DSS requirements to a particular system may vary according to the function of that particular system. For example, PCI DSS Requirements 3.4 ? 3.6 for the secure storage of cardholder would not be applicable to systems that do not in any way store, or manage the storage of, cardholder data. It would also have to be verified that the system does not have any access to stored cardholder data, cryptographic keys, or the encryption/decryption mechanisms, in order for those requirements to be considered "not applicable" for that system.
In another example, PCI DSS Requirement 2.1.1 for securing wireless technologies would not apply to a system component that was verified as not having any wireless technology. Similarly, PCI DSS Requirements for secure firewall configurations (Requirements 1.1 ? 1.3) apply to those components performing firewall functions.
Some PCI DSS requirements may also be applied at the network level, rather than on every system. For example, requirements for intrusion-detection and/or intrusion-prevention systems to monitor traffic in the CDE may be implemented at the network level rather than on every system in the environment. Again, it would have to be verified by the PCI DSS assessor that the network-level control provided coverage for all systems that the requirement applies to.
Determining that any PCI DSS requirement is not applicable to a system must be verified and supported with documented evidence. Any controls used to reduce applicability of PCI DSS requirements (for example, controls to ensure a system component cannot access cardholder data) must also be verified to be implemented properly and working as intended.
Originally published: June 2013
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
-
How does encrypted cardholder data impact PCI DSS scope for third-party service providers?
-
Does PCI SSC provide a list of PCI DSS-compliant third-party service providers?
-
How does encrypted cardholder data impact PCI DSS scope?
-
What effect does the use of a PCI-listed P2PE solution have on a merchant's PCI DSS validation?
-
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?