Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PCI DSS 4.0 Compliance? #960

Open
CtrlAltJohnDough opened this issue Feb 26, 2025 · 0 comments
Open

PCI DSS 4.0 Compliance? #960

CtrlAltJohnDough opened this issue Feb 26, 2025 · 0 comments

Comments

@CtrlAltJohnDough
Copy link

CtrlAltJohnDough commented Feb 26, 2025

Hi, I am not an expert in PCI DSS 4.0 by any means but am understanding from some of our partners that one of its requirements will be to have a content security policy and also discusses monitoring remote scripts.

I assume the language in 6.4.3 of the spec means that how the CSP rules for the drop in form (without Paypal) will be workable.

But opting for the paypal option I see the following script src directives:
www.paypalobjects.com
*.paypal.com
'unsafe-inline'

Please correct me if I'm wrong, but my understanding of CSP is such that this is not one entry, but 3 distinct script-src entries. If that is true, adding unsafe-inline seems to render the script segment of this tool as a security mechanism useless for the other protections we're supposed to be implementing on this page. I understand the reasons they have to list it here to make Paypal's implementation work as it stands, but are there any plans to update that implementation so that the unsafe-inline block isn't needd.

Thanks

@CtrlAltJohnDough CtrlAltJohnDough changed the title PCI 4.0 Compliance? PCI 4.0 DSS Compliance? Feb 26, 2025
@CtrlAltJohnDough CtrlAltJohnDough changed the title PCI 4.0 DSS Compliance? PCI DSS 4.0 Compliance? Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant