Nexudus script integrity checks for PCI DSS 4.0 compliance.
Nexudus checks the integrity of the following scripts to be compliant with the PCI DSS 4.0.
Nexudus script checks
We check the following scripts provided by Nexudus.
app.js
Allows clients to customize the functionality of their Member Portal. SRI is not possible on this inline script that location administrators can edit.
Portal scripts
Covers all scripts that have a source starting with “/v4_portal”. These are in- built scripts for the Member Portal which provide functionality to the app. SRI isnot required as they are all in-built within the app.
NextJS scripts
Covers all scripts that have a source starting with ”/_next/static”. These are in-built scripts for NextJS which provide functionality to the app. SRI is not required as they are all in-built within the app.
Third-party scripts
We also check the following third-party scripts as part of the PCI DSS compliance.
Google Maps scripts
Covers all scripts that have a source starting with “https://maps.googleapis.com”. These are provided by Google and each import a Google Maps related module which provides some map related functionality. SRI is not possible on these scripts, as Google does not currently provide static versions of the scripts.
https://core.spreedly.com/iframe/iframe-v1.min.jsProvides Spreedly iframe and payment functionality. Required for secure tokenization of cardholder data, including PAN and CVV, as part of the overall payment flow.
https://checkout.razorpay.com/v1/checkout.jsProvides RazorPay payment method functionality. Only added if RazorPay is enabled. Script source is not versioned which means no SRI.
Forte script
https://checkout.forte.net/v1/jsProvides Forte payment method functionality. Only added if Forte is enabled. Script source is not versioned which means no SRI.