We have observed the following behavior in Client-Side Defense monitoring:
Each online transaction page is generated with a unique identifier in the URL, for example:
https://www.example-company.com/online-process/unique-session-id.html
Although the URL changes for every individual transaction, the page body contains the same set of inline scripts. These inline scripts are assigned unique hashes and appear consistently across all generated pages.
As a result, for every new transaction page, three additional entries are created in the Script List. Since a large number of such pages are generated, the Script List becomes populated with multiple entries that effectively represent the same inline scripts, reducing overall visibility and making analysis and reporting more complicated.
hash-based grouping of identical inline scripts, URL and fragment normalization, consolidated reporting, and approval at the grouped-script level.
Cluster or group identical inline scripts based on their hash values.
Display inline scripts separately from URL-specific script entries in the Script List.
Provide a reporting view that consolidates identical inline scripts across multiple dynamically generated pages.
Such functionality would significantly reduce operational effort, improve visibility within the Script List, and make reporting and approval processes much more manageable.