Help CenterContact support
All Custos: Store Security Scan articles

PCI script report

Updated

On this page
  1. What the requirements ask
  2. What the report covers
  3. Authorize a script
  4. When a script changes
  5. Change log and alerts
  6. Export
  7. Your data
  8. Sources

With Pro, Custos keeps the evidence that PCI DSS v4.0.1 requirements 6.4.3 and 11.6.1 ask for on your payment-related pages: a list of every script those pages load, your written reason for each one, a check that each script is still what you authorized, and a log of every change Custos detected. You can export it as evidence for your QSA (Qualified Security Assessor), your acquirer or your own self-assessment. It does not make your store compliant: whether 6.4.3 and 11.6.1 apply to a store on Shopify’s checkout, and which evidence is enough, is for your QSA or acquirer to decide.

Open it from Activity > PCI script report, or with Open report on Home.

Evidence for your QSA or your own PCI DSS self-assessment. Not a compliance certification.

What the requirements ask

  • 6.4.3: all payment page scripts loaded and executed in the shopper’s browser are managed: a method to confirm each script is authorized, a method to assure the integrity of each script, and an inventory of all scripts with a written business or technical justification of why each is necessary.
  • 11.6.1: a change- and tamper-detection mechanism alerts your staff to unauthorized changes (including new, changed and removed items) to the security-impacting HTTP headers and the script contents of payment pages as the shopper’s browser receives them. It runs at least weekly, or as often as your targeted risk analysis (12.3.1) says.

Both became mandatory on 31 March 2025.

Most Shopify stores fill in SAQ A. Since its January 2025 revision, SAQ A no longer lists 6.4.3 and 11.6.1. Instead it asks you to confirm that your site isn’t susceptible to attacks from scripts that could affect your e-commerce system. The PCI Security Standards Council’s FAQ 1588 says you can confirm this either with techniques such as those in 6.4.3 and 11.6.1, or with confirmation from your PCI DSS compliant payment provider. This report supports the first route. Ask your acquirer or assessor which one they expect.

What the report covers

Custos’s daily shopper walk opens your cart, your checkout up to the payment step, and your customer account pages (when a test account or login is saved). For each scan it records every script those pages load and the security headers they send (Content-Security-Policy, Strict-Transport-Security, X-Frame-Options and similar).

What it does not cover:

  • The card fields of Shopify’s checkout. They are frames hosted by Shopify, not part of your pages, and aren’t in this inventory. Shopify is responsible for them as your PCI DSS compliant payment provider.
  • Pages the walk didn’t reach. The report says which pages the latest scan reached and when each was last checked. A page that wasn’t reached has no new evidence for that scan.
  • Anything between scans. Scans run once a day on Pro. The report shows how many scans ran in the period, how many reached the checkout, and the longest gap between two checkout checks.

Custos only opens these pages as a shopper would. It never places an order and never types into the checkout.

Authorize a script

Each script shows its address (or a code excerpt for inline code), where it comes from, the pages it was on, when it was first and last seen, and the SHA-256 of its content.

  1. Select Authorize on the script.
  2. Write why your store needs it, for example “Payment provider’s fraud check, required by our contract”. Use 5 to 1000 characters.
  3. Select Authorize.

Custos records the exact content you authorized, your reason, your name and email (as Shopify gives them; otherwise “Store staff”) and the time. Authorizing also marks the script as trusted in your findings.

Scripts marked Shopify’s own code come from Shopify’s platform. They are listed for completeness; you can authorize them too.

If a script’s content couldn’t be read, its integrity can’t be checked and it can’t be authorized until a scan reads it.

When a script changes

If an authorized script’s content changes, its status becomes Changed since authorized and the change log records it. Review the new content and select Authorize again. Until you do, the report shows that the script runs content you haven’t authorized.

Revoke removes an authorization. The script stays in the list as not authorized and the change log records who revoked it.

Change log and alerts

The change log lists, newest first: new, changed and removed scripts, added, changed and removed security headers, and every authorization and revocation, each with the time it was detected or made. A page’s first scan is its baseline and adds no change lines.

When a scan detects a change, it goes into that scan’s one alert, by email to your alert recipients (Settings > Alerts) and to your team chat, while Email me about new findings is on. The Alert column shows whether the email went out.

Export

  • Open printable report: a page with your store, the period, when it was generated, the scan cadence, the pages covered, the script inventory, the headers and the change log. Use your browser’s Print and choose Save as PDF to keep a PDF. If your browser blocks the new tab, the page downloads as an HTML file instead.
  • Export scripts CSV and Export change log CSV: the same data for a spreadsheet.

Choose the period (last 30, 90, 180 or 365 days) at the top of the report. Days and times in the exports are in UTC.

Your data

Custos stores hashes of script contents, never the scripts themselves. Authorizations keep the staff member’s name and email. Uninstalling stops the scans; all report data is deleted when Shopify asks the app to delete your shop’s data after you uninstall.

Sources

Built and supported by StoreFleet, Shopify app developers since 2021.