Every security policy and operational procedure called for in Requirement 8 must be documented, kept up to date, in active use, and communicated to everyone affected. In this requirement set these cover user identification, account lifecycle, authentication factors, password rules, MFA and management of application and system accounts. The guidance adds that documents are best revised as processes, technologies and business objectives change, not only on a set schedule. Objective under the customized approach: expectations, controls and oversight for Requirement 8 activities are defined and followed by the relevant staff, and supporting activities are repeatable, consistent and in line with management intent.
This control maps to 44 controls across 17 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 8.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.