01
What it looks at
What each part of the answer means, and what to do when one is not right.
Card skimmers hide in the scripts a checkout loads. See every one on your payment page, where it comes from and what has changed.
What this checks
Every script on the page – in the page itself and added by other scripts while it runs – with the company it comes from, whether an integrity hash pins its content, and whether it is new or changed since your last check from this browser.
What a new or changed script means
A script nobody on your team added, or one that changed without a release of yours, is how card-skimming attacks reach a checkout. Find out who added it before your next customer pays.
What to do
Keep a list of every script your payment page needs and why, pin other companies’ scripts with an integrity hash where they allow it, and remove what is not needed. PCI DSS 4.0.1 asks shops that take cards for exactly this list (requirement 6.4.3) and for a way to spot changes (requirement 11.6.1).
02
What people ask about it
Straight answers, from what the check itself does.
- Does my page or its list leave my computer?
- No. The bookmark runs on your page in your own browser and opens this page with the list in the part of the address after the #, which browsers never send anywhere. The last list for each page stays in this browser, so the next check can show what changed.
- Is this a PCI DSS assessment?
- No. It gives you the script list and the changes – the evidence those two requirements ask a shop to keep. Only a qualified assessor can say whether your payment page meets PCI DSS.
Add your site to Xovris on the Free plan and this check runs every 3 minutes, with an alert by email or Slack when it fails. On Personal, Xovris investigates the cause, makes the change its finding names and proves the fix.
Watch my site free