Did you know that the Frequently Asked Questions (FAQ) resource on the PCI SSC website is updated regularly to address common questions the PCI SSC receives from stakeholders? This searchable tool includes a library of questions and answers on a variety of topics across PCI Security Standards and programs. In this blog series we highlight some of our most viewed FAQs. Here we look at FAQ 1467 on secure password practices to meet PCI DSS requirement 8.
A: The password requirements in PCI DSS include a minimum level of complexity and strength intended to be met by all types of organizations using a range of technologies. PCI SSC encourages organizations to implement stronger controls or additional security measures as appropriate to meet their security needs.
PCI DSS allows organizations to implement alternative controls than those defined in the standard, as long as the intent of the PCI DSS requirements is met. When considering alternative methods, it is important not to view individual recommendations in isolation but to take all the recommendations as a complete set of controls. For example, when considering the alternative controls described in NIST Special Publication 800-63B, the exclusion of periodic password changes without implementing additional compensating controls would not meet the intent of either the NIST Special Publication or PCI DSS.
Any variation to an authentication method that has been defined in PCI DSS will require that the organization consider how the approach could impact other settings and processes as well as the overall impact to security. Organizations wishing to follow a different combination of password complexity and change frequency than those defined in PCI DSS should document their approach as a compensating control. As part of this process, the organization will need to demonstrate how the risk is mitigated and how the intent of the requirement is met through the implementation of other controls.
PCI SSC continually monitors changes in technologies and payment environments and may incorporate updates in future PCI DSS revisions as needed to support evolving industry best practices.