Site icon RSI Security

PCI DSS Assessment Findings: Where Evidence Falls Short

Assessors work from the testing procedures published in PCI DSS v4.0.1, so a gap usually surfaces as evidence that doesn’t match a procedure. The patterns below are derived from what those procedures examine. They illustrate what a gap would look like and do not describe specific organizations.

How a finding gets decided

A ROC records one of four results for each requirement: In Place, Not Applicable, Not Tested, or Not in Place. The template uses Not in Place when some or all elements are unmet, still being implemented, or need further testing. Section 12 of the standard adds that planned controls don’t count as in place. After remediation, the assessor reassesses. The common mistakes guide covers pitfalls more broadly.

Patterns drawn from the testing procedures

Scope that was documented but not confirmed

Assessors look for: documented results of scope reviews under Requirement 12.5.2, covering every listed element, plus data-flow diagrams under Requirement 1.2.4.

A gap would look like: a diagram that predates a new payment channel, or a scope review that omits backups or third-party connections.

Recurring activities with missing cycles

Assessors look for: records across time. Procedures 11.3.1.a and 11.3.2.a examine scan reports from the last 12 months. Procedures 1.2.7.b and 7.2.4.b examine reviews due at least once every six months.

A gap would look like: three quarterly scan reports where four were due, or an access review with no management acknowledgment.

Flexible frequencies with no risk analysis behind them

Assessors look for: a TRA containing every element of Requirement 12.3.1, wherever a requirement lets the entity set the frequency. Examples include 5.3.2.1 for malware scans and 10.4.2.1 for log reviews.

A gap would look like: a policy stating a frequency with no documented analysis. Another would be using a TRA to stretch a frequency the standard already fixes.

Payment page scripts managed only in part

Assessors look for: inventory records and configurations under procedure 6.4.3.b, and monitored pages and monitoring results under 11.6.1.a. Requirement 11.6.1 concerns payment pages as received by the consumer browser.

A gap would look like: an inventory with no written justification for each script, or monitoring that never evaluates the page the browser receives. Scripts on a merchant page that embeds a processor’s iframe also remain the merchant’s responsibility.

Multi-factor authentication with holes

Assessors look for: configurations and observed logins under 8.4.2 and 8.4.3, and MFA system settings under 8.5.1.

A gap would look like: MFA at the VPN but not again when moving into the CDE, vendor remote access left on one factor, or an open-ended administrator bypass.

Exclusions and logs without support

Assessors look for: periodic evaluations for any component without anti-malware, under procedure 5.2.1.b. Under 10.5.1, they check for 12 months of log history, with the latest three months immediately available.

A gap would look like: a server class excluded by habit rather than evaluation, or older logs that can’t be retrieved.

Service provider records that have gone stale

Assessors look for: a provider list with service descriptions (12.8.1), written acknowledgments (12.8.2), monitoring of compliance status at least once every 12 months (12.8.4), and a record of who manages which requirement (12.8.5).

A gap would look like: a contract with no security acknowledgment, or no record of which party handles a shared control.

Using these patterns

Try testing your own evidence against the procedures before an assessment. Ask whether someone unfamiliar with your environment could confirm each element from the records alone.

Frequently asked questions

Can a partly implemented control be reported as In Place?
No. The ROC Template uses Not in Place when some or all elements of a requirement have not been met or are still being implemented. The assessor reassesses after remediation.
Does a first PCI DSS assessment need four passing ASV scans?
Not necessarily. Requirement 11.3.2 allows fewer if the assessor verifies that the most recent scan passed, policies require scanning at least once every three months, and rescans show that noted vulnerabilities were corrected. Later years need passing scans at least every three months.
Can a targeted risk analysis justify running a control less often than PCI DSS states?
No. PCI SSC’s TRA guidance says that a stated frequency is the minimum. Performing the activity less often means the requirement as stated is not met. The alternative the guidance gives is a customized control under the customized approach.
What does an assessor review for payment page scripts under Requirement 6.4.3?
The testing procedures call for policies and procedures, interviews with responsible personnel, inventory records, and system configurations. Together they show how each script is authorized, how its integrity is assured, and why it is necessary.

Work with RSI Security

RSI Security is a PCI Qualified Security Assessor (QSA) company and an Approved Scanning Vendor (ASV). It performs PCI DSS assessments and quarterly ASV scans. Organizations that need help with scoping or readiness can work with RSI Security through a separate advisory engagement. RSI Security provides either advisory or assessment to a given client, never both.

Schedule a PCI DSS assessment · Talk to an advisor about readiness

Sources

Request a consultation

Exit mobile version