Technical buyer resources
Evaluate PCI DSS script monitoring, payment-page change detection, Magecart risk signals and Subresource Integrity with factual guidance tied to DygDog's passive scanner.
PCI DSS payment-page security
DygDog passively fetches page HTML, inventories up to 500 script tags, fingerprints the sanitised inventory and compares it with the previous successful baseline. It does not execute JavaScript or certify compliance.
Read the guideCheckout change detection
The Pro check records a sanitised script snapshot for the exact scanned page, then compares subsequent successful scans of that page. It surfaces added or removed script URLs, changed inline code, and changed external-script metadata alongside the current CSP and SRI posture; it does not hash remote script bodies.
Read the guideE-skimming risk signals
DygDog combines script inventory, source ownership, SRI/CSP observations, payment-page classification, suspicious-pattern checks and historical drift. That makes it useful for prioritising investigation without overstating certainty.
Read the guidePCI DSS 4.0.1 control guide
DygDog automates technical inventory and integrity observations. Owners still need to approve scripts, record why they are necessary, define scope and validate their compliance approach with an assessor.
Read the guidePCI DSS 4.0.1 control guide
DygDog establishes a per-tenant script baseline, compares later scans and records changes alongside CSP and SRI observations. Teams must schedule the required cadence and investigate alerts through their own response process.
Read the guideThird-party JavaScript integrity
SRI is valuable for static third-party resources whose content is expected to remain stable. It is not a universal answer for vendor scripts that change without a versioned URL, so findings must account for technical suitability.
Read the guide