7.1 Processes and mechanisms are defined and understood
How to meet it
Document an access control policy.
Defined requirements
The individual PCI DSS v4.0.1 requirements under 7.1, in plain English.
7.1.1All security policies and operational procedures for Requirement 7 are documented, kept current, in use, and known to everyone they affect.
7.1.2Roles and responsibilities for carrying out Requirement 7 activities are documented, assigned, and understood.
Policy templates for this control
Use these starting documents to turn the control into evidence. Adapt each template to your scope, systems, legal obligations and actual operating process.
Access control policyUse for ISO 27001 A.5.15, A.5.16, A.5.17, A.5.18, A.8.2, SOC 2 Security, and PCI DSS requirements 7 and 8.Information security roles and responsibilitiesUse for ISO 27001 A.5.2, A.5.3 and A.5.4, defining security roles, segregation of duties, management responsibilities, and SOC 2 organisational controls.Physical and environmental security policyUse for ISO 27001 A.7.1 to A.7.14, SOC 2 Security, and PCI DSS requirement 9 physical access controls.Information risk management procedureThe clause 6.1.2/6.1.3 and 8.2/8.3 engine: risk identification, analysis scales, evaluation, treatment, acceptance and review.
Open the control-to-policy mapBack to Requirement 7, or see PCI DSS templates. To run PCI controls with automation, read how AI manages controls.