PCI DSS Requirement – 3.1.2.a
Defined Approach Requirements 3.1.2 Roles and responsibilities for performing activities in Requirement 3 are documented, assigned, and understood. Customized Approach...
- Home
- Frameworks and Standards
- PCI DSS
PCI DSS
PCI DSS Requirement – 3.2.1.a
Defined Approach Requirements 3.2.1 Account data storage is kept to a minimum through implementation of data retention and disposal policies,...PCI DSS Requirement – 3.3.1.a
Defined Approach Requirements 3.3.1 SAD is not retained after authorization, even if encrypted. All sensitive authentication data received is rendered...PCI DSS Requirement – 3.3.1.1
Defined Approach Requirements 3.3.1.1 The full contents of any track are not retained upon completion of the authorization process. Customized...PCI DSS Requirement – 3.3.1.2
Defined Approach Requirements 3.3.1.2 The card verification code is not retained upon completion of the authorization process. Customized Approach Objective...PCI DSS Requirement – 2.1.2.a
Defined Approach Requirements 2.1.2 Roles and responsibilities for performing activities in Requirement 2 are documented, assigned, and understood. Customized Approach...PCI DSS Requirement – 3.3.1.3
Defined Approach Requirements 3.3.1.3 The personal identification number (PIN) and the PIN block are not retained upon completion of the...PCI DSS Requirement – 2.2.1.a
Defined Approach Requirements 2.2.1 Configuration standards are developed, implemented, and maintained to: • Cover all system components. • Address all...PCI DSS Requirement – 3.3.2
Defined Approach Requirements 3.3.2 SAD that is stored electronically prior to completion of authorization is encrypted using strong cryptography. Customized...PCI DSS Requirement – 2.2.2.a
Defined Approach Requirements 2.2.2 Vendor default accounts are managed as follows: • If the vendor default account(s) will be used,...