Skip to content
STC
Free Assessment

PCI DSS Gap Analyzer

Walk through 38 questions across all 12 PCI DSS requirements. Get an instant compliance score, prioritized gap list, and actionable remediation guidance for your cardholder data environment.

Progress: 0 of 38 answered0%
Q1
CriticalReq 1: Firewalls

Firewall rules are documented and reviewed every six months.

Q2
CriticalReq 1: Firewalls

Default passwords on network security devices have been changed.

Q3
HighReq 1: Firewalls

Cardholder data environment (CDE) is segmented from the rest of the corporate network.

Q4
CriticalReq 2: Defaults

Default system passwords and security parameters have been changed before deployment.

Q5
HighReq 2: Defaults

Only necessary services, protocols, and functions are enabled on systems in the CDE.

Q6
CriticalReq 3: Data Protection

Primary account numbers (PANs) are rendered unreadable (encrypted or tokenized) wherever stored.

Q7
CriticalReq 3: Data Protection

Encryption keys are stored securely and managed with a formal key-management program.

Q8
HighReq 3: Data Protection

PAN display is masked (showing only the last 4 digits) except when required by business need.

Q9
CriticalReq 4: Encryption

Strong cryptography (TLS 1.2 or higher) is used to protect CHD in transit across open/public networks.

Q10
HighReq 4: Encryption

All transmission of CHD over internal networks is encrypted.

Q11
HighReq 5: Anti-Malware

Anti-malware software is deployed on all systems commonly affected by malware (desktops, laptops, servers).

Q12
HighReq 5: Anti-Malware

Anti-malware mechanisms are actively running, cannot be disabled by users, and generate audit logs.

Q13
CriticalReq 6: Secure Systems

Security patches are applied within 30 days of release (critical patches within 15 days).

Q14
HighReq 6: Secure Systems

A formal software development lifecycle (SDLC) includes security reviews for in-scope applications.

Q15
HighReq 6: Secure Systems

Public-facing web applications are protected by an automated technical solution (WAF or code review).

Q16
CriticalReq 7: Access

Access to CHD is restricted on a need-to-know basis with documented business justification.

Q17
HighReq 7: Access

System access is assigned based on job role and minimum necessary privilege.

Q18
CriticalReq 8: Authentication

Strong password policies enforce minimum length (12+ chars), complexity, expiration, and history.

Q19
CriticalReq 8: Authentication

Multi-factor authentication (MFA) is required for all remote and administrative access to the CDE.

Q20
HighReq 8: Authentication

Unique user IDs exist for each person with access to CHD, shared or generic accounts are not used.

Q21
HighReq 9: Physical

Physical access to areas where CHD is processed, stored, or transmitted is restricted and monitored.

Q22
HighReq 9: Physical

All media containing CHD is physically secured and access is logged.

Q23
MediumReq 9: Physical

Media destruction of CHD follows approved procedures and is documented.

Q24
CriticalReq 10: Logging

Audit trails capture all individual user access to CHD and all administrative actions.

Q25
HighReq 10: Logging

System clocks and time settings are synchronized across all in-scope systems.

Q26
HighReq 10: Logging

Logs are protected from tampering and retained for at least 12 months (3 months immediately available).

Q27
CriticalReq 11: Testing

Network vulnerability scans are performed quarterly by an Approved Scanning Vendor (ASV).

Q28
CriticalReq 11: Testing

Penetration testing is performed annually and after significant infrastructure changes.

Q29
HighReq 11: Testing

Intrusion detection/prevention systems (IDS/IPS) monitor all traffic in and out of the CDE.

Q30
HighReq 11: Testing

File integrity monitoring (FIM) detects unauthorized changes to critical system files.

Q31
CriticalReq 12: Policy

A formal information security policy exists, is approved by management, and is reviewed annually.

Q32
CriticalReq 12: Policy

A risk assessment is performed annually and after significant changes.

Q33
HighReq 12: Policy

An incident response plan exists, is tested annually, and includes notification procedures.

Q34
HighReq 12: Policy

A formal change management process is followed for all changes to the CDE.

Q35
HighReq 12: Policy

Third-party service providers with CHD access are assessed and monitored.

Q36
MediumReq 12: Policy

Employees acknowledge the security policy upon hire and annually thereafter.

Q37
HighReq 12: Policy

Security awareness training is delivered to all personnel with CHD access.

Q38
MediumReq 12: Policy

Screening of new hires includes background checks for personnel with CHD access.

Recommended Training

PCI DSS

For any team that handles payment card information

Requirement 12.6 requires a formal security awareness program for everyone who touches cardholder data. This course closes the exact gaps you just found.

Free to use this tool, no signup required. Training is billed per seat, annually.

Talk with Us