Add Script Inventory Collection for PCI DSS v4.0 Compliance #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for script inventory collection in the client-side SDK to align with PCI DSS v4.0 compliance. The feature captures metadata from all script elements present on the payment page and prepares it for secure transmission to the backend.
🔧 Key Features:
Scans the DOM for all <script> tags.
Extracts metadata:
src, type, integrity, async, defer, crossorigin
Identifies third-party scripts by detecting external domains.
Hashes inline scripts using SHA-256 for integrity analysis.
Sends script data via SecuritySDK.sendEvent() to the backend telemetry endpoint.
Modular and extensible design for future additions like:
Justification tagging
Tamper detection
Bulk approvals
🔒 Security & Compliance Notes:
TLS 1.2+ used for data transmission.
No sensitive data or PII is collected.
Compatible with Subresource Integrity (SRI) and strict CSPs.