PCI DSS 2.0 Requirement Mapping Tool Use our interactive tool to select your specific PCI DSS requirements and print a custom report showing the McAfee solutions that suit your needs. Click here for more help.							McAfee Solutions
		Requirement 1: Install and maintain a firewall configuration to protect cardholder data
			1.1 Establish firewall and router configuration standards that include the following:			6
				1.1.1 A formal process for approving and testing all network connections and changes to the firewall and router configurations		6
				1.1.2 Current network diagram with all connections to cardholder data, including any wireless networks		1
				1.1.3 Requirements for a firewall at each Internet connection and between any demilitarized zone (DMZ) and the internal network zone		2
				1.1.4 Description of groups, roles and responsibilities for logical management of network components		6
				1.1.5 Documentation and business justification for use of all services, protocols, and ports allowed, including documentation of security features implemented for those protocols considered to be insecure. Examples of insecure services, protocols, or ports include but are not limited to FTP, Telnet, POP3, IMAP, and SNMP.		2
				1.1.6 Requirement to review firewall and router rule sets at least every six months		6
			1.2 Build firewall and router configurations that restrict connections between untrusted networks and any system components in the cardholder data environment. Note: An "untrusted network" is any network that is external to the networks belonging to the entity under review, and/or which is out of the entity's ability to control or manage.			2
				1.2.1 Restrict inbound and outbound traffic to that which is necessary for the cardholder data environment.		2
				1.2.2 Secure and synchronize router configuration files.		2
				1.2.3 Install perimeter firewalls between any wireless networks and the cardholder data environment, and configure these firewalls to deny or control (if such traffic is necessary for business purposes) any traffic from the wireless environment into the cardholder data environment.		2
			1.3 Prohibit direct public access between the Internet and any system component in the cardholder data environment.			2
				1.3.1 Implement a DMZ to limit inbound traffic to only system components that provide authorized publicly accessible services, protocols, and ports.		2
				1.3.2 Limit inbound Internet traffic to IP addresses within the DMZ.		2
				1.3.3 Do not allow any direct connections inbound or outbound for traffic between the Internet and the cardholder data environment.		2
				1.3.4 Do not allow internal addresses to pass from the Internet into the DMZ.		2
				1.3.5 Do not allow unauthorized outbound traffic from the cardholder data environment to the Internet.		2
				1.3.6 Implement stateful inspection, also known as dynamic packet filtering. (That is, only ”established” connections are allowed into the network.)		2
				1.3.7 Place system components that store cardholder data (such as a database) in an internal network zone, segregated from the DMZ and other untrusted networks.		2
				1.3.8 Do not disclose private IP addresses and routing information to unauthorized parties. Note: Methods to obscure IP addressing may include, but are not limited to: 1) Network Address Translation (NAT), 2) Placing servers containing cardholder data behind proxy servers/firewalls or content caches, 3) Removal or filtering of route advertisements for private networks that employ registered addressing, 4) Internal use of RFC1918 address space instead of registered addresses.		2
			1.4 Install personal firewall software on any mobile and/or employee-owned computers with direct connectivity to the Internet (for example, laptops used by employees), which are used to access the organization’s network.			2
		Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters
			2.1 Always change vendor-supplied defaults before installing a system on the network, including but not limited to passwords, simple network management protocol (SNMP) community strings, and elimination of unnecessary accounts.			2
				2.1.1 For wireless environments connected to the cardholder data environment or transmitting cardholder data, change wireless vendor defaults, including but not limited to default wireless encryption keys, passwords, and SNMP community strings.		2
			2.2 Develop configuration standards for all system components. Assure that these standards address all known security vulnerabilities and are consistent with industry-accepted system hardening standards. Sources of industry-accepted system hardening standards may include, but are not limited to: 1) Center for Internet Security (CIS), 2) International Organization for Standardization (ISO), 3) SysAdmin Audit Network Security (SANS) Institute, 4) National Institute of Standards Technology (NIST)			3
				2.2.1 Implement only one primary function per server to prevent functions that require different security levels from co-existing on the same server. (For example, web servers, database servers, and DNS should be implemented on separate servers.)		3
				2.2.2 Enable only necessary and secure services, protocols, daemons, etc., as required for the function of the system. Implement security features for any required services, protocols or daemons that are considered to be insecure-for example, use secured technologies such as SSH, S-FTP, SSL, or IPSec VPN to protect insecure services such as NetBIOS, file-sharing, Telnet, FTP, etc.		3
				2.2.3 Configure system security parameters to prevent misuse.		3
				2.2.4 Remove all unnecessary functionality, such as scripts, drivers, features, subsystems, file systems, and unnecessary web servers.		3
			2.3 Encrypt all non-console administrative access using strong cryptography. Use technologies such as SSH, VPN, or SSL/TLS for web-based management and other non-console administrative access.			2
			2.4 Shared hosting providers must protect each entity’s hosted environment and cardholder data. These providers must meet specific requirements as detailed in Appendix A: Additional PCI DSS Requirements for Shared Hosting Providers.			3
		Requirement 3: Protect stored cardholder data
			3.1 Keep cardholder data storage to a minimum by implementing data retention and disposal policies, procedures and processes, as follows.			1
				3.1.1 Implement a data retention and disposal policy that includes: 1) Limiting data storage amount and retention time to that which is required for legal, regulatory, and business requirements, 2) Processes for secure deletion of data when no longer needed, 3) Specific retention requirements for cardholder data, 4) A quarterly automatic or manual process for identifying and securely deleting stored cardholder data that exceeds defined retention requirements		1
			3.2 Do not store sensitive authentication data after authorization (even if encrypted). Sensitive authentication data includes the data as cited in the following Requirements 3.2.1 through 3.2.3.			1
				3.2.1 Do not store the full contents of any track (from the magnetic stripe located on the back of a card, equivalent data contained on a chip, or elsewhere). This data is alternatively called full track, track, track 1, track 2, and magnetic-stripe data.		1
				3.2.2 Do not store the card-verification code or value (three-digit or four-digit number printed on the front or back of a payment card) used to verify card-not-present transactions.		1
				3.2.3 Do not store the personal identification number (PIN) or the encrypted PIN block.		1
			3.3 Mask PAN when displayed (the first six and last four digits are the maximum number of digits to be displayed).			5
			3.4 Render PAN unreadable anywhere it is stored (including on portable digital media, backup media, and in logs) by using any of the following approaches: 1) One-way hashes based on strong cryptography (hash must be of the entire PAN), 2) Truncation (hashing cannot be used to replace the truncated segment of PAN), 3) Index tokens and pads (pads must be securely stored), 4) Strong cryptography with associated key-management processes and procedures			5
				3.4.1 If disk encryption is used (rather than file- or column-level database encryption), logical access must be managed independently of native operating system access control mechanisms (for example, by not using local system or Active Directory accounts). Decryption keys must not be tied to user accounts.		5
			3.5 Protect any keys used to secure cardholder data against disclosure and misuse:			5
				3.5.1 Restrict access to cryptographic keys to the fewest number of custodians necessary.		5
				3.5.2 Store cryptographic keys securely in the fewest possible locations and forms.		5
			3.6. Fully document and implement all key-management processes and procedures for cryptographic keys used for encryption of cardholder data, including the following:			5
				3.6.1 Generation of strong cryptographic keys		5
				3.6.2 Secure cryptographic key distribution		5
				3.6.3 Secure cryptographic key storage		5
				3.6.4 Cryptographic key changes for keys that have reached the end of their crypto period (for example, after a defined period of time has passed and/or after a certain amount of cipher-text has been produced by a given key), as defined by the associated application vendor or key owner, and based on industry best practices and guidelines (for example, NIST Special Publication 800-57).		5
				3.6.5 Retirement or replacement (for example, archiving, destruction, and/or revocation) of keys as deemed necessary when the integrity of the key has been weakened (for example, departure of an employee with knowledge of a clear-text key), or keys are suspected of being compromised.		5
				3.6.6 If manual clear-text cryptographic key management operations are used, these operations must be managed using split knowledge and dual control (for example, requiring two or three people, each knowing only their own key component, to reconstruct the whole key).		5
				3.6.7 Prevention of unauthorized substitution of cryptographic keys.		5
				3.6.8 Requirement for cryptographic key custodians to formally acknowledge that they understand and accept their key-custodian responsibilities.		5
		Requirement 4: Encrypt transmission of cardholder data across open, public networks
			4.1 Use strong cryptography and security protocols (for example, SSL/TLS, IPSEC, SSH, etc.) to safeguard sensitive cardholder data during transmission over open, public networks. Examples of open, public networks that are in scope of the PCI DSS include but are not limited to: 1) The Internet, 2) Wireless technologies, 3) Global System for Mobile communications (GSM), 4) General Packet Radio Service (GPRS).			2
				4.1.1 Ensure wireless networks transmitting cardholder data or connected to the cardholder data environment, use industry best practices (for example, IEEE 802.11i) to implement strong encryption for authentication and transmission.		2
			4.2 Never send unprotected PANs by end-user messaging technologies (for example, e-mail, instant messaging, chat, etc.).			2
		Requirement 5: Use and regularly update anti-virus software or programs
			5.1 Deploy anti-virus software on all systems commonly affected by malicious software (particularly personal computers and servers).			2
				5.1.1 Ensure that all anti-virus programs are capable of detecting, removing, and protecting against all known types of malicious software.		2
			5.2 Ensure that all anti-virus mechanisms are current, actively running, and generating audit logs.			2
		Requirement 6: Develop and maintain secure systems and applications
			6.1 Ensure that all system components and software are protected from known vulnerabilities by having the latest vendor-supplied security patches installed. Install critical security patches within one month of release.			3
			6.2 Establish a process to identify and assign a risk ranking to newly discovered security vulnerabilities.			3
			6.3 Develop software applications (internal and external, and including web-based administrative access to applications) in accordance with PCI DSS (for example, secure authentication and logging), and based on industry best practices. Incorporate information security throughout the software development life cycle. These processes must include the following:			3
				6.3.1 Removal of custom application accounts, usernames, and passwords before applications become active or are released to customers		3
				6.3.2 Review of custom code prior to release to production or customer in order to identify any potential coding vulnerability.		3
			6.4. Follow change control processes and procedures for all changes to system components. The processes must include the following:			6
				6.4.1 Separate development/test and production environments		3
				6.4.2 Separation of duties between development/test and production environments		3
				6.4.3 Production data (live PANs) are not used for testing or development		3
				6.4.4 Removal of test data and accounts before production systems become active		3
				6.4.5 Change control procedures for the implementation of security patches and software modifications. Procedures must include the following: 6.4.5.1 Documentation of impact, 6.4.5.2 Documented change approval by authorized parties, 6.4.5.3 Functionality testing to verify that the change does not adversely impact the security of the system, 6.4.5.4 Back-out procedures		6
			6.5 Develop applications based on secure coding guidelines. Prevent common coding vulnerabilities in software development processes, to include the following:			3
				6.5.1 Injection flaws, particularly SQL injection. Also consider LDAP and Xpath injection flaws as well as other injection flaws.		3
				6.5.2 Buffer overflow		3
				6.5.3 Insecure cryptographic storage		3
				6.5.4 Insecure communications		3
				6.5.5 Improper error handling		3
				6.5.6 All "High" vulnerabilities identified in the vulnerability identification process (as defined in PCI DSS Requirement 6.2).		3
				6.5.7 Cross-site scripting (XSS)		3
				6.5.8 Improper Access Control (such as insecure direct object references, failure to restrict URL access, and directory traversal)		3
				6.5.9 Cross-site request forgery (CSRF)		3
			6.6 For public-facing web applications, address new threats and vulnerabilities on an ongoing basis and ensure these applications are protected against known attacks by either of the following methods: 1) Reviewing public-facing web applications via manual or automated application vulnerability security assessment tools or methods, at least annually and after any changes, 2) Installing a web-application firewall in front of public-facing web applications			3
		Requirement 7: Restrict access to cardholder data by business need-to-know
			7.1 Limit access to system components and cardholder data to only those individuals whose job requires such access. Access limitations must include the following:			4
				7.1.1 Restriction of access rights to privileged user IDs to least privileges necessary to perform job responsibilities		4
				7.1.2 Assignment of privileges is based on individual personnel’s job classification and function		4
				7.1.3 Requirement for a documented approval by authorized parties specifying required privileges.		4
				7.1.4 Implementation of an automated access control system		4
			7.2 Establish an access control system for systems components with multiple users that restricts access based on a user’s need to know, and is set to “deny all” unless specifically allowed. This access control system must include the following:			4
				7.2.1 Coverage of all system components		4
				7.2.2 Assignment of privileges to individuals based on job classification and function		4
				7.2.3 Default “deny-all” setting		4
		Requirement 8: Assign a unique ID to each person with computer access
			8.1 Identify all users with a unique user name before allowing them to access system components or cardholder data.			4
			8.2 In addition to assigning a unique ID, employ at least one of the following methods to authenticate all users: 1) Something you know, such as a password or passphrase, 2) Something you have, such as a token device or smart card, 3) Something you are, such as a biometric			4
			8.3 Incorporate two-factor authentication for remote access (network-level access originating from outside the network) to the network by employees, administrators, and third parties. (For example, remote authentication and dial-in service (RADIUS) with tokens; terminal access controller access control system (TACACS) with tokens; or other technologies that facilitate two-factor authentication.)			4
			8.4 Encrypt all passwords during transmission and storage on all system components.			4
			8.5 Ensure proper user identification and authentication management for non-consumer users and administrators on all system components as follows:			4
				8.5.1 Control addition, deletion, and modification of user IDs, credentials, and other identifier objects.		4
				8.5.2 Verify user identity before performing password resets.		4
				8.5.3 Set passwords for first-time use and resets to a unique value for each user and change immediately after the first use.		4
				8.5.4 Immediately revoke access for any terminated users.		4
				8.5.5 Remove/disable inactive user accounts at least every 90 days.		4
				8.5.6 Enable accounts used by vendors for remote access only during the time period needed. Monitor vendor remote access accounts when in use.		4
				8.5.7 Communicate authentication procedures and policies to all users who have access to cardholder data.		4
				8.5.8 Do not use group, shared, or generic accounts and passwords, or other authentication methods.		4
				8.5.9 Change user passwords at least every 90 days.		4
				8.5.10 Require a minimum password length of at least seven characters.		4
				8.5.11 Use passwords containing both numeric and alphabetic characters.		4
				8.5.12 Do not allow an individual to submit a new password that is the same as any of the last four passwords he or she has used.		4
				8.5.13 Limit repeated access attempts by locking out the user ID after not more than six attempts.		4
				8.5.14 Set the lockout duration to a minimum of 30 minutes or until administrator enables the user ID.		4
				8.5.15 If a session has been idle for more than 15 minutes, require the user to re-authenticate to re-activate the terminal or session.		4
				8.5.16 Authenticate all access to any database containing cardholder data. This includes access by applications, administrators, and all other users. Restrict user direct access or queries to databases to database administrators.		4
		Requirement 9: Restrict physical access to cardholder data
			9.1 Use appropriate facility entry controls to limit and monitor physical access to systems in the cardholder data environment.			2
				9.1.1 Use video cameras and/or access control mechanisms to monitor individual physical access to sensitive areas. Review collected data and correlate with other entries. Store for at least three months, unless otherwise restricted by law.		2
				9.1.2 Restrict physical access to publicly accessible network jacks.		2
				9.1.3 Restrict physical access to wireless access points, gateways, handheld devices, networking/communications hardware, and telecommunication lines.		2
			9.2 Develop procedures to easily distinguish between onsite personnel and visitors, especially in areas where cardholder data is accessible.			5
			9.3 Make sure all visitors are handled as follows:			5
				9.3.1 Authorized before entering areas where cardholder data is processed or maintained.		5
				9.3.2 Given a physical token (for example, a badge or access device) that expires and that identifies the visitors as not onsite personnel.		5
				9.3.3 Asked to surrender the physical token before leaving the facility or at the date of expiration.		5
			9.4 Use a visitor log to maintain a physical audit trail of visitor activity. Document the visitor’s name, the firm represented, and the onsite personnel authorizing physical access on the log. Retain this log for a minimum of three months, unless otherwise restricted by law.			5
			9.5 Store media back-ups in a secure location, preferably an off-site facility, such as an alternate or back-up site, or a commercial storage facility. Review the location’s security at least annually.			5
			9.6 Physically secure all media.			5
			9.7 Maintain strict control over the internal or external distribution of any kind of media, including the following:			5
				9.7.1 Classify media so the sensitivity of the data can be determined.		5
				9.7.2 Send the media by secured courier or other delivery method that can be accurately tracked.		5
			9.8 Ensure management approves any and all media that is moved from a secured area (especially when media is distributed to individuals).			5
			9.9 Maintain strict control over the storage and accessibility of media.			5
				9.9.1 Properly maintain inventory logs of all media and conduct media inventories at least annually.		5
			9.10 Destroy media when it is no longer needed for business or legal reasons as follows:			1
				9.10.1 Shred, incinerate, or pulp hardcopy materials so that cardholder data cannot be reconstructed.		1
				9.10.2 Render cardholder data on electronic media unrecoverable so that cardholder data cannot be reconstructed.		1
		Requirement 10: Track and monitor all access to network resources and cardholder data
			10.1 Establish a process for linking all access to system components (especially access done with administrative privileges such as root) to each individual user.			4
			10.2 Implement automated audit trails for all system components to reconstruct the following events:			4
				10.2.1 All individual accesses to cardholder data		4
				10.2.2 All actions taken by any individual with root or administrative privileges		4
				10.2.3 Access to all audit trails		4
				10.2.4 Invalid logical access attempts		4
				10.2 5 Use of identification authentication mechanisms		4
				10.2.6 Initialization of the audit logs		4
				10.2.7 Creation and deletion of system-level objects		4
			10.3 Record at least the following audit trail entries for all system components for each event:			4
				10.3.1 User identification		4
				10.3.2 Type of event		4
				10.3.3 Date and time		4
				10.3.4 Success or failure indication		4
				10.3.5 Origination of event		4
				10.3.6 Identity or name of affected data, system component or resource.		4
			10.4 Using time-synchronization technology, synchronize all critical system clocks and times and ensure that the following is implemented for acquiring, distributing, and storing time.			4
				10.4.1 Critical systems have the correct and consistent time.		4
				10.4.2 Time data is protected.		4
				10.4.3 Time settings are received from industry-accepted time sources.		4
			10.5 Secure audit trails so they cannot be altered.			4
				10.5.1 Limit viewing of audit trails to those with a job-related need.		4
				10.5.2 Protect audit trail files from unauthorized modifications.		4
				10.5.3 Promptly back up audit trail files to a centralized log server or media that is difficult to alter.		4
				10.5.4 Write logs for external-facing technologies onto a log server on the internal LAN.		4
				10.5.5 Use file-integrity monitoring or change-detection software on logs to ensure that existing log data cannot be changed without generating alerts (although new data being added should not cause an alert).		4
			10.6 Review logs for all system components at least daily. Log reviews must include those servers that perform security functions like intrusion-detection system (IDS) and authentication, authorization, and accounting protocol (AAA) servers (for example, RADIUS).			4
			10.7 Retain audit trail history for at least one year, with a minimum of three months immediately available for analysis (for example, online, archived, or restorable from back-up).			4
		Requirement 11: Regularly test security systems and processes
			11.1 Test for the presence of wireless access points and detect unauthorized wireless access points on a quarterly basis.			4
			11.2 Run internal and external network vulnerability scans at least quarterly and after any significant change in the network (such as new system component installations, changes in network topology, firewall rule modifications, product upgrades).			2
				11.2.1 Perform quarterly internal vulnerability scans.		2
				11.2.2 Perform quarterly external vulnerability scans via an Approved Scanning Vendor (ASV), approved by the Payment Card Industry Security Standards Council (PCI SSC).		2
				11.2.3 Perform internal and external scans after any significant change.		2
			11.3 Perform external and internal penetration testing at least once a year and after any significant infrastructure or application upgrade or modification (such as an operating system upgrade, a sub-network added to the environment, or a web server added to the environment). These penetration tests must include the following:			2
				11.3.1 Network-layer penetration tests		2
				11.3.2 Application-layer penetration tests		2
			11.4 Use intrusion-detection systems, and/or intrusion-prevention systems to monitor all traffic at the perimeter of the cardholder data environment as well as at critical points inside of the cardholder data environment, and alert personnel to suspected compromises.Keep all intrusion-detection and prevention engines, baselines, and signatures up-to-date.			2
			11.5 Deploy file-integrity monitoring tools to alert personnel to unauthorized modification of critical system files, configuration files, or content files; and configure the software to perform critical file comparisons at least weekly.			4
		Requirement 12: Maintain a policy that addresses information security for all personnel.
			12.1 Establish, publish, maintain, and disseminate a security policy that accomplishes the following:			6
				12.1.1 Addresses all PCI DSS requirements.		6
				12.1.2 Includes an annual process that identifies threats, and vulnerabilities, and results in a formal risk assessment.		1
				12.1.3 Includes a review at least annually and updates when the environment changes.		6
			12.2 Develop daily operational security procedures that are consistent with requirements in this specification (for example, user account maintenance procedures, and log review procedures).			6
			12.3 Develop usage policies for critical technologies (for example, remote-access technologies, wireless technologies, removable electronic media, laptops, tablets, personal data/digital assistants (PDAs), e-mail usage and Internet usage) and define proper use of these technologies. Ensure these usage policies require the following:			6
				12.3.1 Explicit approval by authorized parties		6
				12.3.2 Authentication for use of the technology		6
				12.3.3 A list of all personnel and devices with such access		6
				12.3.4 Labeling of devices to determine owner, contact information and purpose		6
				12.3.5 Acceptable uses of the technology		6
				12.3.6 Acceptable network locations for the technologies		6
				12.3.7 List of company-approved products		6
				12.3.8 Automatic disconnect of sessions for remote-access technologies after a specific period of inactivity		6
				12.3.9 Activation of remote-access technologies for vendors and business partners only when needed by vendors and business partners, with immediate deactivation after use		6
				12.3.10 For personnel accessing cardholder data via remote-access technologies, prohibit copy, move, and storage of cardholder data onto local hard drives and removable electronic media, unless explicitly authorized for a defined business need.		6
			12.4 Ensure that the security policy and procedures clearly define information security responsibilities for all personnel.			6
			12.5 Assign to an individual or team the following information security management responsibilities:			6
				12.5.1 Establish, document, and distribute security policies and procedures.		6
				12.5.2 Monitor and analyze security alerts and information, and distribute to appropriate personnel.		6
				12.5.3 Establish, document, and distribute security incident response and escalation procedures to ensure timely and effective handling of all situations.		4
				12.5.4 Administer user accounts, including additions, deletions, and modifications		6
				12.5.5 Monitor and control all access to data.		6
			12.6 Implement a formal security awareness program to make all personnel aware of the importance of cardholder data security.			6
				12.6.1 Educate personnel upon hire and at least annually.		6
				12.6.2 Require personnel to acknowledge at least annually that they have read and understood the security policy and procedures.		6
			12.7 Screen potential personnel prior to hire to minimize the risk of attacks from internal sources. (Examples of background checks include previous employment history, criminal record, credit history, and reference checks.)			6
			12.8 If cardholder data is shared with service providers, maintain and implement policies and procedures to manage service providers, to include the following:			2
				12.8.1 Maintain a list of service providers.		2
				12.8.2 Maintain a written agreement that includes an acknowledgement that the service providers are responsible for the security of cardholder data the service providers possess.		2
				12.8.3 Ensure there is an established process for engaging service providers including proper due diligence prior to engagement.		2
				12.8.4 Maintain a program to monitor service providers’ PCI DSS compliance status at least annually.		2
			12.9 Implement an incident response plan. Be prepared to respond immediately to a system breach.			4
				12.9.1 Create the incident response plan to be implemented in the event of system breach. Ensure the plan addresses the following, at a minimum: 1) Roles, responsibilities, and communication and contact strategies in the event of a compromise including notification of the payment brands, at a minimum, 2) Specific incident response procedures, 3) Business recovery and continuity procedures, 4) Data back-up processes, 5) Analysis of legal requirements for reporting compromises, 6) Coverage and responses of all critical system components, 7) Reference or inclusion of incident response procedures from the payment brands		4
				12.9.2 Test the plan at least annually.		4
				12.9.3 Designate specific personnel to be available on a 24/7 basis to respond to alerts.		4
				12.9.4 Provide appropriate training to staff with security breach response responsibilities.		4
				12.9.5 Include alerts from intrusion-detection, intrusion-prevention, and file-integrity monitoring systems.		4
				12.9.6 Develop a process to modify and evolve the incident response plan according to lessons learned and to incorporate industry developments.		4
		Requirement A.1: Shared hosting providers must protect the cardholder data environment
			A.1 Protect each entity’s (that is merchant, service provider, or other entity) hosted environment and data, per A.1.1 through A.1.4: A hosting provider must fulfill these requirements as well as all other relevant sections of the PCI DSS.			3
				A.1.1 Ensure that each entity only runs processes that have access to that entity's cardholder data environment.		3
				A.1.2 Restrict each entity’s access and privileges to its own cardholder data environment only.		3
				A.1.3 Ensure logging and audit trails are enabled and unique to each entity’s cardholder data environment and consistent with PCI DSS Requirement 10.		3
				A.1.4 Enable processes to provide for timely forensic investigation in the event of a compromise to any hosted merchant or service provider.		3
McAfee and/or additional marks herein are registered trademarks or trademarks of McAfee, Inc. and/or its affiliates in the US and/or other countries. McAfee Red in connection with security is distinctive of McAfee brand products. All other registered and unregistered trademarks herein are the sole property of their respective owners. (c) 2011 McAfee, Inc. All rights reserved.