Configuration files for network security controls must be (a) protected against unauthorised access and (b) kept in line with the configurations actually running on the network. Applicability: a configuration file means anything, file or setting, that sets up or synchronises NSCs, including scripts, automated and system-based controls, settings, infrastructure as code and other parameters held in backups, archives or remote storage. Customized approach objective: NSCs cannot be set up or altered using configuration objects, files included, that are not trusted.
This control maps to 38 controls across 15 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 1.2.8 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.