Part of the issue may be that the configuration settings were compliant with the settings specified in the PCI DSS, but only for a point in time. But what happens as soon as the audit is over and changes to computer system configurations take those systems out of compliance? The true intent of the PCI DSS is not for organisations to be compliant at a single point in time, but instead to maintain a compliant state over time, in the face of inevitable change that occurs to in-scope systems.
This white paper, provided by Tripwire, discusses the following:
The high-level goals of the PCI DSS.
The two areas of technical controls the PCI DSS requires-configuration and change process controls.
How Configuration Assessment helps you address the configuration checklist items in the PCI DSS.
How Enhanced File Integrity Monitoring helps you maintain PCI DSS compliance over time in the face of configuration change.