All Vendors
sales_engagement

Salesforce

Salesforce exhibits consent bypass in platform deployment. While CRM functionality appears consent-neutral, runtime tracking components activate before consent framework initialization, creating liability gap in customer data collection.

5 IOCs8 detections100% pre-consent8 sites
70
Vendor Risk Score

How This Briefing Works

This report opens with key findings, then maps the gaps between what Salesforce discloses and what BLACKOUT observed at runtime. From there: what it means for your organization, what to do about it, and the detection data and evidence underneath.

Key Findings

Key Findings

8 detections across 8 sites100% pre-consent activity
CRITICAL

Pre-Consent Activity

Salesforce was observed loading and executing before user consent was obtained on 100% of sites where it was detected.

GDPRePrivacy
Disclosure Gaps

Claims vs. Observed Behavior

1 gaps
Customer Impact

What This Means For You

Sales and marketing teams gain CRM platform but inherit consent timing liability from platform-level tracking. Legal teams face exposure from pre-consent data collection across integrated ecosystem. IT teams must audit Salesforce component activation against consent framework timing.
Recommended Actions

What To Do About It

Role-specific actions based on observed behavior

If You Use Salesforce

  • →Audit Salesforce component load timing against consent framework
  • →Map all integrated tracking (Analytics, Marketing Cloud, Pardot)
  • →Verify DPA covers platform-level data collection and consent requirements

If You're Evaluating Salesforce

  • →Require technical documentation of consent-aware component initialization
  • →Demand demonstration of consent-first platform activation
  • →Negotiate liability provisions covering integrated ecosystem consent violations

Negotiation Leverage

  • →C09 platform risk: Demand DPA amendment requiring consent verification before ANY platform component activation
  • →Request written confirmation of consent integration methodology
  • →Require audit rights covering platform tracking and integrated vendor activation
  • →Negotiate liability caps for consent violations across integrated ecosystem
Runtime Detections

Runtime Detections

1 BTI-C CODES

BLACKOUT observed this vendor's JavaScript executing in a live browser and classified each hostile behavior using our BTI-C (Behavioral Threat Intelligence — Capability) taxonomy. These are not theoretical risks — each code below was triggered by something we watched this vendor's code actually do.

BTI-C09Consent Bypass

Ignoring CMP signals

IOC Manifest

IOC Manifest

4 INDICATORS

Indicators of compromise across 3 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.

No indicators in this category

Ecosystem

Ecosystem & Supply Chain

Salesforce operates as platform layer, integrating with marketing automation, analytics, and advertising vendors. Platform deployment creates infrastructure dependency where consent bypass affects entire integrated ecosystem. Often co-deployed with Salesforce Marketing Cloud, Pardot, creating amplified pre-consent data collection.
Evidence

Evidence Artifacts

Artifacts collected during analysis, available with evidence-tier access.

HAR Capture

Complete network capture with all requests and responses

IOC Manifest

5 detection signatures across scripts, domains, cookies, and network endpoints

Vendor Details