Compare Aleran Merchant Services vs. c/side

The detection system operates on a publicly available large language model (LLM) that is fully contained within a privately managed infrastructure.

The c/side AI system identified that the altered script demonstrated characteristics of a keylogger, categorizing it as harmful. Users are then able to examine the script and, if needed, prevent access by blocking the associated hash values.

Achieving complete session coverage, our solution employs DOM-level comparisons and conditional threat identification based on geographic location, time, and user demographics. The client-side component intercepts all third-party requests, retrieves the relevant JavaScript, and analyzes it instantaneously. This proactive approach ensures that any harmful code is prevented from being executed by the browser before it runs even a single line.

An independent evaluation by VikingCloud verifies that when set up correctly, both the hybrid proxy and crawler modes meet these standards by persistently hashing, analyzing, and blocking scripts in real-time when needed. The c/side platform features a specialized PCI DSS dashboard that specifically addresses the insights related to requirements 6.4.3 and 11.6.1.

The proxy and crawler systems solely retain the requester’s IP address for the purpose of incident analysis; this information is not sold or utilized for marketing purposes. All data from the proxy and crawler is securely maintained within c/side-managed clusters located in AWS.

Combat threats like Magecart, formjacking, token hijacking, and cryptojacking effectively! By implementing a proxy-based framework, a proxy operates between the user’s browser and third-party scripts, enabling it to monitor the code retrieved by the browser. This client-side proxy ensures constant, comprehensive visibility and oversight of every third-party script running in the user's browser at all times, without relying on sampling techniques.

With the capability of real-time payload examination, automated prevention measures, comprehensive storage of historical payloads, and reports that are prepared for auditing, which align precisely with the testing protocols outlined in PCI DSS 4.0.1.

VikingCloud reported that their c/side platform successfully detected and halted a third-party script to safeguard against data breaches.