Proteside Docs

Events and detections

The event types the SDK sends, what each one detects, its severity and when it becomes an alert in the dashboard.

The SDK sends the dashboard two kinds of events: detections (something suspicious happened on the page) and telemetry (pageviews, inventory, payment validations). Detections become alerts; telemetry feeds the Scripts inventory, SDK Health and Payment Integrity.

How an event becomes an alert

  • The dashboard sets the severity, not the SDK. The severity reported by the SDK is recorded on the alert as "Severity reported by the SDK". The tables below show the base severity in the dashboard.
  • Repeated events don't create new alerts. While there's an open alert for the same problem (for example, the same script or the same exfiltration destination), new occurrences are added to the existing alert. If the alert was already resolved, a new occurrence opens a new alert.
  • The notification goes out only when the alert is created. Repeated occurrences don't notify again.
  • Scripts written in the page's HTML show up in Scripts with a note that they keep loading from the HTML. To stop them, remove the tag at the source (HTML or theme).

See how to handle alerts in Alerts.

Page baseline

Right after the page loads, the SDK establishes the page baseline. Scripts present at that moment go into the inventory and need your review in Scripts.

Scripts

EventWhat it detectsSeverityAlert
SCRIPT_INJECTIONA new executable script appears outside what the page already had.high, adjustedyes
SCRIPT_MODIFIEDA known script reappears with different content.high, adjustedyes
SCRIPT_BLOCKEDA script matched a blocking rule and was stopped.highyes
GTM_CONTAINER_BLOCKEDA Google Tag Manager container or a gtag.js tag outside the Allowed GTM containers list.highyes

Adjusted severity: for SCRIPT_INJECTION and SCRIPT_MODIFIED, the dashboard raises it to critical when the vendor is flagged as a threat in the catalog, lowers it to low when it's a cataloged vendor, and uses medium for first-party scripts and inline scripts. In all other cases, it stays high.

Customer data

EventWhat it detectsSeverityAlert
KEYLOGGER_DETECTEDA script starts capturing what is typed into a sensitive field.criticalyes
EXFILTRATION_ATTEMPTSensitive customer data is sent to an untrusted destination.adjustedyes
WEBSOCKET_EXFILTRATIONA WebSocket connection is opened to an untrusted destination.criticalyes
FIELD_ACCESSA script registered a listener on a sensitive field.infono

The SDK sends only the names of the patterns it found, never the content sent.

Adjusted severity: exfiltration is critical when the destination is a vendor flagged as a threat or when it involves card or ID document data; it's low when the destination is a payment processor or a cataloged vendor; in all other cases, it's high.

Forms, iframes and overlays

EventWhat it detectsSeverityAlert
FORM_ACTION_HIJACKA form's action attribute changed, including on forms created later.criticalyes
OVERLAY_DETECTEDAn element is positioned over a sensitive field or the payment area.highyes
IFRAME_REPLACEDThe address of a known payment provider's iframe changed.highyes
IFRAME_UNEXPECTEDA payment iframe outside the Expected iframe origins, or an iframe overlaid on an expected iframe. With the list filled in, iframes outside it raise an alert.highyes
CARD_FIELD_OUTSIDE_VAULTA card field you can type into on the main page, outside the provider's iframe. Fill in Expected iframe origins to turn it on.highyes

Payment

EventWhat it detectsSeverityAlert
PIX_TAMPEREDThe displayed Pix code changed to one that doesn't match the reference, or the recipient isn't among the trusted ones.criticalyes
BOLETO_TAMPEREDThe digit line changed, or the bank isn't among the trusted ones.criticalyes
CRYPTO_ADDRESS_SWAPThe crypto address changed, or isn't among the trusted ones.criticalyes
UPI_TAMPEREDThe UPI code changed, or the VPA isn't among the trusted ones.criticalyes
QR_TAMPEREDThe code for another QR-based method (PayNow, PromptPay, DuitNow, QR Ph, HK FPS, Transferencias 3.0, CoDi or QR wallet) changed, or a QR code image started coming from a different domain.criticalyes
AMOUNT_TAMPEREDThe code's amount differs from the one passed to expectPayment(), or the same recipient appeared with a different amount.criticalyes
CLIPBOARD_HIJACKThe content copied to the clipboard looks like a payment code and doesn't match the reference.highyes
PAYMENT_VALIDATEDA payment code was read and validated. Feeds Payment Integrity.infono

Details in Payment integrity and Pix.

Environment and installation

EventWhat it detectsSeverityAlert
SERVICE_WORKER_BLOCKEDA registered service worker outside the Allowed service workers. With the list filled in, service workers outside it raise an alert.highyes
SERVICE_WORKER_REGISTEREDAn allowed service worker was registered.infono
INSTALLATION_ORDER_WARNINGThere are scripts before the snippet in the <head>. The alert itself offers Stop warning for this store. See Troubleshooting.mediumyes

Telemetry

These events never become alerts:

EventWhen it's sent
PAGEVIEWOn every page load and every Proteside.pageChanged().
BASELINE_CALIBRATINGWhen the SDK starts establishing the page baseline.
BASELINE_CLASSIFIEDWith the page's script inventory (address, content hash, size and classification).
BASELINE_ESTABLISHEDWhen the page baseline is established.

Generated by the dashboard

Some alerts don't come from an SDK event, but from server-side checks:

AlertSourceSeverity
SCRIPT_INTEGRITY_MISMATCHAn authorized script's content changed compared to the approved hash.high
HEADER_CHANGEDA security header on the payment page changed value.medium
CSP_VIOLATIONA CSP report sent to Proteside points to a host outside the inventory. See CSP and headers.low
SDK_SILENTA domain with history stopped receiving real sessions. The alert shows up within a day and resolves itself when traffic comes back.medium

Next steps

On this page