Payment Card Industry Data Security Standard v4.0.1 โ SP 800-53 Coverage
How well do NIST SP 800-53 Rev 5 controls address each PCI DSS v4.0.1 requirement? This analysis maps from framework clauses back to SP 800-53, with expert coverage weightings and gap identification.
Clause-by-Clause Analysis
Sorted by clause1.1.1 Policies and procedures for network security
Rationale
SC-01 and CM-01 ask for documented policies and procedures for communications protection and for configuration management, shared with the people who need them and reviewed on a set cycle. Together they govern how network security controls are set up and changed.
Gaps
PCI DSS asks for the procedures to be in daily use and known to all who apply them. Check that staff follow them.
1.1.2 Roles and duties for network security
Rationale
SC-01 and CM-01 ask the communications protection and configuration management policies to set out roles and responsibilities. PS-09 writes those security duties into the position descriptions of the people who run network security controls.
Gaps
PCI DSS asks for the people given these duties to understand them. Confirm that each one does, for example with a briefing or a signed acknowledgement.
1.2.1 Written standards for network security control rulesets
Rationale
CM-02 holds a documented, current baseline for each network security control and keeps it under configuration control. CM-06 sets restrictive settings from common secure configurations, applies them and approves any deviation. SC-07 arranges boundary devices to fit the security architecture, and SC-07(04) sets a traffic flow policy for each managed interface, which is its ruleset.
Gaps
PCI DSS asks for standards that govern the rules themselves as well as the device settings. Write ruleset standards for each kind of network security control in use.
1.2.2 Change control for network connections and device settings
Rationale
CM-03 names the types of change under configuration control, then reviews, approves, records and implements each one. CM-04 analyses the security impact of a change before it goes ahead.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
1.2.3 Network diagram of every CDE connection, wireless included
Rationale
PL-02 asks the system security plan to describe the operating environment and its connections to other systems, and to stay current as they change. CA-09 authorises internal connections and documents each one's interface, security requirements and the information it carries.
Gaps
PCI DSS asks for an accurate network diagram that shows every connection into and out of the CDE, wireless networks included. Draw one and keep it current.
1.2.4 Data-flow diagram of every path account data takes
Rationale
CM-12 records where account data is processed and stored, on which components, and documents any change to those locations. CM-13 maps the system's data actions and the components involved. SP 800-53 writes it for personal data, and the same map can trace account data.
Gaps
PCI DSS asks for a diagram that traces account data between systems and network segments. Redraw it whenever the environment changes.
1.2.5 Business need for each allowed service, protocol and port
Rationale
CM-07 limits each system to essential capabilities and prohibits or restricts the ports, protocols and services the organisation names. SC-07(04) records each exception to the traffic flow policy with its business need and how long it lasts. SC-07(05) denies all other traffic by default.
Gaps
PCI DSS asks the organisation to approve each allowed service, protocol and port and record its business need. Keep the approver and the reason with each entry.
1.2.6 Network safeguards for insecure services and ports in use
Rationale
CM-07 restricts the ports, protocols and services the organisation names as insecure, and CM-07(01) reviews systems for them on a set cycle. CM-06 hardens the settings of whatever stays in use, and it documents and approves each deviation.
Gaps
PCI DSS asks the organisation to assess the risk of each insecure service, protocol or port in use and add features that reduce it. Record the protection chosen for each one.
1.2.7 Six-monthly review of network security control settings
Rationale
CM-02 reviews and updates the baseline of each network security control at a frequency the organisation sets. CM-07(01) looks for unneeded or insecure ports, protocols and services on a set cycle and removes them. SC-07(04) reviews the exceptions to each traffic flow policy and drops those that have lost their business need.
Gaps
PCI DSS asks for this review at least every six months. Set that interval in CM-02, CM-07(01) and SC-07(04).
1.2.8 Protected configuration files that match live settings
Rationale
AC-03 enforces approved access to stored configuration files, scripts and backups. CM-05 limits who can change network security control settings and the files that hold them. CM-02 keeps a current baseline under configuration control, the reference that stored copies and live settings should both match.
Gaps
PCI DSS asks for the stored copies of each configuration, backups and scripts included, to match what is live. Compare them with the running settings on a regular schedule and correct any drift.
1.3.1 Deny-by-default filtering of traffic into the CDE
Rationale
AC-04 enforces approved flow control policies, so only authorised traffic enters the CDE. SC-07 monitors and controls traffic at the CDE's managed interfaces. SC-07(05) denies traffic by default and allows it by exception, and SC-07(11) routes incoming traffic only from authorised sources to authorised destinations.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
1.3.2 Deny-by-default filtering of traffic leaving the CDE
Rationale
AC-04 enforces approved flow control policies for traffic leaving the CDE. SC-07 controls traffic at the CDE's managed interfaces, and SC-07(05) denies it by default and allows it by exception. SC-07(10) adds measures that prevent the exfiltration of information.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
1.3.3 Filtering between every wireless network and the CDE
Rationale
AC-18 sets configuration and connection requirements for each type of wireless access and authorises it before connections start. AC-04 lets only approved wireless flows into the CDE. SC-07 places managed interfaces between wireless segments and the CDE, and SC-07(05) denies traffic by default.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
1.4.1 Network security controls at every untrusted boundary 95%
Rationale
SC-07 monitors and controls traffic at external and key internal managed interfaces. It connects to outside networks only through boundary protection devices, and it keeps publicly accessible components in separate subnetworks.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
Mapped Controls
1.4.2 Inbound rules for public services and stateful replies
Rationale
AC-04 enforces approved flows from untrusted to trusted networks. SC-07 keeps publicly accessible components in a separate subnetwork. SC-07(05) denies traffic by default, and SC-07(11) routes incoming traffic only from authorised sources to authorised destinations.
Gaps
PCI DSS also lets in replies to sessions that systems inside the trusted network started. Use stateful filtering so that only those replies come back through the boundary.
1.4.3 Blocking spoofed source addresses at the network edge
Rationale
SC-07(11) routes incoming traffic only from authorised sources to authorised destinations. Its guidance uses source address validation to drop illegal addresses and internal-only ones arriving from outside. SI-04 monitors for attacks and their indicators, and SI-04(04) watches inbound traffic against criteria the organisation sets, such as forged source addresses.
Gaps
PCI DSS asks the organisation to stop packets with forged source addresses at the edge of the trusted network. Configure ingress filters that drop outside packets claiming internal or reserved addresses.
1.4.4 Cardholder data stores reachable only from trusted networks
Rationale
AC-04 blocks flows from untrusted networks straight to the systems that store cardholder data. SC-07 keeps internal components apart from public subnetworks. SC-07(21) isolates chosen components behind boundary protection, and SC-07(28) prohibits their direct connection to a public network.
Gaps
PCI DSS covers every component that stores cardholder data, cloud databases included. Place each one behind the internal boundary, reachable only from trusted networks.
1.4.5 Keeping internal addresses and routing details private 75%
Rationale
SC-07 guards the managed interfaces at the boundary. SC-07(16) prevents discovery of the components that form a managed interface, for example by address translation or by leaving their addresses out of DNS. SC-07(04) blocks unauthorised exchange of control plane traffic, such as routing, with outside networks.
Gaps
PCI DSS limits internal addressing and routing details to authorised parties. Keep them out of public DNS and error messages, and share network documents only with approved recipients.
Mapped Controls
1.5.1 Locked-down devices that reach the CDE and untrusted networks
Rationale
AC-19 sets configuration and connection requirements for organisation-controlled mobile devices and authorises each connection. AC-20 sets terms and required controls for personally owned and other external devices. CM-06 defines the mandatory security settings and approves each deviation. AC-06(10) keeps non-privileged users from disabling or altering security controls. SC-07(12) adds host-based protection such as personal firewalls, and SC-07(07) prevents split tunnelling.
Gaps
PCI DSS lets users alter these controls only with documented management approval, case by case and for a set period. Keep the controls running at all other times.
2.1.1 Policies and procedures for secure configuration 85%
Rationale
CM-01 asks for a documented configuration management policy and procedures, shared with the people who need them and reviewed and updated on a set cycle. They govern how every system component is configured securely.
Gaps
PCI DSS asks for the procedures to be in daily use and known to all who apply them. Check that staff follow them.
Mapped Controls
2.1.2 Roles and duties for secure configuration
Rationale
CM-01 asks the configuration management policy to set out roles and responsibilities. PS-09 writes those security duties into the position descriptions of the people who configure system components.
Gaps
PCI DSS asks for the people given these duties to understand them. Confirm that each one does, for example with a briefing or a signed acknowledgement.
2.2.1 Hardening standards for every system component
Rationale
CM-06 takes settings from common secure configurations, such as hardening guides, applies them to each component and approves any deviation. CM-06(01) can manage and verify those settings by automated means. CM-02 keeps a current baseline for each system and updates it on a set cycle and when components are installed or upgraded.
Gaps
PCI DSS asks the organisation to update the standards as new vulnerabilities come to light. Check each new system against them when it goes into production.
2.2.2 Removing or securing vendor default accounts
Rationale
AC-02 defines the account types allowed and disables or removes unneeded accounts. IA-05 changes default authenticators, such as vendor passwords, before first use.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
2.2.3 Separating functions with different security needs
Rationale
CM-07 limits each component to essential capabilities, and its guidance favours one function per component where feasible. SC-32 places components in separate physical or logical domains on grounds the organisation sets. SC-39 gives each process its own execution domain, for example through virtualisation or sandboxing.
Gaps
PCI DSS asks for functions that share a component without isolation to meet the strictest need among them. Harden the whole component to that level.
2.2.4 Stripping unneeded services and functions from systems 95%
Rationale
CM-07 configures each system to provide only essential capabilities and prohibits or restricts the functions, ports, protocols and services the organisation names. CM-07(01) reviews systems on a set cycle and disables or removes what is unnecessary or insecure.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
Mapped Controls
2.2.5 Justifying and protecting insecure services on systems
Rationale
CM-07 limits each insecure protocol, service or daemon the organisation names to approved cases. CM-06 documents and approves each deviation from the secure settings, with its operational reason.
Gaps
PCI DSS asks for added security features on each insecure service, protocol or daemon that stays in use. Record the features for each one and confirm they are in place.
2.2.6 Security parameters set as tightly as operations allow 90%
Rationale
CM-06 sets each component's security parameters to the most restrictive mode that operations allow, using common secure configurations. It implements those settings, approves any deviation and controls later changes.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
Mapped Controls
2.2.7 Encrypting every administrative session over the network
Rationale
AC-17 sets the requirements for each type of remote access, and AC-17(02) protects remote sessions with cryptographic mechanisms. SC-08 protects transmitted information, and SC-08(01) uses cryptography to prevent its disclosure and detect changes in transit. SC-13 names each use of cryptography and the type it requires, which lets the organisation set strong cryptography for administrative access.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
2.3.1 Replacing factory defaults on wireless equipment
Rationale
AC-18 sets configuration requirements for each type of wireless access and authorises it before use. IA-05 changes default authenticators, such as access point passwords and preset keys, before first use. CM-06 applies secure settings in place of other insecure vendor defaults, SNMP community strings included.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
2.3.2 Changing wireless keys after departures or a compromise
Rationale
IA-05 changes authenticators when events the organisation names occur, and changes shared ones when a group's membership changes. It also sets procedures for compromised authenticators. SC-12 manages cryptographic keys to the organisation's rules for their generation, distribution, storage, access and destruction.
Gaps
PCI DSS asks for a new wireless key when anyone who knows it leaves or changes role, and when a compromise is known or suspected. Write those events into IA-05 and the SC-12 key rules as triggers.
3.1.1 Policies and procedures for stored account data
Rationale
SC-01, MP-01 and SI-01 each ask for a documented policy and procedures, shared with the people who need them and reviewed on a set cycle. SC-01 governs encryption and key management. MP-01 governs the media that hold account data, and SI-01 the retention and disposal of data.
Gaps
PCI DSS asks for the procedures to be in daily use and known to all who apply them. Check that the staff who handle stored account data follow them.
3.1.2 Roles and duties for stored account data
Rationale
SC-01, MP-01 and SI-01 each ask for a policy that sets out roles and responsibilities. SC-01 covers encryption and key management. MP-01 covers media handling, and SI-01 retention and disposal. PS-09 writes these security duties into position descriptions.
Gaps
PCI DSS asks for the people given these duties to understand them. Confirm that each one does, for example with a briefing or a signed acknowledgement.
3.2.1 Retention limits and secure deletion of account data
Rationale
CM-12 records each place where account data is stored and processed. SI-12 manages and retains information as the law and operational needs require. SI-12(01) limits the personal data held to the elements the organisation names, and SI-12(03) disposes of data when its retention period ends. MP-06 sanitises media before disposal or reuse, and MP-06(01) verifies each sanitisation.
Gaps
PCI DSS asks for a check every three months that data held past its retention period is gone. Schedule that check, and cover any SAD stored before authorisation in the retention policy.
3.3.1 Erasing all SAD after authorisation, encrypted or not 75%
Rationale
SI-12 manages how long information is kept, so the organisation can end the retention of SAD at authorisation. SI-12(01) limits the personal data held to a set list of elements. SI-12(03) erases data by the organisation's chosen techniques once its retention period ends.
Gaps
PCI DSS asks for all SAD to be made unrecoverable at authorisation, encrypted copies included. Search databases, logs and files for stray copies and purge them.
Mapped Controls
3.3.1.1 Discarding full track data after authorisation 75%
Rationale
SI-12 manages how long information is kept. SI-12(01) limits the personal data held to the elements the organisation names. The organisation can name the PAN, cardholder name, expiry date and service code, and leave full track data out.
Gaps
PCI DSS asks for full track data to be erased once authorisation completes. Search databases, logs and debug output for any that remains and remove it.
Mapped Controls
3.3.1.2 Discarding the card verification code after authorisation 75%
Rationale
SI-12 manages and retains information as the law and operational needs require. The organisation uses it to end the retention of the card verification code when authorisation completes.
Gaps
PCI DSS asks for the card verification code to be erased at authorisation. Search databases, logs and call recordings for the code and purge any copy found.
Mapped Controls
3.3.1.3 Discarding the PIN and PIN block after authorisation 75%
Rationale
SI-12 manages and retains information as the law and operational needs require. The organisation uses it to end the retention of PINs and PIN blocks when authorisation completes.
Gaps
PCI DSS asks for PINs and PIN blocks to be erased once authorisation completes. Search systems, logs and files for any copies and remove them.
Mapped Controls
3.3.2 Strong encryption for SAD stored before authorisation
Rationale
SC-28 protects information at rest, and SC-28(01) encrypts it on the components and media the organisation names. Here that means every electronic store of SAD held before authorisation. SC-13 sets the type of cryptography each use requires.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
3.3.3 SAD held by issuers, limited to need and encrypted
Rationale
SI-12 retains information as operational needs require, here the needs of the issuing function. AC-03 enforces approved access to the stored SAD. SC-28 protects it at rest, and SC-28(01) encrypts it. SC-13 sets the type of cryptography each use requires.
Gaps
PCI DSS asks issuers and the companies that support them to keep only the SAD their issuing work needs. Record that need for each SAD element they store.
3.4.1 Masking the PAN wherever it is shown
Rationale
AC-03 enforces approved access rules, and AC-03(07) bases them on roles, so only the roles allowed to see the full PAN can do so. AC-06 grants each person only the access their duties need.
Gaps
PCI DSS sets the most a display may show at the BIN and the last four digits. Build that masking into every screen and printout, and show more only to people with a business need for it.
3.4.2 Stopping PAN being copied or moved in remote sessions
Rationale
AC-17 sets usage restrictions and connection rules for each type of remote access. AC-04 enforces approved information flows, so PAN stays inside the remote session. AC-06 gives the right to copy or move PAN only to people whose duties need it.
Gaps
PCI DSS asks for copying and moving PAN over remote access to be blocked for all but approved people. Turn off clipboard, file transfer, drive mapping and printing by default, and record who is approved and why.
3.5.1 Hashing, truncating, tokenising or encrypting stored PAN
Rationale
SC-28 protects information at rest, and SC-28(01) encrypts it on the components and media the organisation names, which can include backups and logs. SC-13 sets the cryptography for each use, such as hashing or encryption. SC-12 manages the keys. SI-19 removes named elements of personal data from datasets, and SI-19(04) masks, hashes or replaces direct identifiers, as truncation and tokens do.
Gaps
PCI DSS asks for controls that stop hashed and truncated versions of one PAN being matched to rebuild it. Keep the versions apart so nobody can combine them.
3.5.1.1 Keyed hashes of the whole PAN, with managed keys
Rationale
SC-13 sets the cryptography for each use, here a keyed hash, such as an HMAC, over the full PAN. SC-12 manages the secret key behind the hash. SC-28 protects the stored hashes at rest.
Gaps
PCI DSS asks for every PAN hash to use a secret key and to cover the whole number. Replace any unkeyed hashes with keyed ones.
3.5.1.2 Disk encryption as sole PAN protection, removable media only
Rationale
SC-28 protects information at rest, and SC-28(01) encrypts it on the components and media the organisation names. The organisation can limit disk encryption to removable media and apply file, column or field encryption to PAN on fixed storage. SC-13 sets the type of cryptography each use requires.
Gaps
PCI DSS accepts disk or partition encryption on its own only for removable media. On fixed storage, also protect PAN at the data level, for example with truncation or column encryption.
3.5.1.3 Independent login and key handling for disk encryption
Rationale
AC-03 enforces approved access to the decrypted data, which the organisation can make independent of the operating system login. IA-05 and IA-05(06) protect the passwords and keys that unlock the data. SC-12 sets key requirements that can keep decryption keys apart from user accounts. SC-28 protects data at rest, and SC-28(03) gives the keys protected storage.
Gaps
PCI DSS asks for disk decryption to need its own login, managed apart from the operating system's accounts. Set up that separate unlock step for every encrypted disk.
3.6.1 Protecting data keys and the keys that wrap them
Rationale
SC-12 sets the organisation's rules for key storage and access, key-encrypting keys included. AC-06 limits key access to the custodians whose duties need it. SC-28 protects information at rest, and SC-28(03) gives keys protected storage.
Gaps
PCI DSS asks for each key-encrypting key to be equal to or stronger than the keys it protects, and stored apart from them. Write both rules into the key procedures.
3.6.1.1 Service provider's record of its cryptographic design
Rationale
PL-08 asks for a security architecture, which here sets out how cryptography protects stored account data. SC-13 names each use of cryptography and the type it needs. SC-12 sets key requirements that can record each key's purpose, strength and expiry. CM-08 inventories system components, HSMs and key management systems among them, with details the organisation chooses, such as type and location.
Gaps
PCI DSS asks the service provider to keep production keys out of test environments. State that rule in the architecture description.
3.6.1.2 Approved storage forms for secret and private keys
Rationale
SC-12 sets the organisation's key storage requirements, which can name the forms allowed, such as wrapped keys, keys held in hardware or key shares. SC-12(02) produces, controls and distributes symmetric keys with FIPS-validated or NSA-approved technology. SC-28 protects information at rest, and SC-28(03) keeps keys in protected storage, such as a hardware-protected key store.
Gaps
PCI DSS asks for key shares from an approved random number generator in a secure cryptographic device, or under ISO 19592 or an equal standard. Generate every share one of those ways.
3.6.1.3 Fewest custodians for cleartext key components
Rationale
AC-06 gives access to cleartext key components only to the custodians whose duties need it, which keeps their number small. SC-12 sets the key access rules that say who may handle key components.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
3.6.1.4 Keeping keys in as few places as possible 75%
Rationale
SC-12 manages keys under storage requirements the organisation sets. Those requirements can name the places where keys may be held and limit them to the fewest the business needs.
Gaps
PCI DSS asks for keys to sit in the fewest places possible. List every place a key is held, and keep only the copies the business needs.
Mapped Controls
3.7.1 Generating strong keys for stored account data
Rationale
SC-12 sets the organisation's requirements for key generation. SC-12(02) and (03) name the technology and processes for producing symmetric and asymmetric keys. SC-13 sets the type of cryptography for each use, and with it the algorithm and key strength.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
3.7.2 Delivering keys securely to their custodians 90%
Rationale
SC-12 sets the organisation's key distribution requirements, which can send keys only to authorised custodians by secure means. SC-12(02) and (03) name the technology and processes for distributing symmetric and asymmetric keys.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
Mapped Controls
3.7.3 Storing keys securely as part of key management
Rationale
SC-12 sets the organisation's key storage requirements. SC-28 protects information at rest, and SC-28(03) gives cryptographic keys protected storage, through safeguards the organisation names or a hardware-protected key store.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
3.7.4 Changing each key when its cryptoperiod ends 75%
Rationale
SC-12 manages keys across their life under requirements the organisation sets. Those requirements can give each key type a lifetime and a process for replacing keys when it ends.
Gaps
PCI DSS asks the organisation to set a cryptoperiod for every key type and to change each key when its period ends. Record both in the SC-12 key requirements.
Mapped Controls
3.7.5 Retiring or replacing weakened and compromised keys
Rationale
SC-12 manages keys through their life, destruction included, under requirements the organisation sets, such as when to retire or replace a key. PS-04 revokes the authenticators and credentials of anyone who leaves. Here that reaches the key components a departing custodian knew.
Gaps
PCI DSS asks for a key change on suspected compromise and when a custodian who knew a key component leaves or changes role. Take retired keys out of encryption use.
3.7.6 Dual control and split knowledge in manual key handling
Rationale
AC-03 enforces approved access, and AC-03(02) requires two people to authorise the actions the organisation names, such as manual key operations. AC-05 separates duties so one person never holds a whole key. SC-12 sets how manual key operations run and can require key components held by different people.
Gaps
PCI DSS asks for key components from an approved random number generator in a secure cryptographic device, or under ISO 19592 or an equal standard. Generate each custodian's component one of those ways.
3.7.7 Guarding keys against unauthorised substitution
Rationale
AC-03 enforces approved access, so only authorised people can load or replace keys. SC-12 sets the organisation's key management requirements, which can require authorisation before any key is replaced.
Gaps
PCI DSS asks for safeguards that stop anyone swapping in a key of their own. Verify each key before it is loaded, for example with a key check value.
3.7.8 Key custodians' signed acceptance of their duties
Rationale
PL-04 gives custodians written rules for their duties and takes their documented acknowledgement before granting access, renewed when the rules change. PS-06 has them sign an access agreement before receiving key access, and sign again when it changes.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
3.7.9 Service provider's key guidance for customers
Rationale
SA-05 produces user documentation on secure use and user duties, and distributes it to the people the organisation names, here customers that receive shared keys. SC-12 sets key management requirements that cover keys shared with customers, including how they are distributed and stored.
Gaps
PCI DSS asks the service provider to give every customer that receives shared keys written guidance on sending, storing and updating them. Add that guidance to the customer documentation.
4.1.1 Policies and procedures for encryption in transit 85%
Rationale
SC-01 asks for a documented policy and procedures for communications protection, shared with the people who need them and reviewed on a set cycle. They govern how the organisation protects cardholder data sent across public networks.
Gaps
PCI DSS asks for the procedures to be in daily use and known to all who apply them. Check that staff follow the procedures for encryption in transit.
Mapped Controls
4.1.2 Roles and duties for encryption in transit
Rationale
SC-01 asks for a communications protection policy that sets out roles and responsibilities, including those for protecting data in transit. PS-09 writes those security duties into the position descriptions of the people who carry them out.
Gaps
PCI DSS asks for the people given these duties to understand them. Confirm that each one does, for example with a briefing or a signed acknowledgement.
4.2.1 Strong cryptography for PAN sent over public networks
Rationale
SC-08(01) encrypts PAN while it crosses public networks. SC-13 has the organisation set the cryptography each use requires. SC-17 issues certificates under a set policy or obtains them from an approved provider, and keeps only approved trust anchors in trust stores. IA-05(02) validates each certificate's path to an accepted trust anchor and checks its revocation status.
Gaps
PCI DSS asks each connection to refuse fallback to insecure protocol versions and to reject expired certificates. Build both into the settings for SC-13 and IA-05(02).
4.2.1.1 Inventory of keys and certificates for PAN in transit
Rationale
SC-12 manages the cryptographic keys that protect PAN in transit, from generation to destruction, under rules the organisation sets. SC-17 governs the certificates the organisation issues or obtains and the trust anchors its trust stores hold.
Gaps
PCI DSS asks for an up-to-date inventory of every key and certificate that protects PAN in transit. Record each one's strength, owner and expiry date.
4.2.1.2 Wireless encryption and authentication for PAN and the CDE
Rationale
AC-18 sets configuration and connection rules for each type of wireless access and authorises it before connections start. AC-18(01) protects wireless access with authentication of users or devices and with encryption. SC-08(01) encrypts the data sent over wireless links. SC-13 has the organisation choose the cryptography each use requires.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
4.2.2 Encrypting PAN sent by email and other messaging tools
Rationale
SC-08(01) uses cryptography to prevent unauthorised disclosure of information in transit, which covers PAN sent by email, chat or other messaging tools. SC-13 has the organisation choose the cryptography for that use.
Gaps
PCI DSS asks for PAN to travel only on messaging channels that encrypt it. Block it on every other channel, and delete any PAN that arrives through one.
5.1.1 Policies and procedures for malware protection 85%
Rationale
SI-01 asks for a documented policy and procedures for system and information integrity, shared with those who need them and reviewed on a set cycle. They govern how the organisation guards its systems against malware.
Gaps
PCI DSS asks for the procedures to be in daily use and known to all who apply them. Check that staff follow the anti-malware procedures.
Mapped Controls
5.1.2 Roles and duties for malware protection
Rationale
SI-01 asks for an integrity policy that sets out roles and responsibilities, including those for malware protection. PS-09 writes those security duties into the position descriptions of the people who carry them out.
Gaps
PCI DSS asks for the people given these duties to understand them. Confirm that each one does, for example with a briefing or a signed acknowledgement.
5.2.1 Anti-malware on every system component 90%
Rationale
SI-03 places malicious code protection at system entry and exit points, such as mail gateways and endpoints, to detect and remove malicious code.
Gaps
PCI DSS asks for anti-malware on every system component. Exempt a component only when a recorded evaluation under 5.2.3 finds it free of malware risk.
Mapped Controls
5.2.2 Detecting and stopping every known kind of malware 95%
Rationale
SI-03 detects and removes malicious code, using signature or non-signature methods. On each detection it blocks or quarantines the code and alerts the people the organisation names.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
Mapped Controls
5.2.3 Reviewing components exempted from anti-malware
Rationale
RA-03 identifies threats to the components exempted from anti-malware and updates that assessment on a cycle the organisation sets. SI-05 receives security alerts and advisories from outside sources, such as news of new malware, and passes them to the people who act on them.
Gaps
PCI DSS asks for a written list of the components exempted from anti-malware. At each review, record whether each one stays exempt.
5.2.3.1 Risk-based interval for reviewing exempted components 70%
Rationale
RA-03 asks for a documented risk assessment, reviewed and updated on a cycle the organisation sets. That assessment gives the organisation a basis for how often it re-evaluates the components exempted from anti-malware.
Gaps
PCI DSS asks for the interval to come from a targeted risk analysis that meets 12.3.1. Document that analysis and the interval it sets.
Mapped Controls
5.3.1 Automatic updates to anti-malware tools 95%
Rationale
SI-03 updates the malicious code protection mechanisms automatically whenever new releases are available. The organisation's configuration management policy and procedures govern how those updates roll out.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
Mapped Controls
5.3.2 Malware scans or continuous behaviour analysis 95%
Rationale
SI-03 runs periodic scans at a frequency the organisation sets, and real-time scans of files from outside sources as they are downloaded or opened. Its non-signature methods detect malicious code by how it behaves.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
Mapped Controls
5.3.2.1 Risk-based interval for periodic malware scans
Rationale
SI-03 runs periodic malware scans at a frequency the organisation sets. RA-03 gives the organisation a documented, regularly updated risk assessment to base that frequency on.
Gaps
PCI DSS asks for the scan frequency to come from a targeted risk analysis that meets 12.3.1. Document that analysis and set the SI-03 frequency from it.
5.3.3 Scanning removable media on connection 80%
Rationale
SI-03 scans files from external sources in real time at the endpoint as they are opened or run. That covers files on removable media, such as USB drives.
Gaps
PCI DSS asks for removable media to be scanned automatically, or its use watched by behavioural analysis, as soon as it is inserted or mounted. Set the endpoint protection to act on connection.
Mapped Controls
5.3.4 Audit logs of anti-malware activity
Rationale
AU-02 has the organisation name anti-malware events among the event types it logs, and AU-12 has the components generate audit records for them. AU-11 keeps those records for a period the organisation sets.
Gaps
PCI DSS asks, through 10.5.1, for at least 12 months of log history, with the latest three months on hand for analysis. Set that period in AU-11.
5.3.5 Stopping users from disabling or changing anti-malware
Rationale
AC-06 limits users to the access their duties need, and AC-06(10) stops non-privileged users from running privileged functions, such as disabling or altering malware protection. CM-05 restricts who may change the system, anti-malware settings included. CM-06 has the organisation document and approve any departure from its configuration settings, such as a temporary pause in protection.
Gaps
PCI DSS asks for a time limit on every approved pause, with management signing off each one. Record the end date alongside the CM-06 approval.
5.4.1 Detecting and blocking phishing aimed at staff
Rationale
SI-08 puts spam protection at entry points such as mail gateways, where it detects and acts on unsolicited messages. SI-03 scans the attachments and downloads that phishing delivers and blocks or quarantines malicious code.
Gaps
PCI DSS asks for defences built for phishing. Verify the senders of incoming mail with authentication such as DMARC, and check links against known phishing sites.
6.1.1 Policies and procedures for secure development and change
Rationale
SA-01, SI-01 and CM-01 ask for documented policies and procedures, shared with the people who need them and reviewed on a set cycle. SA-01 covers how systems and software are acquired and developed. SI-01 covers patching and flaw remediation, and CM-01 covers change control.
Gaps
PCI DSS asks for the procedures to be in daily use and known to all who apply them. Check that staff follow them.
6.1.2 Roles and duties for secure development and change
Rationale
SA-01, SI-01 and CM-01 ask for policies that set out roles and responsibilities for development, patching and change control. Each names an official to manage its policy. PS-09 writes these security duties into position descriptions.
Gaps
PCI DSS asks for the people given these duties to understand them. Confirm that each one does, for example with a briefing or a signed acknowledgement.
6.2.1 Secure development life cycle for bespoke and custom code
Rationale
SA-03 runs development under a life cycle that builds in security and ties risk management into each of its activities. SA-08 applies security engineering principles from specification through design, build and change. SA-15 has developers follow a documented process that addresses security requirements and names its standards and tools.
Gaps
PCI DSS asks for the software to meet the standard's own requirements, such as strong authentication and logging. Write those into each project's security requirements.
6.2.2 Yearly software security training for developers 85%
Rationale
AT-03 gives developers security training for their role before they start work and then at a frequency the organisation sets. It also updates the training content on a set cycle and after set events.
Gaps
PCI DSS asks for this training at least every 12 months. Set that frequency in AT-03, and cover secure design and coding in each developer's languages and any testing tools they use.
Mapped Controls
6.2.3 Security review of code before each release
Rationale
SA-11 has developers test and evaluate their code and correct the flaws found. SA-11(01) adds static code analysis and SA-11(04) adds manual code review. SA-15 names the standards developers follow, which the reviews check the code against.
Gaps
PCI DSS asks each review to look for new kinds of flaw as well as known ones. Keep the review checks current and hold each release until its findings are fixed.
6.2.3.1 Independent manual code review and management sign-off
Rationale
AC-05 documents duties that need separating, such as writing and reviewing code, and sets access to keep them apart. SA-11(04) asks for manual code review by set processes. CM-03 has each change reviewed and approved before release.
Gaps
PCI DSS asks for reviewers who are skilled in code review and in secure coding. Choose reviewers with those skills.
6.2.4 Coding techniques that defend against common attacks
Rationale
SA-08 applies security engineering principles in design and build. SA-15 names the standards and tools developers use. SA-11(01) and (08) run static and dynamic code analysis to find common flaws, and SA-11(02) adds threat modelling. SI-10 checks inputs, and SI-10(06) prevents injection of untrusted data. SI-16 protects memory from unauthorised code execution.
Gaps
PCI DSS lists the attack types the techniques must address. Among them are business logic abuse such as XSS and CSRF, misuse of cryptography and bypass of access control. Name a defence for each in the coding standards and tests.
6.3.1 Tracking new vulnerabilities and ranking their risk
Rationale
SI-05 receives security alerts and advisories from outside bodies, such as CERTs, on an ongoing basis. RA-05 monitors for newly reported vulnerabilities and uses standard measures of their impact. SI-02 identifies and reports system flaws, in bespoke and third-party software alike.
Gaps
PCI DSS asks for each new vulnerability to get a risk ranking. Define a ranking scheme that marks out every high and critical vulnerability.
6.3.2 Bespoke and custom code inventory with third-party components
Rationale
CM-08 keeps an accurate inventory of all system components, software included, at the level of detail needed for tracking. SR-04 documents and maintains where components come from. SR-04(04) checks the internal make-up and origin of critical components.
Gaps
PCI DSS asks for the inventory to list the third-party components inside bespoke and custom software. List each library with its version, and use the list to track patches.
6.3.3 Timely security patches, critical ones within a month
Rationale
SI-02 installs security-relevant updates within a time the organisation sets, counted from their release. RA-05 remediates vulnerabilities within response times the organisation sets from its assessment of risk.
Gaps
PCI DSS sets a limit of one month from release for critical patches. Set that period in SI-02 and in the response times of RA-05.
6.4.2 Automated defence against attacks on public web applications
Rationale
SC-07 places boundary protection at the external interfaces, where it monitors and controls traffic to public web applications. SI-04 monitors for attacks, SI-04(05) alerts staff to signs of compromise, and SI-04(07) acts to end suspicious events. AU-12 has the protection generate audit records.
Gaps
PCI DSS asks for the protection to keep running and stay up to date. Set it to block attacks, or to raise alerts that staff investigate at once.
6.4.3 Approving payment page scripts and checking their integrity
Rationale
SC-18 defines acceptable mobile code, such as JavaScript, and authorises and controls its use. SI-07 checks scripts for unauthorised changes, and SI-07(06) does so with cryptographic means such as hashes. CM-08 keeps an inventory of system components, which here lists each script.
Gaps
PCI DSS asks for a written reason, business or technical, why each script is needed. Record one for every script in the inventory, those from third parties included.
6.5.1 Change control for production systems
Rationale
CM-03 reviews and approves each change with its security impact in view, and records the decision. CM-03(02) tests and documents changes before they are finalised. CM-04 analyses each change for security impact before it is made. SA-11 has developers test bespoke code changes and fix the flaws found. CM-02(03) keeps earlier baseline configurations so a failed change can be rolled back.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
6.5.2 Rechecking PCI DSS requirements after a significant change
Rationale
CM-04 analyses the security impact of each change, and CM-04(02) checks afterwards that the affected controls work as intended. PL-02 updates the security plan to reflect changes to the system and its environment.
Gaps
PCI DSS asks for a check of every applicable requirement on new or changed systems, beyond the controls the change touched. Define what counts as a significant change, and run that check after each one.
6.5.3 Separation of pre-production from production
Rationale
SC-32 places pre-production and production in separate physical or logical domains. AC-03 enforces approved access rules between them. CM-04(01) analyses changes in a separate test environment before they go into production.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
6.5.4 Separate duties so only approved changes reach production
Rationale
AC-05 documents duties that need separating, such as pre-production and production work, and sets access to keep them apart. CM-03 puts in place only changes that have been reviewed and approved. CM-05 sets and enforces access restrictions for making changes, and CM-05(05) limits and reviews the privileges to change production.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
6.5.5 Keeping live PANs out of pre-production
Rationale
SA-03(02) approves and controls any use of live data in pre-production, and protects that environment to the level of the data in it. PM-25 keeps the personal data used for testing to a minimum and authorises its use where testing needs it.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
6.5.6 Removing test data and accounts before go-live 70%
Rationale
AC-02 defines which types of account a system allows and which it prohibits. It removes accounts in line with policy, so test accounts can come off a system before it goes live.
Gaps
PCI DSS asks for all test data and test accounts to be cleared before a system goes live. Add a release step that removes both and confirms they are gone.
Mapped Controls
7.1.1 Policies and procedures for access rights 85%
Rationale
AC-01 asks for a documented access control policy and procedures, shared with the people who need them and reviewed on a set cycle. They govern how the organisation grants and limits access.
Gaps
PCI DSS asks for the procedures to be in daily use and known to all who apply them. Check that staff follow them.
Mapped Controls
7.1.2 Roles and duties for access rights
Rationale
AC-01 asks for an access control policy that sets out roles and responsibilities, with a named official to manage it. PS-09 writes these security duties into position descriptions.
Gaps
PCI DSS asks for the people given these duties to understand them. Confirm that each one does, for example with a briefing or a signed acknowledgement.
7.2.1 Access control model tied to job functions
Rationale
AC-02 defines account types, sets the criteria for group and role membership and records each account's privileges. AC-03 enforces approved access, and AC-03(07) bases it on roles the organisation defines, such as job functions. AC-06 allows each user only the access their tasks need.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
7.2.2 Least privilege for every user, administrators included
Rationale
AC-02 grants access on a valid authorisation and the intended use, and assigns each account its roles and privileges. AC-02(07) manages privileged accounts under a role-based or attribute-based scheme. AC-06 allows only the privileges each task needs, and AC-06(05) restricts privileged accounts to named people or roles.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
7.2.3 Approval of each privilege by an authorised person 90%
Rationale
AC-02 requires approval from named people or roles before an account is created. It grants access to a system on a valid authorisation for the intended use.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
Mapped Controls
7.2.4 Six-monthly review of user accounts and their privileges
Rationale
AC-02 reviews accounts against the account management rules at a frequency the organisation sets. AC-06(07) reviews the privileges held by each class of user and removes or reassigns them to match business needs.
Gaps
PCI DSS sets the review interval at six months at most, with vendor and other third-party accounts included. Set that frequency in AC-02 and AC-06(07), and have management sign off each review.
7.2.5 Least privilege for system and application accounts
Rationale
AC-02 manages system and service accounts like any other account type, and AC-02(11) enforces the conditions under which system accounts may be used. AC-06 gives processes acting for users only the access their tasks need.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
7.2.5.1 Risk-based review of system and application account access
Rationale
AC-02 reviews application and system accounts at a frequency the organisation sets. AC-06(07) reviews the privileges they hold and removes or reassigns any excess. RA-03 assesses risk to the system, which gives a basis for setting how often the reviews happen.
Gaps
PCI DSS asks management to confirm at each review that the access is still right. Record that sign-off with each review.
7.2.6 Limits on querying stored cardholder data
Rationale
AC-03(11) restricts access to data repositories that hold chosen types of information, such as cardholder data. AC-03(07) ties that access to roles. AC-06 limits users to the access their tasks need, and AC-06(05) restricts privileged database accounts to the responsible administrators.
Gaps
PCI DSS asks for users to query stored cardholder data through applications that apply role-based limits. Route every user query that way.
7.3.1 Need-to-know access control on every system component
Rationale
AC-03 enforces approved authorisations for logical access to information and system resources. AC-06 allows each user only the access their assigned tasks need, so access follows need to know.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
7.3.2 Role-based permissions enforced by the access control system
Rationale
AC-02 sets the criteria for group and role membership and specifies each account's privileges. AC-03 enforces approved authorisations, and AC-03(07) does so through roles the organisation defines, such as job functions.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
7.3.3 Default deny in every access control system
Rationale
AC-03 enforces approved authorisations, so each access needs an approval behind it and anything unapproved is refused. AC-06 allows only the authorised accesses that each user's tasks require.
Gaps
PCI DSS asks for every access control system to deny access by default. Set each system that way and grant access through specific rules.
8.1.1 Policies and procedures for identification and authentication
Rationale
AC-01 and IA-01 ask for documented policies and procedures for access control and for identification and authentication. Each is shared with the people who need it and reviewed on a set cycle. Together they govern how accounts are managed and how users prove who they are.
Gaps
PCI DSS asks for the procedures to be in daily use and known to all who apply them. Check that the staff who manage accounts and credentials follow them.
8.1.2 Roles and duties for identification and authentication
Rationale
AC-01 and IA-01 ask for policies that set out roles and responsibilities for access control and for identification and authentication. PS-09 writes those security duties into the position descriptions of the people who hold them.
Gaps
PCI DSS asks for the people given these duties to understand them. Confirm that each one does, for example with a briefing or a signed acknowledgement.
8.2.1 A unique ID for each user before any access
Rationale
IA-02 uniquely identifies and authenticates each of the organisation's users and ties that identity to the processes acting for them. Every action then traces to one person. IA-04 assigns each identifier to its intended individual once someone with authority approves it, and stops its reuse for a set period.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
8.2.2 Shared, group and generic IDs as approved exceptions
Rationale
AC-02 defines which types of account are allowed, and AC-02(09) permits shared and group accounts only under conditions the organisation sets. AC-02(11) enforces usage conditions such as time limits, and AC-02(02) removes or disables temporary and emergency accounts after a set period. IA-02(05) authenticates each person before they reach a shared account, so actions trace to one person.
Gaps
PCI DSS asks for a business reason and a time limit for each use of a shared ID. Record the reason every time, and enforce the limit through AC-02(11).
8.2.3 Service provider credentials unique to each customer site 85%
Rationale
IA-05 manages authenticators from issue to revocation. IA-05(08) asks for controls the organisation chooses against the risk of one person holding accounts on many systems. A separate authenticator for each customer site is one such control.
Gaps
PCI DSS asks the service provider to keep a separate set of credentials for each customer's premises. Make that the control chosen under IA-05(08).
Mapped Controls
8.2.4 Approval for every change to user IDs and credentials
Rationale
AC-02 requires approval for each new account, specifies the privileges of every account, and creates, changes and removes accounts by the organisation's procedures. IA-04 requires authorisation before anyone assigns an identifier. IA-05 sets procedures for issuing authenticators, replacing lost or compromised ones and revoking them.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
8.2.5 Revoking access at once when someone leaves
Rationale
AC-02 notifies account managers within a set time when users are terminated, and aligns account management with termination processes. PS-04 disables system access within a set time when employment ends and revokes the person's authenticators and credentials.
Gaps
PCI DSS asks for access to end immediately when someone leaves. Make the time periods in PS-04 and AC-02 immediate.
8.2.6 Disabling user accounts left unused for 90 days 95%
Rationale
AC-02 monitors the use of accounts and disables or removes them under the organisation's rules. AC-02(03) disables an account within a set time once it has been inactive for a period the organisation chooses.
Gaps
PCI DSS sets 90 days of inactivity as the limit. Set the two periods in AC-02(03) so an idle account is disabled by day 90.
Mapped Controls
8.2.7 Time-limited, monitored remote accounts for third parties
Rationale
AC-02 enables and disables accounts under the organisation's rules and monitors their use. AC-02(11) enforces usage conditions on chosen accounts, and AC-02(12) watches for atypical use and reports it. AC-17 authorises each type of remote access, and AC-17(01) monitors and controls it automatically. AC-17(09) can disconnect or disable remote access within a set time. MA-04 approves and monitors remote maintenance and ends the session when the work is done.
Gaps
PCI DSS asks for third-party remote accounts to stay disabled between uses. Enable each one for a support task and disable it when the task ends.
8.2.8 Session lock after 15 minutes of idle time
Rationale
AC-11 locks the device after a set period of inactivity and keeps it locked until the user signs in again. AC-12 ends a session automatically under conditions the organisation sets, such as idle time. IA-11 asks users to authenticate again in situations the organisation names.
Gaps
PCI DSS sets the idle limit at 15 minutes. Use that value for the AC-11 lock and for the AC-12 and IA-11 triggers.
8.3.1 An authentication factor for every user and administrator
Rationale
IA-02 uniquely identifies and authenticates every user and administrator in the organisation. IA-05 manages the authenticators themselves, such as passwords, tokens and biometrics, and gives each enough strength for its intended use.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
8.3.2 Encrypting authentication factors in transit and at rest
Rationale
IA-05 protects authenticator content from disclosure, and IA-05(01) sends passwords only over encrypted channels and stores them with a salted key derivation function. SC-08 protects credentials in transit. SC-28 protects them at rest, and SC-28(01) does so with cryptographic mechanisms. SC-13 has the organisation choose the cryptography for each use.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
8.3.3 Confirming identity before any credential reset or change 80%
Rationale
IA-05 verifies the identity of whoever receives an authenticator when it is first issued. It also sets procedures for authenticators that are lost, compromised or damaged, which govern how they are replaced.
Gaps
PCI DSS asks for the user's identity to be confirmed before every reset or change of a factor, help desk requests included. Extend the IA-05 identity check from first issue to every change.
Mapped Controls
8.3.4 Account lockout after 10 failed logon attempts 95%
Rationale
AC-07 limits the number of consecutive failed logons a user may make in a set period. Once the limit is passed, it locks the account for a set time or until an administrator releases it.
Gaps
PCI DSS caps attempts at 10 and sets a lockout of at least 30 minutes, or until the organisation verifies the user. Set both values in AC-07.
Mapped Controls
8.3.5 Unique initial and reset passwords, changed at first use 85%
Rationale
IA-05 has the organisation set the initial content of every authenticator it issues. IA-05(01) requires a new password straight after account recovery, such as a reset.
Gaps
PCI DSS asks for each first-time or reset password to be unique to its user, and for the user to replace it at first logon. Set both rules in IA-05.
Mapped Controls
8.3.6 Password length and mix of letters and digits 90%
Rationale
IA-05 gives each authenticator enough strength for its intended use. IA-05(01) enforces the composition and complexity rules the organisation sets for passwords, and lets users choose long passwords and passphrases.
Gaps
PCI DSS sets a minimum of 12 characters, mixing letters and digits, with 8 allowed where a system's limit is lower. Set these rules in IA-05(01).
Mapped Controls
8.3.7 Password history against reuse of recent passwords 70%
Rationale
IA-05 changes or refreshes authenticators on a schedule the organisation sets. IA-05(01) screens each new password against a list of commonly used, expected or compromised passwords, and enforces the composition rules the organisation chooses.
Gaps
PCI DSS asks for a password history that rejects any of the user's last four passwords. Add that check to the rules set under IA-05(01).
Mapped Controls
8.3.8 Authentication guidance and rules given to every user
Rationale
IA-01 documents the authentication policy and procedures and shares them with the roles the organisation names. IA-05 requires individuals to take specific steps to protect their authenticators. PL-04 gives users written rules on their responsibilities and collects their acknowledgement. IR-06 has staff report suspected incidents, such as a compromised password, within a set time.
Gaps
PCI DSS asks for the guidance to tell users to avoid reusing old passwords and to change a password at once if they suspect a compromise. Add both points to the PL-04 rules.
8.3.9 Password-only logons: 90-day change or risk-based access
Rationale
IA-05 changes or refreshes authenticators at intervals the organisation sets for each type, or when set events occur. IA-10 asks for extra authentication in situations the organisation defines, which supports deciding access from account risk.
Gaps
PCI DSS asks for passwords used as the only factor to change at least every 90 days. The organisation may instead decide access by account risk in real time. Set the period in IA-05.
8.3.10.1 Customer password-only logons at service providers
Rationale
IA-08 identifies and authenticates people outside the organisation, such as the service provider's customers. IA-05 changes or refreshes authenticators at intervals the organisation sets. IA-10 asks for extra authentication in situations the organisation defines, which supports deciding access from account risk.
Gaps
PCI DSS asks the service provider to change customer passwords used alone at least every 90 days. It may instead judge each customer's access by account risk in real time. Set the period in IA-05.
8.3.11 One user per token, smart card or certificate
Rationale
IA-02 uniquely identifies and authenticates each user, so each authentication binds to one person. IA-05 has individuals protect the authenticators issued to them. IA-05(02) enforces authorised access to each private key and maps the authenticated identity to the holder's account.
Gaps
PCI DSS asks for each token, smart card or certificate to be issued to one person. Protect each one with a PIN or similar, so only its holder can use it.
8.4.1 Multi-factor authentication for admin access into the CDE 95%
Rationale
IA-02 uniquely identifies and authenticates each of the organisation's users. IA-02(01) asks for multi-factor authentication on privileged accounts, which covers administrators who reach the CDE over a network.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
Mapped Controls
8.4.2 Multi-factor authentication for every user entering the CDE 90%
Rationale
IA-02 uniquely identifies and authenticates each of the organisation's users. IA-02(01) and (02) ask for multi-factor authentication on privileged and non-privileged accounts. Every user who reaches the CDE over a network then needs two or more factors.
Gaps
SP 800-53 sets multi-factor authentication by type of account. PCI DSS sets it by path into the CDE. Ask for it again at the CDE boundary, even from users who used it to join the network remotely.
Mapped Controls
8.4.3 Multi-factor authentication for remote access from outside
Rationale
AC-17 sets the conditions for each type of remote access and authorises it before connections start. IA-02(01) and (02) ask for multi-factor authentication on privileged and non-privileged accounts, and IA-02(06) puts one factor on a separate device. NIST writes IA-02 for the organisation's own users. IA-08 authenticates people from outside, such as vendors and customers.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
8.5.1 Multi-factor authentication that resists replay and bypass 80%
Rationale
IA-02(08) asks for replay-resistant authentication on the privileged and non-privileged accounts the organisation selects. IA-02(01) and (02) ask for multi-factor authentication on both kinds of account, which combines factors of different types.
Gaps
PCI DSS lets users, administrators included, bypass multi-factor authentication only under a documented, time-limited exception that management approves. Grant access only once every factor has succeeded.
Mapped Controls
8.6.1 Interactive use of system accounts by approved exception
Rationale
AC-02 defines and documents the types of account allowed on each system. AC-02(11) enforces the usage conditions the organisation sets for system accounts, such as interactive use only in approved cases. IA-02(05) authenticates each person before granting access to a shared account, so each action traces to one person.
Gaps
PCI DSS allows interactive use of application and system accounts only as a documented, time-limited exception that management approves. Record the business reason and the approval each time.
8.6.2 Keeping system account passwords out of code and scripts 85%
Rationale
IA-05 protects authenticator content from disclosure and change. IA-05(07) keeps unencrypted static authenticators out of applications and other static storage, such as scripts and configuration files. That covers the passwords of application and system accounts.
Gaps
PCI DSS asks for these passwords to stay out of scripts, code and configuration files, in encrypted form too. Keep them in a secrets vault that applications call at run time.
Mapped Controls
8.6.3 Change schedule and strength for system account passwords
Rationale
IA-05 changes or refreshes authenticators at intervals the organisation sets and after set events, such as a suspected compromise. IA-05(01) enforces the organisation's composition and complexity rules for passwords. RA-03 provides the risk assessment from which the organisation sets how often each password changes.
Gaps
PCI DSS asks for the complexity of each application or system account password to suit how often it changes. Set the IA-05(01) rules for each account to match its change interval.
9.1.1 Policies and procedures for physical security
Rationale
PE-01 and MP-01 ask for documented policies and procedures for physical protection and for media protection. Each is shared with the people who need it and reviewed on a set cycle. Together they govern how the organisation controls entry to its sites and handles media with cardholder data.
Gaps
PCI DSS asks for the procedures to be in daily use and known to all who apply them. Check that staff follow them.
9.1.2 Roles and duties for physical security
Rationale
PE-01 and MP-01 set out roles and responsibilities in the physical protection and media protection policies. PS-09 writes those security duties into position descriptions, so each one belongs to a named job. AT-03 gives role-based training to the people who hold them, and AT-03(02) trains them to use and run the physical security controls.
Gaps
PCI DSS asks for the people given these duties to understand them. Confirm that each one does, for example with a briefing or a signed acknowledgement.
9.2.1 Controlled entry to facilities that house CDE systems
Rationale
PE-02 keeps the approved list of people allowed into the facility and issues the credentials they use. PE-03 verifies each person's authorisation at the facility's entry and exit points, using badge readers, locks or guards. PE-03(01) enforces the same authorisations again at the spaces that hold CDE systems.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
9.2.1.1 Camera or badge records of who enters sensitive areas
Rationale
PE-03 keeps physical access audit logs at the entry and exit points the organisation chooses. PE-06 monitors physical access and reviews the logs. PE-06(03) adds video surveillance, with recordings reviewed and kept for a period the organisation sets. PE-06(04) extends the monitoring to the rooms that hold the systems themselves.
Gaps
PCI DSS asks for cameras and badge readers to be guarded against tampering and switching off. Compare their records with other entry data. Keep the records at least three months where the law allows, and set that period in PE-06(03).
9.2.2 Controlling network jacks in public areas
Rationale
PE-04 controls physical access to network cabling and outlets inside the facility, for example by disconnecting or locking spare jacks. IA-03 identifies and authenticates each device, for instance through 802.1X, before it connects. Only known devices can then use a public jack.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
9.2.3 Physical security of network hardware and telecom lines
Rationale
PE-03 enforces physical access at the entry points the organisation chooses, inner doors included. PE-03(04) puts exposed devices, such as wireless access points, in lockable casings. PE-04 controls physical access to cabling and telecom lines inside the facility. PE-18 positions components where unauthorised people have the least chance to reach them.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
9.2.4 Locking unattended consoles inside sensitive areas 95%
Rationale
AC-11 locks a device after a period of inactivity the organisation sets, or when the user locks it before leaving. The lock holds until the user signs in again with the usual identification and authentication.
Gaps
PCI DSS asks for every console in a sensitive area to lock whenever it's left idle. Apply the AC-11 lock to each of those consoles.
Mapped Controls
9.3.1 Staff badges and entry rights for the CDE
Rationale
PE-02 approves and keeps the list of people allowed in, issues their credentials, reviews the list and removes people once their need ends. PS-05 reviews and adjusts physical access when someone changes role. PS-04 revokes credentials and recovers badges and keys when employment ends. PE-03 secures keys, combinations and other physical access devices.
Gaps
PCI DSS asks for the badge system itself to be protected. Let only named administrators use it or handle blank badge stock.
9.3.1.1 Role-based staff entry to sensitive areas
Rationale
PE-02 authorises physical access, and PE-02(01) bases it on each person's position or role. PE-03(01) enforces those authorisations again at the spaces that hold system components. PE-03 also changes keys and combinations when holders leave. PS-04 revokes credentials and retrieves keys and cards when employment ends.
Gaps
PCI DSS asks for access to be revoked the moment employment ends. Set the time period in PS-04 to immediate, and apply it to physical access too.
9.3.2 Approving and escorting visitors in the CDE
Rationale
PE-02 authorises access for visitors as well as staff, and issues the badges they carry. PE-02(02) asks each visitor for two forms of identification. PE-03 verifies authorisation before entry, and escorts visitors and controls their activity in the circumstances the organisation defines.
Gaps
PCI DSS asks for visitor badges that expire and look clearly different from staff badges. Issue one to every visitor.
9.3.3 Recovering visitor badges at departure or expiry
Rationale
PE-02 removes people from the access list once their need for access ends, which closes a visitor's authorisation when the visit is over. PE-03 secures physical access devices and keeps an inventory of them, so the organisation can track each visitor badge it issues.
Gaps
PCI DSS asks for each visitor badge to be handed back or switched off before the visitor leaves, or on its expiry date. Make that part of signing visitors out.
9.3.4 Visitor log for the building and sensitive areas 85%
Rationale
PE-08 keeps visitor access records for a period the organisation sets, reviews them and reports anomalies. Its guidance lists who visited, for which organisation, and the dates and times of access among the details to record.
Gaps
PCI DSS asks the log to name the person who authorised each visit. Keep it three months or longer where the law allows, and set that period in PE-08.
Mapped Controls
9.4.1 Securing all media that holds cardholder data
Rationale
MP-02 limits access to digital and paper media to the people or roles the organisation names. MP-04 physically controls media and stores it securely in controlled areas, such as a locked cabinet or media library, until it is destroyed or sanitised.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
9.4.1.1 Secure storage for offline backup media
Rationale
MP-04 stores backup media securely in controlled areas. CP-09 protects the confidentiality, integrity and availability of backup information. CP-09(03) keeps backups of critical software and security information in a separate facility or a fire-rated container. Where backups go off site, CP-06 asks the storage site to match the controls of the main site.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
9.4.1.2 Annual security review of offline backup storage 75%
Rationale
CA-02 assesses the controls in a system and its operating environment at a frequency the organisation sets, and reports the results. Scoped to the offline backup location, that assessment gives the security review the requirement asks for.
Gaps
PCI DSS asks for the security of each offline backup location to be inspected at least every 12 months. Set that frequency in CA-02.
Mapped Controls
9.4.2 Classifying media by how sensitive its data is
Rationale
RA-02 categorises a system's information by the impact its loss would have, and records the result. That category sets how sensitive the media holding the information is. MP-03 marks media with the information's handling caveats, distribution limits and any security markings.
Gaps
PCI DSS asks for a classification on every item of media that holds cardholder data. Apply it to paper as well as electronic media.
9.4.3 Tracked delivery of media sent off site 90%
Rationale
MP-05 protects media carried outside controlled areas and keeps accountability for it in transit. It documents each transport and limits the work to authorised people. MP-05(03) puts a named custodian in charge of the media while it travels.
Gaps
PCI DSS asks for media to travel by secure courier or another method that tracks each shipment. Keep logs that show where each item is while it's off site.
Mapped Controls
9.4.4 Manager approval before media leaves the site
Rationale
MP-05 limits the transport of media outside controlled areas to authorised people and documents each movement. PE-16 authorises and controls system components leaving the facility, which can include media with cardholder data, and keeps records of them.
Gaps
PCI DSS asks for someone with management authority to approve every movement of media off site, including media handed to individuals. Build that approval into the MP-05 transport process.
9.4.5 Inventory of electronic media holding cardholder data
Rationale
CM-08 keeps a system component inventory at the level of detail needed for tracking and accountability, which can include storage devices. Under MP-04, physical control of stored media includes keeping inventories and accounting for each item.
Gaps
PCI DSS asks for an inventory log that lists every item of electronic media holding cardholder data. Extend the CM-08 inventory to cover each of those items.
9.4.5.1 Yearly count of the electronic media inventory
Rationale
CM-08 keeps the component inventory accurate and complete, and reviews and updates it at a frequency the organisation sets. Under MP-04, keeping inventories of stored media is part of controlling it physically.
Gaps
PCI DSS asks for the electronic media inventory to be counted and reconciled at least every 12 months. Set that frequency in CM-08.
9.4.6 Destroying paper records that hold cardholder data
Rationale
MP-04 keeps media in secure storage until it is destroyed, which covers paper waiting for destruction. MP-06 sanitises media before disposal so the information is beyond recovery, and for paper its methods include destruction. SI-12 manages and retains information in line with legal and operational needs. SI-12(03) sets the techniques for destroying it once retention ends.
Gaps
PCI DSS asks for paper to be destroyed by cross-cut shredding, incineration or pulping. Name those methods as the techniques in SI-12(03).
9.4.7 Destroying or wiping retired electronic media
Rationale
MP-06 sanitises electronic media before disposal, release or reuse, by erasing or destroying it, so the data is beyond recovery. It matches the strength of the method to the security category of the information. SI-12 manages and retains information in line with legal and operational needs. SI-12(03) sets the techniques for disposing of or erasing it once retention ends.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
9.5.1 Tamper protection for card-reading POI devices
Rationale
SR-09 runs a tamper protection programme that guards components against modification and substitution. SR-10 inspects the components the organisation chooses, at set intervals or at random, to detect tampering. CM-08 keeps an inventory of the devices, so the organisation can tell when one goes missing or is swapped. AT-03 gives role-based training to staff who work with POI devices, covering how to spot and report tampering.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
9.5.1.1 Current register of POI devices and their locations 95%
Rationale
CM-08 keeps a system component inventory with the details the organisation needs for accountability. Its guidance lists model, serial number, manufacturer and physical location among those details. CM-08(01) updates the inventory whenever devices are installed or removed.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
Mapped Controls
9.5.1.2 Checking POI devices for skimmers and swapped units
Rationale
SR-09 runs a tamper protection programme that covers the substitution of components as well as their modification. SR-10 inspects components at set intervals or at random to detect tampering.
Gaps
PCI DSS asks for each inspection to cover the outer surfaces of every device. Check them for skimming overlays each time.
9.5.1.2.1 Risk-based frequency and type of POI checks
Rationale
SR-10 lets the organisation choose which components to inspect for tampering, and when. RA-03 identifies threats and judges how likely and how harmful they are. That assessment gives the basis for the inspection schedule and method.
Gaps
PCI DSS asks for a targeted risk analysis that sets both how often the devices are inspected and how. Write it to cover every element of Requirement 12.3.1.
9.5.1.3 Training POI staff to spot tampering and impostors
Rationale
AT-02 provides awareness training, and AT-02(03) teaches staff to recognise and report social engineering, such as a stranger posing as a repair technician. AT-02(04) covers suspicious communications and unusual system behaviour. AT-03 gives role-based training to staff in POI environments. MA-05 keeps a list of authorised maintenance people and checks the authorisation of anyone working unescorted. IR-06 requires staff to report suspected incidents, signs of tampering included.
Gaps
PCI DSS asks for staff to be trained to verify each device before it's installed, replaced or returned. Make that check part of the AT-03 training.
10.1.1 Policies and procedures for audit logging 85%
Rationale
AU-01 asks for a documented audit and accountability policy, with procedures that put it into practice. The organisation shares both with the people who need them and reviews them on a set cycle. They govern the audit controls, from logging events to reviewing and keeping the records.
Gaps
PCI DSS asks for the procedures to be in daily use and known to all who apply them. Include time synchronisation in them, and check that staff follow them.
Mapped Controls
10.1.2 Roles and duties for audit logging
Rationale
AU-01 asks for an audit and accountability policy that sets out roles and responsibilities, and for an official who manages it. PS-09 writes the logging and log review duties into position descriptions. AT-03 gives role-based training to the people in those roles, before they start and at set intervals afterwards.
Gaps
PCI DSS asks for the people given these duties to understand them. Confirm that each one does, for example with a briefing or a signed acknowledgement.
10.2.1 Audit logging on every in-scope system and cardholder data store
Rationale
AU-02 has the organisation choose the event types each system logs, and explain why they will support later investigations. AU-12 makes the chosen system components generate audit records for those events.
Gaps
PCI DSS asks for logging on every in-scope system component and wherever cardholder data is held. List all of them as the components AU-12 covers.
10.2.1.1 Logging each user's access to cardholder data
Rationale
AU-02 has the organisation select user access to cardholder data as an event type to log. AU-12 generates a record of each access, including the identity of the user.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
10.2.1.2 Logging everything done with administrator rights
Rationale
AC-06(09) logs each time someone runs a privileged function. AU-02 has the organisation select administrator actions as event types to log, and AU-12 generates those records on each component.
Gaps
PCI DSS also asks for a record of any interactive use of application and system accounts. Add it to the event types in AU-02.
10.2.1.3 Logging every access to the audit logs themselves
Rationale
AU-02 has the organisation select access to the audit logs as an event type to log. AU-12 then generates a record of each such access, with the identity of whoever made it.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
10.2.1.4 Logging failed logons and other invalid access attempts
Rationale
AU-02 has the organisation select failed logons and other invalid access attempts as event types to log. AU-12 generates a record of each failed attempt on the components it covers.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
10.2.1.5 Logging changes to accounts, credentials and privileges
Rationale
AC-02(04) automatically audits the creation, modification, enabling, disabling and removal of accounts. AU-02 has the organisation select changes to accounts and credentials as event types to log, and AU-12 generates a record of each change.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
10.2.1.6 Logging audit logs being created, started, stopped or paused
Rationale
AU-02 has the organisation choose the event types it logs, which can include the start, stop and pause of audit logging. AU-12 generates those records on each component that logs.
Gaps
PCI DSS asks each component to record when its audit logging starts, stops or pauses, and when a new log begins. Check that every platform captures these events.
10.2.1.7 Logging added and removed system-level objects
10.2.2 Details recorded in each audit log entry 95%
Rationale
AU-03 asks each audit record to show the type of event, when and where it occurred, its source and its outcome. It also gives the identity of any person or object linked to the event.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
Mapped Controls
10.3.1 Limiting who can read the audit logs
Rationale
AC-06 grants each person only the access their job needs, log files included. AU-09 protects audit information from unauthorised access. AU-09(06) gives read-only access to a named subset of privileged users or roles. AU-09(04) lets only a chosen subset of them manage audit logging.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
10.3.2 Guarding stored audit logs against any change 90%
Rationale
AU-09 protects audit information from unauthorised change and deletion. AU-09(01) writes audit trails to hardware-enforced write-once media, and AU-09(03) protects their integrity with cryptography. AU-09(06) gives a named subset of privileged users read-only access.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
Mapped Controls
10.3.3 Prompt backup of logs to central, tamper-resistant storage
Rationale
AU-04(01) transfers audit logs from the system that produces them to a different system or media, at a frequency the organisation sets. AU-09(02) stores audit records on a physically separate system, and AU-09(01) writes them to write-once media.
Gaps
PCI DSS asks for logs to reach a central internal log server promptly, those from external-facing systems included. Set the transfer frequency in AU-04(01) to meet that.
10.3.4 Integrity monitoring that alerts on changes to logs
Rationale
AU-09 alerts named staff when someone changes or deletes audit information without authority. SI-07 runs integrity verification tools over the information the organisation names, here the stored logs. SI-07(02) notifies named people of any discrepancy those tools find.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
10.4.1 Daily log review for the CDE and security-critical systems 90%
Rationale
AU-06 reviews and analyses audit records for unusual activity, at a frequency the organisation sets, and reports what it finds. AU-06(04) lets reviewers analyse records from many components in one place.
Gaps
PCI DSS asks for a daily review of security events and of the logs from CDE systems, critical systems and systems with security functions. Set AU-06 to that frequency.
Mapped Controls
10.4.1.1 Automated tools for audit log review
Rationale
AU-06(01) brings automated mechanisms into log review, analysis and reporting. AU-07 provides tools to reduce audit records and report on them, and AU-07(01) sorts and searches them by chosen fields. SI-04(02) uses automated tools for near real-time analysis of events.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
10.4.2 Regular log review for the remaining in-scope systems 90%
Rationale
AU-06 reviews and analyses audit records for unusual activity at a frequency the organisation sets, and reports findings to named roles.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
Mapped Controls
10.4.2.1 Review cycle for other logs, set by targeted risk analysis
Rationale
AU-06 lets the organisation set how often it reviews audit records, and adjust the level of review when risk changes. RA-03 assesses and documents the risk to the system, which gives a basis for that frequency.
Gaps
PCI DSS asks for the review frequency to come from a targeted risk analysis that meets every element of Requirement 12.3.1. Document that analysis alongside the RA-03 results.
10.4.3 Following up anomalies found in log review
Rationale
AU-06 reports the findings of each log review to named roles so they can act on them. IR-04 handles the anomalies that prove to be incidents, from analysis and containment to recovery.
Gaps
PCI DSS asks for action on every exception and anomaly the review finds. Track each one to closure and record the outcome.
10.5.1 Keeping 12 months of logs, the latest three online
Rationale
AU-11 retains audit records for a period the organisation sets, to support later investigations, and AU-11(01) keeps long-term records retrievable. AU-04 allocates enough log storage to hold records for that period.
Gaps
PCI DSS sets retention at 12 months or more, with the latest three months ready for immediate analysis. Set those periods in AU-11 and size AU-04 storage to match.
10.6.1 Clock synchronisation on every system
Rationale
SC-45 synchronises clocks within and between systems and their components. AU-08 uses those internal clocks to time-stamp audit records, in UTC or with a stated offset from it.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
10.6.2 Central time servers fed by trusted outside sources
Rationale
SC-45(01) compares system clocks with an authoritative time source at a set frequency, and corrects any drift beyond a set limit. SC-45(02) names a secondary source in another region for use when the primary is unavailable. AU-08 records time stamps in UTC or with a stated offset from it.
Gaps
PCI DSS asks for designated central time servers that peer with each other. Only they take outside time, from chosen sources based on UTC or International Atomic Time. Point every other system at them.
10.6.3 Restricting and logging changes to time settings
Rationale
AC-06 limits access to time data to the people who need it. AC-06(01) reserves access to security functions and security-relevant information, such as the time configuration, for named roles. AU-02 has the organisation select changes to time settings as an event type to log. AU-12 generates those records, and AU-06 reviews them.
Gaps
PCI DSS asks the organisation to monitor and review each change to time settings on its critical systems. Make those systems part of the AU-06 review.
10.7.2 Prompt alerts when a critical security control fails
Rationale
AU-05 alerts named staff when audit logging fails and takes the actions the organisation sets. SI-06 checks that chosen security functions work, and alerts staff and acts when a check fails. CA-07 monitors how well controls work on an ongoing basis and responds to what it finds.
Gaps
PCI DSS lists the security systems to watch for failure, physical access and segmentation controls among them. Name each one among the functions SI-06 checks, and alert and act on failures promptly.
10.7.3 Recovery and follow-up after a security control fails
Rationale
IR-04 handles each failure as an incident, from containment to recovery, and feeds lessons learned back into procedures. IR-05 tracks and documents each one. SI-02(07) finds the root cause of a failure, then puts fixes in place and checks that they work.
Gaps
PCI DSS asks the organisation to look for security problems that came up while the control was down, and to confirm that monitoring has resumed. Add both steps to the incident procedures.
11.1.1 Policies and procedures for security testing
Rationale
CA-01, RA-01 and SI-01 ask for documented policies and procedures, shared with the people who need them and reviewed on a set cycle. CA-01's assessment policy governs penetration testing. RA-01's risk assessment policy governs vulnerability scanning. SI-01's integrity policy governs intrusion detection, change detection and payment page monitoring.
Gaps
PCI DSS asks for the procedures to be in daily use and known to all who apply them. Check that staff follow them in practice.
11.1.2 Roles and duties for security testing
Rationale
CA-01, RA-01 and SI-01 each ask for a policy that sets out roles and responsibilities, here for the testing and monitoring work. PS-09 writes those duties into position descriptions. AT-03 trains people for their role before they take on its duties, and again at a frequency the organisation sets.
Gaps
PCI DSS asks for the people given these duties to understand them. Confirm that each one does, for example with a briefing or a signed acknowledgement.
11.2.1 Quarterly checks for rogue wireless access points
Rationale
CM-08(03) uses automated tools to detect unauthorised hardware, such as a wireless access point, at a frequency the organisation sets. It then acts on each one it finds. SI-04(14) runs wireless intrusion detection to identify rogue wireless devices. SI-04(05) alerts named staff when the system generates signs of compromise.
Gaps
PCI DSS asks for a search for wireless access points at least once every three months. Set that frequency in CM-08(03).
11.2.2 Wireless access point inventory with business reasons
Rationale
CM-08 keeps an accurate inventory of system components, and here it lists each approved wireless access point. AC-18 sets the requirements for each type of wireless access and authorises it before connections are allowed. That approval is the basis for each access point on the list.
Gaps
PCI DSS asks for a written business reason for each approved access point. CM-08 lets the organisation choose what the inventory records, so add the reason there.
11.3.1 Quarterly internal vulnerability scans and rescans
Rationale
RA-05 scans for vulnerabilities at a frequency the organisation sets and remediates them by risk. RA-05(02) updates the vulnerabilities the tool checks for. CA-02 selects a suitable assessor, CA-02(01) makes the assessor independent and CA-02(02) adds vulnerability scanning to control assessments. SI-02 corrects the flaws the scans find.
Gaps
PCI DSS asks for internal scans at least once every three months. Set that frequency in RA-05, and rescan to confirm each high-risk and critical finding is fixed.
11.3.1.1 Risk-based fixing of lower-ranked vulnerabilities
Rationale
RA-03 assesses risk by identifying threats and vulnerabilities and judging the likelihood and size of harm. It documents the results. RA-05 remediates vulnerabilities within response times the organisation sets from its assessment of risk. SI-02 identifies, reports and corrects system flaws, the lower-ranked ones included.
Gaps
PCI DSS asks for the timing of these fixes to come from a targeted risk analysis that meets requirement 12.3.1. Use that analysis to set the RA-05 response times.
11.3.1.2 Authenticated internal vulnerability scanning
Rationale
RA-05(05) authorises privileged access for scanning on the components the organisation names, which lets scans run with credentials. RA-05(03) sets how broad and deep the scanning goes. AC-02 manages each scanning account like any other account, those that allow interactive logon included.
Gaps
PCI DSS asks for a record of every system that rejects scan credentials. Keep that list current and store it with the scan results.
11.3.1.3 Internal scanning after each significant change
Rationale
CM-04 analyses each change for its security impact before it goes in, and CM-04(02) checks the affected controls once it is made. RA-05 scans when new vulnerabilities may affect the system and remediates them by risk. CA-02 selects the assessor, and CA-02(01) makes the assessor independent. SI-02 corrects the high-risk and critical flaws the scan finds.
Gaps
PCI DSS asks for an internal scan after every significant change. Build that scan into the change process so each significant change triggers one.
11.3.2 Quarterly external scans by an Approved Scanning Vendor
Rationale
CA-02 selects the right assessor for each type of assessment, here an outside scanning vendor, and CA-02(01) makes that assessor independent. RA-05 scans for vulnerabilities at a frequency the organisation sets and remediates them by risk. SI-02 corrects the flaws the external scans report.
Gaps
PCI DSS asks for an external scan every three months by an Approved Scanning Vendor. Each quarter's scan must meet the ASV Program Guide's criteria for a pass, so rescan until it does.
11.3.2.1 External scanning after each significant change
Rationale
CM-04 analyses each change for its security impact, and CM-04(02) verifies the affected controls after the change. RA-05 scans for vulnerabilities, here from outside the network, and remediates them by risk. CA-02 selects the assessor, and CA-02(01) makes the assessor independent. SI-02 corrects the flaws the scan finds.
Gaps
PCI DSS asks for every finding with a CVSS score of 4.0 or higher to be fixed. Set that threshold in RA-05 and rescan to confirm each fix.
11.4.1 Penetration testing methodology and what it covers
Rationale
CA-02 asks for an assessment plan that sets the scope and procedures of each assessment and is approved before it starts. Here that plan serves as the penetration testing methodology. CA-08 runs penetration tests on the systems the organisation names, at a frequency it sets.
Gaps
PCI DSS sets out what the methodology must include. Cover segmentation testing, the application and network layers and the threats seen in the past year. Keep test results and remediation records for at least 12 months.
11.4.2 Internal penetration tests, yearly and after major changes 85%
Rationale
CA-08 runs penetration tests on the systems the organisation names, at a frequency it sets, here from inside the network. CA-08(01) gives the testing to an independent agent or team.
Gaps
PCI DSS asks for an internal test at least once a year and again after any significant upgrade or change. Put both in the CA-08 test schedule.
Mapped Controls
11.4.3 External penetration tests, yearly and after major changes 85%
Rationale
CA-08 runs penetration tests on the systems the organisation names, at a frequency it sets, here from outside the network. CA-08(01) hands the testing to an independent agent or team.
Gaps
PCI DSS asks for an external test at least once a year and again after any significant upgrade or change. Put both in the CA-08 test schedule.
Mapped Controls
11.4.4 Fixing and retesting penetration test findings
Rationale
CA-05 records the planned fix for each weakness the tests find and keeps that plan up to date. RA-07 responds to each finding in line with the organisation's risk tolerance. SI-02 corrects the flaws. CA-08 runs the penetration tests, here repeated to confirm each fix works.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
11.4.5 Yearly penetration tests of CDE segmentation
Rationale
CA-02 assesses whether controls work as intended, here whether segmentation keeps the CDE apart from other networks. CA-08 runs penetration tests on the segmentation controls at a frequency the organisation sets, and CA-08(01) gives the work to an independent tester or team.
Gaps
PCI DSS asks for a test of every segmentation method once a year or more often, and after any change to it. Set that frequency in CA-08.
11.4.6 Six-monthly segmentation tests for service providers
Rationale
CA-02 assesses whether controls work as intended, here whether segmentation isolates the CDE from systems out of scope. CA-08 runs penetration tests on the segmentation controls at a frequency the organisation sets. CA-08(01) gives the tests to an independent tester or team.
Gaps
PCI DSS asks the service provider to test every segmentation method every six months or more often, and after any change to it. Set that frequency in CA-08.
11.4.7 Multi-tenant providers' support for customer penetration tests
Rationale
CA-08 runs penetration tests on the systems the organisation names, here the infrastructure each customer subscribes to. CA-02 gives the results of each assessment to the people or roles the organisation names, here its customers.
Gaps
PCI DSS asks the multi-tenant service provider to support each customer's external penetration testing. Give each customer evidence of external tests on its infrastructure that meet requirement 11.4.3, or prompt access to run its own.
11.5.1 Intrusion detection and prevention for CDE traffic
Rationale
SC-07 monitors and controls traffic at the external boundary and at key internal interfaces. SI-04 monitors the system for attacks and signs of attack. SI-04(01) ties the intrusion detection tools together across the whole system, SI-04(04) watches inbound and outbound traffic, and SI-04(05) alerts staff to signs of compromise.
Gaps
PCI DSS asks for current signatures, baselines and detection engines on every intrusion detection and prevention tool. Update them as part of SI-04 monitoring.
11.5.1.1 Service providers' detection of covert malware channels
Rationale
SC-07(09) detects and denies outgoing traffic that threatens external systems, and SC-07(10) prevents exfiltration. SI-04(18) analyses outbound traffic at the boundary and at chosen interior points to find covert exfiltration. SI-04(11) analyses the same traffic for anomalies.
Gaps
PCI DSS asks the service provider to detect and deal with covert command-and-control channels, such as DNS tunnelling. Point the sensors at those routes and respond to every alert.
11.5.2 Weekly integrity checks on critical files 90%
Rationale
SI-07 uses integrity verification tools to detect unauthorised changes to the software, firmware and information the organisation names, here its critical files. SI-07(01) runs integrity checks at a frequency the organisation sets. SI-07(02) notifies named staff when a check finds a discrepancy.
Gaps
PCI DSS asks for critical files to be compared at least once a week. Set that frequency in SI-07(01).
Mapped Controls
11.6.1 Detecting tampering with payment page scripts and headers
Rationale
SC-18 sets which mobile code, such as JavaScript, is acceptable, and monitors and controls its use, here on payment pages. SI-07 detects unauthorised changes to named information, here the page scripts and headers, and SI-07(02) notifies staff when it finds one. SI-04 watches for signs of attack, and SI-04(24) gathers known indicators of compromise.
Gaps
PCI DSS asks for the check to see headers and scripts as the shopper's browser receives them. Run it at least once a week, or on a schedule set by a targeted risk analysis under requirement 12.3.1.
12.1.1 Information security policy shared with staff and partners
Rationale
PM-01 asks for an organisation-wide information security programme plan that sets out the programme's requirements and the controls that meet them. A senior official approves it. The organisation shares it and keeps it up to date on a cycle it sets. The policy controls of the other families, such as AC-01 and IR-01, supply the policy for each topic the overall policy covers, under OSA's rule for policy clauses, which follows NIST's crosswalks.
Gaps
PCI DSS asks for the policy to reach relevant vendors and business partners as well as staff. Send each of them the current version.
12.1.2 Yearly review and update of the security policy
Rationale
PM-01 has the organisation review and update its information security programme plan at a frequency it sets. The organisation also updates the plan after events it defines, such as a change in business objectives or risk. The policy control of each other family, such as AC-01 and IR-01, does the same for the policy on its topic, under OSA's rule for policy clauses, which follows NIST's crosswalks.
Gaps
PCI DSS sets a review at least every 12 months. Set that frequency in PM-01 and in each policy control.
12.1.3 Security duties for all staff and their acknowledgement
Rationale
PM-01's programme plan identifies security roles and responsibilities and assigns them. PS-09 writes security duties into each position description. PL-04 gives each person who needs access the rules for their security responsibilities, and receives their documented acknowledgement before granting it.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
12.1.4 An executive in charge of information security 95%
Rationale
PM-02 appoints a senior information security officer, such as a CISO, to lead the organisation-wide security programme. It gives that officer the mission and the resources to develop the programme and keep it running.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
Mapped Controls
12.2.1 Acceptable use rules for end-user technology
Rationale
PL-04 sets rules of behaviour for using information and systems, and collects each user's documented acknowledgement. AC-19 sets configuration and connection requirements for mobile devices and authorises each connection. CM-07(05) and (09) keep lists of the software and hardware approved for use and block everything else.
Gaps
PCI DSS asks for acceptable use rules for each end-user technology, such as laptops, phones, removable media, email and internet use. Record who approved each technology for use.
12.3.1 Targeted risk analysis for frequencies the organisation sets 85%
Rationale
RA-03 has the organisation identify threats and vulnerabilities and judge the likelihood and impact of harm. The organisation documents the results and reviews them at a frequency it sets. It updates the assessment after significant changes.
Gaps
PCI DSS asks for a separate written analysis for each requirement that lets the organisation choose a frequency. Justify each chosen frequency, and review each analysis at least every 12 months.
Mapped Controls
12.3.2 Targeted risk analysis for the customised approach
Rationale
RA-03 provides the documented risk analysis behind each customised control. PL-02's security plan describes the controls in place and the reasons for any tailoring, and can serve as the controls matrix. The authorising official approves the plan before it takes effect.
Gaps
PCI DSS Appendix D lists the evidence each customised control needs, such as a controls matrix. Prepare it, and repeat the analysis at least every 12 months.
12.3.3 Inventory and yearly review of cipher suites and protocols
Rationale
SC-13 has the organisation determine each use of cryptography and the type of cryptography that use requires. SI-05 receives security alerts and advisories from outside organisations on an ongoing basis, such as news that an algorithm or protocol has weakened.
Gaps
PCI DSS asks for a list of every cipher suite and protocol in use, with its purpose and location. Review it at least every 12 months, and keep a plan for replacing any that weaken.
12.3.4 Yearly review of vendor support for technology in use
Rationale
SA-22 replaces components once their supplier stops supporting them, or arranges other support for them. CA-05 records planned remediation in a plan of action and milestones, here the replacement of outdated technology.
Gaps
PCI DSS asks for a review of all hardware and software at least every 12 months, recording any vendor end-of-life notices. Have senior management approve the plan to replace outdated technology.
12.4.1 Executive accountability for PCI DSS compliance
Rationale
PM-01 has a senior official, accountable for the risk, approve the organisation-wide security programme plan. The plan assigns roles and responsibilities and covers compliance. PM-02 appoints a senior information security officer to lead the programme, with the mission and resources it needs.
Gaps
PCI DSS asks executive management to hold overall accountability for PCI DSS compliance. Write a charter for the compliance programme and report on it to executive management.
12.4.2 Quarterly checks that staff follow security procedures
Rationale
CA-02 assesses whether controls operate as intended, at a frequency the organisation sets, and CA-02(01) uses independent assessors. CA-07 runs ongoing control assessments, and CA-07(01) has independent assessors do the monitoring. CA-07(05) checks that policies are in place and that controls run consistently.
Gaps
PCI DSS sets these checks at least every three months. Set that frequency in CA-02 and CA-07, and cover each task the requirement lists, such as log reviews and change control.
12.4.2.1 Recording the quarterly checks and their sign-off
Rationale
CA-02 produces a report of each assessment and gives the results to the roles the organisation names. CA-05 documents the planned remediation of each weakness found, in a plan of action and milestones.
Gaps
PCI DSS asks the owner of the compliance programme to review and sign off the results. Name that owner among the roles that receive the CA-02 report.
12.5.1 Inventory of in-scope system components 90%
Rationale
CM-08 keeps an accurate, complete inventory of system components, with the details the organisation sets for accountability. The organisation reviews and updates it at a frequency it chooses.
Gaps
PCI DSS asks for each component's function or use in the inventory. Add it to the details CM-08 records.
Mapped Controls
12.5.2 Confirming PCI DSS scope every year
Rationale
CM-08 inventories every component in the system. CM-12 records where account data is processed and stored, on which components, and each change of location. CA-03 approves each exchange of information with other systems, including those of third parties, and documents it in an agreement. PL-02's security plan defines the system's components, operating environment and connections. The organisation reviews the plan on a cycle it sets.
Gaps
PCI DSS sets a scope check at least every 12 months and after each significant change. Set that cycle for the PL-02 review. Cover the data flows, and justify each network that segmentation keeps out of scope.
12.5.2.1 Confirming PCI DSS scope every six months
Rationale
CM-08 inventories every component in the system. CM-12 records where account data is processed and stored, and on which components. CA-03 documents each exchange of information with other systems, third parties included, in an agreement. PL-02's security plan defines the system's components and connections, and the organisation reviews it on a cycle it sets.
Gaps
PCI DSS asks the service provider to confirm its scope at least every six months and after each significant change. Set that cycle for the PL-02 review.
12.5.3 Scope and control review after a reorganisation
Rationale
PL-02 updates the security plan when the system or its operating environment changes. RA-03 updates the risk assessment after significant changes and shares the results with the roles the organisation names.
Gaps
PCI DSS treats a significant change in the organisation's structure as a trigger for a written review of scope and controls. Report the results to executive management.
12.6.1 Formal security awareness programme for all staff
Rationale
AT-01 asks for a documented awareness and training policy and procedures, shared with the people who need them and reviewed on a set cycle. AT-02 gives security awareness training to every user of the system, managers and contractors included. Together they make awareness a formal programme.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
12.6.2 Yearly review and refresh of awareness content 90%
Rationale
AT-02 updates awareness content at a frequency the organisation sets and after events it names. It also builds lessons from security incidents, inside and outside the organisation, into the training.
Gaps
PCI DSS sets a review of the awareness programme at least once every 12 months. Set that frequency in AT-02.
Mapped Controls
12.6.3 Awareness training at hire and yearly, with policy sign-off
Rationale
AT-02 trains new users when they start and again at a frequency the organisation sets, using awareness techniques it chooses. PL-04 gets each user's documented acknowledgement of the rules of behaviour, and asks for it again at a set frequency or when the rules change.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
12.6.3.1 Teaching staff to spot phishing and social engineering 95%
Rationale
AT-02 gives security awareness training to all users. AT-02(03) trains them to recognise and report social engineering, and AT-02(04) to recognise suspicious communications such as phishing emails. AT-02(01) adds practical exercises that simulate incidents, such as a staged phishing attack.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
Mapped Controls
12.6.3.2 Acceptable use rules in awareness training
Rationale
PL-04 sets the rules for each user's responsibilities and expected behaviour in using information and systems, which covers acceptable use. AT-02 provides awareness training that can carry those rules. SP 800-53 accepts training that covers the rules as the acknowledgement PL-04 asks for.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
12.7.1 Background checks before hiring staff with CDE access
Rationale
PS-02 gives every position a risk designation and sets screening criteria for the people who fill it. PS-03 screens each person before they are given access to the system, and screens them again under conditions the organisation sets.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
12.8.1 Inventory of service providers that touch account data
Rationale
PM-30 sets an organisation-wide strategy for supply chain risk, and PM-30(01) identifies, prioritises and assesses the suppliers of critical products and services. SA-09 defines and documents the oversight, roles and responsibilities for each external service the organisation uses.
Gaps
PCI DSS asks for a list of every service provider that holds account data or could affect its security. Describe what each one provides, and keep the list current.
12.8.2 Contracts where service providers accept responsibility for data
Rationale
SA-04 writes security requirements into each contract and names the parties responsible for information security. SA-09 requires providers of external services to meet the organisation's security requirements, and documents the oversight, roles and responsibilities that go with each service.
Gaps
PCI DSS asks each service provider to accept, in writing, responsibility for the account data it handles or could affect. Get that acknowledgement into every service provider agreement.
12.8.3 Due diligence before taking on a service provider
Rationale
SR-06 assesses and reviews the supply chain risks of each supplier and the services it provides. SR-05 sets the acquisition strategies and procurement methods that guard against supply chain risk, and SR-05(02) assesses a service before it is selected. SA-09(01) assesses risk and gets approval before the organisation outsources information security services.
Gaps
PCI DSS asks for a set process for engaging service providers, with due diligence done before the agreement is signed. Write that process down and apply it to every new provider.
12.8.4 Yearly check of each service provider's PCI DSS status
Rationale
SA-09 monitors each external provider's compliance with the required controls on an ongoing basis, by methods the organisation chooses. SR-06 reviews the risks of each supplier and its services at a frequency the organisation sets.
Gaps
PCI DSS asks the organisation to check, at least once every 12 months, each service provider's compliance status. Set that frequency in SR-06.
12.8.5 Responsibility split for PCI DSS requirements, per provider
Rationale
SA-04 allocates responsibility for information security between the parties in each contract. SA-09 defines and documents the organisation's oversight and the roles and responsibilities that go with each external service.
Gaps
PCI DSS asks for a record of which PCI DSS requirements each service provider manages, which the organisation manages and which they share. Keep it as a responsibility matrix for each provider.
12.9.1 Service provider's written acknowledgement to customers
Rationale
CA-03 records each party's security requirements, controls and responsibilities in the agreement that governs an exchange of information. SA-09 is the customer's side of the same duty: it requires providers of external services to meet the customer's security requirements.
Gaps
PCI DSS asks the service provider to accept, in writing, responsibility for the account data it handles for each customer or could affect. Put that acknowledgement in every customer agreement.
12.9.2 Service provider's answers to customer compliance requests
Rationale
SA-09 is the customer's side of this duty: it monitors each provider's control compliance and documents the roles and responsibilities around each service. SR-08 sets agreements with the parties in a supply chain to share the results of assessments and audits, such as a PCI DSS compliance status.
Gaps
PCI DSS asks the service provider to give customers, when they ask, its PCI DSS compliance status and the split of responsibilities for each service. Set up a way to answer those requests.
12.10.1 Incident response plan and what it covers
Rationale
IR-08 sets out the incident response plan, with its structure, the incidents to report, how incident information is shared and who is responsible. IR-04 handles incidents through containment, eradication and recovery, in step with contingency planning. IR-06 reports incident information to the authorities the organisation names. CP-02 covers business recovery and continuity, and CP-09 provides the backups the plan relies on.
Gaps
PCI DSS asks the plan to name the payment brands and acquirers to notify and to include the brands' own response procedures. Add an analysis of the legal duties to report a compromise.
12.10.2 Yearly incident response plan review and full test
Rationale
IR-08 has the plan reviewed and approved at a frequency the organisation sets, and updated after changes or problems found in use or testing. IR-03 tests how well the incident response capability works, at a set frequency and with tests the organisation chooses.
Gaps
PCI DSS asks for a review and a full test of the plan at least once every 12 months, covering each element of 12.10.1. Set that frequency in IR-03 and IR-08.
12.10.3 Named incident responders on call around the clock
Rationale
IR-08 designates the people or roles responsible for incident response. IR-04 handles incidents, and IR-04(14) adds a security operations centre that monitors systems and responds to incidents on an ongoing basis.
Gaps
PCI DSS asks for named people available to respond at any hour of any day. Keep a 24/7 rota of named responders.
12.10.4 Training incident responders in their duties 95%
Rationale
IR-02 trains each person with an incident response role within a set time of taking it on, and again at a frequency the organisation sets. It also reviews and updates the training content on a set cycle and after events the organisation names.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
Mapped Controls
12.10.4.1 Responder training frequency set by targeted risk analysis
Rationale
IR-02 trains incident responders at a frequency the organisation sets. RA-03 supplies a documented risk assessment, weighing threats, vulnerabilities, likelihood and harm, on which the organisation can base that frequency.
Gaps
PCI DSS asks for a targeted risk analysis that sets the training frequency and covers every element of Requirement 12.3.1. Write that analysis and record the frequency it sets in IR-02.
12.10.5 Alert handling in the incident response plan
Rationale
SI-04 monitors systems for attacks and unauthorised connections. SI-04(05) alerts named staff to signs of compromise, and SI-04(07) notifies incident responders and acts on suspicious events. SI-07(07) feeds the unauthorised changes it detects into incident response. IR-04 handles incidents from detection and analysis onward, and IR-08 sets out the plan and defines which incidents to report.
Gaps
PCI DSS names the alert sources the plan must cover. They include intrusion detection, network security controls, file change detection, payment page tamper alerts and wireless scans. Name each in the plan.
12.10.6 Updating the response plan from lessons and industry change
Rationale
IR-04 builds lessons learned from incident handling into response procedures, training and testing. IR-08 updates the plan for changes to the system and the organisation, and for problems found while using or testing it.
Gaps
PCI DSS also asks for the plan to keep pace with industry developments. Add them to the events that trigger an update.
12.10.7 Responding when stored PAN turns up somewhere unexpected
Rationale
IR-09 responds to information spills. It names who responds, identifies the data, isolates and cleans the affected system and looks for other systems the spill reached. IR-04 analyses the incident, contains it, recovers from it and turns lessons learned into changes.
Gaps
PCI DSS asks the organisation to check whether sensitive authentication data sits alongside the stray PAN, and to trace how the data got there. Add both steps to the procedure.
A1.1.1 Two-way separation of provider and customer environments
Rationale
AC-03 enforces approved authorisations for logical access, so the provider and its customers reach each other's environments only when authorised. SC-07 controls traffic at the managed interfaces between them, and SC-07(21) uses boundary protection to isolate the components the organisation names. SC-50 enforces separation in software between security domains.
Gaps
PCI DSS asks for separation in both directions. Check that customers reach the provider's environment, and the provider reaches theirs, only with authorisation.
A1.1.2 Customer-to-customer separation of data and CDE
Rationale
AC-03 enforces approved authorisations, so each customer's access stops at its own environment and data. SC-04 stops information passing between customers through shared resources, such as memory or storage that one user releases and the next reuses.
Gaps
SP 800-53 states this more generally than PCI DSS. Check the controls against the requirement's own text.
A1.1.3 Keeping each customer within its allocated resources
Rationale
AC-03 enforces approved authorisations to system resources for each customer. SC-06 allocates resources such as processing, storage and bandwidth by quota or priority, so each customer stays within its share and the others keep theirs.
Gaps
PCI DSS asks the service provider to hold each customer to its own allocation. Set quotas on each customer's compute, storage and network, and enforce them.
A1.1.4 Penetration tests of customer separation every six months
Rationale
CA-08 runs penetration tests on the systems the organisation names, at a frequency it sets. CA-02 assesses whether controls, here the separation between customer environments, work as intended and produce the desired outcome.
Gaps
PCI DSS sets penetration testing of the separation at least once every six months. Set that frequency in CA-08.
A1.2.1 Audit logs for each customer, readable by that customer
Rationale
AU-02 selects the events to log in each customer environment, and AU-12 generates audit records for them on the components the organisation names. AU-09 protects the logs from unauthorised access, so only the owning customer reads them. AU-16 coordinates audit information that crosses organisational boundaries, and AU-16(02) shares it with each customer under an agreement.
Gaps
PCI DSS asks the service provider to tell each customer where its logs are. Keep their content and retention in line with Requirement 10.
A1.2.2 Forensic investigation support for every customer
Rationale
IR-07 offers a support resource for handling and reporting incidents, which can include access to forensic services. IR-04 handles incidents. IR-04(12) analyses malicious code and other traces an incident leaves behind, and IR-04(10) coordinates incident handling with the other organisations in the supply chain.
Gaps
PCI DSS asks for prompt forensic support for any customer after a suspected or confirmed incident. Agree with each customer in advance how its investigators reach the evidence.
A1.2.3 Customer reporting channel for incidents and vulnerabilities
Rationale
IR-07 gives the system's users, customers included, a support resource for reporting incidents, and IR-04 handles the incidents they report. RA-05(11) sets up a public channel for vulnerability reports, and RA-05 remediates vulnerabilities in line with an assessment of risk. SI-02 identifies and corrects flaws in the system.
Gaps
PCI DSS asks for a secure channel for customer reports. Protect that channel, and tell customers about the issues that affect them.
A2.1.1 Known-exploit check for POI terminals on SSL or early TLS 75%
Rationale
RA-05 monitors and scans for vulnerabilities at a frequency the organisation sets, and again when new ones are reported. Applied to the terminals, it shows whether any known SSL or early TLS exploit affects them.
Gaps
PCI DSS asks the organisation to confirm that each terminal resists the known SSL and early TLS exploits. Keep evidence of this, such as vendor statements.
Mapped Controls
A2.1.2 Service provider's plan to retire SSL and early TLS
Rationale
RA-03 assesses the risk of the remaining SSL and early TLS connections and documents the results. RA-05 monitors for new vulnerabilities in those protocols. CM-03 reviews each proposed change for its security impact, which keeps the old protocols out of new environments. CA-05 sets out the migration as planned remediation, with milestones.
Gaps
PCI DSS asks the plan to describe how SSL and early TLS are used. Record in it where they run and what data they carry.
A2.1.3 Secure connection option for customers' POI terminals
Rationale
SC-08 protects the confidentiality and integrity of data in transit, and SC-08(01) does it with cryptography. SC-13 has the organisation decide the type of cryptography each use requires, such as a current version of TLS.
Gaps
PCI DSS asks the service provider to give every customer a connection option on a secure protocol version. Customers can then move their terminals off SSL and early TLS.
Methodology and Disclaimer
This coverage analysis maps from PCI DSS v4.0.1 clauses/requirements back to NIST SP 800-53 Rev 5 controls, assessing how well the SP 800-53 control set addresses each framework requirement.
Coverage weighting represents an informed estimate based on control-objective alignment, not a definitive compliance determination. Weightings consider whether SP 800-53 controls address the intent of each framework requirement, even where terminology and structure differ.
This analysis should be validated by qualified assessors for use in compliance or audit activities. The authoritative source for any compliance determination is always the framework itself.