Deploy a change-detection mechanism to alert unauthorized modification of critical files, with weekly comparisons.

Deploy a change-detection mechanism to alert unauthorized modification of critical files, with weekly comparisons.

• A. Do Not Deploy
• B. Deploy With Monthly Checks
• C. Deploy And Perform Weekly Comparisons
• D. Deploy But Never Compare

Answer: (C)

A change-detection mechanism that alerts you to unauthorized modifications keeps critical files under continuous watch and turns any tampering into a detectable event. Pairing that with weekly comparisons provides a regular, verifiable cadence to confirm file integrity: you detect and alert on changes as they happen, and you routinely verify that nothing unexpected has changed since the last check. This directly aligns with PCI DSS practice, which requires deploying a mechanism to monitor and alert on unauthorized modification of critical files and to review changes on a regular basis. Skipping deployment leaves you blind to alterations; delaying checks to monthly creates a longer window for tampering to go unnoticed; deploying without any comparison activity fails to produce timely alerts or confirmations.

A change-detection mechanism that alerts you to unauthorized modifications keeps critical files under continuous watch and turns any tampering into a detectable event. Pairing that with weekly comparisons provides a regular, verifiable cadence to confirm file integrity: you detect and alert on changes as they happen, and you routinely verify that nothing unexpected has changed since the last check. This directly aligns with PCI DSS practice, which requires deploying a mechanism to monitor and alert on unauthorized modification of critical files and to review changes on a regular basis. Skipping deployment leaves you blind to alterations; delaying checks to monthly creates a longer window for tampering to go unnoticed; deploying without any comparison activity fails to produce timely alerts or confirmations.