PCI DSS v4.0.1
PCI DSS applies to any business that accepts, processes, stores, or transmits payment card data. It covers the cardholder data environment and the systems connected to it.
About this standard
The Payment Card Industry Data Security Standard applies to any business that stores, processes, or transmits payment card data, from retailers and restaurants to medical offices that take cards. It applies to the cardholder data environment (CDE) and anything that connects to it, so a finding counts toward PCI DSS when the device or account is in that scope. Requirement numbers are from PCI DSS v4.0.1; the standard's text is copyrighted, so the descriptions are Trimtab's summaries. Read the full requirement in the PCI SSC document library.
Official sources:
Trimtab checks 26 of this standard's requirements with technical evidence. Requirements about policies, training, and physical security need their own evidence and are not listed here.
Requirement 1: Network security controls (1)
1.5.1
Security controls on devices that use untrusted networks
Computers that touch both the internet and the card environment need protections, like a firewall, that stay on and users can't switch off.
Proven by: FW-001
Requirement 2: Secure configurations (2)
2.2.2
Vendor default accounts managed
Built-in accounts are disabled when unused, or given a strong new password if they're used.
Proven by: ACC-002, ACC-003, ACC-008
2.2.4
Only necessary services enabled
Turn off services and features the system doesn't need, so there's less to attack.
Proven by: HRD-001, HRD-002, HRD-003, HRD-004
2.2.5
Insecure services justified and secured
Avoid old, insecure protocols. Any you must keep need a documented reason and extra protection.
Proven by: HRD-001, HRD-010, M365-003, EXO-006, SPO-001
Requirement 4: Strong cryptography in transmission (4)
4.2.1
Strong cryptography for card data in transit
Card numbers sent over the internet must use strong, modern encryption.
Requirement 5: Protection from malicious software (5)
5.2.1
Anti-malware deployed
Install anti-malware on every system, except ones a documented review finds aren't at risk.
5.3.1
Anti-malware kept current
Anti-malware must update itself automatically.
Proven by: AV-002
5.3.2
Anti-malware scans or real-time protection
Anti-malware must scan regularly or watch continuously in real time.
5.3.5
Anti-malware can't be disabled by users
Users can't turn anti-malware off unless management approves a specific, time-limited exception.
Proven by: AV-003
5.4.1
Protection against phishing
Use automated protections that detect phishing and protect staff from it.
Proven by: EXO-007, EXO-008, EXO-009, EXO-010, EXO-011, EXO-012, EXO-013, EXO-014, EXO-015, EXO-020
Requirement 6: Secure systems and software (6)
6.3.3
Security patches installed
Install security updates, with critical and high-risk ones within one month of release.
Proven by: PAT-001, PAT-002, PAT-004
Requirement 7: Access by business need to know (7)
7.2.2
Least privilege
Give users, including admins, only the access their job needs.
Proven by: ACC-001, ACC-009, M365-005, M365-006, M365-007, M365-008, M365-013, M365-021, M365-026
Requirement 8: Identification and authentication (8)
8.2.2
Shared accounts limited
Avoid shared and generic logins. Allow them only as approved exceptions you can trace to a person.
Proven by: ACC-002, ACC-003, EXO-016
8.2.6
Inactive accounts removed
Remove or disable accounts that haven't been used in 90 days.
8.2.8
Idle sessions re-authenticate
After 15 minutes idle, people must sign in again before continuing.
8.3.2
Authentication factors protected
Passwords and other sign-in secrets must be unreadable when stored or sent.
Proven by: HRD-007, HRD-008, HRD-009, M365-016
8.3.4
Lockout after failed attempts
Lock an account after no more than 10 wrong attempts, for at least 30 minutes or until identity is confirmed. For PCI DSS clients, Trimtab checks both.
Proven by: ACC-004
8.3.6
Password length and complexity
Passwords need at least 12 characters, with both letters and numbers.
Proven by: ACC-005, ACC-006, M365-025
8.3.7
Password reuse
A new password can't match any of the last four.
Proven by: ACC-007
8.4.2
MFA for access into the CDE
Require multifactor authentication for all non-console access into the card environment, including cloud services in scope.
Proven by: M365-001, M365-002, M365-003, M365-004, EXO-005, EXO-006, SPO-001, M365-020
8.4.3
MFA for remote access
Require multifactor authentication for remote access from outside your network that could reach the card environment.
Requirement 10: Logging and monitoring (10)
10.2.1
Audit logs enabled
Turn on audit logging for all systems in scope and keep it running.
Proven by: AUD-001, AUD-003, AUD-004, EXO-001, EXO-002
10.5.1
Audit log retention
Keep audit logs for at least 12 months, with the last three months ready to review. A device's own log rarely holds that much; forward logs to a central store.
Proven by: AUD-002
10.6.1
Time synchronization
Keep every system's clock synchronized so log times line up.
Proven by: AUD-005
Requirement 12: Policies and programs (12)
12.3.4
Technologies reviewed, including end of life
At least once a year, review your hardware and software, including anything nearing end of support, and plan replacements.
Proven by: PAT-003
12.5.1
Inventory of system components
Keep a current list of every system in scope and what it does.