4 ms·
> Fourth, PciDSS, where are you when we need you? Weren't it already against the rules to allow third party code on payment pages??? No. You're required to ge
by Someone1234 8y ago
> Fourth, PciDSS, where are you when we need you? Weren't it already against the rules to allow third party code on payment pages???
No.
You're required to get audited, document certain decisions, and follow some pretty high label 101 level security requirements. You can absolutely use third party libraries on payment pages (source: we do and are PCI certified).
- baybal2 8y agoReally, so, you are truly allowed to serve code from random CDNs??? That's really something. I never could've imagined that.
- Someone1234 8y agoPCI is a specific set of requirements. We've met those requirements and our certified auditor agrees. Which specific part of PCI do you feel third party libraries violates?
- baybal2 8y agoI don't know, but I always had that feeling. Given that they are so paranoid with payment terminals, I thought that online payment pages will be no different.
- Someone1234 8y agoThe requirements for payment terminals are extremely lapse. That's why there's the meme about Windows XP restart screens. Several recent breakins at major retailers have been directly against payment terminals.
- numbsafari 8y agoLooking at PCI-DSS v3.2.1, Requirement 11.5: "Deploy a change-detection mechanism (for example, file-integrity monitoring tools) to alert personnel to unauthorized modification (including changes, additions, and deletions) of critical system files, configuration files, or content files; and configure the software to perform critical file comparisons at least weekly." ... "Examples of files that should be monitored: • System executables • Application executables • Configuration and parameter files • Centrally stored, historical or archived, log and audit files • Additional critical files determined by entity (for example, through risk assessment or other means)." ... "Note: For change-detection purposes, critical files are usually those that do not regularly change, but the modification of which could indicate a system compromise or risk of compromise. Change-detection mechanisms such as file-integrity monitoring products usually come preconfigured with critical files for the related operating system. Other critical files, such as those for custom applications, must be evaluated and defined by the entity (that is, the merchant or service provider)."