PCI DSS and the Seven Domains
PCI DSS and the Seven Domains
1. Identify the touch points between the objectives and requirements of PCI DSS and YieldMore’s IT environment.
The objectives and requirements for PCI DSS compliance is the same for every business wanting to accept credit card payments. There are 6 control objectives with 12 requirements.
Control Objectives
PCI DSS Requirements
1. Build and Maintain a Secure Network
1. Install and maintain a firewall configuration to protect cardholder data
2. Do not use vendor-supplied defaults for system passwords and other security parameters
2. Protect Cardholder Data
3. Protect stored cardholder data
4. Encrypt transmission of cardholder data across open, public networks
3. Maintain a Vulnerability Management Program
5. Use and regularly update anti-virus software on all systems commonly affected by malware
6. Develop and maintain secure systems and applications
4. Implement Strong Access Control Measures
7. Restrict access to cardholder data by business need-to-know
8. Assign a unique ID to each person with computer access
9. Restrict physical access to cardholder data
5. Regularly Monitor and Test Networks
10. Track and monitor all access to network resources and cardholder data
11. Regularly test security systems and processes
6. Maintain an Information Security Policy
12. Maintain a policy that addresses information security
2. Determine appropriate best practices to implement when taking steps to meet PCI DSS objectives and requirements.
The best way to implement best practices is following the requirements. Some of the requirements listed above read like a guideline i.e. not using vendor supplied default passwords. Obviously you would want to make your own strong password that would be difficult to guess.
3. Justify your reasoning for each identified best practice.
The justification for best practice is you want to make the credit card information as secured as possible. The company will be handling the income of people and if
1. Identify the touch points between the objectives and requirements of PCI DSS and YieldMore’s IT environment.
The objectives and requirements for PCI DSS compliance is the same for every business wanting to accept credit card payments. There are 6 control objectives with 12 requirements.
Control Objectives
PCI DSS Requirements
1. Build and Maintain a Secure Network
1. Install and maintain a firewall configuration to protect cardholder data
2. Do not use vendor-supplied defaults for system passwords and other security parameters
2. Protect Cardholder Data
3. Protect stored cardholder data
4. Encrypt transmission of cardholder data across open, public networks
3. Maintain a Vulnerability Management Program
5. Use and regularly update anti-virus software on all systems commonly affected by malware
6. Develop and maintain secure systems and applications
4. Implement Strong Access Control Measures
7. Restrict access to cardholder data by business need-to-know
8. Assign a unique ID to each person with computer access
9. Restrict physical access to cardholder data
5. Regularly Monitor and Test Networks
10. Track and monitor all access to network resources and cardholder data
11. Regularly test security systems and processes
6. Maintain an Information Security Policy
12. Maintain a policy that addresses information security
2. Determine appropriate best practices to implement when taking steps to meet PCI DSS objectives and requirements.
The best way to implement best practices is following the requirements. Some of the requirements listed above read like a guideline i.e. not using vendor supplied default passwords. Obviously you would want to make your own strong password that would be difficult to guess.
3. Justify your reasoning for each identified best practice.
The justification for best practice is you want to make the credit card information as secured as possible. The company will be handling the income of people and if