Hi, I'm Matt Crane. I'm a leader in the payment security practice here at Schellman.
We're often asked if we're able to do both PCI assessments and penetration testing for the same client. In this video, we'll explain how we're able to provide both and why it's not an independence issue.
First and foremost, I want to cover what the PCI Council says about this. While they don't specifically state that it is or is not an independence issue, if you look at Requirement 11.4 of PCI DSS v4.0, it talks about penetration testing services methodologies. The two main criteria that you have to have as a penetration tester to meet that requirement are:
At Schellman, we go a little bit further to make sure we don't have independence issues. Our payment security team—which is ultimately comprised of PCI QSAs—and penetration test teams are separate, and they each have different management structures.
We do that really for a couple of different reasons—primarily because a QSA and a penetration tester have very different skill sets, but also so there's no perceived bias for a QSA who's also doing penetration testing services for the same client.