PCI DSS 4.0 11.5.2: 11.5.2 Change detection on critical files
The entity needs a deployed change-detection tool (file integrity monitoring is one example) that: warns personnel when critical files are modified without authorization, whether by change, addition or deletion; and compares critical files at least once a week. Applicability: critical files are usually those that rarely change but whose alteration could signal a compromise or its risk. Such tools typically ship with critical files for the operating system preconfigured, while other critical files, such as those of custom applications, must be assessed and defined by the entity (the merchant or service provider). Guidance (good practice) gives examples of files to monitor: system executables, application executables, configuration or parameter files, audit logs held centrally or archived, and other files the entity judges critical. Objective under the customized approach: unauthorized personnel cannot alter critical files without an alert being raised.
This control maps to 64 controls across 21 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
You are reading one control. How much of PCI DSS 4.0 have you already done?
PCI DSS 4.0 11.5.2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 415 were rejected on the ISO 27001:2022 pair alone.