Use the defined approach when you can meet a PCI DSS requirement as written. Use a compensating control when a legitimate, documented constraint prevents that. Use the customized approach when a risk-mature organization wants to meet a requirement’s stated objective with a control of its own design.
Defined approach, compensating controls, and customized approach
PCI DSS v4.0.1 offers two ways to implement and validate a requirement: the defined approach and the customized approach. Compensating controls sit inside the defined approach, so they are a third option only in a practical sense.
| Question | Defined approach | Compensating control | Customized approach |
|---|---|---|---|
| Starting point | Implement the requirement as stated | A legitimate, documented technical or business constraint blocks the requirement as stated | Meet the Customized Approach Objective in a way that does not strictly follow the requirement |
| Typical fit | Controls already match the requirement, or the entity wants more direction or is new to PCI DSS | The entity can sufficiently mitigate the risk through other controls | Risk-mature entities with a robust risk-management approach |
| Security bar | The requirement itself | Meet the intent and rigor of the original, and go above and beyond other PCI DSS requirements | Meet or exceed the security the defined requirement provides |
| How it is tested | The assessor follows the defined testing procedures | The assessor reviews and validates sufficiency at each annual assessment | The assessor derives testing procedures for the specific implementation |
| Added documentation | Evidence for the defined testing procedures | Compensating Controls Worksheet (Appendix C) | Controls matrix and a targeted risk analysis for each control (Requirement 12.3.2) |
| Available on an SAQ | Yes | Yes, reported as In Place with CCW | No |
Which one is better?
None of the three ranks above the others, because each fits a different situation. Most requirements can be met with either the defined or the customized approach. A single assessment can include both, even for the same requirement on different system components.
Limits on compensating controls
A compensating control needs more than a preference for doing things differently. Appendix B sets these limits:
- PCI DSS requirements that already apply to the item under review cannot count as the compensating control.
- The control must address the additional risk created by not meeting the requirement.
- The control cannot make up for a requirement missed in the past, such as a task due two quarters ago.
- The assessor evaluates each compensating control at every annual assessment, and it must stay effective between assessments.
Limits on the customized approach
The customized approach adds flexibility and also adds work. PCI DSS says the documentation and effort are greater than for the defined approach.
- Several requirements have no Customized Approach Objective, so the option does not exist for them.
- The entity documents each control, performs a targeted risk analysis, tests the control, and monitors its effectiveness.
- A QSA who helps design or implement a customized control cannot derive tests for it or assess it.
- Payment brands and acquirers may regulate its use, so take questions to them first.
A practical order for deciding
- Check the requirement as written. If your controls meet it, use the defined approach and the listed testing procedures.
- Look for a real constraint. If a legitimate technical or business constraint blocks the requirement, test a possible compensating control against the Appendix B criteria.
- Consider the customized approach. Confirm that the requirement has a Customized Approach Objective and that your organization has the risk maturity to support it.
- Confirm your reporting path. The customized approach requires a ROC Template, so ask your acquirer or payment brand before you commit.
SAQ vs ROC
A Self-Assessment Questionnaire (SAQ) and a Report on Compliance (ROC) are both reporting tools for a PCI DSS assessment. Each one is submitted with an Attestation of Compliance.
| Question | SAQ | ROC |
|---|---|---|
| What it records | Self-assessment results | Detailed results of the assessment |
| Who may use it | Entities that meet the eligibility criteria for that SAQ | Entities whose compliance program requires or accepts a ROC |
| Format | A questionnaire with the requirements for the environment it describes | The required PCI DSS ROC Template |
| Who usually completes it | The entity, sometimes with help from an assessor | A QSA, or an ISA where the compliance program allows it |
| Customized approach | Not available | Available, subject to the compliance program |
The organizations that manage compliance programs, such as acquirers and payment brands, decide which report applies. Service providers have one SAQ option, SAQ D for Service Providers, and only when a payment brand defines them as eligible. For help with the forms themselves, see how to prepare for an assessment.
QSA vs ISA
A Qualified Security Assessor (QSA) works for an outside company. An Internal Security Assessor (ISA) works for the organization being assessed.
| Question | QSA | ISA |
|---|---|---|
| Employer | A QSA company qualified and listed by PCI SSC | A company approved as a Sponsor Company under the ISA Program |
| Independence | Must meet PCI SSC independence requirements for each assessment | Internal to the organization |
| Attestation of Compliance for a ROC | Part 3c records the QSA’s role, with lead QSA and company officer signatures | Part 3d records the ISA’s role |
| Customized approach | May document it in a ROC Template | May document it in a ROC Template |
Your acquirer or payment brand decides whether you must use a QSA or may use an ISA, including for the customized approach. If you need an outside assessor, our guide to choosing a provider covers the selection criteria.
Where an ASV fits
An Approved Scanning Vendor (ASV) has a narrower role than either assessor. PCI SSC approves ASVs to run external vulnerability scans, which Requirement 11.3.2 calls for at least once every three months. A scan supports one requirement and does not replace an assessment.
PCI DSS and other frameworks
PCI DSS has its own requirements, reporting templates, and assessor programs. A report under another framework does not stand in for a PCI DSS report. Requirement A3.1.2 names ISO 27001 as one example of a methodology that can support a compliance program. That mention does not make the two equivalent.
Frequently asked questions
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
- PCI DSS v4.0.1 (Section 8, Approaches for Implementing and Validating PCI DSS)
- PCI DSS v4.0.1 (Appendix B, Compensating Controls, and Appendix C, Compensating Controls Worksheet)
- PCI DSS v4.0.1 (Appendix D, Customized Approach, and Requirement 12.3.2)
- PCI DSS v4.0.1 (Requirement 11.3.2, Requirement A3.1.2, and Appendix G glossary entries for ASV, QSA, ROC, and SAQ)
- PCI DSS v4.0.1 SAQ A, Revision 1 (Completing the Self-Assessment Questionnaire, requirement responses)
- PCI DSS v4.0.1 SAQ D for Service Providers (Service Provider Eligibility Criteria)
- PCI DSS v4.0.1 ROC Attestation of Compliance for Merchants (Part 3c and Part 3d)
- QSA Program Guide v4.1 (Section 2.3, Qualified Security Assessor Companies, and Section 6.4, ISA and PCIP Programs)
