Frequently Asked Question

PCI DSS requirements apply to all system components, unless it has been verified that a 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 will vary according to the function of that system. For example, PCI DSS Requirements 3.5 - 3.7 for the secure storage of cardholder data would not be applicable to systems that do not 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 for those requirements to be considered "not applicable" for that system.

In another example, PCI DSS Requirement 2.3.1 for securing wireless technologies would not apply to a system component that was verified as not having any wireless technology.

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. The assessor would need to verify that the network-level control provides coverage for all systems to which the requirement applies.

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 the 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.