Every security policy and operational procedure required under Requirement 2 (secure configuration of system components) must be written down, kept current, followed in practice, and known to every party it affects. This spans hardening standards, vendor default handling, function isolation and wireless configuration procedures. Applicability: no special notes; applies to every assessed entity. Customized approach objective: affected personnel understand and follow the defined expectations, controls and oversight for Requirement 2 work, and supporting activities are repeatable, consistent and in line with management's intent.
This control maps to 116 controls across 34 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
NIST-CSF-GV.PO-02 Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission
You are reading one control. How much of PCI DSS 4.0 have you already done?
PCI DSS 4.0 2.1.1 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.