{
    "catalog": {
        "version": "1.0.0",
        "uuid": "b6e5a99e-fa61-48a2-aa1b-7cb7bfbdc3fd",
        "title": "Payment Card Industry Data Security Standard (PCI DSS) Version 3.2.1",
        "description": "The Payment Card Industry Data Security Standard (PCI DSS) was developed to encourage and enhance payment card account data security and facilitate the broad adoption of consistent data security measures globally. PCI DSS provides a baseline of technical and operational requirements designed to protect account data. While specifically designed to focus on environments with payment card account data, PCI DSS can also be used to protect against threats and secure other elements in the payment ecosystem.",
        "datePublished": "2008-10-01T00:00:00",
        "lastRevisionDate": "2025-12-16",
        "url": "https://www.pcisecuritystandards.org/",
        "abstract": "Principal PCI DSS Requirements PCI Data Security Standard - High Level Overview Build and Maintain a Secure Network and Systems. 1. Install and Maintain Network Security Controls. 2. Apply Secure Configurations to All System Components. Protect Account Data. 3. Protect Stored Account Data. 4. Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Maintain a Vulnerability Management Program. 5. Protect All Systems and Networks from Malicious Software. 6. Develop and Maintain Secure Systems and Software. Implement Strong Access Control Measures. 7. Restrict Access to System Components and Cardholder Data by Business Need to Know. 8. Identify Users and Authenticate Access to System Components. 9. Restrict Physical Access to Cardholder Data. Regularly Monitor and Test Networks. 10. Log and Monitor All Access to System Components and Cardholder Data. 11. Test Security of Systems and Networks Regularly. Maintain an Information Security Policy. 12. Support Information Security with Organizational Policies and Programs.",
        "keywords": "PCI DSS; PCI; Payment Card Industry; Data Security; Payment Card Data; Credit Card Data; Cardholder Data; Sensitive Authentication Data (SAD); Financial Institutions; Financial Services Companies; Financial Firms and Third-Party Providers; cybersecurity; information security; information system; integrity; personally identifiable information; privacy controls; privacy functions; privacy requirements; Risk Management Framework; security controls; security functions; security requirements; system; system security",
        "master": false,
        "regulationDatePublished": "2018-05-31",
        "defaultName": "pci-dss-321",
        "downloadURL": "https://regscaleblob.blob.core.windows.net/catalogs/pci-dss-321.json",
        "securityControls": [
            {
                "uuid": "2b30f5c2-3afa-4f00-a6bc-84446e19611a",
                "controlId": "1.1",
                "title": "1.1",
                "description": "1.1 Establish and implement firewall and router configuration standards that include the following:",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": " ",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "b601e5c7-3a37-44ef-b5f3-96e769b02204",
                "controlId": "1.1.1",
                "title": "1.1.1",
                "description": "1.1.1 A formal process for approving and testing all network connections and changes to the firewall and router configurations",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "cb7ce187-1e2d-4b2b-95fa-c2b30ffdc282",
                "controlId": "1.1.2",
                "title": "1.1.2",
                "description": "1.1.2 Current network diagram that identifies all connections between the cardholder data environment and other networks, including any wireless networks",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 1 Remove sensitive authentication data and limit data retention. This milestone targets a key area of risk for entities that have been compromised. Remember \u2013 if sensitive authentication data and other cardholder data are not stored, the effects of a compromise will be greatly reduced. If you don't need it, don't store it",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "84b587d8-6e53-4fad-8c5d-303435c46491",
                "controlId": "1.1.3",
                "title": "1.1.3",
                "description": "1.1.3 Current diagram that shows all cardholder data flows across systems and networks ",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 1 Remove sensitive authentication data and limit data retention. This milestone targets a key area of risk for entities that have been compromised. Remember \u2013 if sensitive authentication data and other cardholder data are not stored, the effects of a compromise will be greatly reduced. If you don't need it, don't store it",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "e9952f54-021e-49e0-a0f7-4868d7992377",
                "controlId": "1.1.4",
                "title": "1.1.4",
                "description": "1.1.4 Requirements for a firewall at each Internet connection and between any demilitarized zone (DMZ) and the internal network zone",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "c44509c6-0b09-48d6-97b2-59abb406d8eb",
                "controlId": "1.1.5",
                "title": "1.1.5",
                "description": "1.1.5 Description of groups, roles, and responsibilities for management of network components",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "0a5aefec-6398-4e6d-95d0-6d6deb8b1f04",
                "controlId": "1.1.6",
                "title": "1.1.6",
                "description": "1.1.6 Documentation of business justification and approval for use of all services, protocols, and ports allowed, including documentation of security features implemented for those protocols considered to be insecure.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "579b986b-a1c8-4e2a-842c-34aa5c86be12",
                "controlId": "1.1.7",
                "title": "1.1.7",
                "description": "1.1.7 Requirement to review firewall and router rule sets at least every six months",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "33ea7aba-590e-455f-9bbe-0f65b935d0f8",
                "controlId": "1.2",
                "title": "1.2",
                "description": "1.2 Build firewall and router configurations that restrict connections between untrusted networks and any system components in the cardholder data environment.\r\n\r\nNote: An \u201cuntrusted network\u201d 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.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": " ",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "060162d1-7fcf-4e84-a18f-8d74eb62d949",
                "controlId": "1.2.1",
                "title": "1.2.1",
                "description": "1.2.1 Restrict inbound and outbound traffic to that which is necessary for the cardholder data environment, and specifically deny all other traffic.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "3e639d38-1017-41f2-a76f-4ec2a2e55c74",
                "controlId": "1.2.2",
                "title": "1.2.2",
                "description": "1.2.2 Secure and synchronize router configuration files.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "c70fd1bc-2383-4ebc-9484-3afe7fedc197",
                "controlId": "1.2.3",
                "title": "1.2.3",
                "description": "1.2.3 Install perimeter firewalls between all wireless networks and the cardholder data environment, and configure these firewalls to deny or, if traffic is necessary for business purposes, permit only authorized traffic between the wireless environment and the cardholder data environment.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "ca6a1b21-62b3-4728-a93b-894f10240b07",
                "controlId": "1.3",
                "title": "1.3",
                "description": "1.3 Prohibit direct public access between the Internet and any system component in the cardholder data environment.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": " ",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "6fdd2f2f-f9de-46a3-a7ed-9f599091ae22",
                "controlId": "1.3.1",
                "title": "1.3.1",
                "description": "1.3.1 Implement a DMZ to limit inbound traffic to only system components that provide authorized publicly accessible services, protocols, and ports.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "cd6c9497-693d-4ed6-902a-a4b727115c98",
                "controlId": "1.3.2",
                "title": "1.3.2",
                "description": "1.3.2 Limit inbound Internet traffic to IP addresses within the DMZ.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "8b03c6c3-f7f9-4166-9871-54d78a1035a0",
                "controlId": "1.3.3",
                "title": "1.3.3",
                "description": "1.3.3 Implement anti-spoofing measures to detect and block forged source IP addresses from entering the network. \r\n(For example, block traffic originating from the Internet with an internal source address.)",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "5be296f0-b749-4428-a3a3-85ab5526437a",
                "controlId": "1.3.4",
                "title": "1.3.4",
                "description": "1.3.4 Do not allow unauthorized outbound traffic from the cardholder data environment to the Internet.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "e87d2b8a-7302-443c-a5e5-0b170b79c33d",
                "controlId": "1.3.5",
                "title": "1.3.5",
                "description": "1.3.5 Permit only \u201cestablished\u201d connections into the network.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "a10979ae-a978-4a33-89a6-23b50d49482a",
                "controlId": "1.3.6",
                "title": "1.3.6",
                "description": "1.3.6 Place system components that store cardholder data (such as a database) in an internal network zone, segregated from the DMZ and other untrusted networks.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "7f5d082d-e2b2-4629-9a58-3ee56ceddc07",
                "controlId": "1.3.7",
                "title": "1.3.7",
                "description": "1.3.7 Do not disclose private IP addresses and routing information to unauthorized parties.\r\n\r\nNote: Methods to obscure IP addressing may include, but are not limited to:\r\n\u2022  Network Address Translation (NAT)\r\n\u2022  Placing servers containing cardholder data behind proxy servers/firewalls, \r\n\u2022  Removal or filtering of route advertisements for private networks that employ registered addressing, \r\n\u2022  Internal use of RFC1918 address space instead of registered addresses.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "953f3d3d-5c99-4570-96f4-a6481617eb92",
                "controlId": "1.4 I",
                "title": "1.4 I",
                "description": "1.4 Install personal firewall software or equivalent functionality on any portable computing devices (including company and/or employee-owned) that connect to the Internet when outside the network (for example, laptops used by employees), and which are also used to access the CDE. Firewall (or equivalent) configurations include:\r\n\u2022  Specific configuration settings are defined.\r\n\u2022  Personal firewall (or equivalent functionality) is actively running.\r\n\u2022  Personal firewall (or equivalent functionality) is not alterable by users of the portable computing devices.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "cd241aa5-6828-46ae-83bd-e4a1680aa10c",
                "controlId": "1.5",
                "title": "1.5",
                "description": "1.5 Ensure that security policies and operational procedures for managing firewalls are documented, in use, and known to all affected parties.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 1: Install and maintain a firewall configuration to protect cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "b8ac5200-ba70-41c4-a87a-6c932f9858ce",
                "controlId": "2.1",
                "title": "2.1",
                "description": "2.1 Always change vendor-supplied defaults and remove or disable unnecessary default accounts before installing a system on the network.\r\n\r\nThis applies to ALL default passwords, including but not limited to those used by operating systems, software that provides security services, application and system accounts, point-of-sale (POS) terminals, payment applications, Simple Network Management Protocol (SNMP) community strings, etc.).",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "e9372684-a48c-4721-98de-a049bbfee3e8",
                "controlId": "2.1.1",
                "title": "2.1.1",
                "description": "2.1.1 For wireless environments connected to the cardholder data environment or transmitting cardholder data, change ALL wireless vendor defaults at installation, including but not limited to default wireless encryption keys, passwords, and SNMP community strings.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "8790c0d6-5ae2-4320-9a72-d03ed043d84c",
                "controlId": "2.2",
                "title": "2.2",
                "description": "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.\r\n\r\nSources of industry-accepted system hardening standards may include, but are not limited to:\r\n\u2022  Center for Internet Security (CIS)\r\n\u2022  International Organization for Standardization (ISO)\r\n\u2022  SysAdmin Audit Network Security (SANS) Institute\r\n\u2022  National Institute of Standards Technology (NIST).",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "3ff07f54-caac-4011-817f-55e05a5c2397",
                "controlId": "2.2.1",
                "title": "2.2.1",
                "description": "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.)\r\n\r\nNote: Where virtualization technologies are in use, implement only one primary function per virtual system component.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "7651ee06-af30-4f0c-aeac-4a13885e5308",
                "controlId": "2.2.2",
                "title": "2.2.2",
                "description": "2.2.2 Enable only necessary services, protocols, daemons, etc., as required for the function of the system.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "31b78a88-e42a-4bb6-bcfd-d3148c5bd349",
                "controlId": "2.2.3",
                "title": "2.2.3",
                "description": "2.2.3 Implement additional security features for any required services, protocols, or daemons that are considered to be insecure.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "a469a0b8-4217-4ae3-9a91-2dd8e7c1e305",
                "controlId": "2.2.4",
                "title": "2.2.4",
                "description": "2.2.4 Configure system security parameters to prevent misuse.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "4a14b57f-c591-4a2b-a5ce-443ce5f50385",
                "controlId": "2.2.5",
                "title": "2.2.5",
                "description": "2.2.5 Remove all unnecessary functionality, such as scripts, drivers, features, subsystems, file systems, and unnecessary web servers.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "42b61f1a-6875-4b3e-81ef-abc40e43d4af",
                "controlId": "2.3",
                "title": "2.3",
                "description": "2.3 Encrypt all non-console administrative access using strong cryptography.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "63175697-3d94-4ac1-9b22-9248efa86b03",
                "controlId": "2.4",
                "title": "2.4",
                "description": "2.4 Maintain an inventory of system components that are in scope for PCI DSS.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "2535176c-674c-438b-8317-7010372b4a94",
                "controlId": "2.5",
                "title": "2.5",
                "description": "2.5 Ensure that security policies and operational procedures for managing vendor defaults and other security parameters are documented, in use, and known to all affected parties.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "efc29e24-b474-42fd-b87d-5a41f27d7246",
                "controlId": "2.6",
                "title": "2.6",
                "description": "2.6 Shared hosting providers must protect each entity\u2019s hosted environment and cardholder data. These providers must meet specific requirements as detailed in Appendix A1: Additional PCI DSS Requirements for Shared Hosting Providers. \r\n\r\nAppendix A1 Details: Protect each entity\u2019s (that is, merchant, service provider, or other entity) hosted environment and data, per A1.1 through A1.4:\r\n\r\nA hosting provider must fulfill these requirements as well as all other relevant sections of the PCI DSS.\r\n\r\nNote: Even though a hosting provider may meet these requirements, the compliance of the entity that uses the hosting provider is not guaranteed. Each entity must comply with the PCI DSS and validate compliance as applicable.\r\n\r\nA1.1 Ensure that each entity only runs processes that have access to that entity\u2019s cardholder data environment.\r\n\r\nA1.2 Restrict each entity\u2019s access and privileges to its own cardholder data environment only.\r\n\r\nA1.3 Ensure logging and audit trails are enabled and unique to each entity\u2019s cardholder data environment and consistent with PCI DSS Requirement 10.\r\n\r\nA1.4 Enable processes to provide for timely forensic investigation in the event of a compromise to any hosted merchant or service provider.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "70977be0-6841-4635-a2a4-ee8e1bd20f14",
                "controlId": "3.1",
                "title": "3.1",
                "description": "3.1 Keep cardholder data storage to a minimum by implementing data retention and disposal policies, procedures and processes that include at least the following for all cardholder data (CHD) storage:\r\n\u2022  Limiting data storage amount and retention time to that which is required for legal, regulatory, and/or business requirements\r\n\u2022  Specific retention requirements for cardholder data\r\n\u2022  Processes for secure deletion of data when no longer needed\r\n\u2022  A quarterly process for identifying and securely deleting stored cardholder data that exceeds defined retention.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 1 Remove sensitive authentication data and limit data retention. This milestone targets a key area of risk for entities that have been compromised. Remember \u2013 if sensitive authentication data and other cardholder data are not stored, the effects of a compromise will be greatly reduced. If you don't need it, don't store it",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "2f0759f0-5975-4442-96b0-e6af04e8e048",
                "controlId": "3.2",
                "title": "3.2",
                "description": "3.2 Do not store sensitive authentication data after authorization (even if encrypted). If sensitive authentication data is received, render all data unrecoverable upon completion of the authorization process.\r\nIt is permissible for issuers and companies that support issuing services to store sensitive authentication data if:\r\n\u2022  There is a business justification and \r\n\u2022  The data is stored securely.\r\n\r\nSensitive authentication data includes the data as cited in the following Requirements 3.2.1 through 3.2.3:",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 1 Remove sensitive authentication data and limit data retention. This milestone targets a key area of risk for entities that have been compromised. Remember \u2013 if sensitive authentication data and other cardholder data are not stored, the effects of a compromise will be greatly reduced. If you don't need it, don't store it",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "ae7ef7f8-558f-405b-bfbe-aa4c6735d8e9",
                "controlId": "3.2.1",
                "title": "3.2.1",
                "description": "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) after authorization. This data is alternatively called full track, track, track 1, track 2, and magnetic-stripe data.\r\n\r\nNote: In the normal course of business, the following data elements from the magnetic stripe may need to be retained: \r\n\u2022  The cardholder\u2019s name \r\n\u2022  Primary account number (PAN) \r\n\u2022  Expiration date \r\n\u2022  Service code \r\nTo minimize risk, store only these data elements as needed for business.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 1 Remove sensitive authentication data and limit data retention. This milestone targets a key area of risk for entities that have been compromised. Remember \u2013 if sensitive authentication data and other cardholder data are not stored, the effects of a compromise will be greatly reduced. If you don't need it, don't store it",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "cc71cfd1-9c8b-4276-891a-0c0977bf5987",
                "controlId": "3.2.2",
                "title": "3.2.2",
                "description": "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) after authorization.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 1 Remove sensitive authentication data and limit data retention. This milestone targets a key area of risk for entities that have been compromised. Remember \u2013 if sensitive authentication data and other cardholder data are not stored, the effects of a compromise will be greatly reduced. If you don't need it, don't store it",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "996efc64-7f63-4ad5-92c3-8bee022d51f7",
                "controlId": "3.2.3",
                "title": "3.2.3",
                "description": "3.2.3 Do not store the personal identification number (PIN) or the encrypted PIN block after authorization.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 1 Remove sensitive authentication data and limit data retention. This milestone targets a key area of risk for entities that have been compromised. Remember \u2013 if sensitive authentication data and other cardholder data are not stored, the effects of a compromise will be greatly reduced. If you don't need it, don't store it",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "ddf0cb3b-7eb2-446c-a0cd-eac0cc8e2aaa",
                "controlId": "3.3",
                "title": "3.3",
                "description": "3.3 Mask PAN when displayed (the first six and last four digits are the maximum number of digits to be displayed), such that only personnel with a legitimate business need can see more than the first six/last four digits of the PAN.\r\n\r\nNote: This requirement does not supersede stricter requirements in place for displays of cardholder data\u2014for example, legal or payment card brand requirements for point-of-sale (POS) receipts.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "c8742fac-40de-4929-9f2f-f0a76842bfa1",
                "controlId": "3.4",
                "title": "3.4",
                "description": "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:\r\n\u2022  One-way hashes based on strong cryptography, (hash must be of the entire PAN)\r\n\u2022  Truncation (hashing cannot be used to replace the truncated segment of PAN)\r\n\u2022  Index tokens and pads (pads must be securely stored)\r\n\u2022  Strong cryptography with associated key-management processes and procedures.\r\n\r\nNote: It is a relatively trivial effort for a malicious individual to reconstruct original PAN data if they have access to both the truncated and hashed version of a PAN. Where hashed and truncated versions of the same PAN are present in an entity\u2019s environment, additional controls must be in place to ensure that the hashed and truncated versions cannot be correlated to reconstruct the original PAN.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "16909000-f5d3-48e0-92a7-383157849433",
                "controlId": "3.4.1",
                "title": "3.4.1",
                "description": "3.4.1 If disk encryption is used (rather than file- or column-level database encryption), logical access must be managed separately and independently of native operating system authentication and access control mechanisms (for example, by not using local user account databases or general network login credentials). Decryption keys must not be associated with user accounts. \r\n\r\nNote: This requirement applies in addition to all other PCI DSS encryption and key-management requirements.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "ba998c6e-27d3-4ef8-8473-1fcbb41fd626",
                "controlId": "3.5",
                "title": "3.5",
                "description": "3.5 Document and implement procedures to protect keys used to secure stored cardholder data against disclosure and misuse:\r\n\r\nNote: This requirement applies to keys used to encrypt stored cardholder data, and also applies to key-encrypting keys used to protect data-encrypting keys\u2014such key-encrypting keys must be at least as strong as the data-encrypting key.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": " ",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "45675336-de82-4e0d-af25-36aa4fb05cc9",
                "controlId": "3.5.1",
                "title": "3.5.1",
                "description": "3.5.1   Additional requirement for service providers only: Maintain a documented description of the cryptographic architecture that includes:\r\n\u2022 Details of all algorithms, protocols, and keys used for the protection of cardholder data, including key strength and expiry date\r\n\u2022 Description of the key usage for each key.\r\n\u2022 Inventory of any HSMs and other SCDs used for key management",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "770ea880-f249-4216-aabf-8e06888b33e3",
                "controlId": "3.5.2",
                "title": "3.5.2",
                "description": "3.5.2 Restrict access to cryptographic keys to the fewest number of custodians necessary.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "1189981f-7e30-4720-b9ab-3f6f59edb0b5",
                "controlId": "3.5.3",
                "title": "3.5.3",
                "description": "3.5.3 Store secret and private keys used to encrypt/decrypt cardholder data in one (or more) of the following forms at all times:\r\n\u2022  Encrypted with a key-encrypting key that is at least as strong as the data-encrypting key, and that is stored separately from the data-encrypting key\r\n\u2022  Within a secure cryptographic device (such as a hardware (host) security module (HSM) or PTS-approved point-of-interaction device)\r\n\u2022  As at least two full-length key components or key shares, in accordance with an industry-accepted method\r\n\r\nNote: It is not required that public keys be stored in one of these forms.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "d05366e1-1fa8-445b-928c-c73784e37f1a",
                "controlId": "3.5.4",
                "title": "3.5.4",
                "description": "3.5.4 Store cryptographic keys in the fewest possible locations.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "67668e74-cb29-4ce7-894c-697de51dc3a8",
                "controlId": "3.6",
                "title": "3.6",
                "description": "3.6 Fully document and implement all key-management processes and procedures for cryptographic keys used for encryption of cardholder data, including the following:\r\n\r\nNote: Numerous industry standards for key management are available from various resources including NIST, which can be found at http://csrc.nist.gov.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": " ",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "d3ab8ddc-cbae-4447-b301-902aab2f838f",
                "controlId": "3.6.1",
                "title": "3.6.1",
                "description": "3.6.1 Generation of strong cryptographic keys",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "c7f7e21f-7bcf-49fe-a774-a27ad29ced19",
                "controlId": "3.6.2",
                "title": "3.6.2",
                "description": "3.6.2 Secure cryptographic key distribution",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "e56ed4d7-f297-4fb7-a91d-f284b620ac68",
                "controlId": "3.6.3",
                "title": "3.6.3",
                "description": "3.6.3 Secure cryptographic key storage",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "140ed009-8c3f-4176-a923-bee07960442d",
                "controlId": "3.6.4",
                "title": "3.6.4",
                "description": "3.6.4 Cryptographic key changes for keys that have reached the end of their cryptoperiod (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).",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "a4ab8be9-bb0f-44bc-a6fe-171232a6bf78",
                "controlId": "3.6.5",
                "title": "3.6.5",
                "description": "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 component), or keys are suspected of being compromised.\r\n\r\nNote: If retired or replaced cryptographic keys need to be retained, these keys must be securely archived (for example, by using a key-encryption key). Archived cryptographic keys should only be used for decryption/verification purposes.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "7d002870-6dfd-4621-a773-1527e95dc998",
                "controlId": "3.6.6",
                "title": "3.6.6",
                "description": "3.6.6 If manual clear-text cryptographic key-management operations are used, these operations must be managed using split knowledge and dual control.\r\n\r\nNote: Examples of manual key-management operations include, but are not limited to: key generation, transmission, loading, storage and destruction.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "7b275457-0a38-4b18-ab28-93f806c39c8f",
                "controlId": "3.6.7",
                "title": "3.6.7",
                "description": "3.6.7 Prevention of unauthorized substitution of cryptographic keys.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "ffe4ea41-523e-4633-a4de-4867e6ea2901",
                "controlId": "3.6.8",
                "title": "3.6.8",
                "description": "3.6.8 Requirement for cryptographic key custodians to formally acknowledge that they understand and accept their key-custodian responsibilities.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "6d0d81f5-5905-4d29-b3e8-fa68cb1da14c",
                "controlId": "3.7",
                "title": "3.7",
                "description": "3.7 Ensure that security policies and operational procedures for protecting stored cardholder data are documented, in use, and known to all affected parties.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 3: Protect stored cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "227fd7b9-8ab3-4bac-9e53-1fabfa8440c5",
                "controlId": "4.1",
                "title": "4.1",
                "description": "4.1 Use strong cryptography and security protocols to safeguard sensitive cardholder data during transmission over open, public networks, including the following:\r\n\u2022  Only trusted keys and certificates are accepted.\r\n\u2022  The protocol in use only supports secure versions or configurations.\r\n\u2022  The encryption strength is appropriate for the encryption methodology in use.\r\n\r\nExamples of open, public networks include but are not limited to:\r\n\u2022  The Internet\r\n\u2022  Wireless technologies, including 802.11 and Bluetooth\r\n\u2022  Cellular technologies, for example, Global System for Mobile communications (GSM), Code division multiple access (CDMA)\r\n\u2022   General Packet Radio Service (GPRS).\r\n\u2022  Satellite communications.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 4: Encrypt transmission of cardholder data across open, public networks",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "7f693e9d-e38e-4932-914b-6620ad83cb8a",
                "controlId": "4.1.1",
                "title": "4.1.1",
                "description": "4.1.1 Ensure wireless networks transmitting cardholder data or connected to the cardholder data environment, use industry best practices to implement strong encryption for authentication and transmission.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 4: Encrypt transmission of cardholder data across open, public networks",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "a0063541-ac60-4d08-b216-b39b551c162d",
                "controlId": "4.2",
                "title": "4.2",
                "description": "4.2 Never send unprotected PANs by end-user messaging technologies (for example, e-mail, instant messaging, SMS, chat, etc.).",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 4: Encrypt transmission of cardholder data across open, public networks",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "471fc875-ea81-4431-82cd-e06178585e48",
                "controlId": "4.3",
                "title": "4.3",
                "description": "4.3 Ensure that security policies and operational procedures for encrypting transmissions of cardholder data are documented, in use, and known to all affected parties.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 4: Encrypt transmission of cardholder data across open, public networks",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "cdff06b1-871e-498c-ae30-097f476cb0d1",
                "controlId": "5.1",
                "title": "5.1",
                "description": "5.1 Deploy anti-virus software on all systems commonly affected by malicious software (particularly personal computers and servers).",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 5: Use and regularly update anti-virus software or programs",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "b802536f-65fe-4c33-852f-9179e7caa3b4",
                "controlId": "5.1.1",
                "title": "5.1.1",
                "description": "5.1.1 Ensure that anti-virus programs are capable of detecting, removing, and protecting against all known types of malicious software.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 5: Use and regularly update anti-virus software or programs",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "e407d26e-5782-4b21-99aa-1fcbc065bc39",
                "controlId": "5.1.2",
                "title": "5.1.2",
                "description": "5.1.2 For systems considered to be not commonly affected by malicious software, perform periodic evaluations to identify and evaluate evolving malware threats in order to confirm whether such systems continue to not require anti-virus software.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 5: Use and regularly update anti-virus software or programs",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "2a5b3c8b-3aa1-46d0-8a3a-94175a0f9cf8",
                "controlId": "5.2",
                "title": "5.2",
                "description": "5.2 Ensure that all anti-virus mechanisms are maintained as follows:\r\n\r\n\u2022  Are kept current, \r\n\u2022  Perform periodic scans\r\n\u2022  Generate audit logs which are retained per PCI DSS Requirement 10.7.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 5: Use and regularly update anti-virus software or programs",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "f21fc4e5-fc50-4bf2-98ec-1f268f3772e3",
                "controlId": "5.3",
                "title": "5.3",
                "description": "5.3 Ensure that anti-virus mechanisms are actively running and cannot be disabled or altered by users, unless specifically authorized by management on a case-by-case basis for a limited time period. \r\n\r\nNote: Anti-virus solutions may be temporarily disabled only if there is legitimate technical need, as authorized by management on a case-by-case basis. If anti-virus protection needs to be disabled for a specific purpose, it must be formally authorized. Additional security measures may also need to be implemented for the period of time during which anti-virus protection is not active.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 5: Use and regularly update anti-virus software or programs",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "1eedd979-8db9-4688-aae8-deacb43799d4",
                "controlId": "5.4",
                "title": "5.4",
                "description": "5.4 Ensure that security policies and operational procedures for protecting systems against malware are documented, in use, and known to all affected parties.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 5: Use and regularly update anti-virus software or programs",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "b7e7c8eb-8133-4f07-ae62-68c3ae72d959",
                "controlId": "6.1",
                "title": "6.1",
                "description": "6.1 Establish a process to identify security vulnerabilities, using reputable outside sources for security vulnerability information, and assign a risk ranking (for example, as \u201chigh,\u201d \u201cmedium,\u201d or \u201clow\u201d) to newly discovered security vulnerabilities.\r\n\r\nNote: Risk rankings should be based on industry best practices as well as consideration of potential impact. For example, criteria for ranking vulnerabilities may include consideration of the CVSS base score, and/or the classification by the vendor, and/or type of systems affected.\r\n\r\nMethods for evaluating vulnerabilities and assigning risk ratings will vary based on an organization\u2019s environment and risk-assessment strategy. Risk rankings should, at a minimum, identify all vulnerabilities considered to be a \u201chigh risk\u201d to the environment. In addition to the risk ranking, vulnerabilities may be considered \u201ccritical\u201d if they pose an imminent threat to the environment, impact critical systems, and/or would result in a potential compromise if not addressed. Examples of critical systems may include security systems, public-facing devices and systems, databases, and other systems that store, process, or transmit cardholder data.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "e0d36ec2-8ea2-410c-9760-2f72b844dadc",
                "controlId": "6.2",
                "title": "6.2",
                "description": "6.2 Ensure that all system components and software are protected from known vulnerabilities by installing applicable vendor-supplied security patches. Install critical security patches within one month of release.\r\nNote: Critical security patches should be identified according to the risk ranking process defined in Requirement 6.1.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "ba35c006-42d6-4c38-9f3b-5da5964384a8",
                "controlId": "6.3",
                "title": "6.3",
                "description": "6.3 Develop internal and external software applications (including web-based administrative access to applications) securely, as follows:\r\n\r\n\u2022  In accordance with PCI DSS (for example, secure authentication and logging)\r\n\u2022  Based on industry standards and/or best practices.\r\n\u2022  Incorporating information security throughout the software-development life cycle\r\n\r\nNote: This applies to all software developed internally as well as bespoke or custom software developed by a third party.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "6305c122-b87f-40d3-b91f-4bd71e33ecd4",
                "controlId": "6.3.1",
                "title": "6.3.1",
                "description": "6.3.1 Remove development, test and/or custom application accounts, user IDs, and passwords before applications become active or are released to customers.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "2efce01d-c1f9-48e7-91ff-96a78372bb70",
                "controlId": "6.3.2",
                "title": "6.3.2",
                "description": "6.3.2 Review custom code prior to release to production or customers in order to identify any potential coding vulnerability (using either manual or automated processes) to include at least the following:\r\n\u2022  Code changes are reviewed by individuals other than the originating code author, and by individuals knowledgeable about code-review techniques and secure coding practices.\r\n\u2022  Code reviews ensure code is developed according to secure coding guidelines\r\n\u2022  Appropriate corrections are implemented prior to release.\r\n\u2022  Code-review results are reviewed and approved by management prior to release.\r\n\r\nNote: This requirement for code reviews applies to all custom code (both internal and public-facing), as part of the system development life cycle. Code reviews can be conducted by knowledgeable internal personnel or third parties. Public-facing web applications are also subject to additional controls, to address ongoing threats and vulnerabilities after implementation, as defined at PCI DSS Requirement 6.6.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "333ab94a-8978-4d24-83e4-33bc5a36436f",
                "controlId": "6.4",
                "title": "6.4",
                "description": "6.4 Follow change control processes and procedures for all changes to system components. The processes must include the following:",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "15907dcb-c06b-4a6d-bfd1-8009b4d3333f",
                "controlId": "6.4.1",
                "title": "6.4.1",
                "description": "6.4.1 Separate development/test environments from production environments, and enforce the separation with access controls.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "bb731062-7c02-40d2-96cb-721b395a4ead",
                "controlId": "6.4.2",
                "title": "6.4.2",
                "description": "6.4.2 Separation of duties between development/test and production environments",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "a0628c5a-366a-40c6-afbd-2980fc15b400",
                "controlId": "6.4.3",
                "title": "6.4.3",
                "description": "6.4.3 Production data (live PANs) are not used for testing or development",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "3b80251b-20d4-4d17-8d17-7fbdd93632b0",
                "controlId": "6.4.4",
                "title": "6.4.4",
                "description": "6.4.4 Removal of test data and accounts from system components before the system becomes active/goes into production.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "8bc0c0ee-ec32-4938-8d76-21e33c50127b",
                "controlId": "6.4.5",
                "title": "6.4.5",
                "description": "6.4.5 Change control procedures must include the following:",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "78382c05-95bf-4c47-be53-6d859cef1a06",
                "controlId": "6.4.5.1",
                "title": "6.4.5.1",
                "description": "6.4.5.1 Documentation of impact.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "fcc66ab3-e00e-4fd0-80fa-f280a105e558",
                "controlId": "6.4.5.2",
                "title": "6.4.5.2",
                "description": "6.4.5.2 Documented change approval by authorized parties. ",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "0e1d8f09-12b0-43ef-8876-9a741525a56e",
                "controlId": "6.4.5.3",
                "title": "6.4.5.3",
                "description": "6.4.5.3 Functionality testing to verify that the change does not adversely impact the security of the system.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "8258c6a3-7307-4895-b6f1-4ed6971ea50d",
                "controlId": "6.4.5.4",
                "title": "6.4.5.4",
                "description": "6.4.5.4 Back-out procedures.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "c01667ff-ef58-4333-8b6f-23c7f042091c",
                "controlId": "6.4.6",
                "title": "6.4.6",
                "description": "6.4.6 Upon completion of a significant change, all relevant PCI DSS requirements must be implemented on all new or changed systems and networks, and documentation updated as applicable.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "1b568091-00e0-466e-a430-dff4d972ddb2",
                "controlId": "6.5",
                "title": "6.5",
                "description": "6.5 Address common coding vulnerabilities in software-development processes as follows:\r\n\u2022  Train developers at least annually  in up-to-date secure coding techniques, including how to avoid common coding vulnerabilities.\r\n\u2022  Develop applications based on secure coding guidelines.\r\n\r\nNote: The vulnerabilities listed at 6.5.1 through 6.5.10 were current with industry best practices when this version of PCI DSS was published. However, as industry best practices for vulnerability management are updated (for example, the OWASP Guide, SANS CWE Top 25, CERT Secure Coding, etc.), the current best practices must be used for these requirements.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "8af5eb2e-4c35-4e8f-904e-efc15f8094d0",
                "controlId": "6.5.1",
                "title": "6.5.1",
                "description": "6.5.1 Injection flaws, particularly SQL injection. Also consider OS Command Injection, LDAP and XPath injection flaws as well as other injection flaws. Note: Requirements 6.5.1 through 6.5.6 apply to all applications (internal or external).",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "4a984fa3-b82f-4544-8860-ae96ba2dd0a0",
                "controlId": "6.5.2",
                "title": "6.5.2",
                "description": "6.5.2 Buffer overflows. Note: Requirements 6.5.1 through 6.5.6 apply to all applications (internal or external).",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "ac32d24e-b8f0-41f4-9ef0-278d8a828a03",
                "controlId": "6.5.3",
                "title": "6.5.3",
                "description": "6.5.3 Insecure cryptographic storage. Note: Requirements 6.5.1 through 6.5.6 apply to all applications (internal or external).",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "13feae7f-6fb1-4780-bd32-215b89ebbf4d",
                "controlId": "6.5.4",
                "title": "6.5.4",
                "description": "6.5.4 Insecure communications. Note: Requirements 6.5.1 through 6.5.6 apply to all applications (internal or external).",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "92e7de67-0433-4448-bc3b-4d52478617f5",
                "controlId": "6.5.5",
                "title": "6.5.5",
                "description": "6.5.5 Improper error handling. Note: Requirements 6.5.1 through 6.5.6 apply to all applications (internal or external).",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "68dd6dbc-574b-4982-8cda-7a446f9a8874",
                "controlId": "6.5.6",
                "title": "6.5.6",
                "description": "6.5.6 All \u201chigh risk\u201d vulnerabilities identified in the vulnerability identification process (as defined in PCI DSS Requirement 6.1). Note: Requirements 6.5.1 through 6.5.6 apply to all applications (internal or external). ",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "c4ba247b-9ee8-4286-af5c-0c17414d474c",
                "controlId": "6.5.7",
                "title": "6.5.7",
                "description": "6.5.7 Cross-site scripting (XSS). Note: Requirements 6.5.7 through 6.5.10 apply to web applications and application interfaces (internal or external):",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "b762c3ef-e731-467e-a668-23f754016b8c",
                "controlId": "6.5.8",
                "title": "6.5.8",
                "description": "6.5.8 Improper access control (such as insecure direct object references, failure to restrict URL access, directory traversal, and failure to restrict user access to functions). Note: Requirements 6.5.7 through 6.5.10 apply to web applications and application interfaces (internal or external):",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "ddc6bc4a-2cad-496a-a1ba-c916468e95a0",
                "controlId": "6.5.9",
                "title": "6.5.9",
                "description": "6.5.9 Cross-site request forgery (CSRF). Note: Requirements 6.5.7 through 6.5.10 apply to web applications and application interfaces (internal or external):",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "6359560d-7b30-4716-81dd-5bdee782cd2c",
                "controlId": "6.5.10",
                "title": "6.5.10",
                "description": "6.5.10 Broken authentication and session management. Note: Requirements 6.5.7 through 6.5.10 apply to web applications and application interfaces (internal or external):",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "300951ca-c566-44cf-af76-32a7e3fa3add",
                "controlId": "6.6",
                "title": "6.6",
                "description": "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:\r\n\u2022  Reviewing public-facing web applications via manual or automated application vulnerability security assessment tools or methods, at least annually and after any changes\r\nNote: This assessment is not the same as the vulnerability scans performed for Requirement 11.2.\r\n\r\n\u2022  Installing an automated technical solution that detects and prevents web-based attacks (for example, a web-application firewall) in front of public-facing web applications, to continually check all traffic.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "f398967b-fae1-42e0-9825-262b658aa38d",
                "controlId": "6.7",
                "title": "6.7",
                "description": "6.7 Ensure that security policies and operational procedures for developing and maintaining secure systems and applications are documented, in use, and known to all affected parties.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Requirement 6: Develop and maintain secure systems and applications",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "bd38c880-5eb5-4bf3-8482-d57392a6e904",
                "controlId": "7.1",
                "title": "7.1",
                "description": "7.1 Limit access to system components and cardholder data to only those individuals whose job requires such access.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": " ",
                "family": "Requirement 7: Restrict access to cardholder data by business need to know",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "6e618770-5eb5-4488-ab44-92ad8fae7cb4",
                "controlId": "7.1.1",
                "title": "7.1.1",
                "description": "7.1.1 Define access needs for each role, including:\r\n\u2022  System components and data resources that each role needs to access for their job function\r\n\u2022  Level of privilege required (for example, user, administrator, etc.) for accessing resources.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 7: Restrict access to cardholder data by business need to know",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "e2e0281c-94cc-4d99-a674-ba7b591c0487",
                "controlId": "7.1.2",
                "title": "7.1.2",
                "description": "7.1.2 Restrict access to privileged user IDs to least privileges necessary to perform job responsibilities. ",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 7: Restrict access to cardholder data by business need to know",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "a491508a-a986-42ba-bca5-9cb6afd02441",
                "controlId": "7.1.3",
                "title": "7.1.3",
                "description": "7.1.3 Assign access based on individual personnel\u2019s job classification and function.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 7: Restrict access to cardholder data by business need to know",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "27fc51d8-6451-414d-bdda-bb9516c7be4d",
                "controlId": "7.1.4",
                "title": "7.1.4",
                "description": "7.1.4 Require documented approval by authorized parties specifying required privileges.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 7: Restrict access to cardholder data by business need to know",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "ed0123f2-9380-411a-b031-c512480e876d",
                "controlId": "7.2",
                "title": "7.2",
                "description": "7.2 Establish an access control system(s) for systems components that restricts access based on a user\u2019s need to know, and is set to \u201cdeny all\u201d unless specifically allowed.\r\nThis access control system(s) must include the following:",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": " ",
                "family": "Requirement 7: Restrict access to cardholder data by business need to know",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "9aac5382-2454-4561-9f95-206fa91ecd2c",
                "controlId": "7.2.1",
                "title": "7.2.1",
                "description": "7.2.1 Coverage of all system components",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 7: Restrict access to cardholder data by business need to know",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "0be84374-5dc3-4254-a85a-cda75bc42210",
                "controlId": "7.2.2",
                "title": "7.2.2",
                "description": "7.2.2 Assignment of privileges to individuals based on job classification and function.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 7: Restrict access to cardholder data by business need to know",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "22f73c6a-2deb-4dd4-aabf-03fb14c19011",
                "controlId": "7.2.3",
                "title": "7.2.3",
                "description": "7.2.3 Default \u201cdeny-all\u201d setting.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 7: Restrict access to cardholder data by business need to know",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "32f74fea-8e06-487c-92c1-27e7688c24f8",
                "controlId": "7.3",
                "title": "7.3",
                "description": "7.3 Ensure that security policies and operational procedures for restricting access to cardholder data are documented, in use, and known to all affected parties.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 7: Restrict access to cardholder data by business need to know",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "cf04aa25-ccdc-4d64-ab9b-c6e2b0f7f7d8",
                "controlId": "8.1",
                "title": "8.1",
                "description": "8.1 Define and implement policies and procedures to ensure proper user identification management for non-consumer users and administrators on all system components as follows:",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": " ",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "5075c72a-a386-4e47-a543-e5db7fd7e6eb",
                "controlId": "8.1.1",
                "title": "8.1.1",
                "description": "8.1.1 Assign all users a unique ID before allowing them to access system components or cardholder data.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "aca41f04-8500-4eb2-82df-c3a87e3ae92a",
                "controlId": "8.1.2",
                "title": "8.1.2",
                "description": "8.1.2 Control addition, deletion, and modification of user IDs, credentials, and other identifier objects.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "9a61fcb1-8e69-4d00-b59d-eca82d6ab5d6",
                "controlId": "8.1.3",
                "title": "8.1.3",
                "description": "8.1.3 Immediately revoke access for any terminated users.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "1028922e-dbd1-4752-8b2e-02a0d62f6849",
                "controlId": "8.1.4",
                "title": "8.1.4",
                "description": "8.1.4 Remove/disable inactive user accounts within 90 days.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "59f63d77-8cd0-4a9a-b552-c64838725c52",
                "controlId": "8.1.5",
                "title": "8.1.5",
                "description": "8.1.5 Manage IDs used by third parties to access, support, or maintain system components via remote access as follows:\r\n\u2022  Enabled only during the time period needed and disabled when not in use. \r\n\u2022  Monitored when in use.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "9995f457-037d-47ab-95ed-2e6019ec3d6d",
                "controlId": "8.1.6",
                "title": "8.1.6",
                "description": "8.1.6 Limit repeated access attempts by locking out the user ID after not more than six attempts.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "d0230592-7241-4094-84fa-f8eea4e88c71",
                "controlId": "8.1.7",
                "title": "8.1.7",
                "description": "8.1.7 Set the lockout duration to a minimum of 30 minutes or until an administrator enables the user ID.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "b8675077-738f-41d5-81da-fda85ac4f4d4",
                "controlId": "8.1.8",
                "title": "8.1.8",
                "description": "8.1.8 If a session has been idle for more than 15 minutes, require the user to re-authenticate to re-activate the terminal or session.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "7e98c1a8-6424-4807-a6ac-4eaf5856b7ea",
                "controlId": "8.2",
                "title": "8.2",
                "description": "8.2 In addition to assigning a unique ID, ensure proper user-authentication management for non-consumer users and administrators on all system components by employing at least one of the following methods to authenticate all users:\r\n\u2022  Something you know, such as a password or passphrase\r\n\u2022  Something you have, such as a token device or smart card\r\n\u2022  Something you are, such as a biometric.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "7e993785-8278-46d1-a881-192f96052e4e",
                "controlId": "8.2.1",
                "title": "8.2.1",
                "description": "8.2.1 Using strong cryptography, render all authentication credentials (such as passwords/phrases) unreadable during transmission and storage on all system components.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "82a1478c-4aac-4d95-8ceb-97681555e56f",
                "controlId": "8.2.2",
                "title": "8.2.2",
                "description": "8.2.2 Verify user identity before modifying any authentication credential\u2014for example, performing password resets, provisioning new tokens, or generating new keys.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "e93fed7b-1d2a-40d5-8d3d-8a9321f1b2c4",
                "controlId": "8.2.3",
                "title": "8.2.3",
                "description": "8.2.3 Passwords/passphrases must meet the following:\r\n\u2022  Require a minimum length of at least seven characters.\r\n\u2022  Contain both numeric and alphabetic characters.\r\n\r\nAlternatively, the passwords/passphrases must have complexity and strength at least equivalent to the parameters specified above.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "9afedb81-bf0f-4c69-842f-db1af870e4c2",
                "controlId": "8.2.4",
                "title": "8.2.4",
                "description": "8.2.4 Change user passwords/passphrases at least once every 90 days.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "ae4f29fc-0cbe-41ce-92f6-49d514fc857f",
                "controlId": "8.2.5",
                "title": "8.2.5",
                "description": "8.2.5 Do not allow an individual to submit a new password/passphrase that is the same as any of the last four passwords/passphrases he or she has used.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "95cecda1-fa34-4cd6-a3ba-ec424e157ead",
                "controlId": "8.2.6",
                "title": "8.2.6",
                "description": "8.2.6 Set passwords/passphrases for first-time use and upon reset to a unique value for each user, and change immediately after the first use.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "dadc2216-f161-45c0-8d40-5ac958ae2647",
                "controlId": "8.3",
                "title": "8.3",
                "description": "8.3 Secure all individual non-console administrative access and all remote access to the CDE using multi-factor authentication. \r\n\r\nNote: Multi-factor authentication requires that a minimum of two of the three authentication methods (see Requirement 8.2 for descriptions of authentication methods) be used for authentication. Using one factor twice (for example, using two separate passwords) is not considered multi-factor authentication.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": " ",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "cc76528e-3071-4b04-a2a5-7b71e822230f",
                "controlId": "8.3.1",
                "title": "8.3.1",
                "description": "8.3.1 Incorporate multi-factor authentication for all non-console access into the CDE for personnel with administrative access. \r\n",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "5ac2f7f5-c98e-4029-8660-c2f53543412c",
                "controlId": "8.3.2",
                "title": "8.3.2",
                "description": "8.3.2 Incorporate multi-factor authentication for all remote network access (both user and administrator, and including third party access for support or maintenance) originating from outside the entity's network.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "547bd69c-456a-4fa1-b90c-d8d58fdf59d3",
                "controlId": "8.4",
                "title": "8.4",
                "description": "8.4 Document and communicate authentication policies and procedures to all users including:\r\n\u2022  Guidance on selecting strong authentication credentials\r\n\u2022  Guidance for how users should protect their authentication credentials\r\n\u2022  Instructions not to reuse previously used passwords\r\n\u2022  Instructions to change passwords if there is any suspicion the password could be compromised.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "984334be-c4cf-4933-9b1d-95e6095360c8",
                "controlId": "8.5",
                "title": "8.5",
                "description": "8.5 Do not use group, shared, or generic IDs, passwords, or other authentication methods as follows:\r\n\u2022  Generic user IDs are disabled or removed.\r\n\u2022  Shared user IDs do not exist for system administration and other critical functions.\r\n\u2022  Shared and generic user IDs are not used to administer any system components.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "70e5105e-2be2-47ee-9fa4-d58fa22832fc",
                "controlId": "8.5.1",
                "title": "8.5.1",
                "description": "8.5.1 Additional requirement for service providers only: Service providers with remote access to customer premises (for example, for support of POS systems or servers) must use a unique authentication credential (such as a password/phrase) for each customer.\r\n\r\nNote: This requirement is not intended to apply to shared hosting providers accessing their own hosting environment, where multiple customer environments are hosted.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "5e746b01-acf0-4802-aaa3-4784f892d10d",
                "controlId": "8.6",
                "title": "8.6",
                "description": "8.6 Where other authentication mechanisms are used (for example, physical or logical security tokens, smart cards, certificates, etc.), use of these mechanisms must be assigned as follows:\r\n\r\n\u2022  Authentication mechanisms must be assigned to an individual account and not shared among multiple accounts.\r\n\u2022  Physical and/or logical controls must be in place to ensure only the intended account can use that mechanism to gain access. ",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "691c42ed-7cc6-48ab-8b8f-01bfb45b5419",
                "controlId": "8.7",
                "title": "8.7",
                "description": "8.7 All access to any database containing cardholder data (including access by applications, administrators, and all other users) is restricted as follows:\r\n\r\n\u2022  All user access to, user queries of, and user actions on databases are through programmatic methods.\r\n\u2022  Only database administrators have the ability to directly access or query databases.\r\n\u2022  Application IDs for database applications can only be used by the applications (and not by individual users or other non-application processes).",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "a6724a5f-23e1-431f-b7d9-e00736231416",
                "controlId": "8.8",
                "title": "8.8",
                "description": "8.8 Ensure that security policies and operational procedures for identification and authentication are documented, in use, and known to all affected parties.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 8: Assign a unique ID to each person with computer access",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "e15198da-b4a8-4b96-98e6-e27a99a239ee",
                "controlId": "9.1",
                "title": "9.1",
                "description": "9.1 Use appropriate facility entry controls to limit and monitor physical access to systems in the cardholder data environment.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "b8caa755-555e-477b-81b0-ab51de3b72e6",
                "controlId": "9.1.1",
                "title": "9.1.1",
                "description": "9.1.1 Use either video cameras or access control mechanisms (or both) 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.\r\n\r\nNote: \u201cSensitive areas\u201d refers to any data center, server room or any area that houses systems that store, process, or transmit cardholder data. This excludes public-facing areas where only point-of-sale terminals are present, such as the cashier areas in a retail store.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "04e15e08-f088-461c-b422-5e5e0a347e0c",
                "controlId": "9.1.2",
                "title": "9.1.2",
                "description": "9.1.2 Implement physical and/or logical controls to restrict access to publicly accessible network jacks.\r\nFor example, network jacks located in public areas and areas accessible to visitors could be disabled and only enabled when network access is explicitly authorized. Alternatively, processes could be implemented to ensure that visitors are escorted at all times in areas with active network jacks.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "af848f0e-b717-4220-adc5-e833daca259a",
                "controlId": "9.1.3",
                "title": "9.1.3",
                "description": "9.1.3 Restrict physical access to wireless access points, gateways, handheld devices, networking/communications hardware, and telecommunication lines.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "d59d04cb-f169-4f36-81a2-ba8e9c7703cb",
                "controlId": "9.2",
                "title": "9.2",
                "description": "9.2 Develop procedures to easily distinguish between onsite personnel and visitors, to include:\r\n\u2022  Identifying onsite personnel and visitors (for example, assigning badges)\r\n\u2022  Changes to access requirements\r\n\u2022  Revoking or terminating onsite personnel and expired visitor identification (such as ID badges).",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "fad0a620-ae91-47f9-b633-f65607009921",
                "controlId": "9.3",
                "title": "9.3",
                "description": "9.3 Control physical access for onsite personnel to sensitive areas as follows:\r\n\u2022  Access must be authorized and based on individual job function.\r\n\u2022  Access is revoked immediately upon termination, and all physical access mechanisms, such as keys, access cards, etc., are returned or disabled.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "bc4af0c9-ee8c-42d8-958a-db15c9769d58",
                "controlId": "9.4 I",
                "title": "9.4 I",
                "description": "9.4 Implement procedures to identify and authorize visitors.\r\nProcedures should include the following:",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": " ",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "cb419c6a-14cb-425b-8626-d75fcd5d8904",
                "controlId": "9.4.1",
                "title": "9.4.1",
                "description": "9.4.1 Visitors are authorized before entering, and escorted at all times within, areas where cardholder data is processed or maintained.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "af7e59b8-954a-40ef-96e5-44fdedbc9eee",
                "controlId": "9.4.2",
                "title": "9.4.2",
                "description": "9.4.2 Visitors are identified and given a badge or other identification that expires and that visibly distinguishes the visitors from onsite personnel.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "8b3e43ca-172f-4871-98ca-b200943bf55c",
                "controlId": "9.4.3",
                "title": "9.4.3",
                "description": "9.4.3 Visitors are asked to surrender the badge or identification before leaving the facility or at the date of expiration.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "0629df2c-37f9-43db-a403-f03a5a264a81",
                "controlId": "9.4.4",
                "title": "9.4.4",
                "description": "9.4.4 A visitor log is used to maintain a physical audit trail of visitor activity to the facility as well as computer rooms and data centers where cardholder data is stored or transmitted.\r\nDocument the visitor\u2019s name, the firm represented, and the onsite personnel authorizing physical access on the log.\r\nRetain this log for a minimum of three months, unless otherwise restricted by law.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "85bfaadf-74db-4a6a-bdc7-305348424f5d",
                "controlId": "9.5",
                "title": "9.5",
                "description": "9.5 Physically secure all media.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "048a44d5-78c0-4dcf-8f58-db40dfe9d9f4",
                "controlId": "9.5.1",
                "title": "9.5.1",
                "description": "9.5.1 Store media backups in a secure location, preferably an off-site facility, such as an alternate or backup site, or a commercial storage facility. Review the location\u2019s security at least annually.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "a9f78541-052b-4798-b96c-fa01a3ab71c5",
                "controlId": "9.6",
                "title": "9.6",
                "description": "9.6 Maintain strict control over the internal or external distribution of any kind of media, including the following: ",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": " ",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "e38f8bd8-dd62-4b70-9d02-7d9d775ed74d",
                "controlId": "9.6.1",
                "title": "9.6.1",
                "description": "9.6.1 Classify media so the sensitivity of the data can be determined.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "0afb8acc-922b-45d7-9caf-2108f7124f8e",
                "controlId": "9.6.2",
                "title": "9.6.2",
                "description": "9.6.2 Send the media by secured courier or other delivery method that can be accurately tracked.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "a3f0533d-06d2-4c1a-b2d0-346f8cc2b719",
                "controlId": "9.6.3",
                "title": "9.6.3",
                "description": "9.6.3 Ensure management approves any and all media that is moved from a secured area (including when media is distributed to individuals).",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "fa0e1dea-119f-45a3-b2b5-1bcb8fa99bef",
                "controlId": "9.7",
                "title": "9.7",
                "description": "9.7 Maintain strict control over the storage and accessibility of media.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": " ",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "fda6fc85-c87a-419e-b0c6-f6b6aafc2576",
                "controlId": "9.7.1",
                "title": "9.7.1",
                "description": "9.7.1 Properly maintain inventory logs of all media and conduct media inventories at least annually.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "c78715fb-c3f1-4b69-9a39-484cd55af187",
                "controlId": "9.8",
                "title": "9.8",
                "description": "9.8 Destroy media when it is no longer needed for business or legal reasons as follows:",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": " ",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "9cc6439e-24f1-43d8-a3d1-c3c1a87fb16e",
                "controlId": "9.8.1",
                "title": "9.8.1",
                "description": "9.8.1 Shred, incinerate, or pulp hard-copy materials so that cardholder data cannot be reconstructed. Secure storage containers used for materials that are to be destroyed.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 1 Remove sensitive authentication data and limit data retention. This milestone targets a key area of risk for entities that have been compromised. Remember \u2013 if sensitive authentication data and other cardholder data are not stored, the effects of a compromise will be greatly reduced. If you don't need it, don't store it",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "d0c21bff-1719-4c43-997a-871e97cbdfbb",
                "controlId": "9.8.2",
                "title": "9.8.2",
                "description": "9.8.2 Render cardholder data on electronic media unrecoverable so that cardholder data cannot be reconstructed.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 1 Remove sensitive authentication data and limit data retention. This milestone targets a key area of risk for entities that have been compromised. Remember \u2013 if sensitive authentication data and other cardholder data are not stored, the effects of a compromise will be greatly reduced. If you don't need it, don't store it",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "957c3108-75c9-4344-9d6d-10efc1ae43b6",
                "controlId": "9.9",
                "title": "9.9",
                "description": "9.9 Protect devices that capture payment card data via direct physical interaction with the card from tampering and substitution.\r\n\r\nNote: These requirements apply to card-reading devices used in card-present transactions (that is, card swipe or dip) at the point of sale. This requirement is not intended to apply to manual key-entry components such as computer keyboards and POS keypads.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": " ",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "1a2b7c0f-8cf6-45c6-afb1-ae4c1327d4e9",
                "controlId": "9.9.1",
                "title": "9.9.1",
                "description": "9.9.1 Maintain an up-to-date list of devices. The list should include the following:\r\n\u2022  Make, model of device\r\n\u2022  Location of device (for example, the address of the site or facility where the device is located)\r\n\u2022  Device serial number or other method of unique identification.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "b01ec054-7f28-4285-8f81-f303d7a918e2",
                "controlId": "9.9.2",
                "title": "9.9.2",
                "description": "9.9.2 Periodically inspect device surfaces to detect tampering (for example, addition of card skimmers to devices), or substitution (for example, by checking the serial number or other device characteristics to verify it has not been swapped with a fraudulent device).\r\n\r\nNote: Examples of signs that a device might have been tampered with or substituted include unexpected attachments or cables plugged into the device, missing or changed security labels, broken or differently colored casing, or changes to the serial number or other external markings.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "81fd3501-e742-46b5-81e2-0d5d116dde07",
                "controlId": "9.9.3",
                "title": "9.9.3",
                "description": "9.9.3 Provide training for personnel to be aware of attempted tampering or replacement of devices. Training should include the following:\r\n\u2022  Verify the identity of any third-party persons claiming to be repair or maintenance personnel, prior to granting them access to modify or troubleshoot devices.\r\n\u2022  Do not install, replace, or return devices without verification.\r\n\u2022  Be aware of suspicious behavior around devices (for example, attempts by unknown persons to unplug or open devices).\r\n\u2022  Report suspicious behavior and indications of device tampering or substitution to appropriate personnel (for example, to a manager or security officer).",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "47bd52df-517d-4ac5-803e-41422a80fe19",
                "controlId": "9.10",
                "title": "9.10",
                "description": "9.10 Ensure that security policies and operational procedures for restricting physical access to cardholder data are documented, in use, and known to all affected parties.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 5 Protect stored cardholder data. For those organizations that have analyzed their business processes and determined that they must store Primary Account Numbers, Milestone Five targets key protection mechanisms for that stored data.",
                "family": "Requirement 9: Restrict physical access to cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "67596735-d5e9-4d22-994a-1b60045395e1",
                "controlId": "10.1",
                "title": "10.1",
                "description": "10.1 Implement audit trails to link all access to system components to each individual user.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "5a805daa-c24a-4116-be93-e3b990c85d74",
                "controlId": "10.2",
                "title": "10.2",
                "description": "10.2 Implement automated audit trails for all system components to reconstruct the following events:",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": " ",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "7378fe9e-e98e-4ae1-8ac0-006d2f1b023b",
                "controlId": "10.2.1",
                "title": "10.2.1",
                "description": "10.2.1 All individual user accesses to cardholder data",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "10c66e14-5e72-49c1-a4b5-6be57df20658",
                "controlId": "10.2.2",
                "title": "10.2.2",
                "description": "10.2.2 All actions taken by any individual with root or administrative privileges",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "c55773d9-97ba-4193-ace5-157af10c6876",
                "controlId": "10.2.3",
                "title": "10.2.3",
                "description": "10.2.3 Access to all audit trails",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "53c53ab3-03d3-4585-9ca7-46b04cdfa516",
                "controlId": "10.2.4",
                "title": "10.2.4",
                "description": "10.2.4 Invalid logical access attempts",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "a23adbe0-3bce-41f1-a39a-198fa4e40f4b",
                "controlId": "10.2.5",
                "title": "10.2.5",
                "description": "10.2.5 Use of and changes to identification and authentication mechanisms\u2014including but not limited to creation of new accounts and elevation of privileges\u2014and all changes, additions, or deletions to accounts with root or administrative privileges",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "29d6cd14-8b7e-489f-a314-925fef8d1018",
                "controlId": "10.2.6",
                "title": "10.2.6",
                "description": "10.2.6 Initialization, stopping, or pausing of the audit logs",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "96c98979-530e-4252-be1b-4e2e3d6d2916",
                "controlId": "10.2.7",
                "title": "10.2.7",
                "description": "10.2.7 Creation and deletion of system-level objects",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "6c60dadd-f7bc-4dc9-9aa2-33b65af8c573",
                "controlId": "10.3",
                "title": "10.3",
                "description": "10.3 Record at least the following audit trail entries for all system components for each event:",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": " ",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "06c6e07d-ba7a-4328-ad8c-4705b5969142",
                "controlId": "10.3.1",
                "title": "10.3.1",
                "description": "10.3.1 User identification",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "695e94cd-a9a5-4ed9-bd93-1ed1c3c89eb3",
                "controlId": "10.3.2",
                "title": "10.3.2",
                "description": "10.3.2 Type of event",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "a3f0c25b-5716-4662-8ee4-0ccce1172aa3",
                "controlId": "10.3.3",
                "title": "10.3.3",
                "description": "10.3.3 Date and time",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "388376ff-ece1-4644-95e8-12ade35727e0",
                "controlId": "10.3.4",
                "title": "10.3.4",
                "description": "10.3.4 Success or failure indication",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "9b1d4934-11a9-495f-b6b7-0a1a09efaffe",
                "controlId": "10.3.5",
                "title": "10.3.5",
                "description": "10.3.5 Origination of event",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "143e4611-64a4-4135-ba2b-a885ca01602d",
                "controlId": "10.3.6",
                "title": "10.3.6",
                "description": "10.3.6 Identity or name of affected data, system component, or resource.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "58c0c66e-2ff5-4ee5-b2c8-e82d8fb30744",
                "controlId": "10.4",
                "title": "10.4",
                "description": "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.\r\n\r\nNote: One example of time synchronization technology is Network Time Protocol (NTP).",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "f5e7471f-af50-4487-8b3d-f0200d8370f7",
                "controlId": "10.4.1",
                "title": "10.4.1",
                "description": "10.4.1 Critical systems have the correct and consistent time.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "66250f28-1cb6-4a34-a694-227463c35298",
                "controlId": "10.4.2",
                "title": "10.4.2",
                "description": "10.4.2 Time data is protected.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "86f68bbc-f329-42d1-a358-d462a3a146bf",
                "controlId": "10.4.3",
                "title": "10.4.3",
                "description": "10.4.3 Time settings are received from industry-accepted time sources.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "2c74118b-02f0-4c3f-9dff-c5e2ecaf27c1",
                "controlId": "10.5",
                "title": "10.5",
                "description": "10.5 Secure audit trails so they cannot be altered.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": " ",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "d8077612-5de0-4923-848a-292ffe249a0b",
                "controlId": "10.5.1",
                "title": "10.5.1",
                "description": "10.5.1 Limit viewing of audit trails to those with a job-related need.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "aaddb297-3ad1-4972-a2ff-d4aba7e77c85",
                "controlId": "10.5.2",
                "title": "10.5.2",
                "description": "10.5.2 Protect audit trail files from unauthorized modifications.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "3e53c4e4-cbaa-4e3a-9298-00b5a985af47",
                "controlId": "10.5.3",
                "title": "10.5.3",
                "description": "10.5.3 Promptly back up audit trail files to a centralized log server or media that is difficult to alter.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "6dee943f-8d74-4299-93c3-8b2d6ea95629",
                "controlId": "10.5.4",
                "title": "10.5.4",
                "description": "10.5.4 Write logs for external-facing technologies onto a secure, centralized, internal log server or media device.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "e02a4701-7b68-47fe-873a-7b7420905c24",
                "controlId": "10.5.5",
                "title": "10.5.5",
                "description": "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).",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "5d38b131-25de-4436-a03c-ed2a6a76be37",
                "controlId": "10.6",
                "title": "10.6",
                "description": "10.6 Review logs and security events for all system components to identify anomalies or suspicious activity.\r\n\r\nNote: Log harvesting, parsing, and alerting tools may be used to meet this Requirement.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": " ",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "47e8c6e3-0a26-4dae-8380-46cd1b31af4a",
                "controlId": "10.6.1",
                "title": "10.6.1",
                "description": "10.6.1 Review the following at least daily:\r\n\u2022  All security events\r\n\u2022  Logs of all system components that store, process, or transmit CHD and/or SAD\r\n\u2022  Logs of all critical system components\r\n\u2022  Logs of all servers and system components that perform security functions (for example, firewalls, intrusion-detection systems/intrusion-prevention systems (IDS/IPS), authentication servers, e-commerce redirection servers, etc.).",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "6ccc21af-9177-4bfd-93a9-8feda46f7418",
                "controlId": "10.6.2",
                "title": "10.6.2",
                "description": "10.6.2 Review logs of all other system components periodically based on the organization\u2019s policies and risk management strategy, as determined by the organization\u2019s annual risk assessment. ",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "58872ad2-420c-4c30-b7b1-4608e9ce085b",
                "controlId": "10.6.3",
                "title": "10.6.3",
                "description": "10.6.3 Follow up exceptions and anomalies identified during the review process.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "9ce9ff00-c246-4e28-b0db-efc8bc9f3ab4",
                "controlId": "10.7",
                "title": "10.7",
                "description": "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 backup).",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "a244890e-58dd-4dff-ba9e-77f00f705570",
                "controlId": "10.8",
                "title": "10.8",
                "description": "10.8   Additional requirement for service providers only: Implement a process for the timely detection and reporting of failures of critical security control systems, including but not limited to failure of: \r\n\u2022 Firewalls \r\n\u2022 IDS/IPS \r\n\u2022 FIM \r\n\u2022 Anti-virus \r\n\u2022 Physical access controls \r\n\u2022 Logical access controls \r\n\u2022 Audit logging mechanisms \r\n\u2022 Segmentation controls (if used) ",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "f02424c3-3ac2-4f3f-8244-d7d3635b5934",
                "controlId": "10.8.1",
                "title": "10.8.1",
                "description": "10.8.1 Additional requirement for service providers only: Respond to failures of any critical security controls in a timely manner. Processes for responding to failures in security controls must include: \r\n\u2022 Restoring security functions \r\n\u2022 Identifying and documenting the duration (date and time start to end) of the security failure \r\n\u2022 Identifying and documenting cause(s) of failure, including root cause, and documenting remediation required to address root cause \r\n\u2022 Identifying and addressing any security issues that arose during the failure \r\n\u2022 Performing a risk assessment to determine whether further actions are required as a result of the security failure \r\n\u2022 Implementing controls to prevent cause of failure from reoccurring \r\n\u2022 Resuming monitoring of security controls ",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "7cc941b8-3ec5-4f70-8368-ca0109a2766d",
                "controlId": "10.9",
                "title": "10.9",
                "description": "10.9 Ensure that security policies and operational procedures for monitoring all access to network resources and cardholder data are documented, in use, and known to all affected parties.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 10: Track and monitor all access to network resources and cardholder data",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "c1d04cd7-a8a9-43aa-b24b-e9d008a73d22",
                "controlId": "11.1",
                "title": "11.1",
                "description": "11.1 Implement processes to test for the presence of wireless access points (802.11), and detect and identify all authorized and unauthorized wireless access points on a quarterly basis.\r\n\r\nNote: Methods that may be used in the process include but are not limited to wireless network scans, physical/logical inspections of system components and infrastructure, network access control (NAC), or wireless IDS/IPS.  Whichever methods are used, they must be sufficient to detect and identify both authorized and unauthorized devices.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 11: Regularly test security systems and processes",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "3cd877d0-a8d3-46de-8925-63cd32f38c29",
                "controlId": "11.1.1",
                "title": "11.1.1",
                "description": "11.1.1 Maintain an inventory of authorized wireless access points including a documented business justification.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 11: Regularly test security systems and processes",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "7df95dc4-65d9-4e20-9fec-77a0e779a501",
                "controlId": "11.1.2",
                "title": "11.1.2",
                "description": "11.1.2 Implement incident response procedures in the event unauthorized wireless access points are detected.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 11: Regularly test security systems and processes",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "a5fb332b-0d87-4209-afb6-dd162ec6672b",
                "controlId": "11.2",
                "title": "11.2",
                "description": "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).\r\n\r\nNote: Multiple scan reports can be combined for the quarterly scan process to show that all systems were scanned and all applicable vulnerabilities have been addressed. Additional documentation may be required to verify non-remediated vulnerabilities are in the process of being addressed. \r\n\r\nFor initial PCI DSS compliance, it is not required that four quarters of passing scans be completed if the assessor verifies 1) the most recent scan result was a passing scan, 2) the entity has documented policies and procedures requiring quarterly scanning, and 3) vulnerabilities noted in the scan results have been corrected as shown in a re-scan(s). For subsequent years after the initial PCI DSS review, four quarters of passing scans must have occurred.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 11: Regularly test security systems and processes",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "5c801324-03a8-4b51-a190-bdbc6b61c35c",
                "controlId": "11.2.1",
                "title": "11.2.1",
                "description": "11.2.1 Perform quarterly internal vulnerability scans. Address vulnerabilities and perform rescans to verify all \u201chigh risk\u201d vulnerabilities are resolved in accordance with the entity\u2019s vulnerability ranking (per Requirement 6.1). Scans must be performed by qualified personnel.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 11: Regularly test security systems and processes",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "6f2ad387-59c6-4d79-90c7-c1387c085132",
                "controlId": "11.2.2",
                "title": "11.2.2",
                "description": "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). Perform rescans as needed, until passing scans are achieved.\r\n\r\nNote: Quarterly external vulnerability scans must be performed by an Approved Scanning Vendor (ASV), approved by the Payment Card Industry Security Standards Council (PCI SSC). Refer to the ASV Program Guide published on the PCI SSC website for scan customer responsibilities, scan preparation, etc.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 11: Regularly test security systems and processes",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "f416a4cd-3121-46a3-a6a2-a8b9446738d4",
                "controlId": "11.2.3",
                "title": "11.2.3",
                "description": "11.2.3 Perform internal and external scans, and rescans as needed, after any significant change. Scans must be performed by qualified personnel.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 11: Regularly test security systems and processes",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "7e5d4cad-cb2d-48d6-8054-954a4e0fe2fb",
                "controlId": "11.3",
                "title": "11.3",
                "description": "11.3 Implement a methodology for penetration testing that includes the following:\r\n\u2022  Is based on industry-accepted penetration testing approaches (for example, NIST SP800-115)\r\n\u2022  Includes coverage for the entire CDE perimeter and critical systems\r\n\u2022  Includes testing from both inside and outside the network\r\n\u2022  Includes testing to validate any segmentation and scope-reduction controls\r\n\u2022  Defines application-layer penetration tests to include, at a minimum, the vulnerabilities listed in Requirement 6.5\r\n\u2022  Defines network-layer penetration tests to include components that support network functions as well as operating systems\r\n\u2022  Includes review and consideration of threats and vulnerabilities experienced in the last 12 months\r\n\u2022  Specifies retention of penetration testing results and remediation activities results.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 11: Regularly test security systems and processes",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "d01a84fb-eb1f-4215-a7a9-09819fa78962",
                "controlId": "11.3.1",
                "title": "11.3.1",
                "description": "11.3.1 Perform external penetration testing at least annually 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).",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 11: Regularly test security systems and processes",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "ec424381-5585-4131-bc8a-df3d868f9111",
                "controlId": "11.3.2",
                "title": "11.3.2",
                "description": "11.3.2 Perform internal penetration testing at least annually 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). ",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 11: Regularly test security systems and processes",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "9e662205-9cf1-4138-b29a-0ec1f9c94850",
                "controlId": "11.3.3",
                "title": "11.3.3",
                "description": "11.3.3 Exploitable vulnerabilities found during penetration testing are corrected and testing is repeated to verify the corrections.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 11: Regularly test security systems and processes",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "8425a0c6-f7d9-4574-b327-caadd7b09eef",
                "controlId": "11.3.4",
                "title": "11.3.4",
                "description": "11.3.4 If segmentation is used to isolate the CDE from other networks, perform penetration tests at least annually and after any changes to segmentation controls/methods to verify that the segmentation methods are operational and effective, and isolate all out-of-scope systems from systems in the CDE.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 11: Regularly test security systems and processes",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "353258d1-86e1-44ef-b3f7-a455924f1d1b",
                "controlId": "11.3.4.1",
                "title": "11.3.4.1",
                "description": "11.3.4.1 Additional requirement for service providers only:  If segmentation is used, confirm PCI DSS scope by performing penetration testing on segmentation controls at least every six months and after any changes to segmentation controls/methods. \r\n",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 11: Regularly test security systems and processes",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "1cc0b6a2-b1ca-414a-b822-54fca1d47736",
                "controlId": "11.4",
                "title": "11.4",
                "description": "11.4 Use intrusion-detection and/or intrusion-prevention techniques to detect and/or prevent intrusions into the network. Monitor all traffic at the perimeter of the cardholder data environment as well as at critical points in the cardholder data environment, and alert personnel to suspected compromises.\r\nKeep all intrusion-detection and prevention engines, baselines, and signatures up to date.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 11: Regularly test security systems and processes",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "764e7186-9085-4698-af48-aa5cb13cf1f0",
                "controlId": "11.5",
                "title": "11.5",
                "description": "11.5 Deploy a change-detection mechanism (for example, file-integrity monitoring tools) to alert personnel to unauthorized modification (including changes, additions, and deletions) of critical system files, configuration files, or content files; and configure the software to perform critical file comparisons at least weekly.\r\n\r\nNote: For change-detection purposes, critical files are usually those that do not regularly change, but the modification of which could indicate a system compromise or risk of compromise. Change-detection mechanisms such as file-integrity monitoring products usually come pre-configured with critical files for the related operating system. Other critical files, such as those for custom applications, must be evaluated and defined by the entity (that is, the merchant or service provider).",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 11: Regularly test security systems and processes",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "fde45078-4127-4c3b-b04e-198cd65be4ae",
                "controlId": "11.5.1",
                "title": "11.5.1",
                "description": "11.5.1 Implement a process to respond to any alerts generated by the change-detection solution.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 11: Regularly test security systems and processes",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "93eb8a8d-e1ae-49d3-a5b8-c3a976817369",
                "controlId": "11.6",
                "title": "11.6",
                "description": "11.6 Ensure that security policies and operational procedures for security monitoring and testing are documented, in use, and known to all affected parties.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 4 Monitor and control access to your systems.  Controls for this milestone allow you to detect the who, what, when, and how concerning who is accessing your network and cardholder data environment.",
                "family": "Requirement 11: Regularly test security systems and processes",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "ae3c3864-aaff-410c-9e19-592183bc4a39",
                "controlId": "12.1",
                "title": "12.1",
                "description": "12.1 Establish, publish, maintain, and disseminate a security policy.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "f7223d0b-e471-462e-ba48-db9e0b5cbbf4",
                "controlId": "12.1.1",
                "title": "12.1.1",
                "description": "12.1.1 Review the security policy at least annually and update the policy when the environment changes.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "5daa7505-9b1f-4adf-9892-3f9bdb8e229f",
                "controlId": "12.2",
                "title": "12.2",
                "description": "12.2 Implement a risk-assessment process that:\r\n\u2022  Is performed at least annually and upon significant changes to the environment (for example, acquisition, merger, relocation, etc.),\r\n\u2022  Identifies critical assets, threats, and vulnerabilities, and\r\n\u2022  Results in a formal, documented analysis of risk.\r\n\r\nExamples of risk-assessment methodologies include but are not limited to OCTAVE, ISO 27005 and NIST SP 800-30.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 1 Remove sensitive authentication data and limit data retention. This milestone targets a key area of risk for entities that have been compromised. Remember \u2013 if sensitive authentication data and other cardholder data are not stored, the effects of a compromise will be greatly reduced. If you don't need it, don't store it",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "1d73166e-a90b-468f-a4d8-92866d1ea8d0",
                "controlId": "12.3",
                "title": "12.3",
                "description": "12.3 Develop usage policies for critical technologies and define proper use of these technologies.\r\n\r\n  Note: Examples of critical technologies include, but are not limited to, remote access and wireless technologies, laptops, tablets, removable electronic media, e-mail usage and Internet usage.\r\n\r\nEnsure these usage policies require the following:",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "47cd5c8b-a172-4b8c-9844-b7d4a0602e91",
                "controlId": "12.3.1",
                "title": "12.3.1",
                "description": "12.3.1 Explicit approval by authorized parties",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "3ffe0951-ce3d-46b9-bc47-628a6554d115",
                "controlId": "12.3.2",
                "title": "12.3.2",
                "description": "12.3.2 Authentication for use of the technology",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "ba36c015-5c68-43f2-b378-50e6c42e4e41",
                "controlId": "12.3.3",
                "title": "12.3.3",
                "description": "12.3.3 A list of all such devices and personnel with access",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "612f7f17-6299-4d92-b253-bec84ec4989d",
                "controlId": "12.3.4",
                "title": "12.3.4",
                "description": "12.3.4 A method to accurately and readily determine owner, contact information, and purpose (for example, labeling, coding, and/or inventorying of devices)",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "600dd0af-a8a3-496b-b249-ac482e0c8802",
                "controlId": "12.3.5",
                "title": "12.3.5",
                "description": "12.3.5 Acceptable uses of the technology",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "d59af299-c05f-4985-87e6-5f3ce80cf5b2",
                "controlId": "12.3.6",
                "title": "12.3.6",
                "description": "12.3.6 Acceptable network locations for the technologies",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "2c5a4559-60c0-4b43-88b5-1d465aecdf50",
                "controlId": "12.3.7",
                "title": "12.3.7",
                "description": "12.3.7 List of company-approved products",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "8d77643f-2bee-4628-a0f8-bd077c34b8f2",
                "controlId": "12.3.8",
                "title": "12.3.8",
                "description": "12.3.8 Automatic disconnect of sessions for remote-access technologies after a specific period of inactivity",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "5b766369-2b94-4dd9-894b-bcf5ef5ec948",
                "controlId": "12.3.9",
                "title": "12.3.9",
                "description": "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",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "7764bcfc-2bcb-43f9-87d2-3b78c0888dd1",
                "controlId": "12.3.10",
                "title": "12.3.10",
                "description": "12.3.10 For personnel accessing cardholder data via remote-access technologies, prohibit the copying, moving, and storage of cardholder data onto local hard drives and removable electronic media, unless explicitly authorized for a defined business need.\r\nWhere there is an authorized business need, the usage policies must require the data be protected in accordance with all applicable PCI DSS Requirements. ",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "249cbc7e-ca70-4495-8131-e6fac4fca15a",
                "controlId": "12.4",
                "title": "12.4",
                "description": "12.4 Ensure that the security policy and procedures clearly define information security responsibilities for all personnel.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "71ec5da9-a908-4570-8649-15f0c9e1202c",
                "controlId": "12.4.1",
                "title": "12.4.1",
                "description": "12.4.1  Additional requirement for service providers only:  Executive management shall establish responsibility for the protection of cardholder data and a PCI DSS compliance program to include: \r\n\u2022 Overall accountability for maintaining PCI DSS compliance \r\n\u2022 Defining a charter for a PCI DSS compliance program and communication to executive management ",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "1294723b-10cc-4938-8648-87926d7f8e4e",
                "controlId": "12.5",
                "title": "12.5",
                "description": "12.5 Assign to an individual or team the following information security management responsibilities:",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "e415544f-d7d1-4bd5-a614-d1719ee392c6",
                "controlId": "12.5.1",
                "title": "12.5.1",
                "description": "12.5.1 Establish, document, and distribute security policies and procedures.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "d1894e86-440a-4a73-9021-21882573645f",
                "controlId": "12.5.2",
                "title": "12.5.2",
                "description": "12.5.2 Monitor and analyze security alerts and information, and distribute to appropriate personnel.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "3532861b-549f-4b36-a9ea-9f466d7721da",
                "controlId": "12.5.3",
                "title": "12.5.3",
                "description": "12.5.3 Establish, document, and distribute security incident response and escalation procedures to ensure timely and effective handling of all situations.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "b21e7e3b-59b4-4f7f-a810-8b3f61e74d64",
                "controlId": "12.5.4",
                "title": "12.5.4",
                "description": "12.5.4 Administer user accounts, including additions, deletions, and modifications.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "bc3811e2-d4e0-4b3f-8f10-6121e97bf4ac",
                "controlId": "12.5.5",
                "title": "12.5.5",
                "description": "12.5.5 Monitor and control all access to data.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "6b2e803e-3d6d-4801-bfbb-a0807fee3796",
                "controlId": "12.6",
                "title": "12.6",
                "description": "12.6 Implement a formal security awareness program to make all personnel aware of the cardholder data security policy and procedures.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "e372498a-2d6d-427a-bab4-070425e5cffd",
                "controlId": "12.6.1",
                "title": "12.6.1",
                "description": "12.6.1 Educate personnel upon hire and at least annually.\r\n\r\nNote: Methods can vary depending on the role of the personnel and their level of access to the cardholder data.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "618a5c73-7dbe-4b4d-b9df-8d2c8434dcb4",
                "controlId": "12.6.2",
                "title": "12.6.2",
                "description": "12.6.2 Require personnel to acknowledge at least annually that they have read and understood the security policy and procedures.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "55131303-af65-4c50-b625-09f0c7e62cc5",
                "controlId": "12.7",
                "title": "12.7",
                "description": "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.)\r\n\r\nNote: For those potential personnel to be hired for certain positions such as store cashiers who only have access to one card number at a time when facilitating a transaction, this requirement is a recommendation only.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "0d6c51b7-df2d-4359-ae3e-c2581bd27128",
                "controlId": "12.8",
                "title": "12.8",
                "description": "12.8 Maintain and implement policies and procedures to manage service providers, with whom cardholder data is shared, or that could affect the security of cardholder data, as follows ",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "7ece55dc-67dc-454c-8125-0254ab72e8e1",
                "controlId": "12.8.1",
                "title": "12.8.1",
                "description": "12.8.1 Maintain a list of service providers including a description of the service provided.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "5b1cd19f-08d8-4148-b7cc-32a0bd42bf2e",
                "controlId": "12.8.2",
                "title": "12.8.2",
                "description": "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 or otherwise store, process or transmit on behalf of the customer, or to the extent that they could impact the security of the customer\u2019s cardholder data environment.\r\n\r\nNote: The exact wording of an acknowledgement will depend on the agreement between the two parties, the details of the service being provided, and the responsibilities assigned to each party. The acknowledgement does not have to include the exact wording provided in this requirement.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "0307e84b-66ab-4f63-a940-e304ab8b922a",
                "controlId": "12.8.3",
                "title": "12.8.3",
                "description": "12.8.3 Ensure there is an established process for engaging service providers including proper due diligence prior to engagement.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "3df5becd-f7f0-4028-b694-f5620b3de5ee",
                "controlId": "12.8.4",
                "title": "12.8.4",
                "description": "12.8.4 Maintain a program to monitor service providers\u2019 PCI DSS compliance status at least annually.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "9f93a1b3-d4d8-4a37-8156-f5371f62e487",
                "controlId": "12.8.5",
                "title": "12.8.5",
                "description": "12.8.5 Maintain information about which PCI DSS requirements are managed by each service provider, and which are managed by the entity.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "72f43887-8fdb-44fe-b4e0-d4a2961aa5c8",
                "controlId": "12.9",
                "title": "12.9",
                "description": "12.9 Additional requirement for service providers only: Service providers acknowledge in writing to customers that they are responsible for the security of cardholder data the service provider possesses or otherwise stores, processes, or transmits on behalf of the customer, or to the extent that they could impact the security of the customer\u2019s cardholder data environment.\r\n\r\nNote: The exact wording of an acknowledgement will depend on the agreement between the two parties, the details of the service being provided, and the responsibilities assigned to each party. The acknowledgement does not have to include the exact wording provided in this requirement.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "4d554cb7-e46a-49fc-a10a-c2a1a8b14dfa",
                "controlId": "12.10",
                "title": "12.10",
                "description": "12.10 Implement an incident response plan. Be prepared to respond immediately to a system breach.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": " ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "731b89e8-abfe-4618-94e6-cfc25988a814",
                "controlId": "12.10.1",
                "title": "12.10.1",
                "description": "12.10.1 Create the incident response plan to be implemented in the event of system breach. Ensure the plan addresses the following, at a minimum:\r\n\u2022  Roles, responsibilities, and communication and contact strategies in the event of a compromise including notification of the payment brands, at a minimum\r\n\u2022  Specific incident response procedures\r\n\u2022  Business recovery and continuity procedures\r\n\u2022  Data backup processes\r\n\u2022  Analysis of legal requirements for reporting compromises\r\n\u2022  Coverage and responses of all critical system components\r\n\u2022  Reference or inclusion of incident response procedures from the payment brands.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "2ba151f7-d9ea-4267-91ed-16fc02f1b32a",
                "controlId": "12.10.2",
                "title": "12.10.2",
                "description": "12.10.2 Review and test the plan, including all elements listed in Requirement 12.10.1, at least annually.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "3dec02b6-35fb-4fc9-a13e-6e02f52066ea",
                "controlId": "12.10.3",
                "title": "12.10.3",
                "description": "12.10.3 Designate specific personnel to be available on a 24/7 basis to respond to alerts.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "c5b4d665-9389-4cad-b5aa-950678ac5425",
                "controlId": "12.10.4",
                "title": "12.10.4",
                "description": "12.10.4 Provide appropriate training to staff with security breach response responsibilities.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "9d9b46e4-c639-4f2e-9e44-387a1ea19c05",
                "controlId": "12.10.5",
                "title": "12.10.5",
                "description": "12.10.5 Include alerts from security monitoring systems, including but not limited to intrusion-detection, intrusion-prevention, firewalls, and file-integrity monitoring systems.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "303a9018-7615-4412-be86-7f0213b80af0",
                "controlId": "12.10.6",
                "title": "12.10.6",
                "description": "12.10.6 Develop a process to modify and evolve the incident response plan according to lessons learned and to incorporate industry developments.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "c7f221a5-2c69-4938-b3b4-8eded408639c",
                "controlId": "12.11",
                "title": "12.11",
                "description": "12.11  Additional requirement for service providers only: Perform reviews at least quarterly to confirm personnel are following security policies and operational procedures. Reviews must cover the following processes: \r\n\u2022 Daily log reviews \r\n\u2022 Firewall rule-set reviews \r\n\u2022 Applying configuration standards to new systems \r\n\u2022 Responding to security alerts \r\n\u2022 Change management processes \r\n",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "3e7a4cb3-6188-4a8b-b798-2aa43a297af9",
                "controlId": "12.11.1",
                "title": "12.11.1",
                "description": "12.11.1 Additional requirement for service providers only:  Maintain documentation of quarterly review process to include: \r\n\u2022 Documenting results of the reviews \r\n\u2022 Review and sign off of results by personnel assigned responsibility for the PCI DSS compliance program  ",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 6 Finalize remaining compliance efforts, and ensure all controls are in place.  The intent of Milestone Six is to complete PCI DSS requirements, and to finalize all remaining related policies, procedures, and processes needed to protect the cardholder data environment. ",
                "family": "Requirement 12: Maintain a policy that addresses information security for all personnel",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "ef429406-3fb7-4112-bdf4-8ba77ccd529e",
                "controlId": "A1",
                "title": "A1",
                "description": "A1 Protect each entity\u2019s (that is, merchant, service provider, or other entity) hosted environment and data, per A1.1 through A1.4:\r\n\r\nA hosting provider must fulfill these requirements as well as all other relevant sections of the PCI DSS.\r\n\r\nNote: Even though a hosting provider may meet these requirements, the compliance of the entity that uses the hosting provider is not guaranteed. Each entity must comply with the PCI DSS and validate compliance as applicable.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Appendix A1: Additional PCI DSS Requirements for Shared Hosting Providers",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "56224ad2-5cab-4537-bbcf-1f4431351f3a",
                "controlId": "A1.1",
                "title": "A1.1",
                "description": "A1.1 Ensure that each entity only runs processes that have access to that entity\u2019s cardholder data environment.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Appendix A1: Additional PCI DSS Requirements for Shared Hosting Providers",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "1ec32253-13ce-45e1-b183-acbe5a430d2f",
                "controlId": "A1.2",
                "title": "A1.2",
                "description": "A1.2 Restrict each entity\u2019s access and privileges to its own cardholder data environment only.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Appendix A1: Additional PCI DSS Requirements for Shared Hosting Providers",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "afd2abbc-6cf1-461e-8883-19f953ec9236",
                "controlId": "A1.3",
                "title": "A1.3",
                "description": "A1.3 Ensure logging and audit trails are enabled and unique to each entity\u2019s cardholder data environment and consistent with PCI DSS Requirement 10.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Appendix A1: Additional PCI DSS Requirements for Shared Hosting Providers",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "a100c649-a979-49d1-91ab-83e9b7219829",
                "controlId": "A1.4",
                "title": "A1.4",
                "description": "A1.4 Enable processes to provide for timely forensic investigation in the event of a compromise to any hosted merchant or service provider.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 3 Secure payment card applications.  This milestone targets controls for applications, application processes, and application servers. Weaknesses in these areas offer easy prey for compromising systems and obtaining access to cardholder data.",
                "family": "Appendix A1: Additional PCI DSS Requirements for Shared Hosting Providers",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "1398bd81-73d4-4a64-ba0b-bdf30d3c1cad",
                "controlId": "A2",
                "title": "A2",
                "description": "Appendix A2: Additional PCI DSS Requirements for Entities using SSL/Early TLS for Card-Present POS POI Terminal Connections\r\n\r\nNote: SSL/early TLS  may not be used as a security control, except by POS POI terminals that are verified as not being susceptible to known exploits and the termination points to which they connect, as defined in this Appendix.",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": " ",
                "family": "Appendix A2: Additional PCI DSS Requirements for Entities using SSL/Early TLS for Card-Present POS POI Terminal Connections\r\n\r\nNote: SSL/early TLS  may not be used as a security control, except by POS POI terminals that are verified as not being susceptible to known exploits and the termination points to which they connect, as defined in this Appendix.",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "c9aa41a3-b231-4b74-9b72-2cd34e9668c1",
                "controlId": "A2.1",
                "title": "A2.1",
                "description": "A2.1 Where POS POI terminals (at the merchant or payment acceptance location) use SSL and/or early TLS, the entity must confirm the devices are not susceptible to any known exploits for those protocols.\r\n\r\nNote:  This requirement is intended to apply to the entity with the POS POI terminal, such as a merchant.  This requirement is not intended for service providers who serve as the termination or connection point to those POS POI terminals. Requirements A2.2 and A2.3 apply to POS POI service providers. ",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Appendix A2: Additional PCI DSS Requirements for Entities using SSL/Early TLS for Card-Present POS POI Terminal Connections\r\n\r\nNote: SSL/early TLS  may not be used as a security control, except by POS POI terminals that are verified as not being susceptible to known exploits and the termination points to which they connect, as defined in this Appendix.",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "9c3ba780-7254-4637-b884-becda0fd461c",
                "controlId": "A2.2",
                "title": "A2.2",
                "description": "A2.2 Requirement for Service Providers Only: All service providers with existing connection points to POS POI terminals referred to in A2.1 that use SSL and/or early TLS must have a formal Risk Mitigation and Migration Plan in place.  ",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Appendix A2: Additional PCI DSS Requirements for Entities using SSL/Early TLS for Card-Present POS POI Terminal Connections\r\n\r\nNote: SSL/early TLS  may not be used as a security control, except by POS POI terminals that are verified as not being susceptible to known exploits and the termination points to which they connect, as defined in this Appendix.",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            },
            {
                "uuid": "9747ad6b-7627-41c5-b902-34fcdc2a071d",
                "controlId": "A2.3",
                "title": "A2.3",
                "description": "A2.3 Requirement for Service Providers Only: All service providers must provide a secure service offering. ",
                "references": "",
                "relatedControls": "",
                "subControls": "",
                "enhancements": "Milestone 2 Protect systems and networks, and be prepared to respond to a system breach.  This milestone targets controls for points of access to most compromises, and the processes for responding.",
                "family": "Appendix A2: Additional PCI DSS Requirements for Entities using SSL/Early TLS for Card-Present POS POI Terminal Connections\r\n\r\nNote: SSL/early TLS  may not be used as a security control, except by POS POI terminals that are verified as not being susceptible to known exploits and the termination points to which they connect, as defined in this Appendix.",
                "mappings": "",
                "assessmentPlan": "",
                "weight": 0,
                "catalogueID": 319,
                "practiceLevel": ""
            }
        ]
    }
}