See how Nextiva closed its eSkimming risk gap and automated PCI DSS 4.0.1 compliance.

Nextiva needed to comply with new PCI DSS 4.0.1 requirements for payment page scripts while managing a complex web environment with many third and fourth party integrations. Like most teams, they had limited visibility into JavaScript running in the browser and no easy way to prove control for 6.4.3 and 11.6.1.
In this case study, you will see how Nextiva used Source Defense to reach full compliance in about a week, automate ongoing monitoring, and reduce eSkimming risk without a large internal project.

What you will learn

After reading the case study, you will learn how Nextiva:

• Built a complete inventory of third and fourth party scripts on its payment pages
• Confirmed which scripts were authorized and ensured script integrity for PCI DSS 4.0.1
• Implemented real time monitoring to detect and block suspicious script behavior
• Simplified evidence gathering for assessors with a dedicated PCI dashboard
• Deployed Source Defense with minimal engineering effort and low ongoing maintenance

Use Nextiva’s experience as a practical blueprint to de-risk your own payment pages and take pressure off your PCI DSS 4.0.1 program.